Re: Linux 2.6.24-rc4

Re: Linux 2.6.24-rc4

[Maciej Rutecki]

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/


-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: Linux 2.6.24-rc4

[Linus Torvalds]

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

Re: Linux 2.6.24-rc4

[Maciej Rutecki]

2007/12/4, Linus Torvalds <torvalds@linux-foundation.org>:

> 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
>

Sorry for incomplete report.

Unfortunately, until Sunday I don't have any free time. But after I
will try find last good kernel and report it in bugzilla.


-- 
Maciej Rutecki
http://www.maciek.unixy.pl

ATA ACPI (was Re: Linux 2.6.24-rc4)

[Jeff Garzik]

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

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Jeff Garzik]

Jeff Garzik wrote:
> Some BIOS writer probably thought that was a good idea, but maybe not 
> for Linus.

er, s/Linus/Linux/

:)

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Alan Cox]

On Tue, 04 Dec 2007 16:25:07 -0500
Jeff Garzik <jeff@garzik.org> wrote:

> Jeff Garzik wrote:
> > Some BIOS writer probably thought that was a good idea, but maybe not 
> > for Linus.
> 
> er, s/Linus/Linux/

It probably is a good idea - if issued validly to supporting devices. It
stops attackers passwording your disk for amusement.

Is there a reason we give up when a command supplied by ACPI fails rather
than carrying on - which from the above is I assume what xp does ?

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Jeff Garzik]

Jeff Garzik wrote:
>> 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?


Third question -- this is just cosmetic, right?

According to the output above, error recovery succeeded and you continue 
booting and talking to your disk?

	Jeff

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Maciej Rutecki]

2007/12/4, Jeff Garzik <jeff@garzik.org>:
> Jeff Garzik wrote:
> >> 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?

http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmidecode.txt.gz

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

noacpi=1 kernel command line or module parameters?

First, no change:
http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmesg_noacpi.txt.gz
Kernel command line: root=/dev/sda2 ro vga=0x318 resume=/dev/sda3
selinux=1 enforcing=1  noacpi=1

How to add this option to module? Sorry I'm newbie ;-)

BTW My config:
http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/config-2.6.24-rc4

>
>
> Third question -- this is just cosmetic, right?

Linux works fine, but because of this message  I have about 10 seconds delay.

Unfortunately, until Sunday I don't have free time. Any suggestions I
can test on Sunday/Monday.
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Jeff Garzik]

Maciej Rutecki wrote:
> http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmidecode.txt.gz

Thanks.


>>> And may I presume that booting with libata module option 'noacpi=1'
>>> fixes the problem?
> 
> noacpi=1 kernel command line or module parameters?
> 
> First, no change:
> http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmesg_noacpi.txt.gz
> Kernel command line: root=/dev/sda2 ro vga=0x318 resume=/dev/sda3
> selinux=1 enforcing=1  noacpi=1


Yes, that's a module option.

_If_ libata is built into the kernel, and not a kernel module, then you 
can supply "libata.noacpi=1" on the kernel command line.  I don't think 
that works with modules.

With libata built as a module (libata.ko), you will probably need to 
edit /etc/modprobe.conf.

	Jeff

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Maciej Rutecki]

2007/12/5, Jeff Garzik <jeff@garzik.org>:

>
> _If_ libata is built into the kernel, and not a kernel module, then you
> can supply "libata.noacpi=1" on the kernel command line.  I don't think
> that works with modules.
>

With libata.noacpi=1"  kernel command line, errors has gone:
http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmesg_libata_noacpi.txt.gz

ahci 0000:00:1f.2: nr_ports (4) and implemented port map (0x1) don't
match, using nr_ports
ahci 0000:00:1f.2: forcing PORTS_IMPL to 0xf
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led clo pmp pio slum part
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
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: ATA-7: ST9120822AS, 3.ALC, max UDMA/133
ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link down (SStatus 0 SControl 0)
ata3: SATA link down (SStatus 0 SControl 0)
ata4: SATA link down (SStatus 0 SControl 0)
scsi 0:0:0:0: Direct-Access     ATA      ST9120822AS      3.AL PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: [sda] Attached SCSI disk

Thanks for help.
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: ATA ACPI (was Re: Linux 2.6.24-rc4)

[Tejun Heo]

Maciej Rutecki wrote:
> 2007/12/5, Jeff Garzik <jeff@garzik.org>:
> 
>> _If_ libata is built into the kernel, and not a kernel module, then you
>> can supply "libata.noacpi=1" on the kernel command line.  I don't think
>> that works with modules.

JFYI: fix for this and other ACPI issues is being tested.  Please take a
look at the following bug.

  http://bugzilla.kernel.org/show_bug.cgi?id=9320

-- 
tejun