Bug 188840 – gentoo-sources-2.6.21-r4 - sata_sil issues with ASUS A7N8X-Deluxe

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Andrea Truccone 2007-08-14 14:42:42 UTC]

I have an ASUS A7N8X-Deluxe mobo, with a SATA hd, with kernel 2.6.14-gentoo-r4 I had no problem during boot:

ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [LNK3] -> GSI 11 (level, low) ->
IRQ 11
ata1: SATA max UDMA/100 cmd 0xE0A74080 ctl 0xE0A7408A bmdma 0xE0A74000 irq 11
ata2: SATA max UDMA/100 cmd 0xE0A740C0 ctl 0xE0A740CA bmdma 0xE0A74008 irq 11
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 160086528 sectors:
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: Maxtor 6Y080M0    Rev: YAR5
  Type:   Direct-Access                      ANSI SCSI revision: 05
st: Version 20050830, fixed bufsize 32768, s/g segs 256
SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 160086528 512-byte hdwr sectors (81964 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0

Trying to upgrade to kernel 2.6.21-gentoo-r4 I have the following message during boot:

ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 17
ata1: SATA max UDMA/100 cmd 0xe0814080 ctl 0xe081408a bmdma 0xe0814000 irq 17
ata2: SATA max UDMA/100 cmd 0xe08140c0 ctl 0xe08140ca bmdma 0xe0814008 irq 17
scsi0: sata_sil
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: ATA-7: Maxtor 6Y080M0, YAR51BW0, max UDMA/100
ata1.00: 160086528 sectors, multi 16, LBA
ata1.00: configured for UDMA/100
scsi1: sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y080M0 YAR5 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache, enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache, enabled, doesn't support DPO or FUA
  sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached SCSI generic sg0 type 0

Going through dmesg (using Busybox shell) I have the following messages:

ata1: hard resetting port
ata1: COMRESET failed (device not ready)
ata1: hardreset failed, retrying in 5 secs
ata1: hard resetting port
ata1: COMRESET failed (device not ready)
ata1: hardreset failed, retrying in 5 secs
ata1: hard resetting port
ata1: COMRESET failed (device not ready)
ata1: reset failed, giving up
ata1.00: disabled
ata1: EH completed

following by more errors like this:

sd 0:0:0:0: SCSI error: return code 0x00040000

Obviously I'm not able to boot, since my root partition is on the SATA hd and I received the following message:

mounting /dev/sda3 on /newroot failed: Invalid argument

I'm still using the old 2.6.16 kernel, that works without trouble. I'm not an expert, but I feal strange that kernel 2.6.16 used irq 11 while 2.6.21 is trying to use irq 17. What happened from the introduction of new SATA management?

Thank you very much,

Andrea



Reproducible: Always

[Comment 1 Jakub Moc (RETIRED) 2007-08-14 14:45:12 UTC]

Well, this MB has completely FUBARed BIOS, not really surprised you get issues with this.

[Comment 2 Andrea Truccone 2007-08-14 14:45:30 UTC]

Created attachment 128076 [details]
Kernel config file

I attached also my kernel configuration file, thanks.

[Comment 3 Mike Pagano 2007-08-16 01:10:41 UTC]

Can you test with the latest gentoo-sources which as of this writing is 2.6.22-r3.

If this fails, can you please test with the latest development kernel; vanilla-sources-2.6.23_rc3.

Jakub's concerns are warranted regarding the history of this motherboard as a quick search of the linux kernel mailing list does reveal past issues.

[Comment 4 Andrea Truccone 2007-08-16 10:02:27 UTC]

Created attachment 128248 [details]
This is my new kernel 2.6.22 configuration file

Thanks for your very fast answer!

I'm trying gentoo-sources 2.6.22-gentoo-r2 (not r3 just because I want to keep with unmasked release), I started over with menuconfig (using genkernel 3.4.8) and now I'm able to boot and mount my SATA hd. I have to understand where the trick is, since the output messages seem the same of the not-working 2.6.21 version, I guess it's a configuration issue:

sata_sil 0000:01:0b.0: version 2.2
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:0b.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 17
scsi0 : sata_sil
scsi1 : sata_sil
ata1: SATA max UDMA/100 cmd 0xe0814080 ctl 0xe081408a bmdma 0xe0814000 irq 17
ata2: SATA max UDMA/100 cmd 0xe08140c0 ctl 0xe08140ca bmdma 0xe0814008 irq 17
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: ATA-7: Maxtor 6Y080M0, YAR51BW0, max UDMA/133
ata1.00: 160086528 sectors, multi 16: LBA
ata1.00: configured for UDMA/100
ata2: SATA link down (SStatus 0 SControl 310)
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6Y080M0   YAR5 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 160086528 512-byte hardware sectors (81964 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] 160086528 512-byte hardware sectors (81964 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
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0

(this didn't work on the 2.6.21 kernel)
ata1: hard resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete

I'll keep testing this configuration (I want to move my system to 2.6.22 kernel), maybe the issue is not related to sata_sil driver, but to ACPI management or something around it (more likely in configuration setup).

Thanks, Andrea

[Comment 5 Mike Pagano 2007-08-28 15:24:42 UTC]

I'm going to close this as it is suspected that the problem might have been caused by a possible configuration issue.

Please reopen if you continue to have problems with the latest stable gentoo-sources kernel.