kernel-2.6.23.1-30.fc8 problem with symbios scsi controllers.

Dave Jones davej at redhat.com
Wed Oct 31 14:08:35 UTC 2007


On Wed, Oct 24, 2007 at 06:14:36PM +0100, Howard Wilkinson wrote:

 > PCI quirk: region 0c00-0c3f claimed by PIIX4 ACPI
 > PCI quirk: region 0cc0-0ccf claimed by PIIX4 SMB
 > PIIX4 devres B PIO at 0ca2-0ca3
 > PIIX4 devres C PIO at 0ca0-0ca1
 > PCI: Searching for i450NX host bridges on 0000:00:10.0
 > ACPI: PCI Root Bridge [PCI1] (0000:01)
 > ACPI: Bus 0000:01 not present in PCI namespace
 > ACPI: PCI Interrupt Link [IT00] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT01] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT02] (IRQs 3 4 5 7 *10 11 12 14 15)
 > ACPI: PCI Interrupt Link [IT10] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT11] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT12] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT20] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT21] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT22] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT30] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT31] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT32] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT42] (IRQs 3 4 5 7 10 *11 12 14 15)
 > ACPI: PCI Interrupt Link [IT38] (IRQs 3 4 5 7 10 11 12 14 *15)
 > ACPI: PCI Interrupt Link [IT39] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT03] (IRQs 3 4 *5 7 10 11 12 14 15)
 > ACPI: PCI Interrupt Link [IT04] (IRQs 3 5 7 10 *11 15)
 > ACPI: PCI Interrupt Link [IT05] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT06] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT13] (IRQs 3 4 5 7 10 *11 12 14 15)
 > ACPI: PCI Interrupt Link [IT14] (IRQs 3 4 5 7 10 *11 12 14 15)
 > ACPI: PCI Interrupt Link [IT15] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT16] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT23] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT24] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT25] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT26] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT33] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT34] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT35] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT36] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled.
 > ACPI: PCI Interrupt Link [IT41] (IRQs 3 4 5 7 10 *11 12 14 15)
 > ACPI: PCI Interrupt Link [IT40] (IRQs 3 4 5 7 10 *11 12 14 15)

On the kernel that works, is anything in the above section different?

 > PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a 
 > report

Worth a shot.  Also give pci=noacpi a try if that still doesn't fix it.

 > ACPI: Unable to derive IRQ for device 0000:01:03.0
 > ACPI: PCI Interrupt 0000:01:03.0[A]: no GSI - using IRQ 11
 > sym0: <896> rev 0x1 at pci 0000:01:03.0 irq 11
 > sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
 > sym0: SCSI BUS has been reset.
 > scsi0 : sym-2.2.3
 > ACPI: Unable to derive IRQ for device 0000:01:03.1
 > ACPI: PCI Interrupt 0000:01:03.1[B]: no GSI - using IRQ 11
 > sym1: <896> rev 0x1 at pci 0000:01:03.1 irq 11
 > sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
 > sym1: SCSI BUS has been reset.
 > scsi1 : sym-2.2.3
 > ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 58 (level, low) -> IRQ 17
 > sym2: <810a> rev 0x23 at pci 0000:00:08.0 irq 17
 > sym2: No NVRAM, ID 7, Fast-10, SE, parity checking
 > sym2: SCSI BUS has been reset.

On the face of things, interrupt routing is screwed up somehow, and
everything goes south shortly after initialisation.
Give those boot params a try, and see if that helps any.
Sadly, this isn't going to get fixed in time for F8 now, so we're
in the "hope there are workarounds" area for this.

(Final big hammer to try if all else fails - acpi=off)

	Dave

-- 
http://www.codemonkey.org.uk




More information about the fedora-devel-list mailing list