I've seen this symptom in the past with updated tulip and eepro drivers.
Basically, it appears that it detects the same card more than once. In
the case of the below dmesg output - the machine has 1 tulip based card,
and 1 Adaptec Quartet64. The eth[5-8] are bogus.
In the past, if I remember correctly, so long as I didn't do anything to
the bogus interfaces, stuff was fine, but it's a little disturbing.
Note - I've added the module directly to the kernel (added the .o files
in the drivers/net/Makefile, and the pci_scan/kern_compat stuff etc.)
Any ideas on how I can correct this symptom?
Moving to 2.4.1 isn't an option just yet, although I am considering it
as I'm deploying new machines.
-- Nathan
eth0: Digital DS21143-xD Tulip rev 65 at 0xe000, 00:C0:F0:6B:61:BC, IRQ
5.
eth0: EEPROM default media type Autosense.
eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3)
block.
eth0: MII transceiver #1 config 1000 status 782d advertising 01e1.
tulip.c:v0.92t 1/15/2001 Written by Donald Becker <[email protected]>
http://www.scyld.com/network/tulip.html
eth1: Adaptec Starfire 6915 at 0xd0000000, 00:00:d1:ee:77:71, IRQ 11.
eth1: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth2: Adaptec Starfire 6915 at 0xd0081000, 00:00:d1:ee:77:72, IRQ 9.
eth2: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth3: Adaptec Starfire 6915 at 0xd0102000, 00:00:d1:ee:77:73, IRQ 10.
eth3: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth4: Adaptec Starfire 6915 at 0xd0183000, 00:00:d1:ee:77:74, IRQ 5.
eth4: MII PHY found at address 1, status 0x7809 advertising 01e1.
starfire.c:v1.03 7/26/2000 Written by Donald Becker <[email protected]>
Updates and info at http://www.scyld.com/network/starfire.html
eth5: Adaptec Starfire 6915 at 0xd0204000, 00:00:d1:ee:77:71, IRQ 11.
eth5: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth6: Adaptec Starfire 6915 at 0xd0285000, 00:00:d1:ee:77:72, IRQ 9.
eth6: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth7: Adaptec Starfire 6915 at 0xd0306000, 00:00:d1:ee:77:73, IRQ 10.
eth7: MII PHY found at address 1, status 0x7809 advertising 01e1.
early initialization of device eth8 is deferred
eth8: Adaptec Starfire 6915 at 0xd0387000, 00:00:d1:ee:77:74, IRQ 5.
eth8: MII PHY found at address 1, status 0x7809 advertising 01e1.
starfire.c:v1.03 7/26/2000 Written by Donald Becker <[email protected]>
------------------------------------------------------------
Nathan Neulinger EMail: [email protected]
University of Missouri - Rolla Phone: (573) 341-4841
CIS - Systems Programming Fax: (573) 341-4216
On Sat, 10 Feb 2001 16:46:01 -0600, Nathan Neulinger <[email protected]> wrote:
> Any ideas on how I can correct this symptom?
This seems to be Donald Becker's driver, right? Please try with the
starfire driver for 2.2.x I posted a few hours ago to the list. If you
don't have it, contact me privately and I'll resend it to you.
Becker's PCI detection code is known to have, well, "issues".
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
> Basically, it appears that it detects the same card more than once. In
> the case of the below dmesg output - the machine has 1 tulip based card,
> and 1 Adaptec Quartet64. The eth[5-8] are bogus.
The Don Becker drivers have had this bug for ages and ages now, long after
it has been reported it has not been fixed.
I think you'll have to hack on that yourself