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

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.

I did a clean rebuild, but it still happens. I guess I'll have to try with some slab debugging and see if its an overrun or something.

   J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.18-rc3-mm2: bad e1000 device name
    • From: Arjan van de Ven <[email protected]>

• References:
  • 2.6.18-rc3-mm2: bad e1000 device name
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: 2.6.18-rc3-mm2: bad e1000 device name
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH] simplify update_times (avoid jiffies/jiffies_64 aliasing problem)
• Next by Date: [PATCH] i386: mark two more functions as __init
• Previous by thread: Re: 2.6.18-rc3-mm2: bad e1000 device name
• Next by thread: Re: 2.6.18-rc3-mm2: bad e1000 device name
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]