Skip to contentSkip to conversation

PCI bridge handling 2.4.0-test10 -> 2.4.2-pre3

DISCUSSION Jan-Benedict Glaw 4 participants 6 messages Feb 12, 2001 – Feb 13, 2001

lore
Share & tools
lore
#0 lore raw

Hi!

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID controller. The mainboard is ServerWorks based and however, 2.4.2-pre3 fails to find the RAID controller. I think there's a problem at scanning PCI busses behind PCI bridges. Here's the PCI bus layout as 2.4.0-test10 recognizes it:

-+-[01]-+-04.0 Adaptec 7899P

 |      +-04.1  Adaptec 7899P
 |      \-0a.0-[02]--+-08.0  Digital Equipment Corporation: Unknown device 1065
 |                   \-09.0  Mylex Corporation eXtremeRAID support Device
 \-[00]-+-00.0  Relience Computer CNB20HE
        +-00.1  Relience Computer CNB20HE
        +-02.0  ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC]
        +-03.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-06.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-07.0  Intel Corporation 82557 [Ethernet Pro 100]
        +-0f.0  Relience Computer: Unknown device 0200
        \-0f.1  Relience Computer: Unknown device 0211

Here's log output from both 2.4.0-test10 (successfully booting) and 2.4.2-pre3 (no success due to missing root fs):

----------------------- 2.4.0-test10 -----------------------
PCI: PCI BIOS revision 2.10 entry at 0xfdb3c, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ServerWorks host bridge: secondary bus 00
PCI: ServerWorks host bridge: secondary bus 01
PCI->APIC IRQ transform: (B1,I4,P0) -> 16
PCI->APIC IRQ transform: (B1,I4,P1) -> 17
PCI->APIC IRQ transform: (B2,I8,P0) -> 20
PCI->APIC IRQ transform: (B0,I2,P0) -> 19
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I6,P0) -> 26
PCI->APIC IRQ transform: (B0,I7,P0) -> 23
[...]
DAC960: ***** DAC960 RAID Driver Version 2.4.8 of 19 August 2000 *****
DAC960: Copyright 1998-2000 by Leonard N. Zubkoff <[email protected]> DAC960#0: Configuring Mylex DAC1164P PCI RAID Controller

DAC960#0:   Firmware Version: 5.07-0-79, Channels: 3, Memory Size: 16MB
DAC960#0:   PCI Bus: 2, Device: 8, Function: 0, I/O Address: Unassigned
DAC960#0:   PCI Address: 0xFB110000 mapped at 0xE0800000, IRQ Channel: 20
DAC960#0:   Controller Queue Depth: 128, Maximum Blocks per Command: 128
DAC960#0:   Driver Queue Depth: 127, Scatter/Gather Limit: 33 of 33 Segments
DAC960#0:   Stripe Size: 64KB, Segment Size: 8KB, BIOS Geometry: 255/63
DAC960#0:   SAF-TE Enclosure Management Enabled

----------------------- 2.4.2-pre3 -------------------------------
PCI: PCI BIOS revision 2.10 entry at 0xfdb3c, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ServerWorks host bridge: last bus ff
PCI->APIC IRQ transform: (B0,I2,P0) -> 19
PCI->APIC IRQ transform: (B0,I3,P0) -> 18
PCI->APIC IRQ transform: (B0,I6,P0) -> 26
PCI->APIC IRQ transform: (B0,I7,P0) -> 23

Can you give me some advice on how to hack those PCI bridges?

MfG, JBG

Signature · 4 lines
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <[email protected]> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
#1 lore raw
Quoted 5 lines · Jan-Benedict Glaw

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID controller. The mainboard is ServerWorks based and however, 2.4.2-pre3 fails to find the RAID controller. I think there's a problem at scanning PCI busses behind PCI bridges. Here's the PCI bus layout as 2.4.0-test10 recognizes it:

There's was a change in the PCI bus scan code in pre3.

Could you please apply the following patch to arch/i386/kernel/pci-pc.c (against 2.4.1-pre3) and tell us your results? The fixup functions do not seem to work right now so we'll trust the BIOS...

pci-pc.c Tue Feb 13 00:19:29 2001 renamed from pci-pc.c.orig Tue Feb 13 00:02:50 2001 +0 -3
@@ -953,9 +953,6 @@
 struct pci_fixup pcibios_fixups[] = {
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,    PCI_DEVICE_ID_INTEL_82451NX,    pci_fixup_i450nx },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_INTEL,    PCI_DEVICE_ID_INTEL_82454GX,    pci_fixup_i450gx },
-       { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_HE,           pci_fixup_serverworks },
-       { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_LE,           pci_fixup_serverworks },
-       { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SERVERWORKS,      PCI_DEVICE_ID_SERVERWORKS_CMIC_HE,      pci_fixup_serverworks },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_COMPAQ,   PCI_DEVICE_ID_COMPAQ_6010,      pci_fixup_compaq },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_UMC,      PCI_DEVICE_ID_UMC_UM8886BF,     pci_fixup_umc_ide },
        { PCI_FIXUP_HEADER,     PCI_VENDOR_ID_SI,       PCI_DEVICE_ID_SI_5513, pci_fixup_ide_trash },

Adam

Signature · 7 lines
Adam                 [email protected]
  Lackorzynski         http://a.home.dhs.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/
#2 lore raw
In reply to Jan-Benedict Glaw

On Tue, Feb 13, 2001 at 12:38:15AM +0100, Adam Lackorzynski wrote:

Hi Adam!

pci-pc.c Tue Feb 13 00:19:29 2001

Quoted 12 lines · Jan-Benedict Glaw
Quoted 5 lines

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID controller. The mainboard is ServerWorks based and however, 2.4.2-pre3 fails to find the RAID controller. I think there's a problem at scanning PCI busses behind PCI bridges. Here's the PCI bus layout as 2.4.0-test10 recognizes it:

There's was a change in the PCI bus scan code in pre3.

pci-pc.c Tue Feb 13 00:19:29 2001 renamed from pci-pc.c.orig Tue Feb 13 00:02:50 2001 +0 -0
@@ -953,9 +953,6 @@

[Removal of serverworks fixup routines]

That patch cured the problem; the box is up'n'running again. Thanks!

Is there somebody to work on specivic serverworks fixup routines or should this patch simply go into stock kernel (to not treat serverworks machines specifically)?

MfG, JBG

Signature · 4 lines
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <[email protected]> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
#3 lore raw
In reply to Jan-Benedict Glaw
Quoted 8 lines · Jan-Benedict Glaw
Quoted 7 lines · Adam Lackorzynski
Quoted 5 lines · Jan-Benedict Glaw

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID controller. The mainboard is ServerWorks based and however, 2.4.2-pre3 fails to find the RAID controller. I think there's a problem at scanning PCI busses behind PCI bridges. Here's the PCI bus layout as 2.4.0-test10 recognizes it:

Quoted 6 lines

pci-pc.c Tue Feb 13 00:19:29 2001

Quoted 3 lines
pci-pc.c Tue Feb 13 00:19:29 2001 renamed from pci-pc.c.orig Tue Feb 13 00:02:50 2001 +0 -0
@@ -953,9 +953,6 @@

[Removal of serverworks fixup routines]

That patch cured the problem; the box is up'n'running again. Thanks!

Ok, fine.

Since this patch works for Jan, Dan and me I'd suggest putting it into the kernel and thus removing the fixup routines (Anyone know the reason why they're there?).

Comments?!

Adam

Signature · 2 lines
Adam                 [email protected]
  Lackorzynski         http://a.home.dhs.org
#4 lore raw
In reply to Jan-Benedict Glaw

I believe that, in general, we want working fixup routines so the we don't have to rely on the BIOS. That said, it's apparent that the ServerWorks routines are broken. Fixing them is going to be troublesome, given ServerWorks attitude towards releasing specs. It's on my list of things to try to sort out, since some of the Netfinities I use are ServerWorks based.

Tim

Quoted 29 lines · Adam Lackorzynski
Quoted 8 lines · Jan-Benedict Glaw
Quoted 7 lines · Adam Lackorzynski
Quoted 5 lines · Jan-Benedict Glaw

I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID controller. The mainboard is ServerWorks based and however, 2.4.2-pre3 fails to find the RAID controller. I think there's a problem at scanning PCI busses behind PCI bridges. Here's the PCI bus layout as 2.4.0-test10 recognizes it:

Quoted 6 lines

pci-pc.c Tue Feb 13 00:19:29 2001

Quoted 3 lines
pci-pc.c Tue Feb 13 00:19:29 2001 renamed from pci-pc.c.orig Tue Feb 13 00:02:50 2001 +0 -0
@@ -953,9 +953,6 @@

[Removal of serverworks fixup routines]

That patch cured the problem; the box is up'n'running again. Thanks!

Ok, fine.

Since this patch works for Jan, Dan and me I'd suggest putting it into the kernel and thus removing the fixup routines (Anyone know the reason why they're there?).

Comments?!

Adam

Signature · 2 lines
Adam                 [email protected]
  Lackorzynski         http://a.home.dhs.org
Signature · 4 lines
Tim Wright - [email protected] or [email protected] or [email protected]
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
#5 lore raw
Quoted 5 lines · Tim Wright

I believe that, in general, we want working fixup routines so the we don't have to rely on the BIOS. That said, it's apparent that the ServerWorks routines are broken. Fixing them is going to be troublesome, given ServerWorks attitude towards releasing specs. It's on my list of things to try to sort out, since some of the Netfinities I use are ServerWorks based.

We can get tech info on ServerWorks... just ask specific questions, and hardware contacts etc. will do the rest.

Jeff