Solved: 860 EVO 250GB causing freezes on AMD system

masterIdori · ‎26-06-2018

Hello,

I bought 860 EVO 250GB 2.5" SATA few days ago (it came with the latest firmware) but there seems to be some sort of incompatibility with AMD 9xx chipsets. I have ASRock 970 Pro3 which has 970 NB + 950 SB, no additional storage controllers. I installed Windows 10 64 bit on it, then Magician, ran the "Performance Optimization" option there and left RAPID off since it says it may cause conflicts with AMD/AsMedia controllers. The problem is that Windows hangs at random times (it's not that often but it's annoying). For example, if it happens while there is a YouTube video running in the background, the sound continues and I can open a new tab in the web browser but the website won't load, I can't minimize the browser, if I click on the start menu button with the mouse, the menu won't come up, the task manager won't load when I press Ctrl + Shift + Esc and if I click on too many things everything freezes for 1-2 minutes, then goes back to normal. Also, everytime this happens, there are some CRC communication errors appearing in the SMART status. At first I thought it's a bad SATA cable, although I used the same cable with and HDD for 2 years and no such things occured, so I tried with another SATA cable and the result was the same. I upgraded the BIOS of the motherboard to the latest version, reset the CMOS, turned off any IDE legacy and power saving options for the storage, there is an option "AMD AHCI BIOS ROM" in the BIOS of the MB which also did not resolve the issue whether it's turned on or off.

What I found as an easy way to reproduce the issue is to run CrystalDiskMark, it hangs everytime at the 4KiB Q8T8 write test. Another scenario is to run virutalbox with ubuntu VM, for example - the PC hanged on both installation and update of ubuntu 16.04. Basically, you can reproduce the issue by putting the SSD on 9xx chipset AM3+ motherboard with FX CPU and then run CrystalDiskMark (I tested with version 6).

I also tested it on 2 Intel systems - one HP desktop PC with i3-3220 and one old HP laptop (with Intel T6570 CPU) and I didn't observe this issue on them.

My specifications are:

ASRock 970 Pro3 (the first version not the R2.0 one)

AMD FX-6300 3.5GHz

11GB RAM DDR3 1333MHz

Samsung 860 EVO 250 GB SATA

Hitachi Ultrastar 2TB (HUA723020ALA640)

If you can come up with a fix, either new firmware or software workaround in Windows, it will be appreciated.

Regards,

Martin

masterIdori · ‎24-10-2018

To put an end of the thread - I returned the SSD to the reseller. Just don't buy Samsung SSD if you will use the AMD SATA controller in the chipset

Thank you all for sharing opinions and test results, I hope this thread will serve well to someone looking for an SSD.

View solution in context

afri83 · ‎24-07-2018

Hello same problem with my evo 860 and gigabyte 970a-ud3 rev. 1.0

Amd phenom 1055t.

I have now more than 200 crc errors. And cant complete as ssd benchmark.

Freezes at 4k-64Thrd test.

Any solution please?

Kris8 · ‎26-07-2018

I have similar issue. Logs are form brand new SATA evo 860 on AMD SATA controller

00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
	Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
	Kernel driver in use: ahci
	Kernel modules: ahci

Noticed ATA errors

[  383.327718] ata4.00: exception Emask 0x0 SAct 0x1ff00 SErr 0x0 action 0x6
[  383.327727] ata4.00: irq_stat 0x40000008
[  383.327734] ata4.00: failed command: READ FPDMA QUEUED
[  383.327746] ata4.00: cmd 60/00:40:90:3c:b7/01:00:0f:00:00/40 tag 8 ncq dma 131072 in
                        res 41/84:00:90:3c:b7/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[  383.327753] ata4.00: status: { DRDY ERR }
[  383.327757] ata4.00: error: { ICRC ABRT }
[  383.327765] ata4: hard resetting link
[  383.802893] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  383.803217] ata4.00: supports DRM functions and may not be fully accessible
[  383.806666] ata4.00: supports DRM functions and may not be fully accessible
[  383.809702] ata4.00: configured for UDMA/133
[  383.809738] ata4: EH complete
[  383.809889] ata4.00: Enabling discard_zeroes_data
[  624.191556] ata4: log page 10h reported inactive tag 6
[  624.191567] ata4.00: exception Emask 0x1 SAct 0x7ff80 SErr 0x0 action 0x0
[  624.191570] ata4.00: irq_stat 0x40000008
[  624.191574] ata4.00: failed command: READ FPDMA QUEUED
[  624.191583] ata4.00: cmd 60/80:38:c0:2d:ce/00:00:07:00:00/40 tag 7 ncq dma 65536 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191587] ata4.00: status: { DRDY }
[  624.191591] ata4.00: failed command: READ FPDMA QUEUED
[  624.191598] ata4.00: cmd 60/60:40:00:b3:ce/00:00:07:00:00/40 tag 8 ncq dma 49152 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191602] ata4.00: status: { DRDY }
[  624.191605] ata4.00: failed command: READ FPDMA QUEUED
[  624.191613] ata4.00: cmd 60/18:48:70:b3:ce/00:00:07:00:00/40 tag 9 ncq dma 12288 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191617] ata4.00: status: { DRDY }
[  624.191620] ata4.00: failed command: READ FPDMA QUEUED
[  624.191627] ata4.00: cmd 60/18:50:b0:b3:ce/00:00:07:00:00/40 tag 10 ncq dma 12288 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191631] ata4.00: status: { DRDY }
[  624.191634] ata4.00: failed command: READ FPDMA QUEUED
[  624.191642] ata4.00: cmd 60/00:58:68:39:95/01:00:02:00:00/40 tag 11 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191646] ata4.00: status: { DRDY }
[  624.191649] ata4.00: failed command: READ FPDMA QUEUED
[  624.191657] ata4.00: cmd 60/10:60:a8:2d:cf/00:00:07:00:00/40 tag 12 ncq dma 8192 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191660] ata4.00: status: { DRDY }
[  624.191663] ata4.00: failed command: READ FPDMA QUEUED
[  624.191671] ata4.00: cmd 60/28:68:f8:2d:cf/00:00:07:00:00/40 tag 13 ncq dma 20480 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191674] ata4.00: status: { DRDY }
[  624.191677] ata4.00: failed command: READ FPDMA QUEUED
[  624.191685] ata4.00: cmd 60/08:70:28:2e:cf/00:00:07:00:00/40 tag 14 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191689] ata4.00: status: { DRDY }
[  624.191692] ata4.00: failed command: READ FPDMA QUEUED
[  624.191699] ata4.00: cmd 60/08:78:90:2e:cf/00:00:07:00:00/40 tag 15 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191703] ata4.00: status: { DRDY }
[  624.191706] ata4.00: failed command: READ FPDMA QUEUED
[  624.191714] ata4.00: cmd 60/08:80:a0:2e:cf/00:00:07:00:00/40 tag 16 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191717] ata4.00: status: { DRDY }
[  624.191720] ata4.00: failed command: READ FPDMA QUEUED
[  624.191728] ata4.00: cmd 60/00:88:e0:bb:76/01:00:1a:00:00/40 tag 17 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191732] ata4.00: status: { DRDY }
[  624.191735] ata4.00: failed command: READ FPDMA QUEUED
[  624.191742] ata4.00: cmd 60/00:90:e0:bc:76/01:00:1a:00:00/40 tag 18 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191746] ata4.00: status: { DRDY }

This is brand new evo 960 on Ubuntu 18.04

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-29-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 860 EVO 250GB
Serial Number:    S3YJNB0K252437D
LU WWN Device Id: 5 002538 e4014b81b
Firmware Version: RVT01B6Q
User Capacity:    250 059 350 016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   Unknown(0x09fc), ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jul 26 21:42:50 2018 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       6
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       9
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       1
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   067   046   000    Old_age   Always       -       33
195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x003e   099   099   000    Old_age   Always       -       32
235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       1
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       473803679

SSD was tested on two different machines (both with the same AMD SATA controller) I observed mentioned ATA errors

on both machines. I also installed SSD from different vendor and it works without issues.

Is it known issue? What's the latest firmware version for Samsung SATA SSD 860 EVO 250GB?

Please note that I don't use windows. Is there firmware update list I can track?

Regards,

Kris

afri83 · ‎28-07-2018

@Kris8 wrote:

I have similar issue. Logs are form brand new SATA evo 860 on AMD SATA controller

00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
	Subsystem: Gigabyte Technology Co., Ltd SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
	Kernel driver in use: ahci
	Kernel modules: ahci

Noticed ATA errors

[  383.327718] ata4.00: exception Emask 0x0 SAct 0x1ff00 SErr 0x0 action 0x6
[  383.327727] ata4.00: irq_stat 0x40000008
[  383.327734] ata4.00: failed command: READ FPDMA QUEUED
[  383.327746] ata4.00: cmd 60/00:40:90:3c:b7/01:00:0f:00:00/40 tag 8 ncq dma 131072 in
                        res 41/84:00:90:3c:b7/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[  383.327753] ata4.00: status: { DRDY ERR }
[  383.327757] ata4.00: error: { ICRC ABRT }
[  383.327765] ata4: hard resetting link
[  383.802893] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  383.803217] ata4.00: supports DRM functions and may not be fully accessible
[  383.806666] ata4.00: supports DRM functions and may not be fully accessible
[  383.809702] ata4.00: configured for UDMA/133
[  383.809738] ata4: EH complete
[  383.809889] ata4.00: Enabling discard_zeroes_data
[  624.191556] ata4: log page 10h reported inactive tag 6
[  624.191567] ata4.00: exception Emask 0x1 SAct 0x7ff80 SErr 0x0 action 0x0
[  624.191570] ata4.00: irq_stat 0x40000008
[  624.191574] ata4.00: failed command: READ FPDMA QUEUED
[  624.191583] ata4.00: cmd 60/80:38:c0:2d:ce/00:00:07:00:00/40 tag 7 ncq dma 65536 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191587] ata4.00: status: { DRDY }
[  624.191591] ata4.00: failed command: READ FPDMA QUEUED
[  624.191598] ata4.00: cmd 60/60:40:00:b3:ce/00:00:07:00:00/40 tag 8 ncq dma 49152 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191602] ata4.00: status: { DRDY }
[  624.191605] ata4.00: failed command: READ FPDMA QUEUED
[  624.191613] ata4.00: cmd 60/18:48:70:b3:ce/00:00:07:00:00/40 tag 9 ncq dma 12288 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191617] ata4.00: status: { DRDY }
[  624.191620] ata4.00: failed command: READ FPDMA QUEUED
[  624.191627] ata4.00: cmd 60/18:50:b0:b3:ce/00:00:07:00:00/40 tag 10 ncq dma 12288 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191631] ata4.00: status: { DRDY }
[  624.191634] ata4.00: failed command: READ FPDMA QUEUED
[  624.191642] ata4.00: cmd 60/00:58:68:39:95/01:00:02:00:00/40 tag 11 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191646] ata4.00: status: { DRDY }
[  624.191649] ata4.00: failed command: READ FPDMA QUEUED
[  624.191657] ata4.00: cmd 60/10:60:a8:2d:cf/00:00:07:00:00/40 tag 12 ncq dma 8192 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191660] ata4.00: status: { DRDY }
[  624.191663] ata4.00: failed command: READ FPDMA QUEUED
[  624.191671] ata4.00: cmd 60/28:68:f8:2d:cf/00:00:07:00:00/40 tag 13 ncq dma 20480 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191674] ata4.00: status: { DRDY }
[  624.191677] ata4.00: failed command: READ FPDMA QUEUED
[  624.191685] ata4.00: cmd 60/08:70:28:2e:cf/00:00:07:00:00/40 tag 14 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191689] ata4.00: status: { DRDY }
[  624.191692] ata4.00: failed command: READ FPDMA QUEUED
[  624.191699] ata4.00: cmd 60/08:78:90:2e:cf/00:00:07:00:00/40 tag 15 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191703] ata4.00: status: { DRDY }
[  624.191706] ata4.00: failed command: READ FPDMA QUEUED
[  624.191714] ata4.00: cmd 60/08:80:a0:2e:cf/00:00:07:00:00/40 tag 16 ncq dma 4096 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191717] ata4.00: status: { DRDY }
[  624.191720] ata4.00: failed command: READ FPDMA QUEUED
[  624.191728] ata4.00: cmd 60/00:88:e0:bb:76/01:00:1a:00:00/40 tag 17 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191732] ata4.00: status: { DRDY }
[  624.191735] ata4.00: failed command: READ FPDMA QUEUED
[  624.191742] ata4.00: cmd 60/00:90:e0:bc:76/01:00:1a:00:00/40 tag 18 ncq dma 131072 in
                        res 40/00:90:e0:bc:76/00:00:1a:00:00/40 Emask 0x1 (device error)
[  624.191746] ata4.00: status: { DRDY }

This is brand new evo 960 on Ubuntu 18.04

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-29-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 860 EVO 250GB
Serial Number:    S3YJNB0K252437D
LU WWN Device Id: 5 002538 e4014b81b
Firmware Version: RVT01B6Q
User Capacity:    250 059 350 016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   Unknown(0x09fc), ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jul 26 21:42:50 2018 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       6
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       9
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       1
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   067   046   000    Old_age   Always       -       33
195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x003e   099   099   000    Old_age   Always       -       32
235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       1
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       473803679

SSD was tested on two different machines (both with the same AMD SATA controller) I observed mentioned ATA errors

on both machines. I also installed SSD from different vendor and it works without issues.

Is it known issue? What's the latest firmware version for Samsung SATA SSD 860 EVO 250GB?

Please note that I don't use windows. Is there firmware update list I can track?

Regards,

Kris

For now only solution that i found work for me is to install windows in ide mode. Not ahci just ide or native ide on some maschines.

Only problem is that disk works with reduced speed than with ahci mode but no freezes and crc errors anymore.

Only solution until samsung respond about this issue.

Which ssd brands works without problem on Your tests?

Cheers

Kris8 · ‎29-07-2018

@afri83 Native IDE mode didn't help (I tried it before posting). I think my SSD is failed. I'm going to return it. I checked it today on

	Manufacturer: Gigabyte Technology Co., Ltd.
	Product Name: G41M-Combo

and I'm experiencing system freez and following logs appear

[  967.772072] INFO: task cupsd:615 blocked for more than 120 seconds.
[  967.772080]       Not tainted 4.15.0-29-generic #31-Ubuntu
[  967.772082] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  967.772085] cupsd           D    0   615      1 0x00000004
[  967.772090] Call Trace:
[  967.772101]  __schedule+0x291/0x8a0
[  967.772104]  schedule+0x2c/0x80
[  967.772108]  jbd2_log_wait_commit+0xb0/0x120
[  967.772123]  ? wait_woken+0x80/0x80
[  967.772125]  jbd2_complete_transaction+0x5c/0xa0
[  967.772128]  ext4_sync_file+0x226/0x3b0
[  967.772131]  vfs_fsync_range+0x51/0xb0
[  967.772133]  do_fsync+0x3d/0x70
[  967.772135]  SyS_fsync+0x10/0x20
[  967.772137]  do_syscall_64+0x73/0x130
[  967.772140]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  967.772148] RIP: 0033:0x7f17c3942ae1
[  967.772149] RSP: 002b:00007ffffbe14378 EFLAGS: 00000246 ORIG_RAX: 000000000000004a
[  967.772151] RAX: ffffffffffffffda RBX: 00007ffffbe14bd0 RCX: 00007f17c3942ae1
[  967.772152] RDX: 00000000000002a9 RSI: 00005647161d4bc8 RDI: 0000000000000006
[  967.772154] RBP: 00005647161d4bc0 R08: 0000000000000000 R09: 00007f17c36ae1b0
[  967.772155] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000200000
[  967.772156] R13: 00005647146a1bc4 R14: 00005647148b55d8 R15: 0000000000000000
[  967.772161] INFO: task snapd:731 blocked for more than 120 seconds.
[  967.772163]       Not tainted 4.15.0-29-generic #31-Ubuntu
[  967.772164] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  967.772166] snapd           D    0   731      1 0x00000000
[  967.772168] Call Trace:
[  967.772171]  __schedule+0x291/0x8a0
[  967.772173]  schedule+0x2c/0x80
[  967.772174]  jbd2_log_wait_commit+0xb0/0x120
[  967.772176]  ? wait_woken+0x80/0x80
[  967.772178]  jbd2_complete_transaction+0x5c/0xa0
[  967.772180]  ext4_sync_file+0x226/0x3b0
[  967.772182]  vfs_fsync_range+0x51/0xb0
[  967.772184]  do_fsync+0x3d/0x70
[  967.772186]  SyS_fsync+0x10/0x20
[  967.772187]  do_syscall_64+0x73/0x130
[  967.772189]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  967.772191] RIP: 0033:0x56039346adb0
[  967.772192] RSP: 002b:000000c42071b878 EFLAGS: 00000212 ORIG_RAX: 000000000000004a
[  967.772194] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000056039346adb0
[  967.772195] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
[  967.772196] RBP: 000000c42071b8c0 R08: 0000000000000000 R09: 0000000000000000
[  967.772197] R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000000
[  967.772198] R13: 00000000000000f5 R14: 0000000000000075 R15: 0000000000000004
[  967.772208] INFO: task upowerd:993 blocked for more than 120 seconds.
[  967.772210]       Not tainted 4.15.0-29-generic #31-Ubuntu
[  967.772212] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  967.772213] upowerd         D    0   993      1 0x00000000
[  967.772215] Call Trace:
[  967.772218]  __schedule+0x291/0x8a0
[  967.772220]  schedule+0x2c/0x80
[  967.772222]  jbd2_log_wait_commit+0xb0/0x120
[  967.772224]  ? wait_woken+0x80/0x80
[  967.772226]  jbd2_complete_transaction+0x5c/0xa0
[  967.772228]  ext4_sync_file+0x226/0x3b0
[  967.772230]  vfs_fsync_range+0x51/0xb0
[  967.772231]  do_fsync+0x3d/0x70
[  967.772233]  SyS_fsync+0x10/0x20
[  967.772235]  do_syscall_64+0x73/0x130
[  967.772237]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  967.772238] RIP: 0033:0x7f4ef8562237
[  967.772239] RSP: 002b:00007fff07065fe0 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
[  967.772241] RAX: ffffffffffffffda RBX: 000000000000000a RCX: 00007f4ef8562237
[  967.772242] RDX: 0000000000000000 RSI: 00007fff07066010 RDI: 000000000000000a
[  967.772243] RBP: 000000000000000a R08: 0000000000000000 R09: 000000000000003d
[  967.772244] R10: 0000000000000019 R11: 0000000000000293 R12: 00007f4ef9dbfc80
[  967.772245] R13: 00005605d05bd1a0 R14: 00005605d05dfc80 R15: 0000000000000000

@afri83 Answering your question, I'm using two Goodram Iridium Pro 480GB SSD's.

masterIdori · ‎30-07-2018

I wrote to Samsung's EU support (samsungmemory@hanaro.eu) and they told me to "use an Intel controller or SATA AHCI controller." to which I explained that it's obvious that the controller in the AMD chipset is SATA AHCI. After few more mails where I explained that it's not normal for the SSD to act like that, they continued to blame the AMD SATA controller, I clearly stated that I'm not going to buy new system just to get the SSD working correctly and that the issue is in their SSD controller and not the AMD SATA controller and it's up to them to fix it with firmware update. Well, it's seems that it's not going to happen - they told me to return the SSD back to the retailer or to send it to their service center in the Netherlands :). I will probably make a trip to the hardware store in few days to return it.

afri83 · ‎09-08-2018

Any new information? I wqrote to samsung also.They told me to speak with store where i bought disk. Very disapointing. How to speak with right people to reslove this by new firmware ? Any ideas?

GlennDa5id · ‎15-08-2018

I am in US and have this issue with EVO 860 512GB. Returned the first drive and got a brand new replacement and same issue. Random SMART CRC errors which cause system to hang. I have an ASUS M5A97 R2.0 which uses the 970 chipset. My older EVO 830 drive works fine.

I just purchased a 2 port SATAIII controller and that may be the best option. I'll report back.

GlennDa5id · ‎17-08-2018

I bought and installed a 2 port SATA controller model# SY-PEX40039 ($14). It is bootable if this is your primary drive. If you use the latest drivers from Syba's site (recommend), version 3.2.3.0 you must use the installer to install them. If you have windows try to find them from device manager in the extracted direcotories from the downloaded driver zip, the system will bluescreen and then bluescreen on reboot. Pain to revert if you didn't make a restore point.

Connected to the SATA card, Crystal Diskmark performance is very good and AHCI is functiontioning. The 860 drive plugged into the card outperforms my older 830 drive plugged into the mainboard. The only drawback is that Samsung Magician does not recognize the drive.

I also found that if I configured my SATA ports on my motherboard for IDE instead of AHCI that the 860 drive was stable. However DiskMark showed very poor performance which is to be expected in the absense of AHCI.

Hopefully Samsung releases a firmware update to resolve this issue. In the meantime the SATA card seems like a good option and performance is very acceptable.

Kris8 · ‎18-08-2018

@afri83 wrote:
Any new information? I wqrote to samsung also.They told me to speak with store where i bought disk. Very disapointing. How to speak with right people to reslove this by new firmware ? Any ideas?

I have returned my SSD and substituted by one from different vendor. All is working fine now. For me it's obvious FW issue or HW damage.

860 EVO 250GB causing freezes on AMD system

1 Solution