Bug 150773 – gentoo-sources-2.6.18: VIA SATA (libata 2.0) problem

• Product: Gentoo Linux
• Status: VERIFIED UPSTREAM

[Description J.Taimr 2006-10-10 11:26:56 UTC]

hw: Abit AV8/AMD X2 4800 (Toledo), 2x 200 GB SATA disk. The SATA subsystem is vt6420 based.
After upgrade from 2.6.17-gentoo-r8 to 2.6.18 (both gentoo-sources) none of SATA hard disks is available anymore. No substantial change for new kernel, just make oldconfig, make menuconfig, make.
During the initialization libata subsytem complains:

libata version 2.00 loaded.
sata_via 0000:00:0f.0: version 2.0
ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 18
PCI: VIA IRQ fixup for 0000:00:0f.0, from 11 to 2
sata_via 0000:00:0f.0: routed to hard irq line 2
ata1: SATA max UDMA/133 cmd 0xE000 ctl 0xE102 bmdma 0xE400 irq 18
ata2: SATA max UDMA/133 cmd 0xE200 ctl 0xE302 bmdma 0xE408 irq 18
scsi0 : sata_via
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ATA: abnormal status 0xD8 on port 0xE007
scsi1 : sata_via
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: qc timeout (cmd 0xec)
ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ATA: abnormal status 0xD8 on port 0xE207

and none of SATA disks is available, the boot process ends with the kernel panic. Boot into 2.6.17-gentoo-r8 is still possible, there is none hw trouble (both disks passed smartmonctl long test repeatedly and without flaws or warnings or suspicious values). The same with/without acpi=off, noacpi or apic pameters.
As I found via Google in news, it could be because I have CDRW and DVD on IDE iface and there was at least once mentioned problem with the combination VIA SATA and VIA IDE. Anyhow, 2.6.18 kernel is so far unusable for me.

[Comment 1 Daniel Drake (RETIRED) 2006-10-11 17:47:45 UTC]

Please attach dmesg from 2.6.17

[Comment 2 J.Taimr 2006-10-12 08:45:23 UTC]

Created attachment 99441 [details]
dmesg after booting to 2.6.17-gentoo-r8

bzip2 compressed

[Comment 3 J.Taimr 2006-10-12 08:47:00 UTC]

Comment on attachment 99441 [details]
dmesg after booting to 2.6.17-gentoo-r8

Here it is. I hope, it will help, but I did not find anything spectacular in..

[Comment 4 Daniel Drake (RETIRED) 2006-10-12 09:02:34 UTC]

Never attach anything compressed to bugs. Make it easy for us to read it. Please reattach as plain text.

[Comment 5 J.Taimr 2006-10-12 10:53:50 UTC]

Created attachment 99454 [details]
2.6.17-gentoo-r8 dmesg log

sorry for sending of bzipped file. This is the same, but plain text.

[Comment 6 Daniel Drake (RETIRED) 2006-10-12 19:21:27 UTC]

Try booting 2.6.18 with the "acpi=off noapic" kernel parameters

[Comment 7 J.Taimr 2006-10-13 08:30:10 UTC]

(In reply to comment #6)
> Try booting 2.6.18 with the "acpi=off noapic" kernel parameters
> 

As you can find above (in my first post), I already tried
acpi=off, acpi, apic, apic=off, noapic and all combinations. Perhaps it was not clear enough from the text; but no variant helped, the SATA subsystem was never initialized properly, kernel panic happened always and it ended always with the message mentioned above. The combinations I tried include also recommended
acpi=off noapic
combination. The problem is somewhere else, not in ACPI/APIC.

[Comment 8 Daniel Drake (RETIRED) 2006-10-14 11:43:55 UTC]

OK. This looks very much like a current issue with IRQ routing but the logs suggest otherwise. Please try the latest development kernel, currently 2.6.19-rc2

[Comment 9 J.Taimr 2006-10-15 00:26:19 UTC]

(In reply to comment #8)
> OK. This looks very much like a current issue with IRQ routing but the logs
> suggest otherwise. Please try the latest development kernel, currently
> 2.6.19-rc2
> 
So, I tried. The situation is identical with vanilla-sources 2.6.19-rc2, the SATA system fails. Only the message is a little bit different:
PCI: VIA IRQ fixup for 0000:00:0f.0, from 11 to 2
sata_via 0000:00:0f.0: routed to hard irq line 2
ata1: SATA max UDMA/133 cmd 0xE000 ctl 0xE102 bmdma 0xE400 irq 18
ata2: SATA max UDMA/133 cmd 0xE200 ctl 0xE302 bmdma 0xE408 irq 18
scsi0 : sata_via
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1: SATA link up 1.5 Gbps (SStatus 113 SCATA: ontrol 300)
ATA: abnormal status 0xD8 on port 0xE007
ATA: abnormal status 0xD8 on port 0xE007
ATA: abnormal status 0xD8 on port 0xE007
ATA: abnormal status 0xD8 on port 0xE007
ATA: abnormal status 0xD8 on port 0xE007
ATA: abnormal status 0xD8 on port 0xE007
ata1: port is slow to respond, please be patient (status 0xd8)
ata1: port failed to respond (30 sec, status 0xd8)

then there is a second initialization attempt at ata1, with the same result (starting with the line ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)) and finally it goes via analogical failures on ata2; the last end is again kernel panic.

[Comment 10 J.Taimr 2006-10-15 00:29:01 UTC]

(In reply to comment #9)
Just one info more:
The same happened without any acpi/apic parameters, as like as with the
acpi=off noapic
line. I did not try another combinations of acpi/apic params.

[Comment 11 Daniel Drake (RETIRED) 2006-10-19 05:12:54 UTC]

Please attach lspci output

[Comment 12 Daniel Drake (RETIRED) 2006-10-19 05:13:12 UTC]

and lspci -n

[Comment 13 J.Taimr 2006-10-19 10:06:08 UTC]

Created attachment 100028 [details]
output of lspci

[Comment 14 J.Taimr 2006-10-19 10:06:38 UTC]

Created attachment 100029 [details]
Output of lspci -n

[Comment 15 J.Taimr 2006-10-19 10:07:35 UTC]

Created attachment 100030 [details]
output of lspci -v

just for a case - more verbose output of lspci

[Comment 16 Daniel Drake (RETIRED) 2006-10-19 19:31:56 UTC]

Nothing jumps out. Please report this as an upstream bug in 2.6.19-rc2 at http://bugzilla.kernel.org

Point out that it is a 2.6.18 regression, and post the new bug URL here. Thanks!

[Comment 17 J.Taimr 2006-10-21 05:37:01 UTC]

(In reply to comment #16)
> Nothing jumps out. Please report this as an upstream bug in 2.6.19-rc2 at
> http://bugzilla.kernel.org
> 
> Point out that it is a 2.6.18 regression, and post the new bug URL here.
> Thanks!
> 

Done. Very likely it is the same bug as: http://bugzilla.kernel.org/show_bug.cgi?id=7235

[Comment 18 Daniel Drake (RETIRED) 2006-10-23 17:05:32 UTC]

That bug is a different driver and is very unlikely to be related. Please file a new bug for your own issue.

[Comment 19 J.Taimr 2006-10-25 09:52:26 UTC]

(In reply to comment #18)
> That bug is a different driver and is very unlikely to be related. Please file
> a new bug for your own issue.
> 

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

[Comment 20 Daniel Drake (RETIRED) 2006-11-14 08:14:03 UTC]

Thanks, will keep an eye on that

[Comment 21 Daniel Drake (RETIRED) 2006-11-14 08:14:44 UTC]

.

[Comment 22 J.Taimr 2006-12-03 11:57:02 UTC]

After few weeks my situation remains unchanged; I tried new kernels
gentoo-sources-2.6.18-r1, gentoo-sources-2.6.18-r2, gentoo-sources-2.6.18-r3,
gentoo-sources-2.6.19 and gentoo-sources-2.6.19-r1. The symptoms are still the
same as I wrote above, none of my SATA disks is accessible after a boot attempt
with any of the kernels mentioned. (sent to bugzilla.kernel.org, bug #7415 as well).

[Comment 23 Daniel Drake (RETIRED) 2007-03-07 22:49:12 UTC]

Please reopen if this is not fixed in gentoo-sources-2.6.20-r1