Bug 49841 - NCQ causes SSD on a Marvell 6123 controller to crash
Summary: NCQ causes SSD on a Marvell 6123 controller to crash
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: Jeff Garzik
URL: https://bugs.launchpad.net/ubuntu/+so...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-01 06:08 UTC by Laurent Dinclaux
Modified: 2016-03-19 17:01 UTC (History)
5 users (show)

See Also:
Kernel Version: 3.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Laurent Dinclaux 2012-11-01 06:08:11 UTC
Hello,

I have just bought a brand new corsair neutron SSD. When trying to install Ubuntu I faced many IO errors after which the file system is remounted read only.

I marked it as blocking because it prevents installing or using linux on such hardware setups.

I also tried the 3.7-rc2 kernel from the mainline repository, which have the same issue.

A workaround exists, adding libata.force:noncq to grub, so it seems that the NCQ implementation for that controller is guilty.

Here is a log file with the encountered errors while installing Ubuntu: https://launchpadlibrarian.net/121694147/UbiquitySyslog.txt

The bug report on launchpad: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1073391

Another relevant duplicate that shows that the issue occurs with other SSD: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/550559
Comment 1 Alan 2012-11-01 14:18:51 UTC
Oct 31 11:31:46 ubuntu kernel: [  306.020806] ata7.00: failed command: READ FPDMA QUEUED
Oct 31 11:31:46 ubuntu kernel: [  306.020813] ata7.00: cmd 60/10:28:38:59:c6/00:00:0c:00:00/40 tag 5 ncq 8192 in
Oct 31 11:31:46 ubuntu kernel: [  306.020813]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 31 11:31:46 ubuntu kernel: [  306.020816] ata7.00: status: { DRDY }
Oct 31 11:31:46 ubuntu kernel: [  306.020822] ata7: hard resetting link
Oct 31 11:31:47 ubuntu kernel: [  306.512975] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Oct 31 11:31:47 ubuntu kernel: [  306.513808] ata7.00: configured for UDMA/133
Oct 31 11:31:47 ubuntu kernel: [  306.513884] ata7.00: device reported invalid CHS sector 0

So your drive stopped responding and then went insane. Doesn't look anything to do with Linux.

Possibly we need to blacklist NCQ on that version of the drive, but I would suggest the starting point for everyone with this problem will be to check with Corsair for known problems in the firmware and any firmware updates available.
Comment 2 Alan 2012-11-01 16:26:53 UTC
Having dug a bit further - there are no other similar reports I can find for this drive. The Ubuntu other SSD report is a mix of stuff in one messy report - some drives we know are bad and have blacklisted NCQ on, some hardware problems people were having and so on.

We could add it to the blacklist but I'm not happy to do so until we understand whether its a weird problem on your box or something more general. In particular we've seen situations where marginal power supplies cause NCQ to flake out.
Comment 3 Laurent Dinclaux 2012-11-01 22:29:05 UTC
I have exchanged my drive once at my retailer, both time the drive's box was sealed so it is not a drive defect.

It seems people have this issue specifically when plugging in an SSD on that Marvell 6123 controller. Reading the #550559 launchpad bug report, the use of another SATA3 controller, from another brand, seems to solve the issue.
Comment 4 Laurent Dinclaux 2012-11-01 23:06:48 UTC
After trying again 3.7-rc2 and 3.7-rc3 it seems that I face something similar to that bug: https://bugzilla.kernel.org/show_bug.cgi?id=15573

There are some READ FPDMA QUEUED errors at boot, and then the system starts and seems to run well (with NCQ enabled).

# cat /var/log/dmesg | grep ata7

[    0.812802] ata7: SATA max UDMA/133 abar m2048@0xf7eff000 port 0xf7eff100 irq 51
[    1.303872] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[    1.304288] ata7.00: ATA-8: Corsair Neutron SSD, M206, max UDMA/133
[    1.304292] ata7.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[    1.304337] ata7.00: failed to get Identify Device Data, Emask 0x1
[    1.305080] ata7.00: failed to get Identify Device Data, Emask 0x1
[    1.305088] ata7.00: configured for UDMA/133
[   34.007192] ata7.00: exception Emask 0x0 SAct 0x1000001 SErr 0x0 action 0x6 frozen
[   34.007248] ata7.00: failed command: READ FPDMA QUEUED
[   34.007299] ata7.00: cmd 60/08:00:80:f7:c5/00:00:13:00:00/40 tag 0 ncq 4096 in
[   34.007351] ata7.00: status: { DRDY }
[   34.007387] ata7.00: failed command: READ FPDMA QUEUED
[   34.007426] ata7.00: cmd 60/08:c0:e0:0e:00/00:00:05:00:00/40 tag 24 ncq 4096 in
[   34.007478] ata7.00: status: { DRDY }
[   34.007516] ata7: hard resetting link
[   34.499171] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[   34.499652] ata7.00: failed to get Identify Device Data, Emask 0x1
[   34.500398] ata7.00: failed to get Identify Device Data, Emask 0x1
[   34.500406] ata7.00: configured for UDMA/133
[   34.500411] ata7.00: device reported invalid CHS sector 0
[   34.500414] ata7.00: device reported invalid CHS sector 0
[   34.500589] ata7: EH complete
[   64.918616] ata7.00: exception Emask 0x0 SAct 0x3fff1000 SErr 0x0 action 0x6 frozen
[   64.918674] ata7.00: failed command: READ FPDMA QUEUED
[   64.918728] ata7.00: cmd 60/08:60:60:09:40/00:00:04:00:00/40 tag 12 ncq 4096 in
[   64.918794] ata7.00: status: { DRDY }
[   64.918842] ata7.00: failed command: READ FPDMA QUEUED
[   64.918893] ata7.00: cmd 60/08:80:80:09:40/00:00:04:00:00/40 tag 16 ncq 4096 in
[   64.918990] ata7.00: status: { DRDY }
[   64.919037] ata7.00: failed command: READ FPDMA QUEUED
[   64.919087] ata7.00: cmd 60/08:88:88:09:40/00:00:04:00:00/40 tag 17 ncq 4096 in
[   64.919184] ata7.00: status: { DRDY }
[   64.919231] ata7.00: failed command: READ FPDMA QUEUED
[   64.919282] ata7.00: cmd 60/08:90:98:09:40/00:00:04:00:00/40 tag 18 ncq 4096 in
[   64.919379] ata7.00: status: { DRDY }
[   64.919426] ata7.00: failed command: READ FPDMA QUEUED
[   64.919727] ata7.00: cmd 60/08:98:a8:09:40/00:00:04:00:00/40 tag 19 ncq 4096 in
[   64.919828] ata7.00: status: { DRDY }
[   64.919875] ata7.00: failed command: READ FPDMA QUEUED
[   64.919925] ata7.00: cmd 60/08:a0:b0:09:40/00:00:04:00:00/40 tag 20 ncq 4096 in
[   64.920023] ata7.00: status: { DRDY }
[   64.920069] ata7.00: failed command: READ FPDMA QUEUED
[   64.920120] ata7.00: cmd 60/08:a8:b8:09:40/00:00:04:00:00/40 tag 21 ncq 4096 in
[   64.920217] ata7.00: status: { DRDY }
[   64.920264] ata7.00: failed command: READ FPDMA QUEUED
[   64.920314] ata7.00: cmd 60/08:b0:c0:09:40/00:00:04:00:00/40 tag 22 ncq 4096 in
[   64.920411] ata7.00: status: { DRDY }
[   64.920458] ata7.00: failed command: READ FPDMA QUEUED
[   64.920509] ata7.00: cmd 60/08:b8:c8:09:40/00:00:04:00:00/40 tag 23 ncq 4096 in
[   64.920606] ata7.00: status: { DRDY }
[   64.920653] ata7.00: failed command: READ FPDMA QUEUED
[   64.920703] ata7.00: cmd 60/08:c0:d0:09:40/00:00:04:00:00/40 tag 24 ncq 4096 in
[   64.920800] ata7.00: status: { DRDY }
[   64.920847] ata7.00: failed command: READ FPDMA QUEUED
[   64.920898] ata7.00: cmd 60/08:c8:d8:09:40/00:00:04:00:00/40 tag 25 ncq 4096 in
[   64.920995] ata7.00: status: { DRDY }
[   64.921042] ata7.00: failed command: READ FPDMA QUEUED
[   64.921092] ata7.00: cmd 60/08:d0:e8:09:40/00:00:04:00:00/40 tag 26 ncq 4096 in
[   64.921189] ata7.00: status: { DRDY }
[   64.921236] ata7.00: failed command: READ FPDMA QUEUED
[   64.921287] ata7.00: cmd 60/08:d8:f8:09:40/00:00:04:00:00/40 tag 27 ncq 4096 in
[   64.921384] ata7.00: status: { DRDY }
[   64.921431] ata7.00: failed command: READ FPDMA QUEUED
[   64.921481] ata7.00: cmd 60/08:e0:00:0a:40/00:00:04:00:00/40 tag 28 ncq 4096 in
[   64.921578] ata7.00: status: { DRDY }
[   64.921625] ata7.00: failed command: READ FPDMA QUEUED
[   64.921676] ata7.00: cmd 60/08:e8:a0:09:40/00:00:04:00:00/40 tag 29 ncq 4096 in
[   64.921773] ata7.00: status: { DRDY }
[   64.921821] ata7: hard resetting link
[   65.410485] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[   65.410872] ata7.00: failed to get Identify Device Data, Emask 0x1
[   65.411605] ata7.00: failed to get Identify Device Data, Emask 0x1
[   65.411613] ata7.00: configured for UDMA/133
[   65.411618] ata7.00: device reported invalid CHS sector 0
[   65.411622] ata7.00: device reported invalid CHS sector 0
[   65.411624] ata7.00: device reported invalid CHS sector 0
[   65.411627] ata7.00: device reported invalid CHS sector 0
[   65.411630] ata7.00: device reported invalid CHS sector 0
[   65.411632] ata7.00: device reported invalid CHS sector 0
[   65.411635] ata7.00: device reported invalid CHS sector 0
[   65.411637] ata7.00: device reported invalid CHS sector 0
[   65.411640] ata7.00: device reported invalid CHS sector 0
[   65.411642] ata7.00: device reported invalid CHS sector 0
[   65.411645] ata7.00: device reported invalid CHS sector 0
[   65.411648] ata7.00: device reported invalid CHS sector 0
[   65.411650] ata7.00: device reported invalid CHS sector 0
[   65.411653] ata7.00: device reported invalid CHS sector 0
[   65.411655] ata7.00: device reported invalid CHS sector 0
[   65.412446] ata7: EH complete
[   96.021806] ata7.00: exception Emask 0x0 SAct 0x3fffffff SErr 0x0 action 0x6 frozen
[   96.021890] ata7.00: failed command: READ FPDMA QUEUED
[   96.021949] ata7.00: cmd 60/08:00:d8:1d:80/00:00:10:00:00/40 tag 0 ncq 4096 in
[   96.022049] ata7.00: status: { DRDY }
[   96.022096] ata7.00: failed command: READ FPDMA QUEUED
[   96.022149] ata7.00: cmd 60/08:08:e0:1d:80/00:00:10:00:00/40 tag 1 ncq 4096 in
[   96.022248] ata7.00: status: { DRDY }
[   96.022296] ata7.00: failed command: READ FPDMA QUEUED
[   96.022347] ata7.00: cmd 60/08:10:10:1d:80/00:00:10:00:00/40 tag 2 ncq 4096 in
[   96.022444] ata7.00: status: { DRDY }
[   96.022490] ata7.00: failed command: READ FPDMA QUEUED
[   96.022541] ata7.00: cmd 60/08:18:20:1d:80/00:00:10:00:00/40 tag 3 ncq 4096 in
[   96.022638] ata7.00: status: { DRDY }
[   96.022685] ata7.00: failed command: READ FPDMA QUEUED
[   96.022735] ata7.00: cmd 60/08:20:28:1d:80/00:00:10:00:00/40 tag 4 ncq 4096 in
[   96.022832] ata7.00: status: { DRDY }
[   96.022879] ata7.00: failed command: READ FPDMA QUEUED
[   96.022930] ata7.00: cmd 60/08:28:30:1d:80/00:00:10:00:00/40 tag 5 ncq 4096 in
[   96.023027] ata7.00: status: { DRDY }
[   96.023074] ata7.00: failed command: READ FPDMA QUEUED
[   96.023124] ata7.00: cmd 60/08:30:38:1d:80/00:00:10:00:00/40 tag 6 ncq 4096 in
[   96.023221] ata7.00: status: { DRDY }
[   96.023268] ata7.00: failed command: READ FPDMA QUEUED
[   96.023318] ata7.00: cmd 60/08:38:40:1d:80/00:00:10:00:00/40 tag 7 ncq 4096 in
[   96.023415] ata7.00: status: { DRDY }
[   96.023462] ata7.00: failed command: READ FPDMA QUEUED
[   96.023513] ata7.00: cmd 60/08:40:48:1d:80/00:00:10:00:00/40 tag 8 ncq 4096 in
[   96.023610] ata7.00: status: { DRDY }
[   96.023657] ata7.00: failed command: READ FPDMA QUEUED
[   96.023707] ata7.00: cmd 60/08:48:50:1d:80/00:00:10:00:00/40 tag 9 ncq 4096 in
[   96.023804] ata7.00: status: { DRDY }
[   96.023851] ata7.00: failed command: READ FPDMA QUEUED
[   96.023902] ata7.00: cmd 60/08:50:58:1d:80/00:00:10:00:00/40 tag 10 ncq 4096 in
[   96.023999] ata7.00: status: { DRDY }
[   96.024045] ata7.00: failed command: READ FPDMA QUEUED
[   96.024096] ata7.00: cmd 60/08:58:60:1d:80/00:00:10:00:00/40 tag 11 ncq 4096 in
[   96.024193] ata7.00: status: { DRDY }
[   96.024240] ata7.00: failed command: READ FPDMA QUEUED
[   96.024291] ata7.00: cmd 60/08:60:68:1d:80/00:00:10:00:00/40 tag 12 ncq 4096 in
[   96.024388] ata7.00: status: { DRDY }
[   96.024434] ata7.00: failed command: READ FPDMA QUEUED
[   96.024485] ata7.00: cmd 60/08:68:70:1d:80/00:00:10:00:00/40 tag 13 ncq 4096 in
[   96.025550] ata7.00: status: { DRDY }
[   96.025600] ata7.00: failed command: READ FPDMA QUEUED
[   96.025651] ata7.00: cmd 60/08:70:78:1d:80/00:00:10:00:00/40 tag 14 ncq 4096 in
[   96.025838] ata7.00: status: { DRDY }
[   96.025892] ata7.00: failed command: READ FPDMA QUEUED
[   96.025945] ata7.00: cmd 60/08:78:80:1d:80/00:00:10:00:00/40 tag 15 ncq 4096 in
[   96.026042] ata7.00: status: { DRDY }
[   96.026089] ata7.00: failed command: READ FPDMA QUEUED
[   96.026140] ata7.00: cmd 60/08:80:88:1d:80/00:00:10:00:00/40 tag 16 ncq 4096 in
[   96.026237] ata7.00: status: { DRDY }
[   96.026284] ata7.00: failed command: READ FPDMA QUEUED
[   96.026334] ata7.00: cmd 60/08:88:90:1d:80/00:00:10:00:00/40 tag 17 ncq 4096 in
[   96.026431] ata7.00: status: { DRDY }
[   96.026478] ata7.00: failed command: READ FPDMA QUEUED
[   96.026529] ata7.00: cmd 60/08:90:98:1d:80/00:00:10:00:00/40 tag 18 ncq 4096 in
[   96.026626] ata7.00: status: { DRDY }
[   96.026673] ata7.00: failed command: READ FPDMA QUEUED
[   96.026723] ata7.00: cmd 60/08:98:a0:1d:80/00:00:10:00:00/40 tag 19 ncq 4096 in
[   96.026820] ata7.00: status: { DRDY }
[   96.026867] ata7.00: failed command: READ FPDMA QUEUED
[   96.026918] ata7.00: cmd 60/08:a0:a8:1d:80/00:00:10:00:00/40 tag 20 ncq 4096 in
[   96.027015] ata7.00: status: { DRDY }
[   96.027061] ata7.00: failed command: READ FPDMA QUEUED
[   96.027112] ata7.00: cmd 60/08:a8:b0:1d:80/00:00:10:00:00/40 tag 21 ncq 4096 in
[   96.027209] ata7.00: status: { DRDY }
[   96.027256] ata7.00: failed command: READ FPDMA QUEUED
[   96.027306] ata7.00: cmd 60/08:b0:b8:1d:80/00:00:10:00:00/40 tag 22 ncq 4096 in
[   96.027404] ata7.00: status: { DRDY }
[   96.027450] ata7.00: failed command: READ FPDMA QUEUED
[   96.027501] ata7.00: cmd 60/08:b8:c0:1d:80/00:00:10:00:00/40 tag 23 ncq 4096 in
[   96.027598] ata7.00: status: { DRDY }
[   96.027645] ata7.00: failed command: READ FPDMA QUEUED
[   96.027696] ata7.00: cmd 60/08:c0:c8:1d:80/00:00:10:00:00/40 tag 24 ncq 4096 in
[   96.027793] ata7.00: status: { DRDY }
[   96.027840] ata7.00: failed command: READ FPDMA QUEUED
[   96.027890] ata7.00: cmd 60/08:c8:d0:1d:80/00:00:10:00:00/40 tag 25 ncq 4096 in
[   96.027987] ata7.00: status: { DRDY }
[   96.028034] ata7.00: failed command: READ FPDMA QUEUED
[   96.028084] ata7.00: cmd 60/08:d0:e8:1d:80/00:00:10:00:00/40 tag 26 ncq 4096 in
[   96.028181] ata7.00: status: { DRDY }
[   96.028228] ata7.00: failed command: READ FPDMA QUEUED
[   96.028279] ata7.00: cmd 60/08:d8:f0:1d:80/00:00:10:00:00/40 tag 27 ncq 4096 in
[   96.028376] ata7.00: status: { DRDY }
[   96.028423] ata7.00: failed command: READ FPDMA QUEUED
[   96.028473] ata7.00: cmd 60/08:e0:00:1e:80/00:00:10:00:00/40 tag 28 ncq 4096 in
[   96.028570] ata7.00: status: { DRDY }
[   96.028617] ata7.00: failed command: READ FPDMA QUEUED
[   96.028668] ata7.00: cmd 60/08:e8:18:1d:80/00:00:10:00:00/40 tag 29 ncq 4096 in
[   96.028765] ata7.00: status: { DRDY }
[   96.028812] ata7: hard resetting link
[   96.517790] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[   96.518168] ata7.00: failed to get Identify Device Data, Emask 0x1
[   96.518785] ata7.00: failed to get Identify Device Data, Emask 0x1
[   96.518792] ata7.00: configured for UDMA/133
[   96.518798] ata7.00: device reported invalid CHS sector 0
[   96.518801] ata7.00: device reported invalid CHS sector 0
[   96.518803] ata7.00: device reported invalid CHS sector 0
[   96.518806] ata7.00: device reported invalid CHS sector 0
[   96.518809] ata7.00: device reported invalid CHS sector 0
[   96.518811] ata7.00: device reported invalid CHS sector 0
[   96.518814] ata7.00: device reported invalid CHS sector 0
[   96.518816] ata7.00: device reported invalid CHS sector 0
[   96.518819] ata7.00: device reported invalid CHS sector 0
[   96.518822] ata7.00: device reported invalid CHS sector 0
[   96.518824] ata7.00: device reported invalid CHS sector 0
[   96.518827] ata7.00: device reported invalid CHS sector 0
[   96.518829] ata7.00: device reported invalid CHS sector 0
[   96.518832] ata7.00: device reported invalid CHS sector 0
[   96.518834] ata7.00: device reported invalid CHS sector 0
[   96.518837] ata7.00: device reported invalid CHS sector 0
[   96.518839] ata7.00: device reported invalid CHS sector 0
[   96.518842] ata7.00: device reported invalid CHS sector 0
[   96.518845] ata7.00: device reported invalid CHS sector 0
[   96.518847] ata7.00: device reported invalid CHS sector 0
[   96.518850] ata7.00: device reported invalid CHS sector 0
[   96.518852] ata7.00: device reported invalid CHS sector 0
[   96.518855] ata7.00: device reported invalid CHS sector 0
[   96.518857] ata7.00: device reported invalid CHS sector 0
[   96.518860] ata7.00: device reported invalid CHS sector 0
[   96.518862] ata7.00: device reported invalid CHS sector 0
[   96.518865] ata7.00: device reported invalid CHS sector 0
[   96.518868] ata7.00: device reported invalid CHS sector 0
[   96.518870] ata7.00: device reported invalid CHS sector 0
[   96.518873] ata7.00: device reported invalid CHS sector 0
[   96.519907] ata7: EH complete
[  126.997111] ata7.00: NCQ disabled due to excessive errors
[  126.997118] ata7.00: exception Emask 0x0 SAct 0x76ecc002 SErr 0x0 action 0x6 frozen
[  126.997200] ata7.00: failed command: READ FPDMA QUEUED
[  126.997259] ata7.00: cmd 60/08:08:08:0f:40/00:00:10:00:00/40 tag 1 ncq 4096 in
[  126.997357] ata7.00: status: { DRDY }
[  126.997405] ata7.00: failed command: READ FPDMA QUEUED
[  126.997456] ata7.00: cmd 60/08:70:70:0f:40/00:00:10:00:00/40 tag 14 ncq 4096 in
[  126.997553] ata7.00: status: { DRDY }
[  126.997600] ata7.00: failed command: READ FPDMA QUEUED
[  126.997651] ata7.00: cmd 60/08:78:80:0f:40/00:00:10:00:00/40 tag 15 ncq 4096 in
[  126.997748] ata7.00: status: { DRDY }
[  126.997795] ata7.00: failed command: READ FPDMA QUEUED
[  126.997845] ata7.00: cmd 60/08:90:98:0f:40/00:00:10:00:00/40 tag 18 ncq 4096 in
[  126.997942] ata7.00: status: { DRDY }
[  126.997989] ata7.00: failed command: READ FPDMA QUEUED
[  126.998040] ata7.00: cmd 60/08:98:a0:0f:40/00:00:10:00:00/40 tag 19 ncq 4096 in
[  126.998137] ata7.00: status: { DRDY }
[  126.998184] ata7.00: failed command: READ FPDMA QUEUED
[  126.998234] ata7.00: cmd 60/08:a8:b0:0f:40/00:00:10:00:00/40 tag 21 ncq 4096 in
[  126.998331] ata7.00: status: { DRDY }
[  126.998378] ata7.00: failed command: READ FPDMA QUEUED
[  126.998429] ata7.00: cmd 60/08:b0:b8:0f:40/00:00:10:00:00/40 tag 22 ncq 4096 in
[  126.998526] ata7.00: status: { DRDY }
[  126.998573] ata7.00: failed command: READ FPDMA QUEUED
[  126.998623] ata7.00: cmd 60/08:b8:f8:0f:40/00:00:10:00:00/40 tag 23 ncq 4096 in
[  126.998720] ata7.00: status: { DRDY }
[  126.998767] ata7.00: failed command: READ FPDMA QUEUED
[  126.998818] ata7.00: cmd 60/08:c8:e0:0f:40/00:00:10:00:00/40 tag 25 ncq 4096 in
[  126.998915] ata7.00: status: { DRDY }
[  126.998962] ata7.00: failed command: READ FPDMA QUEUED
[  126.999012] ata7.00: cmd 60/08:d0:00:10:40/00:00:10:00:00/40 tag 26 ncq 4096 in
[  126.999109] ata7.00: status: { DRDY }
[  126.999156] ata7.00: failed command: READ FPDMA QUEUED
[  126.999207] ata7.00: cmd 60/08:e0:d8:0f:40/00:00:10:00:00/40 tag 28 ncq 4096 in
[  126.999304] ata7.00: status: { DRDY }
[  127.000082] ata7.00: failed command: READ FPDMA QUEUED
[  127.000132] ata7.00: cmd 60/08:e8:e8:0f:40/00:00:10:00:00/40 tag 29 ncq 4096 in
[  127.000229] ata7.00: status: { DRDY }
[  127.000276] ata7.00: failed command: READ FPDMA QUEUED
[  127.000327] ata7.00: cmd 60/08:f0:f0:0f:40/00:00:10:00:00/40 tag 30 ncq 4096 in
[  127.000424] ata7.00: status: { DRDY }
[  127.000471] ata7: hard resetting link
[  127.489106] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[  127.489498] ata7.00: failed to get Identify Device Data, Emask 0x1
[  127.490223] ata7.00: failed to get Identify Device Data, Emask 0x1
[  127.490231] ata7.00: configured for UDMA/133
[  127.490236] ata7.00: device reported invalid CHS sector 0
[  127.490239] ata7.00: device reported invalid CHS sector 0
[  127.490242] ata7.00: device reported invalid CHS sector 0
[  127.490245] ata7.00: device reported invalid CHS sector 0
[  127.490248] ata7.00: device reported invalid CHS sector 0
[  127.490250] ata7.00: device reported invalid CHS sector 0
[  127.490253] ata7.00: device reported invalid CHS sector 0
[  127.490255] ata7.00: device reported invalid CHS sector 0
[  127.490258] ata7.00: device reported invalid CHS sector 0
[  127.490261] ata7.00: device reported invalid CHS sector 0
[  127.490263] ata7.00: device reported invalid CHS sector 0
[  127.490266] ata7.00: device reported invalid CHS sector 0
[  127.490268] ata7.00: device reported invalid CHS sector 0
[  127.491041] ata7: EH complete

# cat /var/log/syslog | grep ata7

Nov  2 09:42:51 lion kernel: [    0.812802] ata7: SATA max UDMA/133 abar m2048@0xf7eff000 port 0xf7eff100 irq 51
Nov  2 09:42:51 lion kernel: [    1.303872] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Nov  2 09:42:51 lion kernel: [    1.304288] ata7.00: ATA-8: Corsair Neutron SSD, M206, max UDMA/133
Nov  2 09:42:51 lion kernel: [    1.304292] ata7.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
Nov  2 09:42:51 lion kernel: [    1.304337] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [    1.305080] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [    1.305088] ata7.00: configured for UDMA/133
Nov  2 09:42:51 lion kernel: [   34.007192] ata7.00: exception Emask 0x0 SAct 0x1000001 SErr 0x0 action 0x6 frozen
Nov  2 09:42:51 lion kernel: [   34.007248] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   34.007299] ata7.00: cmd 60/08:00:80:f7:c5/00:00:13:00:00/40 tag 0 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   34.007351] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   34.007387] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   34.007426] ata7.00: cmd 60/08:c0:e0:0e:00/00:00:05:00:00/40 tag 24 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   34.007478] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   34.007516] ata7: hard resetting link
Nov  2 09:42:51 lion kernel: [   34.499171] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Nov  2 09:42:51 lion kernel: [   34.499652] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   34.500398] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   34.500406] ata7.00: configured for UDMA/133
Nov  2 09:42:51 lion kernel: [   34.500411] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   34.500414] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   34.500589] ata7: EH complete
Nov  2 09:42:51 lion kernel: [   64.918616] ata7.00: exception Emask 0x0 SAct 0x3fff1000 SErr 0x0 action 0x6 frozen
Nov  2 09:42:51 lion kernel: [   64.918674] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.918728] ata7.00: cmd 60/08:60:60:09:40/00:00:04:00:00/40 tag 12 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.918794] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.918842] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.918893] ata7.00: cmd 60/08:80:80:09:40/00:00:04:00:00/40 tag 16 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.918990] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.919037] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.919087] ata7.00: cmd 60/08:88:88:09:40/00:00:04:00:00/40 tag 17 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.919184] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.919231] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.919282] ata7.00: cmd 60/08:90:98:09:40/00:00:04:00:00/40 tag 18 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.919379] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.919426] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.919727] ata7.00: cmd 60/08:98:a8:09:40/00:00:04:00:00/40 tag 19 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.919828] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.919875] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.919925] ata7.00: cmd 60/08:a0:b0:09:40/00:00:04:00:00/40 tag 20 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920023] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.920069] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.920120] ata7.00: cmd 60/08:a8:b8:09:40/00:00:04:00:00/40 tag 21 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920217] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.920264] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.920314] ata7.00: cmd 60/08:b0:c0:09:40/00:00:04:00:00/40 tag 22 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920411] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.920458] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.920509] ata7.00: cmd 60/08:b8:c8:09:40/00:00:04:00:00/40 tag 23 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920606] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.920653] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.920703] ata7.00: cmd 60/08:c0:d0:09:40/00:00:04:00:00/40 tag 24 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920800] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.920847] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.920898] ata7.00: cmd 60/08:c8:d8:09:40/00:00:04:00:00/40 tag 25 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.920995] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.921042] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.921092] ata7.00: cmd 60/08:d0:e8:09:40/00:00:04:00:00/40 tag 26 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.921189] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.921236] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.921287] ata7.00: cmd 60/08:d8:f8:09:40/00:00:04:00:00/40 tag 27 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.921384] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.921431] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.921481] ata7.00: cmd 60/08:e0:00:0a:40/00:00:04:00:00/40 tag 28 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.921578] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.921625] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   64.921676] ata7.00: cmd 60/08:e8:a0:09:40/00:00:04:00:00/40 tag 29 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   64.921773] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   64.921821] ata7: hard resetting link
Nov  2 09:42:51 lion kernel: [   65.410485] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Nov  2 09:42:51 lion kernel: [   65.410872] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   65.411605] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   65.411613] ata7.00: configured for UDMA/133
Nov  2 09:42:51 lion kernel: [   65.411618] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411622] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411624] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411627] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411630] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411632] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411635] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411637] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411640] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411642] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411645] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411648] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411650] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411653] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.411655] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   65.412446] ata7: EH complete
Nov  2 09:42:51 lion kernel: [   96.021806] ata7.00: exception Emask 0x0 SAct 0x3fffffff SErr 0x0 action 0x6 frozen
Nov  2 09:42:51 lion kernel: [   96.021890] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.021949] ata7.00: cmd 60/08:00:d8:1d:80/00:00:10:00:00/40 tag 0 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.022049] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.022096] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.022149] ata7.00: cmd 60/08:08:e0:1d:80/00:00:10:00:00/40 tag 1 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.022248] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.022296] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.022347] ata7.00: cmd 60/08:10:10:1d:80/00:00:10:00:00/40 tag 2 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.022444] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.022490] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.022541] ata7.00: cmd 60/08:18:20:1d:80/00:00:10:00:00/40 tag 3 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.022638] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.022685] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.022735] ata7.00: cmd 60/08:20:28:1d:80/00:00:10:00:00/40 tag 4 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.022832] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.022879] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.022930] ata7.00: cmd 60/08:28:30:1d:80/00:00:10:00:00/40 tag 5 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023027] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.023074] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.023124] ata7.00: cmd 60/08:30:38:1d:80/00:00:10:00:00/40 tag 6 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023221] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.023268] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.023318] ata7.00: cmd 60/08:38:40:1d:80/00:00:10:00:00/40 tag 7 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023415] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.023462] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.023513] ata7.00: cmd 60/08:40:48:1d:80/00:00:10:00:00/40 tag 8 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023610] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.023657] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.023707] ata7.00: cmd 60/08:48:50:1d:80/00:00:10:00:00/40 tag 9 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023804] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.023851] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.023902] ata7.00: cmd 60/08:50:58:1d:80/00:00:10:00:00/40 tag 10 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.023999] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.024045] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.024096] ata7.00: cmd 60/08:58:60:1d:80/00:00:10:00:00/40 tag 11 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.024193] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.024240] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.024291] ata7.00: cmd 60/08:60:68:1d:80/00:00:10:00:00/40 tag 12 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.024388] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.024434] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.024485] ata7.00: cmd 60/08:68:70:1d:80/00:00:10:00:00/40 tag 13 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.025550] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.025600] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.025651] ata7.00: cmd 60/08:70:78:1d:80/00:00:10:00:00/40 tag 14 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.025838] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.025892] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.025945] ata7.00: cmd 60/08:78:80:1d:80/00:00:10:00:00/40 tag 15 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.026042] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.026089] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.026140] ata7.00: cmd 60/08:80:88:1d:80/00:00:10:00:00/40 tag 16 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.026237] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.026284] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.026334] ata7.00: cmd 60/08:88:90:1d:80/00:00:10:00:00/40 tag 17 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.026431] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.026478] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.026529] ata7.00: cmd 60/08:90:98:1d:80/00:00:10:00:00/40 tag 18 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.026626] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.026673] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.026723] ata7.00: cmd 60/08:98:a0:1d:80/00:00:10:00:00/40 tag 19 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.026820] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.026867] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.026918] ata7.00: cmd 60/08:a0:a8:1d:80/00:00:10:00:00/40 tag 20 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027015] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.027061] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.027112] ata7.00: cmd 60/08:a8:b0:1d:80/00:00:10:00:00/40 tag 21 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027209] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.027256] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.027306] ata7.00: cmd 60/08:b0:b8:1d:80/00:00:10:00:00/40 tag 22 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027404] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.027450] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.027501] ata7.00: cmd 60/08:b8:c0:1d:80/00:00:10:00:00/40 tag 23 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027598] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.027645] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.027696] ata7.00: cmd 60/08:c0:c8:1d:80/00:00:10:00:00/40 tag 24 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027793] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.027840] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.027890] ata7.00: cmd 60/08:c8:d0:1d:80/00:00:10:00:00/40 tag 25 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.027987] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.028034] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.028084] ata7.00: cmd 60/08:d0:e8:1d:80/00:00:10:00:00/40 tag 26 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.028181] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.028228] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.028279] ata7.00: cmd 60/08:d8:f0:1d:80/00:00:10:00:00/40 tag 27 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.028376] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.028423] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.028473] ata7.00: cmd 60/08:e0:00:1e:80/00:00:10:00:00/40 tag 28 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.028570] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.028617] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [   96.028668] ata7.00: cmd 60/08:e8:18:1d:80/00:00:10:00:00/40 tag 29 ncq 4096 in
Nov  2 09:42:51 lion kernel: [   96.028765] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [   96.028812] ata7: hard resetting link
Nov  2 09:42:51 lion kernel: [   96.517790] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Nov  2 09:42:51 lion kernel: [   96.518168] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   96.518785] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [   96.518792] ata7.00: configured for UDMA/133
Nov  2 09:42:51 lion kernel: [   96.518798] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518801] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518803] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518806] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518809] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518811] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518814] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518816] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518819] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518822] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518824] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518827] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518829] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518832] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518834] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518837] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518839] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518842] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518845] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518847] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518850] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518852] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518855] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518857] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518860] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518862] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518865] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518868] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518870] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.518873] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [   96.519907] ata7: EH complete
Nov  2 09:42:51 lion kernel: [  126.997111] ata7.00: NCQ disabled due to excessive errors
Nov  2 09:42:51 lion kernel: [  126.997118] ata7.00: exception Emask 0x0 SAct 0x76ecc002 SErr 0x0 action 0x6 frozen
Nov  2 09:42:51 lion kernel: [  126.997200] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.997259] ata7.00: cmd 60/08:08:08:0f:40/00:00:10:00:00/40 tag 1 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.997357] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.997405] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.997456] ata7.00: cmd 60/08:70:70:0f:40/00:00:10:00:00/40 tag 14 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.997553] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.997600] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.997651] ata7.00: cmd 60/08:78:80:0f:40/00:00:10:00:00/40 tag 15 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.997748] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.997795] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.997845] ata7.00: cmd 60/08:90:98:0f:40/00:00:10:00:00/40 tag 18 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.997942] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.997989] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.998040] ata7.00: cmd 60/08:98:a0:0f:40/00:00:10:00:00/40 tag 19 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.998137] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.998184] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.998234] ata7.00: cmd 60/08:a8:b0:0f:40/00:00:10:00:00/40 tag 21 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.998331] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.998378] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.998429] ata7.00: cmd 60/08:b0:b8:0f:40/00:00:10:00:00/40 tag 22 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.998526] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.998573] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.998623] ata7.00: cmd 60/08:b8:f8:0f:40/00:00:10:00:00/40 tag 23 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.998720] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.998767] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.998818] ata7.00: cmd 60/08:c8:e0:0f:40/00:00:10:00:00/40 tag 25 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.998915] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.998962] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.999012] ata7.00: cmd 60/08:d0:00:10:40/00:00:10:00:00/40 tag 26 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.999109] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  126.999156] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  126.999207] ata7.00: cmd 60/08:e0:d8:0f:40/00:00:10:00:00/40 tag 28 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  126.999304] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  127.000082] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  127.000132] ata7.00: cmd 60/08:e8:e8:0f:40/00:00:10:00:00/40 tag 29 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  127.000229] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  127.000276] ata7.00: failed command: READ FPDMA QUEUED
Nov  2 09:42:51 lion kernel: [  127.000327] ata7.00: cmd 60/08:f0:f0:0f:40/00:00:10:00:00/40 tag 30 ncq 4096 in
Nov  2 09:42:51 lion kernel: [  127.000424] ata7.00: status: { DRDY }
Nov  2 09:42:51 lion kernel: [  127.000471] ata7: hard resetting link
Nov  2 09:42:51 lion kernel: [  127.489106] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
Nov  2 09:42:51 lion kernel: [  127.489498] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [  127.490223] ata7.00: failed to get Identify Device Data, Emask 0x1
Nov  2 09:42:51 lion kernel: [  127.490231] ata7.00: configured for UDMA/133
Nov  2 09:42:51 lion kernel: [  127.490236] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490239] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490242] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490245] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490248] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490250] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490253] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490255] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490258] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490261] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490263] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490266] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.490268] ata7.00: device reported invalid CHS sector 0
Nov  2 09:42:51 lion kernel: [  127.491041] ata7: EH complete
Comment 5 Country Boy 2012-11-08 17:20:13 UTC
I'm facing a similar problem in these days. 

I bought a new TRANSCEND SSD disk (model TS128GSSD320) and I installed the debian testing with kernel 3.2.0 and i have the failed command: READ FPDMA
QUEUED problem.

First: i found a way to reproduce the problem sistematically, is sufficient to submit the command: hdparm -t /dev/sda 

Second: i attach the disk with usb interface and i boot the system. All work fine.
So the disk don't have any problem.

Third: I tried various kernel parameters (libata.xxx) but none of these solve the problem.

Today i installed the stable version of debian (with kernel 2.6.32) and the problem appeare, but if i pass the kernel parameters libata.force=3.0G all working fine!!

It seems the mainboard controller is unable the negotiate a 6Gb link in conjunction with the kernel device driver. I don't understand why the old kernel is able to force 3Gb link and the newer not.

The sata controller is:

00:1f.2 SATA controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller (rev 04) (prog-if 01 [AHCI 1.0])
	Subsystem: Dell Device 0493
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 33
	Region 0: I/O ports at 6090 [size=8]
	Region 1: I/O ports at 6080 [size=4]
	Region 2: I/O ports at 6070 [size=8]
	Region 3: I/O ports at 6060 [size=4]
	Region 4: I/O ports at 6020 [size=32]
	Region 5: Memory at e6740000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee00438  Data: 0000
	Capabilities: [70] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
	Capabilities: [b0] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ahci

Have any idea?

thanks
Comment 6 Laurent Dinclaux 2014-04-08 00:56:38 UTC
I just installed Ubuntu Trusty and the bug still exists, on the same Marvell controller using a brand new Samsung 840 SSD
Comment 7 Levente Kurusa 2014-04-17 18:33:16 UTC
(In reply to Laurent Dinclaux from comment #6)
> I just installed Ubuntu Trusty and the bug still exists, on the same Marvell
> controller using a brand new Samsung 840 SSD

Please post the outpout of 'lspci -vvk'.

Try booting with this kernel parameter added: 'libata.force=noncq'.

Thanks
Levente Kurusa
Comment 8 Christian Stadelmann 2015-08-09 15:28:33 UTC
This possibly is a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=43160

Note You need to log in before you can comment on or make changes to this bug.