I tested using the kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-trusty/
I'm still getting the same errors in dmesg, triggered by running apt-get
upgrade:
[ 329.070415] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x40000 action 0x6
frozen
[ 329.070423] ata3: SError: { CommWake }
[ 329.070427] ata3.00: failed command: WRITE FPDMA QUEUED
[ 329.070434] ata3.00: cmd 61/08:00:f7:9b:32/00:00:0a:00:00/40 tag 0 ncq 4096
out
[ 329.070434] res 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4
(timeout)
[ 329.070438] ata3.00: status: { DRDY }
[ 329.070443] ata3: hard resetting link
[ 329.612086] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 329.613207] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 329.613212] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK)
filtered out
[ 329.613432] ata3.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 329.613437] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered
out
[ 329.615920] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 329.615927] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK)
filtered out
[ 329.616115] ata3.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 329.616122] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered
out
[ 329.617303] ata3.00: configured for UDMA/100
[ 329.617542] ata3.00: device reported invalid CHS sector 0
[ 329.617551] ata3: EH complete
[ 428.128137] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x6
frozen
[ 428.128149] ata3: SError: { PHYRdyChg CommWake }
[ 428.128152] ata3.00: failed command: FLUSH CACHE
[ 428.128158] ata3.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 428.128158] res 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4
(timeout)
[ 428.128161] ata3.00: status: { DRDY }
[ 428.128166] ata3: hard resetting link
[ 428.448135] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 428.449256] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 428.449261] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK)
filtered out
[ 428.449482] ata3.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 428.449486] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered
out
[ 428.451921] ata3.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 428.451927] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK)
filtered out
[ 428.452129] ata3.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) succeeded
[ 428.452135] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered
out
[ 428.453325] ata3.00: configured for UDMA/100
[ 428.453329] ata3.00: retrying FLUSH 0xe7 Emask 0x4
[ 428.453613] ata3.00: device reported invalid CHS sector 0
[ 428.453621] ata3: EH complete
** Tags added: kernel-bug-exists-upstream-v3.12
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993507
Title:
ATA errors when link_power_management_policy is min_power
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/993507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
