E100 PCI bridge problem

Does the machine #3 have a PCI slot connected to a "secondary" bus?
Have you tried with any other machine with a secondary bus?

Could be a hardware/BIOS problem on machines #1 and #2. Could be
a Linux bug as well, though similar configurations are known to work
fine. I don't think it has anything to do with IRQs.

Perhaps it doesn't like a bridge (on the card) behind a bridge
(on the motherboard). I would test with another multiport card
such as old DLink DFE-570TX (using a DEC 21150 bridge and four
21143 Ethernet chips).

I'd probably use some PCI analyzer or, at least, I'd check
the bus state with a multimeter.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at #
Please read the FAQ at #

No. This is a Pentium 4 - single core, 2.8GHz.

Not sure how windows applies here; I only use Linux. The main data
point so far is that the card works fine when on the primary PCI bus but
locks up hard after a few minutes when installed in a slot behind a PCI
to PCI bridge. I can provide the dmesg info on Monday.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at #
Please read the FAQ at #

are you running any form of irqbalance, either in-kernel (bad) or the userspace
(better) one?

irq routing in linux may not be the same as in windows. I have no idea how to
compare them either (dmesg will show the linux setup, but I don't know how to
retreive this info under linux).

I personally have no idea and am not knowledgeable enough on this issue, sorry :)

Auke

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at #
Please read the FAQ at #

Thanks for responding. I am very interested to find the source of this
problem.

The strange thing is that all the ports on the card work fine for a few
minutes, then when some condition (as yet unknown) occurs the system
locks up hard. I am currently using a PCI bus analyzer to capture bus
activity just prior to the lockup to try and find out what leads up to
this condition.

I am aware of the bridge chip on the card but not sure what you mean
when you say this explains the issues? I sure would like to figure out
a way around this.

The PCI info follows:
00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
Controller/Host-Hub Interface (rev 03)
00:02.0 VGA compatible controller: Intel Corp.
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to
PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corp. 82801DB (ICH4) LPC Bridge (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801DB (ICH4) Ultra ATA 100
Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev 02)
01:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (CNR)
Ethernet Controller (rev 82)
01:0c.0 PCI bridge: Pericom Semiconductor: Unknown device 8150 (rev 02)
02:06.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge
(non-transparent mode) (rev 15)
03:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
03:05.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
03:06.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
03:07.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)

I will look into that on Monday and report what I find. It seems like
it is premature to say how much effort the fix will take since the
problem is not yet known? At least not known to me yet. I would just
like to find out what parameters on the bridge/bridges might affect this
problem and how to modify them.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at #
Please read the FAQ at #

sounds like int-A/B/C/D routing issues

this issue might be resolvable by quirking the bridgee chips and adjusting any
APIC where needed. Unfortunately I don't know much about this but it's
physically not possible from the e100 driver. The special (non-intel) card that
has these 4 ports onboard contains a bridge chip itself which explains the
issues. Even a BIOS issue could be the cause here.

Perhaps the linuxfirmwarekit will reveal more information. In any case, fixing
this in software would be a gigantic effort.

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at #
Please read the FAQ at #