From: Andries Brouwer <aebr@win.tue.nl>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: jgarzik@pobox.com, aeb@cwi.nl
Subject: Re: NICs trading places ?
Date: Fri, 28 Mar 2003 23:48:43 +0100 [thread overview]
Message-ID: <20030328224843.GA11980@win.tue.nl> (raw)
In-Reply-To: <20030328221037.GB25846@suse.de>
On Fri, Mar 28, 2003 at 10:10:37PM +0000, Dave Jones wrote:
> I just upgraded a box with 2 NICs in it to 2.5.66, and found
> that what was eth0 in 2.4 is now eth1, and vice versa.
> Is this phenomenon intentional ? documented ?
> What caused it to do this ?
>
> The box in question has a DEC Tulip and a 3com 3c905,
> but I imagine this would affect any system with >1 NIC
> of different vendors/drivers ?
Intentional? No.
Documented? I suppose you can find complaints from others
mentioning the same thing.
Cause? eth discovery order is not well-defined.
Once or twice I have submitted patches to rectify.
They help for a while and then someone breaks things again.
I am not quite sure, apologies in case I misremember, but
maybe the most recent breakage was caused by Marc Zyngier
with EISA bus changes.
Google turns up
http://www.uwsg.iu.edu/hypermail/linux/kernel/0301.2/1139.html
Let me add the patch referred to there. Maybe Jeff likes it this time.
Andries
diff -u --recursive --new-file -X /linux/dontdiff a/drivers/net/3c59x.c b/drivers/net/3c59x.c
--- a/drivers/net/3c59x.c Sat Jan 18 23:54:39 2003
+++ b/drivers/net/3c59x.c Tue Jan 21 18:36:25 2003
@@ -1439,8 +1439,14 @@
acpi_set_WOL(dev);
}
retval = register_netdev(dev);
- if (retval == 0)
+ if (retval == 0) {
+ int i;
+ printk("%s: 3c59x, address", dev->name);
+ for (i = 0; i < 6; i++)
+ printk("%c%2.2x", i ? ':' : ' ', dev->dev_addr[i]);
+ printk("\n");
return 0;
+ }
free_ring:
pci_free_consistent(pdev,
next prev parent reply other threads:[~2003-03-28 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 22:10 Dave Jones
2003-03-28 22:14 ` Jeff Garzik
2003-03-28 22:15 ` jjs
2003-03-28 22:25 ` Joel Becker
2003-03-28 22:27 ` Randy.Dunlap
2003-03-28 22:34 ` Dave Jones
2003-03-28 22:48 ` Andries Brouwer [this message]
2003-03-28 23:02 ` Andrew Morton
2003-03-28 23:20 ` Andries Brouwer
2003-03-28 23:41 ` Greg KH
2003-03-28 23:56 ` Jeff Garzik
2003-03-29 0:03 ` Greg KH
2003-03-29 9:20 ` Marc Zyngier
2003-03-28 23:30 ` Dax Kelson
2003-03-28 23:42 ` Sean Neakums
[not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29 4:47 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030328224843.GA11980@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=aeb@cwi.nl \
--cc=davej@codemonkey.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®