Comment 132 for bug 263555

Revision history for this message
Shwan (shwan-ciyako) wrote : Re: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk

Please ask in the forum not here

On Fri, Oct 3, 2008 at 9:29 AM, Daniel Kutik <email address hidden> wrote:
> How could I install this fix manually (not over the internet).
> At the time I've got no other connection as a wired. Is there a possibility to update the system via usb stick?
>
> --
> [intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
> https://bugs.launchpad.net/bugs/263555
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: In Progress
> Status in "linux" source package in Ubuntu: Fix Released
> Status in linux in Ubuntu Intrepid: Fix Released
> Status in "linux" source package in Fedora: Confirmed
> Status in "linux" source package in Gentoo Linux: Confirmed
> Status in "linux" source package in Mandriva: Confirmed
> Status in "linux" source package in Suse: In Progress
>
> Bug description:
> In some circumstances it appears possible for the 2.6.27-rc kernels to corrupt the NVRAM used by some Intel network parts to store data such as MAC addresses.
> This is limited to the new e1000e driver, and reports have only appeared from users of "82566 and 82567 based LAN parts (ich8 and ich9)" (to quote Intel). The reports seem to be isolated to laptops, but it is not clear if this is because desktop/server parts are not vulnerable, or if use cases simply increase the chances of laptop users being hit.
>
> Once this corruption has occurred, recovery may be possible via a BIOS update, but may well require replacement of the hardware. Use of Intel's IABUTIL.EXE is strongly discouraged, as it will worsen the problem to the point where the network part will no longer appear on the PCI bus.
>
> (this is a new description, the original one was based on too much guesswork. Below are the URLs originally referenced)
> (the driver i blacklisted in Ubuntu for 2.6.27-rc in the latest releases, so if your network is not working, it doesn't have to be damaged, but just disabled in order to prevent any accidents until this bug is solved, don't wary!)
> http://www.blahonga.org/~art/rant.html (search for "em0")
> http://<email address hidden>/msg00360.html
> http://<email address hidden>/msg00398.html
>