ATA ACPI (was Re: Linux 2.6.24-rc4)

[Jeff Garzik <jeff@garzik.org>]

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)

ATA command:  DEVICE CONFIGURATION FREEZE LOCK

Prevents "accidental modification" of device configuration, after this 
command has been submitted.

Some BIOS writer probably thought that was a good idea, but maybe not 
for Linus.


> 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 also post dmidecode output?

And may I presume that booting with libata module option 'noacpi=1' 
fixes the problem?

We just turned on ATA ACPI support, which sends commands the BIOS has 
prepared for us to the device...  which is generally a good thing that 
makes suspend/resume and BIOS passwords work.  But it's also trusting a 
BIOS to get ATA commands right -- and it does not appear to, in your case.

	Jeff