Comment 187 for bug 263555
Revision history for this message
| John (jsobernheim) wrote unsubscribe | #187 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
unsubscribe
-John
John B. Sobernheim
Microsel Of Colorado
7002 South Revere Parkway, Suite 90
Centennial, CO 80112
http://
Phn 720.488.9800 x213 or 800.381.1083
Fax 720.488.9885 Cel 720-317-7587
email:<email address hidden>
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Bug Watch Updater
Sent: Friday, October 24, 2008 8:51 AM
To: John B. Sobernheim
Subject: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8and ICH9 gigE chipsets at risk
** Changed in: linux (Gentoo Linux)
Status: Confirmed => Fix Released
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Status in The Linux Kernel: Fix Released
Status in “linux” source package in Ubuntu: Fix Released
Status in “linux-lpia” source package in Ubuntu: Fix Released
Status in linux in Ubuntu Intrepid: Fix Released
Status in linux-lpia in Ubuntu Intrepid: Fix Released
Status in “linux” source package in Fedora: Fix Released
Status in “linux” source package in Gentoo Linux: Fix Released
Status in “linux” source package in Mandriva: Fix Released
Status in “linux” source package in Suse: Fix Released
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://
http://<email address hidden>
http://<email address hidden>