public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: linux-kernel@vger.kernel.org, Matt_Domsch@dell.com
Subject: Re: [Bug ??] 2.6.18-rc6-mm2 - PCI ethernet board does not seem to work
Date: Fri, 15 Sep 2006 03:29:54 -0700	[thread overview]
Message-ID: <20060915102954.GA7014@suse.de> (raw)
In-Reply-To: <450A7EC5.2090909@bull.net>

On Fri, Sep 15, 2006 at 12:21:57PM +0200, Pierre Peiffer wrote:
> Hi,
> 
> My Ethernet board (Intel(R) PRO/1000) "doesn't seems" to work any more
> with this kernel, but all is ok with kernel 2.6.18-rc6-mm1.
> 
> A bisection search show this patch:
> gregkh-pci-pci-sort-device-lists-breadth-first.patch
> as being the faulty one...
> 
> But after reading the content of this patch, I understood that the order
> of the ethernet boards had changed. In fact,  I have four ethernet
> boards and now, my eth0 does not point on the same card...
> So all is now ok by changing my cable to the right board.
> 
> But is this really the expected behavior ?

Yes.  You should use a persistent name for your network devices to
prevent this from happening.

That being said, I think we need to reverse the order of this patch,
keeping the current scheme as default, and allowing it to be overridden
on the command line for those few machines where it matters to be
compatible with the old, 2.4 ordering scheme.

Matt, care to rework the patch in this manner?

thanks,

greg k-h

  reply	other threads:[~2006-09-15 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 10:21 [Bug ??] 2.6.18-rc6-mm2 - PCI ethernet board does not seem to work Pierre Peiffer
2006-09-15 10:29 ` Greg KH [this message]
2006-09-15 21:43   ` Matt Domsch
2006-09-15 12:59 ` Matt Domsch
2006-09-15 13:28   ` Pierre Peiffer

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=20060915102954.GA7014@suse.de \
    --to=gregkh@suse.de \
    --cc=Matt_Domsch@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.peiffer@bull.net \
    /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