netdev - Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200612052308.51265.rjw@sisk.pl>
Date:	Tue, 5 Dec 2006 23:08:50 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Auke Kok <auke-jan.h.kok@...el.com>
Cc:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: 2.6.19-rc6-mm2: Network device naming starts at 1 instead of 0

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 netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html