From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0
Date: Tue, 5 Dec 2006 23:08:50 +0100
User-Agent: KMail/1.9.1
Cc: Andrew Morton <akpm@osdl.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       NetDev <netdev@vger.kernel.org>
References: <4575EDAB.6060305@intel.com>
In-Reply-To: <4575EDAB.6060305@intel.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612052308.51265.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 980
Lines: 29

On Tuesday, 5 December 2006 23:07, Auke Kok wrote:
> [resend]
> 
> Quick note: I loaded up 2.6.19-rc6-mm2 on a platform here and noticed that the onboard
> e1000 NIC was enumerated to eth1 instead of eth0. on 2.6.18.5 and any other kernel I
> used before, it was properly named eth0 after startup. eth0 itself is completely missing
> (-ENODEV).
> 
> I'll try to see if I can point out the culprit, but perhaps this rings a bell to anyone.

Please try to revert

gregkh-driver-driver-core-fixes-sysfs_create_link-retval-checks-in-core.c.patch

I had some similar problems that went away after I had reverted it.

Greetings,
Rafael


-- 
If you don't have the time to read,
you don't have the time or the tools to write.
		- Stephen King
-
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/