linux-kernel - Re: 2.6.18-rc3-mm2: bad e1000 device name

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 08 Aug 2006 08:26:53 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	NetDev <netdev@...r.kernel.org>
Subject: Re: 2.6.18-rc3-mm2: bad e1000 device name

Jeremy Fitzhardinge wrote:
> Arjan van de Ven wrote:
>> Jeremy Fitzhardinge wrote:
>>> Andrew Morton wrote:
>>>> e1000 seems OK here.  Don't know, sorry.
>>>>   
>>>
>>> It's happening to all my ethernet-like devices: the Atheros wireless 
>>> comes up as a mess too.  It's different each time, so it looks like 
>>> random uninitialized crud.
>>>
>>
>> is this the binary atheros driver? then please try without that.. 
> 
> It happens regardless of whether the atheros driver is loaded (or has 
> ever been loaded).  But it also happens to the atheros driver, so it 
> isn't specific to the e1000.
> 

and you're also sure this is not your userspace using interface renaming...
(could be an initscripts bug for name-by-MAC ethernet device naming)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/