[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Upgraded to Ubuntu 17.04 = Linux 4.10.x Problem has gone away. I'm assuming the 4.10 queueing changes have fixed the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Expired Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel: [18500.172758] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00: status: { DRDY } Apr 14 18:02:06
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Expired Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel: [18500.172758] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00: status: { DRDY }
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Now using: 4.8.0-49-generic #52-Ubuntu SMP Thu Apr 20 09:38:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux related to heavy disc load, typically an rsync running as part of backup. But the sda drive is the only one that generates the errors, sdb and sdc that actually have the backup files don't give errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Incomplete Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel:
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Tried the kernel above, unfortunately dkms fails trying to add nvidia module so I can't get it running. Attaching dkms log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Incomplete Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel: [18500.172758] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00: status: { DRDY } Apr 14 18:02:06
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
** Attachment added: "dkms log for kerel 3.11 and nvidia 378" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682892/+attachment/4868342/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Incomplete Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel: [18500.172758] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00:
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
This has only started happening recently, so I'm trying -45 and -41 to see if it goes away partly because I need to use this machine but also to see if I can identify when the problem was introduced. Is the 4.11 r7 reasonably stable? I don't want to lose any data (even with backups) as it's a pain to fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Incomplete Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out Apr 14 18:02:06 mark-linux kernel:
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682892 Title: failed command: READ FPDMA QUEUED Status in linux package in Ubuntu: Incomplete Bug description: occurs intermittently usually when under load, causes the system to hang for a while, needs a reboot which then normally fixes the file system errors. Seems same symptoms and error message as bug 550559 but in a current kernel. I have a Seagate SSHD drive as ata5. Trying the libata.force=noncq kernel param to see if the hangs and errors go away. Drive passes SMART self test. RElevant part of kern.log: Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6 Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008 Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: READ FPDMA QUEUED Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in Apr 14 16:52:01 mark-linux kernel: [14294.691839] res 41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR } Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT } Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for UDMA/133 Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out Apr 14 18:02:06 mark-linux kernel: [18500.172617] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out Apr 14 18:02:06 mark-linux kernel: [18500.172643] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172667] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out Apr 14 18:02:06 mark-linux kernel: [18500.172689] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out Apr 14 18:02:06 mark-linux kernel: [18500.172712] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY } Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: WRITE FPDMA QUEUED Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out Apr 14 18:02:06 mark-linux kernel: [18500.172735] res 40/00:01:00:4f:c2/00:00:00:00:00/00
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Kernel param set but still seeing the issue: Apr 15 10:08:58 mark-linux kernel: [3.467285] ata3.00: FORCE: horkage modified (noncq) Apr 15 10:08:58 mark-linux kernel: [3.467531] ata3.00: ATA-9: ST2000DX001-1CM164, CC43, max UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.467532] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (not used) Apr 15 10:08:58 mark-linux kernel: [3.500871] ata3.00: configured for UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.501102] scsi 2:0:0:0: Direct-Access ATA ST2000DX001-1CM1 CC43 PQ: 0 ANSI: 5 Apr 15 12:37:06 mark-linux kernel: [ 8937.088290] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 15 12:37:06 mark-linux kernel: [ 8937.088297] ata3.00: irq_stat 0x4001 Apr 15 12:37:06 mark-linux kernel: [ 8937.088302] ata3.00: failed command: READ DMA EXT Apr 15 12:37:06 mark-linux kernel: [ 8937.088311] ata3.00: cmd 25/00:08:16:af:10/00:00:30:00:00/e0 tag 18 dma 4096 in Apr 15 12:37:06 mark-linux kernel: [ 8937.088311] res 51/84:00:16:af:10/00:00:30:00:00/00 Emask 0x10 (ATA bus error) Apr 15 12:37:06 mark-linux kernel: [ 8937.088316] ata3.00: status: { DRDY ERR } Apr 15 12:37:06 mark-linux kernel: [ 8937.088319] ata3.00: error: { ICRC ABRT } Apr 15 12:37:06 mark-linux kernel: [ 8937.088324] ata3: hard resetting link Apr 15 12:37:07 mark-linux kernel: [ 8937.564284] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 15 12:37:07 mark-linux kernel: [ 8937.644128] ata3.00: configured for UDMA/133 Apr 15 12:37:07 mark-linux kernel: [ 8937.644282] ata3: EH complete Apr 15 13:42:24 mark-linux kernel: [12854.761799] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 15 13:42:24 mark-linux kernel: [12854.761814] ata3.00: failed command: WRITE DMA EXT Apr 15 13:42:24 mark-linux kernel: [12854.761830] ata3.00: cmd 35/00:b8:07:e0:58/00:00:71:00:00/e0 tag 15 dma 94208 out Apr 15 13:42:24 mark-linux kernel: [12854.761830] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 15 13:42:24 mark-linux kernel: [12854.761839] ata3.00: status: { DRDY } Apr 15 13:42:24 mark-linux kernel: [12854.761848] ata3: hard resetting link Apr 15 13:42:34 mark-linux kernel: [12864.762972] ata3: softreset failed (1st FIS failed) Apr 15 13:42:34 mark-linux kernel: [12864.762986] ata3: hard resetting link Apr 15 13:42:44 mark-linux kernel: [12874.762852] ata3: softreset failed (1st FIS failed) Apr 15 13:42:44 mark-linux kernel: [12874.762866] ata3: hard resetting link Apr 15 13:43:19 mark-linux kernel: [12909.763715] ata3: softreset failed (1st FIS failed) Apr 15 13:43:19 mark-linux kernel: [12909.763730] ata3: limiting SATA link speed to 3.0 Gbps Apr 15 13:43:19 mark-linux kernel: [12909.763734] ata3: hard resetting link Apr 15 13:43:24 mark-linux kernel: [12914.979066] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Apr 15 13:43:24 mark-linux kernel: [12914.979073] ata3.00: link online but device misclassified Apr 15 13:43:29 mark-linux kernel: [12920.031161] ata3.00: qc timeout (cmd 0xec) Apr 15 13:43:29 mark-linux kernel: [12920.031174] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Apr 15 13:43:29 mark-linux kernel: [12920.031178] ata3.00: revalidation failed (errno=-5) Apr 15 13:43:29 mark-linux kernel: [12920.031191] ata3: hard resetting link Apr 15 13:43:39 mark-linux kernel: [12930.031937] ata3: softreset failed (1st FIS failed) Apr 15 13:43:39 mark-linux kernel: [12930.031951] ata3: hard resetting link Apr 15 13:43:49 mark-linux kernel: [12940.032465] ata3: softreset failed (1st FIS failed) Apr 15 13:43:49 mark-linux kernel: [12940.032479] ata3: hard resetting link Apr 15 13:44:24 mark-linux kernel: [12975.033296] ata3: softreset failed (1st FIS failed) Apr 15 13:44:24 mark-linux kernel: [12975.033311] ata3: limiting SATA link speed to 1.5 Gbps Apr 15 13:44:24 mark-linux kernel: [12975.033315] ata3: hard resetting link Apr 15 13:44:29 mark-linux kernel: [12980.244430] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 15 13:44:29 mark-linux kernel: [12980.244437] ata3.00: link online but device misclassified Apr 15 13:44:40 mark-linux kernel: [12990.432579] ata3.00: qc timeout (cmd 0xec) Apr 15 13:44:40 mark-linux kernel: [12990.432591] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Apr 15 13:44:40 mark-linux kernel: [12990.432595] ata3.00: revalidation failed (errno=-5) Apr 15 13:44:40 mark-linux kernel: [12990.432610] ata3: hard resetting link Apr 15 13:44:50 mark-linux kernel: [13000.433388] ata3: softreset failed (1st FIS failed) Apr 15 13:44:50 mark-linux kernel: [13000.433402] ata3: hard resetting link Apr 15 13:45:00 mark-linux kernel: [13010.433808] ata3: softreset failed (1st FIS failed) Apr 15 13:45:00 mark-linux kernel: [13010.433823] ata3: hard resetting link Apr 15 13:45:11 mark-linux kernel: [13022.309318] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 15 13:45:12 mark-linux kernel: [13022.449662] ata3.00: configured
[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED
Kernel param set but still seeing the issue: Apr 15 10:08:58 mark-linux kernel: [3.467285] ata3.00: FORCE: horkage modified (noncq) Apr 15 10:08:58 mark-linux kernel: [3.467531] ata3.00: ATA-9: ST2000DX001-1CM164, CC43, max UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.467532] ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (not used) Apr 15 10:08:58 mark-linux kernel: [3.500871] ata3.00: configured for UDMA/133 Apr 15 10:08:58 mark-linux kernel: [3.501102] scsi 2:0:0:0: Direct-Access ATA ST2000DX001-1CM1 CC43 PQ: 0 ANSI: 5 Apr 15 12:37:06 mark-linux kernel: [ 8937.088290] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 15 12:37:06 mark-linux kernel: [ 8937.088297] ata3.00: irq_stat 0x4001 Apr 15 12:37:06 mark-linux kernel: [ 8937.088302] ata3.00: failed command: READ DMA EXT Apr 15 12:37:06 mark-linux kernel: [ 8937.088311] ata3.00: cmd 25/00:08:16:af:10/00:00:30:00:00/e0 tag 18 dma 4096 in Apr 15 12:37:06 mark-linux kernel: [ 8937.088311] res 51/84:00:16:af:10/00:00:30:00:00/00 Emask 0x10 (ATA bus error) Apr 15 12:37:06 mark-linux kernel: [ 8937.088316] ata3.00: status: { DRDY ERR } Apr 15 12:37:06 mark-linux kernel: [ 8937.088319] ata3.00: error: { ICRC ABRT } Apr 15 12:37:06 mark-linux kernel: [ 8937.088324] ata3: hard resetting link Apr 15 12:37:07 mark-linux kernel: [ 8937.564284] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 15 12:37:07 mark-linux kernel: [ 8937.644128] ata3.00: configured for UDMA/133 Apr 15 12:37:07 mark-linux kernel: [ 8937.644282] ata3: EH complete Apr 15 13:42:24 mark-linux kernel: [12854.761799] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 15 13:42:24 mark-linux kernel: [12854.761814] ata3.00: failed command: WRITE DMA EXT Apr 15 13:42:24 mark-linux kernel: [12854.761830] ata3.00: cmd 35/00:b8:07:e0:58/00:00:71:00:00/e0 tag 15 dma 94208 out Apr 15 13:42:24 mark-linux kernel: [12854.761830] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout) Apr 15 13:42:24 mark-linux kernel: [12854.761839] ata3.00: status: { DRDY } Apr 15 13:42:24 mark-linux kernel: [12854.761848] ata3: hard resetting link Apr 15 13:42:34 mark-linux kernel: [12864.762972] ata3: softreset failed (1st FIS failed) Apr 15 13:42:34 mark-linux kernel: [12864.762986] ata3: hard resetting link Apr 15 13:42:44 mark-linux kernel: [12874.762852] ata3: softreset failed (1st FIS failed) Apr 15 13:42:44 mark-linux kernel: [12874.762866] ata3: hard resetting link Apr 15 13:43:19 mark-linux kernel: [12909.763715] ata3: softreset failed (1st FIS failed) Apr 15 13:43:19 mark-linux kernel: [12909.763730] ata3: limiting SATA link speed to 3.0 Gbps Apr 15 13:43:19 mark-linux kernel: [12909.763734] ata3: hard resetting link Apr 15 13:43:24 mark-linux kernel: [12914.979066] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Apr 15 13:43:24 mark-linux kernel: [12914.979073] ata3.00: link online but device misclassified Apr 15 13:43:29 mark-linux kernel: [12920.031161] ata3.00: qc timeout (cmd 0xec) Apr 15 13:43:29 mark-linux kernel: [12920.031174] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Apr 15 13:43:29 mark-linux kernel: [12920.031178] ata3.00: revalidation failed (errno=-5) Apr 15 13:43:29 mark-linux kernel: [12920.031191] ata3: hard resetting link Apr 15 13:43:39 mark-linux kernel: [12930.031937] ata3: softreset failed (1st FIS failed) Apr 15 13:43:39 mark-linux kernel: [12930.031951] ata3: hard resetting link Apr 15 13:43:49 mark-linux kernel: [12940.032465] ata3: softreset failed (1st FIS failed) Apr 15 13:43:49 mark-linux kernel: [12940.032479] ata3: hard resetting link Apr 15 13:44:24 mark-linux kernel: [12975.033296] ata3: softreset failed (1st FIS failed) Apr 15 13:44:24 mark-linux kernel: [12975.033311] ata3: limiting SATA link speed to 1.5 Gbps Apr 15 13:44:24 mark-linux kernel: [12975.033315] ata3: hard resetting link Apr 15 13:44:29 mark-linux kernel: [12980.244430] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 15 13:44:29 mark-linux kernel: [12980.244437] ata3.00: link online but device misclassified Apr 15 13:44:40 mark-linux kernel: [12990.432579] ata3.00: qc timeout (cmd 0xec) Apr 15 13:44:40 mark-linux kernel: [12990.432591] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) Apr 15 13:44:40 mark-linux kernel: [12990.432595] ata3.00: revalidation failed (errno=-5) Apr 15 13:44:40 mark-linux kernel: [12990.432610] ata3: hard resetting link Apr 15 13:44:50 mark-linux kernel: [13000.433388] ata3: softreset failed (1st FIS failed) Apr 15 13:44:50 mark-linux kernel: [13000.433402] ata3: hard resetting link Apr 15 13:45:00 mark-linux kernel: [13010.433808] ata3: softreset failed (1st FIS failed) Apr 15 13:45:00 mark-linux kernel: [13010.433823] ata3: hard resetting link Apr 15 13:45:11 mark-linux kernel: [13022.309318] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 15 13:45:12 mark-linux kernel: [13022.449662] ata3.00: configured