i.MX6Q SATA sometimes (approx. every 240 minutes) fails due to a DMA error.
Here is the dmesg message:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 61/04:80:45:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
ata1.00: status: { DRDY DF ERR }
ata1.00: error: { ABRT }
ata1.00: configured for UDMA/133 (device error ignored)
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 61/04:80:45:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
ata1.00: status: { DRDY DF ERR }
ata1.00: error: { ABRT }
ata1.00: configured for UDMA/133 (device error ignored)
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 61/04:80:45:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
ata1.00: status: { DRDY DF ERR }
ata1.00: error: { ABRT }
ata1.00: configured for UDMA/133 (device error ignored)
sd 1:0:0:0: [sda]
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 1:0:0:0: [sda]
Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
00 00 00 45
sd 1:0:0:0: [sda]
Add. Sense: No additional sense information
sd 1:0:0:0: [sda] CDB:
Read(16): 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
end_request: I/O error, dev sda, sector 0
ata1: EH complete
and uname -a:
Linux homeserver 3.10.17 #3 SMP PREEMPT Sun Dec 25 11:38:32 CST 2016 armv7l armv7l armv7l GNU/Linux
So I wonder if anybody know this issue and how to fix it.
Thanks.
Hi Peter
new kernels fixed some sata errata like ERR009598, so recommended to try them.
Below link for nxp bsps with documentation
Best regards
igor
Are you able to run a more recent kernel, such as 4.1.15? Does the problem also happen with 4.1.15?