public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Clark <jclark@metricsystems.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Strange ethN numbering problem.
Date: Mon, 08 Jan 2007 16:28:15 -0800	[thread overview]
Message-ID: <45A2E19F.4070307@metricsystems.com> (raw)

On a system which has one Intel Ethernet 1 Gb interface, and 4 'Marvel', 
interfaces,
during kernel initialization the interfaces indicate they have 'normal' 
ethernet ethN names,
ie, eth0, eth1, eth2, eth3, eth4, eth5 are reported from the 'dmesg' output.

However, when the system comes up and attempt to do an ifconfig, the 
'ethN' numbers
have changed to a some what intermengled seriese starting with eth6... 
eth10.

I have never seen this sort of problem before, and so I have no clue 
what is causing
the later changes in the numbering scheme.

Does anyone have any idea where to look.

Thanks
John Clark


             reply	other threads:[~2007-01-09  0:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  0:28 John Clark [this message]
2007-01-09  1:15 ` Strange ethN numbering problem Bernd Eckenfels
2007-01-09  1:38   ` John Clark
2007-01-09  4:06     ` Andrey Borzenkov
2007-01-09 18:22       ` John Clark

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=45A2E19F.4070307@metricsystems.com \
    --to=jclark@metricsystems.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