Examining the log, looks like the error start with ata hard reset
Feb 27 22:53:04 armada1 kernel: [ 1162.849379] ata1.00: exception Emask 0x0
SAct 0x1 SErr 0x0 action 0x6
Feb 27 22:53:04 armada1 kernel: [ 1162.855846] ata1.00: edma_err_cause=02000084
pp_flags=00000003, dev error, EDMA self-disable
Feb 27 22:53:04 armada1 kernel: [ 1162.864342] ata1.00: failed command: READ
FPDMA QUEUED
Feb 27 22:53:04 armada1 kernel: [ 1162.869527] ata1.00: cmd
60/08:00:98:22:34/00:00:11:00:00/40 tag 0 ncq 4096 in
Feb 27 22:53:04 armada1 kernel: [ 1162.869527] res
41/40:00:98:22:34/00:00:11:00:00/40 Emask 0x409 (media error) <F>
Feb 27 22:53:04 armada1 kernel: [ 1162.885061] ata1.00: status: { DRDY ERR }
Feb 27 22:53:04 armada1 kernel: [ 1162.889092] ata1.00: error: { UNC }
Feb 27 22:53:04 armada1 kernel: [ 1162.892623] ata1: hard resetting link
Feb 27 22:53:05 armada1 kernel: [ 1163.399289] ata1: SATA link up 3.0 Gbps
(SStatus 123 SControl F300)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133586
Title:
linux-armadaxp: 3.5.0-1610.14 -proposed tracker
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1133586/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
