I created a Bugzilla entry at https://bugzilla.kernel.org/show_bug.cgi?id=34952 for your bug report, please add your address to the CC list in there, thanks! On poniedziaÅek, 9 maja 2011 o 22:48:01 Tino Keitel wrote: > Hi, > > I get a hanging SATA port for a few seconds during boot, with these > kernel messages: > > ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x40000 action 0x6 frozen > ata1.00: cmd 60/20:00:55:e1:65/00:00:00:00:00/40 tag 0 ncq 16384 in > res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata1.00: cmd 60/02:08:c1:5c:03/00:00:00:00:00/40 tag 1 ncq 1024 in > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata1: hard resetting link > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: both IDENTIFYs aborted, assuming NODEV > ata1.00: revalidation failed (errno=-2) > ata1: hard resetting link > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (unknown) succeeded > ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (unknown) filtered out > ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (unknown) succeeded > ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (unknown) filtered out > ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (unknown) succeeded > ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (unknown) filtered out > ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (unknown) succeeded > ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (unknown) filtered out > ata1.00: configured for UDMA/133 > ata1.00: device reported invalid CHS sector 0 > ata1.00: device reported invalid CHS sector 0 > ata1: EH complete > > This happens with 2.6.39-rc6 with TuxOnIce patch included, but during boot > without any suspend actions. The hardware is a ThinkPad X61s: > > 00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) > SATA AHCI Controller (rev 03) > > Complete dmesg is attached. > > Regards, > Tino -- Maciej Rutecki http://www.maciek.unixy.pl -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html