Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 28 Mar 2003 17:03:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 28 Mar 2003 17:03:35 -0500 Received: from havoc.daloft.com ([64.213.145.173]:38312 "EHLO havoc.gtf.org") by vger.kernel.org with ESMTP id ; Fri, 28 Mar 2003 17:03:34 -0500 Date: Fri, 28 Mar 2003 17:14:46 -0500 From: Jeff Garzik To: Dave Jones , Linux Kernel Cc: davem@redhat.com Subject: Re: NICs trading places ? Message-ID: <20030328221446.GA1549@gtf.org> References: <20030328221037.GB25846@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030328221037.GB25846@suse.de> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 648 Lines: 21 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 ? That's a bug that no one has tracked down yet. Jamal reported it, too. ethX numbering shouldn't be changing without a good reason... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/