Messages in this thread |  | | | Date | Mon, 6 Sep 2010 15:35:02 -0400 | | From | Kyle McMartin <> | | Subject | libata acpi issue on gateway laptop |
| |
Hi Jeff,
A user is reporting an issue with 2.6.34.6 on a Gateway laptop that booting with libata.noacpi=1 resolves.
Symptom is that their device dumps a lot of messages like this:
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) ata1.00: ATA-8: Hitachi HTS545050B9A300, PB4OC60F, max UDMA/133 ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) ata1.00: configured for UDMA/133
on boot and resume from suspend.
Dmesg is at https://bugzilla.redhat.com/attachment.cgi?id=442529 and the full bug report at https://bugzilla.redhat.com/show_bug.cgi?id=629315.
Any ideas? They say the issue exists all the way back to 2.6.31, so it seems like a pretty long-lived bug.
Thanks! Kyle
|  |