Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: 2.6.27 Kernel Killing Network Hardware

  1. #11
    Join Date
    Dec 2007
    Posts
    39

    Default

    How do I test to see what card I'm using so I don't encounter the problem when I update.

    Also, isn't Canonical's work around just getting rid of that driver?

    Also, would it be easier to just import the driver from a previous Kernel?

    Possible problems I can see:
    1. It not being compatible with the 2.6.27 kernel
    2. It's not the driver that's corrupting (which that is being talked about in the bug report)

    Thanks a lot.


    Bas.

  2. #12
    Join Date
    Sep 2006
    Location
    PL
    Posts
    906

    Default

    but it's also true that a user that's running 2.6.27rc must be at least a user that understands a minimum of "computer things" so he's able somehow to reflash it.
    anybody running -rc* kernels must be ready for anything, be it hardware failure, your pc killing your dog, or kernel devs kidnapping your girlfriend :]

    Also, would it be easier to just import the driver from a previous Kernel?
    i think this one will nail down the problem - http://lkml.org/lkml/2008/9/23/431 .

    the issue might lay deep within the kernel, and not the driver itself.

    remember how rtorrent exposed a deep bug in the kernel in 2.6.18 ?

  3. #13
    Join Date
    Sep 2006
    Posts
    353

    Default

    Quote Originally Posted by bulletxt View Post
    If something like this happens for example with an Ubuntu stable release, oh well, I couldn't blame if Microsoft pays some newspaper to FUD about it..lol
    What most likely happened is Microsoft paid a Linux kernel saboteur to have the kernel trash your LAN card.

    See: The Linux Kernel SABOTEURS at
    http://www.phoronix.com/forums/showthread.php?t=9509
    Last edited by Jade; 09-26-2008 at 07:04 PM.

  4. #14
    Join Date
    Mar 2008
    Posts
    569

    Default

    oh....I was just joking but it seems the thing is more serious than I thought... I'll read your link!

  5. #15
    Join Date
    Jul 2008
    Posts
    31

    Default

    Quote Originally Posted by bulletxt View Post
    oh....I was just joking but it seems the thing is more serious than I thought... I'll read your link!
    Being friends with one of the Intel linux devs, he told me that this issue is most likely related to core kernel changes rather than a bug with the actual driver. The nvram on the e1000* based cards are shared between the rest of the hardware components on the machine, as its a part of the address space. Anything can have a flaw that writes to the wrong address, such blame can be bugs in the kernel, a buggy X11 graphics driver writing to a bad memory address, or a combination of both could be the culprit here. From what I understand this is mainly happening with laptops, and no reported happenings with PCIe based server adapters yet.

  6. #16
    Join Date
    Aug 2007
    Posts
    6,598

    Default

    I know of one defect adapter on an asus q35 board. saidly the system locks when you try to load a patched driver (without crc check).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •