Ubuntu
linux package

failed command: READ FPDMA QUEUED

Bug #1682892 reported by xenus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

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 0x40000008
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) <F>
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 0x7fffffff 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 mark-linux kernel: [18500.172770] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172782] ata5.00: cmd 61/08:38:1f:aa:92/00:00:49:00:00/40 tag 7 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172782] 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.172788] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172793] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172805] ata5.00: cmd 61/08:40:5f:aa:92/00:00:49:00:00/40 tag 8 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172805] 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.172811] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172816] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172827] ata5.00: cmd 61/08:48:8f:ab:92/00:00:49:00:00/40 tag 9 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172827] 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.172833] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172838] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172850] ata5.00: cmd 61/08:50:af:b0:92/00:00:49:00:00/40 tag 10 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172850] 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.172856] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172862] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172873] ata5.00: cmd 61/08:58:2f:b6:92/00:00:49:00:00/40 tag 11 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172873] 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.172880] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172885] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172896] ata5.00: cmd 61/08:60:e7:b9:93/00:00:49:00:00/40 tag 12 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172896] 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.172903] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172908] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172919] ata5.00: cmd 61/08:68:57:8a:d2/00:00:57:00:00/40 tag 13 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172919] 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.172925] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172930] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172942] ata5.00: cmd 61/08:70:af:8b:d2/00:00:57:00:00/40 tag 14 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172942] 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.172948] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172953] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172965] ata5.00: cmd 61/08:78:df:8b:d2/00:00:57:00:00/40 tag 15 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172965] 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.172971] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172976] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.172987] ata5.00: cmd 61/08:80:07:8c:d2/00:00:57:00:00/40 tag 16 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.172987] 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.172994] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.172999] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173010] ata5.00: cmd 61/08:88:8f:8b:d3/00:00:57:00:00/40 tag 17 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173010] 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.173017] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173022] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173034] ata5.00: cmd 61/08:90:ef:89:92/00:00:5a:00:00/40 tag 18 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173034] 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.173040] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173045] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173056] ata5.00: cmd 61/08:98:8f:a9:13/00:00:62:00:00/40 tag 19 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173056] 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.173063] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173068] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173079] ata5.00: cmd 61/08:a0:d7:aa:13/00:00:62:00:00/40 tag 20 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173079] 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.173086] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173091] ata5.00: failed command: READ FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173102] ata5.00: cmd 60/08:a8:17:9f:13/00:00:62:00:00/40 tag 21 ncq dma 4096 in
Apr 14 18:02:06 mark-linux kernel: [18500.173102] res 40/00:01:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.173109] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173114] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173125] ata5.00: cmd 61/08:b0:ee:4f:26/00:00:2f:00:00/40 tag 22 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173125] 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.173131] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173136] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173148] ata5.00: cmd 61/08:b8:a6:ee:f8/00:00:2f:00:00/40 tag 23 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173148] 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.173154] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173159] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173171] ata5.00: cmd 61/08:c0:a6:ae:0e/00:00:30:00:00/40 tag 24 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173171] 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.173177] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173182] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173193] ata5.00: cmd 61/08:c8:e6:60:24/00:00:31:00:00/40 tag 25 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173193] res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 14 18:02:06 mark-linux kernel: [18500.173200] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173205] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173216] ata5.00: cmd 61/08:d0:f6:70:24/00:00:31:00:00/40 tag 26 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173216] 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.173222] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173227] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173239] ata5.00: cmd 61/40:d8:df:a9:ae/05:00:49:00:00/40 tag 27 ncq dma 688128 out
Apr 14 18:02:06 mark-linux kernel: [18500.173239] 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.173245] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173250] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173262] ata5.00: cmd 61/e8:e0:1f:af:ae/01:00:49:00:00/40 tag 28 ncq dma 249856 out
Apr 14 18:02:06 mark-linux kernel: [18500.173262] 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.173268] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173273] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173285] ata5.00: cmd 61/08:e8:77:d3:e2/00:00:49:00:00/40 tag 29 ncq dma 4096 out
Apr 14 18:02:06 mark-linux kernel: [18500.173285] 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.173291] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173296] ata5.00: failed command: WRITE FPDMA QUEUED
Apr 14 18:02:06 mark-linux kernel: [18500.173307] ata5.00: cmd 61/10:f0:97:d3:e2/00:00:49:00:00/40 tag 30 ncq dma 8192 out
Apr 14 18:02:06 mark-linux kernel: [18500.173307] 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.173314] ata5.00: status: { DRDY }
Apr 14 18:02:06 mark-linux kernel: [18500.173322] ata5: hard resetting link
Apr 14 18:02:16 mark-linux kernel: [18510.172727] ata5: softreset failed (1st FIS failed)
Apr 14 18:02:16 mark-linux kernel: [18510.172741] ata5: hard resetting link
Apr 14 18:02:26 mark-linux kernel: [18520.172910] ata5: softreset failed (1st FIS failed)
Apr 14 18:02:26 mark-linux kernel: [18520.172924] ata5: hard resetting link
Apr 14 18:03:01 mark-linux kernel: [18555.173890] ata5: softreset failed (1st FIS failed)
Apr 14 18:03:01 mark-linux kernel: [18555.173906] ata5: limiting SATA link speed to 3.0 Gbps
Apr 14 18:03:01 mark-linux kernel: [18555.173909] ata5: hard resetting link
Apr 14 18:03:07 mark-linux kernel: [18560.345099] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Apr 14 18:03:07 mark-linux kernel: [18560.345106] ata5.00: link online but device misclassified
Apr 14 18:03:12 mark-linux kernel: [18565.485164] ata5.00: qc timeout (cmd 0xec)
Apr 14 18:03:12 mark-linux kernel: [18565.485176] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Apr 14 18:03:12 mark-linux kernel: [18565.485180] ata5.00: revalidation failed (errno=-5)
Apr 14 18:03:12 mark-linux kernel: [18565.485193] ata5: hard resetting link
Apr 14 18:03:22 mark-linux kernel: [18575.485721] ata5: softreset failed (1st FIS failed)
Apr 14 18:03:22 mark-linux kernel: [18575.485735] ata5: hard resetting link
Apr 14 18:03:32 mark-linux kernel: [18585.486134] ata5: softreset failed (1st FIS failed)
Apr 14 18:03:32 mark-linux kernel: [18585.486148] ata5: hard resetting link
Apr 14 18:03:56 mark-linux kernel: [18609.517553] INFO: task jbd2/sda6-8:321 blocked for more than 120 seconds.
Apr 14 18:03:56 mark-linux kernel: [18609.517564] Tainted: P OE 4.8.0-46-generic #49-Ubuntu
Apr 14 18:03:56 mark-linux kernel: [18609.517569] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 14 18:03:56 mark-linux kernel: [18609.517574] jbd2/sda6-8 D ffff928adcfb7c98 0 321 2 0x00000000
Apr 14 18:03:56 mark-linux kernel: [18609.517584] ffff928adcfb7c98 00ffffffa32c0c37 ffff928ae6252880 ffff928add265e80
Apr 14 18:03:56 mark-linux kernel: [18609.517591] 0000000000000000 ffff928adcfb8000 ffff928adcfb7d88 ffff928adcfb7d70
Apr 14 18:03:56 mark-linux kernel: [18609.517597] ffff928ab9a88b00 ffffffffa32c7510 ffff928adcfb7cb0 ffffffffa3a9ad55
Apr 14 18:03:56 mark-linux kernel: [18609.517602] Call Trace:
Apr 14 18:03:56 mark-linux kernel: [18609.517616] [<ffffffffa32c7510>] ? wake_atomic_t_function+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517622] [<ffffffffa3a9ad55>] schedule+0x35/0x80
Apr 14 18:03:56 mark-linux kernel: [18609.517630] [<ffffffffa3518f8f>] jbd2_journal_commit_transaction+0x25f/0x17c0
Apr 14 18:03:56 mark-linux kernel: [18609.517637] [<ffffffffa32370e9>] ? sched_clock+0x9/0x10
Apr 14 18:03:56 mark-linux kernel: [18609.517643] [<ffffffffa32bd213>] ? put_prev_entity+0x33/0x3e0
Apr 14 18:03:56 mark-linux kernel: [18609.517648] [<ffffffffa32c7510>] ? wake_atomic_t_function+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517654] [<ffffffffa32ab0b1>] ? finish_task_switch+0x151/0x1f0
Apr 14 18:03:56 mark-linux kernel: [18609.517660] [<ffffffffa32f2e4a>] ? try_to_del_timer_sync+0x5a/0x80
Apr 14 18:03:56 mark-linux kernel: [18609.517665] [<ffffffffa351ec0a>] kjournald2+0xca/0x260
Apr 14 18:03:56 mark-linux kernel: [18609.517669] [<ffffffffa32c7510>] ? wake_atomic_t_function+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517673] [<ffffffffa351eb40>] ? commit_timeout+0x10/0x10
Apr 14 18:03:56 mark-linux kernel: [18609.517679] [<ffffffffa32a40d8>] kthread+0xd8/0xf0
Apr 14 18:03:56 mark-linux kernel: [18609.517686] [<ffffffffa3a9f75f>] ret_from_fork+0x1f/0x40
Apr 14 18:03:56 mark-linux kernel: [18609.517692] [<ffffffffa32a4000>] ? kthread_create_on_node+0x1e0/0x1e0
Apr 14 18:03:56 mark-linux kernel: [18609.517705] INFO: task jbd2/sda8-8:878 blocked for more than 120 seconds.
Apr 14 18:03:56 mark-linux kernel: [18609.517710] Tainted: P OE 4.8.0-46-generic #49-Ubuntu
Apr 14 18:03:56 mark-linux kernel: [18609.517714] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 14 18:03:56 mark-linux kernel: [18609.517718] jbd2/sda8-8 D ffff928adc64fa08 0 878 2 0x00000000
Apr 14 18:03:56 mark-linux kernel: [18609.517724] ffff928adc64fa08 00ff928adc5d1bb0 ffff928ae6252880 ffff928ae4a60000
Apr 14 18:03:56 mark-linux kernel: [18609.517731] 0000000000000046 ffff928adc650000 ffff928aefc59300 7fffffffffffffff
Apr 14 18:03:56 mark-linux kernel: [18609.517737] ffffffffa3a9b540 ffff928adc64fb60 ffff928adc64fa20 ffffffffa3a9ad55
Apr 14 18:03:56 mark-linux kernel: [18609.517742] Call Trace:
Apr 14 18:03:56 mark-linux kernel: [18609.517747] [<ffffffffa3a9b540>] ? bit_wait+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517752] [<ffffffffa3a9ad55>] schedule+0x35/0x80
Apr 14 18:03:56 mark-linux kernel: [18609.517758] [<ffffffffa3a9e52a>] schedule_timeout+0x22a/0x3f0
Apr 14 18:03:56 mark-linux kernel: [18609.517764] [<ffffffffa35fbdfc>] ? queue_unplugged+0x9c/0xa0
Apr 14 18:03:56 mark-linux kernel: [18609.517769] [<ffffffffa32fcb01>] ? ktime_get+0x41/0xb0
Apr 14 18:03:56 mark-linux kernel: [18609.517773] [<ffffffffa32fcb01>] ? ktime_get+0x41/0xb0
Apr 14 18:03:56 mark-linux kernel: [18609.517777] [<ffffffffa3a9b540>] ? bit_wait+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517782] [<ffffffffa3a9a544>] io_schedule_timeout+0xa4/0x110
Apr 14 18:03:56 mark-linux kernel: [18609.517787] [<ffffffffa3a9b55b>] bit_wait_io+0x1b/0x70
Apr 14 18:03:56 mark-linux kernel: [18609.517792] [<ffffffffa3a9b0f8>] __wait_on_bit+0x58/0x90
Apr 14 18:03:56 mark-linux kernel: [18609.517798] [<ffffffffa33a1281>] ? find_get_pages_tag+0x161/0x2e0
Apr 14 18:03:56 mark-linux kernel: [18609.517803] [<ffffffffa33a0367>] wait_on_page_bit+0xc7/0xe0
Apr 14 18:03:56 mark-linux kernel: [18609.517808] [<ffffffffa32c7550>] ? autoremove_wake_function+0x40/0x40
Apr 14 18:03:56 mark-linux kernel: [18609.517813] [<ffffffffa33a047f>] __filemap_fdatawait_range+0xff/0x170
Apr 14 18:03:56 mark-linux kernel: [18609.517820] [<ffffffffa35ff38d>] ? submit_bio+0x7d/0x150
Apr 14 18:03:56 mark-linux kernel: [18609.517825] [<ffffffffa3521d30>] ? jbd2_journal_write_metadata_buffer+0x2a0/0x430
Apr 14 18:03:56 mark-linux kernel: [18609.517831] [<ffffffffa3518910>] ? jbd2_journal_begin_ordered_truncate+0xb0/0xb0
Apr 14 18:03:56 mark-linux kernel: [18609.517836] [<ffffffffa33a0504>] filemap_fdatawait_range+0x14/0x30
Apr 14 18:03:56 mark-linux kernel: [18609.517840] [<ffffffffa33a0543>] filemap_fdatawait+0x23/0x30
Apr 14 18:03:56 mark-linux kernel: [18609.517846] [<ffffffffa3519460>] jbd2_journal_commit_transaction+0x730/0x17c0
Apr 14 18:03:56 mark-linux kernel: [18609.517852] [<ffffffffa32bd213>] ? put_prev_entity+0x33/0x3e0
Apr 14 18:03:56 mark-linux kernel: [18609.517857] [<ffffffffa32ab0b1>] ? finish_task_switch+0x151/0x1f0
Apr 14 18:03:56 mark-linux kernel: [18609.517863] [<ffffffffa32f2e4a>] ? try_to_del_timer_sync+0x5a/0x80
Apr 14 18:03:56 mark-linux kernel: [18609.517867] [<ffffffffa351ec0a>] kjournald2+0xca/0x260
Apr 14 18:03:56 mark-linux kernel: [18609.517871] [<ffffffffa32c7510>] ? wake_atomic_t_function+0x60/0x60
Apr 14 18:03:56 mark-linux kernel: [18609.517875] [<ffffffffa351eb40>] ? commit_timeout+0x10/0x10
Apr 14 18:03:56 mark-linux kernel: [18609.517880] [<ffffffffa32a40d8>] kthread+0xd8/0xf0
Apr 14 18:03:56 mark-linux kernel: [18609.517886] [<ffffffffa3a9f75f>] ret_from_fork+0x1f/0x40
Apr 14 18:03:56 mark-linux kernel: [18609.517892] [<ffffffffa32a4000>] ? kthread_create_on_node+0x1e0/0x1e0

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-46-generic 4.8.0-46.49
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: mark 3280 F.... pulseaudio
 /dev/snd/controlC2: mark 3280 F.... pulseaudio
 /dev/snd/controlC1: mark 3280 F.... pulseaudio
 /dev/snd/controlC0: mark 3280 F.... pulseaudio
CurrentDesktop: XFCE
Date: Fri Apr 14 18:55:32 2017
HibernationDevice: RESUME=UUID=3e34a9fd-33a3-4027-86ff-5151122c5379
InstallationDate: Installed on 2010-03-14 (2587 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=bf8502af-6555-4b4c-a93f-11ee7121da7d ro quiet nosplash
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-46-generic N/A
 linux-backports-modules-4.8.0-46-generic N/A
 linux-firmware 1.161.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2001
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A87TD/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd03/08/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A87TD/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
xenus (xenus) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
xenus (xenus) wrote :
Download full text (4.9 KiB)

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 0x40000001
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] ata...

Read more...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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
status: Confirmed → Incomplete
Revision history for this message
xenus (xenus) wrote :

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.

Revision history for this message
xenus (xenus) wrote :

Tried the kernel above, unfortunately dkms fails trying to add nvidia module so I can't get it running.
Attaching dkms log.

Revision history for this message
xenus (xenus) wrote :
Revision history for this message
xenus (xenus) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
xenus (xenus) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.