According to the original report, the driver provided by Intel used by LinuxKernel2.6.27-RC will damage the NVRAM (non-volatile random access memory) that Intel NICs use to store MAC address and other data ), specifically, the IntelICH8/9 south bridge chip uses 82566 and 82567 Gigabit Ethernet controllers, but only when using the new e1000e series drivers. For more information, see <G id = "1"> </G>.
According to the original report, the driver provided by Intel used by Linux Kernel 2.6.27-RC will damage the NVRAM (non-volatile random access memory) that Intel NICs use to store MAC address and other data ), specifically, the Intel ICH8/9 nanqiao chip uses 82566 and 82567 Gigabit Ethernet controllers, but only when using the new e1000e series drivers.
Related reading:If you use Ubuntu 8.10 Alpha, pay attention to your NicHttp://www.linuxidc.com/Linux/2008-09/16150.htm)
According to the latest official bug list, this problem is now fixed.
The original English text is as follows:
In some circumstances it appears possible for the 2.6.27-rc kernels to upload upt 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 happens uption 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 stronugly 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 !)