Re: 2.4.29-pre1 OOPS early in boot with Intel ICH5 SATA controller
From: Alan J. Wylie
Date: Fri Dec 10 2004 - 11:13:20 EST
On Thu, 9 Dec 2004 09:49:33 +0000, "Alan J. Wylie" <alan@xxxxxxxxxxx> said:
> See also: <http://lkml.org/lkml/2004/12/3/68>
> With 2.4.27 patched with
> <http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.4/2.4.27-rc3-libata1.patch.bz2>
> the system works. I have not been able to make it work with any
> later 2.4 kernel
> Motherboard: Supermicro X6DA8-G2
Changing the BIOS settings from the default:
With BIOS setting "Native Mode Operation: [Auto]"
to:
With BIOS setting "Native Mode Operation: [Both]"
results in the system working OK with the later kernel.
There is still an issue, however with trying to use two drives and
software RAID. With both drives, or with one drive pulled, the system
boots OK. If the other drive (Channel 3 Master) is pulled, however,
the system fails to boot, after producing the following error messages
- both 2.4.29-pre1-bk5 and 2.6.9 kernels produce very similar messages.
With BIOS setting "Native Mode Operation: [Both]"
ACPI:PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 18
ata1: SATA max UDMA/133 cmd 0x1C00 ctl 0x18F6 bmdma 0x18E0 irq 18
ata2: SATA max UDMA/133 cmd 0x18F8 ctl 0x18F2 bmdma 0x18E8 irq 18
ata1: SATA port has no device.
scsi0: ata_piix
ATA abnormal status 0x7F on port 0x18FF
scsi1: ata_piix
With BIOS setting "Native Mode Operation: [Auto]"
ACPI:PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 18
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x18E0 irq 14
ata1: SATA port has no device.
scsi0: ata_piix
Using anticpatory io scheduler
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x18E8 irq 15
ata2: SATA port has no device.
scsi1: ata_piix
--
Alan J. Wylie http://www.wylie.me.uk/
"Perfection [in design] is achieved not when there is nothing left to add,
but rather when there is nothing left to take away."
-- Antoine de Saint-Exupery
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/