You are not logged in.

#1 2015-04-29 20:12:33

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

[workaround]temporary system freeze with ata errors (samsung 840evo)

Since today I experience random freezes (up to 1 minute).
At first programs become unresponsive and later mouse and keyboard stop working.
Suddenly everything works again.
I found these error messages occur during the freeze.

[ 3785.581955] ata1.00: exception Emask 0x0 SAct 0x30 SErr 0x0 action 0x6 frozen
[ 3785.581965] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3785.581973] ata1.00: cmd 61/30:20:88:8a:76/00:00:11:00:00/40 tag 4 ncq 24576 out
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3785.581977] ata1.00: status: { DRDY }
[ 3785.581980] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3785.581986] ata1.00: cmd 61/18:28:00:e3:76/00:00:11:00:00/40 tag 5 ncq 12288 out
                        res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3785.581989] ata1.00: status: { DRDY }
[ 3785.581995] ata1: hard resetting link
[ 3785.902292] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3785.903724] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3785.903728] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3785.903730] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3785.903965] ata1.00: supports DRM functions and may not be fully accessible
[ 3785.905359] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3785.905362] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3785.905364] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3785.905484] ata1.00: supports DRM functions and may not be fully accessible
[ 3785.905524] ata1.00: configured for UDMA/133
[ 3785.915632] ata1.00: device reported invalid CHS sector 0
[ 3785.915636] ata1.00: device reported invalid CHS sector 0
[ 3785.915654] ata1: EH complete
[ 3816.656228] ata1.00: exception Emask 0x0 SAct 0xc SErr 0x0 action 0x6 frozen
[ 3816.656236] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3816.656243] ata1.00: cmd 61/10:10:20:e3:76/00:00:11:00:00/40 tag 2 ncq 8192 out
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3816.656247] ata1.00: status: { DRDY }
[ 3816.656250] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3816.656255] ata1.00: cmd 61/18:18:e8:e3:76/00:00:11:00:00/40 tag 3 ncq 12288 out
                        res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3816.656258] ata1.00: status: { DRDY }
[ 3816.656263] ata1: hard resetting link
[ 3816.976499] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3816.977814] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3816.977818] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3816.977820] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3816.977976] ata1.00: supports DRM functions and may not be fully accessible
[ 3816.979397] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3816.979399] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3816.979401] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3816.979520] ata1.00: supports DRM functions and may not be fully accessible
[ 3816.979560] ata1.00: configured for UDMA/133
[ 3816.989850] ata1.00: device reported invalid CHS sector 0
[ 3816.989853] ata1.00: device reported invalid CHS sector 0
[ 3816.989866] ata1: EH complete
[ 3847.613653] ata1.00: exception Emask 0x0 SAct 0x22000000 SErr 0x0 action 0x6 frozen
[ 3847.613720] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3847.613763] ata1.00: cmd 61/10:c8:c8:b6:51/00:00:11:00:00/40 tag 25 ncq 8192 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3847.613862] ata1.00: status: { DRDY }
[ 3847.613891] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3847.613932] ata1.00: cmd 61/08:e8:78:b8:54/00:00:11:00:00/40 tag 29 ncq 4096 out
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3847.614029] ata1.00: status: { DRDY }
[ 3847.614059] ata1: hard resetting link
[ 3847.933935] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3847.935279] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3847.935284] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3847.935286] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3847.935410] ata1.00: supports DRM functions and may not be fully accessible
[ 3847.936728] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3847.936730] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3847.936732] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3847.936850] ata1.00: supports DRM functions and may not be fully accessible
[ 3847.936890] ata1.00: configured for UDMA/133
[ 3847.947303] ata1.00: device reported invalid CHS sector 0
[ 3847.947305] ata1.00: device reported invalid CHS sector 0
[ 3847.947318] ata1: EH complete
[ 3878.698011] ata1.00: NCQ disabled due to excessive errors
[ 3878.698022] ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x6 frozen
[ 3878.698030] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3878.698039] ata1.00: cmd 61/08:70:a0:c8:4d/00:00:02:00:00/40 tag 14 ncq 4096 out
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3878.698044] ata1.00: status: { DRDY }
[ 3878.698051] ata1: hard resetting link
[ 3879.018298] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 3879.019780] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3879.019787] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3879.019790] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3879.019988] ata1.00: supports DRM functions and may not be fully accessible
[ 3879.021453] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3879.021459] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[ 3879.021461] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3879.021662] ata1.00: supports DRM functions and may not be fully accessible
[ 3879.021798] ata1.00: configured for UDMA/133
[ 3879.034970] ata1.00: device reported invalid CHS sector 0
[ 3879.034990] ata1: EH complete

I have made two significant changes today:

  1. kernel upgrade to 4.0

  2. firmware upgrade of my samsung ssd 840evo (because of this performance bug thing)

Is there anybody with similar issues (especially on the 840evo with the new firmware)?
Or does anybody even understand these error messages?

EDIT: I found this section in the wiki. I will try that and see if it helps

Last edited by dice (2015-05-01 09:24:02)


I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#2 2015-04-30 12:42:47

rtoijala
Member
Registered: 2011-09-11
Posts: 36

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

Hello,

I have the same problem since updating the Samsung SSD Ev0 250GB to the latest firmware (EXT0DB6Q) four days ago.
There is also an ubuntu bug about it (https://bugs.launchpad.net/ubuntu/+sour … ug/1449005).

The freezes usually occur during high I/O load.

The problem does not seem to appear on Windows, I tested by writing to several large files at the same time for over a minute.

I tried disabling NCQ, but it did not seem to help. I might retry that, though.

EDIT: I could not reproduce the error when booted with libata.force=noncq. I'll be using that as a temporary fix now.

Last edited by rtoijala (2015-04-30 12:49:41)

Offline

#3 2015-04-30 15:56:37

PootisBird
Member
Registered: 2014-04-16
Posts: 117

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

I have same issue since firmware update, I have disabled NCQ and it's ok now. It would be cooler if someone at Samsung would fix it on kernel side.

Offline

#4 2015-05-01 09:23:27

dice
Member
From: Germany
Registered: 2014-02-10
Posts: 413

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

After two days of testing I can confirm that disabling NCQ via kernel command line helps. The error does not appear any more.
I also cannot see any loss of performance so far.
Looking at this kernel commit (https://git.kernel.org/cgit/linux/kerne … 996626221a) for Samsung's 850 pro SSD I have the feeling that the latest generation of their firmware doe not like how Linux handles NCQ.


I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do.  (Gune | Titan A.E.)

Offline

#5 2015-05-29 18:39:13

PootisBird
Member
Registered: 2014-04-16
Posts: 117

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

It seems that kernel devs has decided to revert this commit and go in balls deep. It's applied to whole 8xx series now.
https://git.kernel.org/cgit/linux/kerne … 324d396967
It will arrive when 4.1 hits upstream.

Offline

#6 2016-10-31 19:29:14

kaipee
Member
From: Belfast, UK
Registered: 2012-07-07
Posts: 203

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

dice wrote:

After two days of testing I can confirm that disabling NCQ via kernel command line helps. The error does not appear any more.
I also cannot see any loss of performance so far.
Looking at this kernel commit (https://git.kernel.org/cgit/linux/kerne … 996626221a) for Samsung's 850 pro SSD I have the feeling that the latest generation of their firmware doe not like how Linux handles NCQ.

I've just booted to my Windows partition, probably for the first time this year lol, and noticed this firmware update was available for my 840 EVO.
Can you confirm there are no issues with this firmware release on Arch now?

Thanks in advance

Offline

#7 2016-10-31 19:51:21

rtoijala
Member
Registered: 2011-09-11
Posts: 36

Re: [workaround]temporary system freeze with ata errors (samsung 840evo)

Hi,
I've been using the 840 EVO with the newest firmware for over a year and it causes no problems since a kernel update around that time.

The following message should be printed to dmesg:

ata5.00: disabling queued TRIM support

(with the appropriate ata port, of course).

So yes, I can confirm that there are no problems with the firmware update.

Offline

Board footer

Powered by FluxBB