As a "Christmas present", I got a few (5) 21164LX 533MHz machines. After
getting RedHat 5.0 installed, I started experimenting with the 2.1.x
kernels (in order to get DU 4.0B binary support).
2.1.75 compiled fine (except for the millions of "__r16 uninitialized"
warnings). After bootup with the new kernel, I discovered that the
networking was not functional (could not ping anything but machine's own
ip). On closer inspection I noticed that the IRQ detected for the network
card was not the same as that detected under the 2.0.x kernels. The
networking in the 2.0.x kernels functions correctly.
Next I downloaded the 2.1.76 kernel & compiled/installed. About 30 seconds
after bootup had completed, the system spontaneously rebooted. These
reboots are reproducable. In order to isolate the problem, I build a
kernel without the network driver and stress tested that. No further
reboots or funnies.
Has anyone else encounter similar PCI probe failures with 2.1.x kernels?
Can any kernel guru give me a hint on where to start the hunt to fix this
problem? My guess would be arch/alpha/kernel/bios32.c? The comments
however mention bios emulation code. How do I know if my system is using
emulation code or not?
Here are relevant /proc/pci extracts:
For 2.0.33:
Bus 1, device 2, function 0:
Ethernet controller: DEC DC21140 (rev 34).
Medium devsel. Fast back-to-back capable. IRQ 30. Master Capable.
Latency=32. Min Gnt=20.Max Lat=40.
I/O at 0xb000.
Non-prefetchable 32 bit memory at 0xb000000.
For 2.1.76:
Bus 1, device 2, function 0:
Ethernet controller: DEC DC21140 (rev 34).
Medium devsel. Fast back-to-back capable. IRQ 28. Master Capable.
Latency=32. Min Gnt=20.Max Lat=40.
I/O at 0xd000 [0xb001].
Non-prefetchable 32 bit memory at 0x3000000 [0xb000000].
Thanks & regards.
-- Hans Grobler <grobh@sun.ac.za> Department Electrical & Electronic Engineering University of Stellenbosch, South Africa