okay, lets just use the data we *have* now. What we know is that some users have reported a corrupt NVM. Intel networking does not have a current reproduction but is *fully engaged* on trying to solve this problem. We have only had reports on 82566 and 82567 based machines, no others. Trying to extrapolate this out to "1 of 2" users is just fear mongering.
These kernels being released with this problem are still in alpha/beta, which means our testing audience is smaller, but so is the potential impact of any problem. The process is working as far as I can see, we have a set of users that is reporting the problem, which will help keep the kernels with the issue from being promoted to full production status. If you have some useful data to add to this bug, please comment, we're listening. I think the discussion about pulling alpha cds or whatever should go to some mailing list, and not be inside this bug. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of abingham Sent: Tuesday, September 23, 2008 9:55 AM To: Brandeburg, Jesse Subject: [Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8and ICH9 gigE chipsets at risk Intel has ~80% CPU market share and >=70% of the chipset market for their own CPU. So at least 56% of machines sold are Intel CPUs with Intel chipsets that are susceptible to this bug. 1 in 2 of Ubuntu testers could be vulnerable to this. -- [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: Confirmed Status in "linux" source package in Ubuntu: Triaged Status in linux in Ubuntu Intrepid: Triaged Status in "linux" source package in Fedora: Confirmed Status in "linux" source package in Suse: Incomplete 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) http://www.blahonga.org/~art/rant.html (search for "em0") http://www.mail-archive.com/[EMAIL PROTECTED]/msg00360.h tml http://www.mail-archive.com/[EMAIL PROTECTED]/msg00398.h tml -- [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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
