On Tue, 4 Dec 2007, Maciej Rutecki wrote: > ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 220 > ata2: SATA max UDMA/133 abar m1024@0xe8585000 port 0xe8585180 irq 220 > ata3: SATA max UDMA/133 abar m1024@0xe8585000 port 0xe8585200 irq 220 > ata4: SATA max UDMA/133 abar m1024@0xe8585000 port 0xe8585280 irq 220 > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 failed (Emask=0x1 Stat=0x51 Err=0x04) > ata1: failed to recover some devices, retrying in 5 secs > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 failed (Emask=0x1 Stat=0x51 Err=0x04) > ata1.00: ACPI on devcfg failed the second time, disabling (errno=-5) > ata1.00: revalidation failed (errno=1) > ata1: failed to recover some devices, retrying in 5 secs > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata1.00: configured for UDMA/133 > > dmesg, lspci, hdparm: > http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/ Can you make a real bug report, which includes things like whether this ever worked without that timeout, and if so, when it last worked and what the dmesg was then? (Also, it's almost totally pointless to make me the primary To: target for something like this. Jeff Garzik hopefully picks this up from the linux-ide list, but I'm adding him to the Cc too) Linus - 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
