OSNews: http://www.osnews.com/story/20318/Major_Corruption_Bug_in_e1000e_Driver_in_Linux_Kernel_2_6_27 Exploring the Future of Computing en-us Copyright 2001-2009, David Adams adam+nospam@osnews.com Tue, 10 Nov 2009 06:39:44 GMT http://www.osnews.com/images/osnews.gif OSNews.com http://www.osnews.com Sorry, couldn't resist... http://osnews.com/thread?331191 http://osnews.com/thread?331191 All your 1000-baseT are belong to us. Tue, 23 Sep 2008 21:01:00 GMT donotreply@osnews.com (fretinator) Comments Tidbits http://osnews.com/thread?331194 http://osnews.com/thread?331194 I haven't RTFA, but I have been generally following the situation. Apparently, trying to use Intel's utility to fix it sometimes helps and sometimes makes it worse. I've heard that a bios flash does fix it. YMMV. Thank God my 1000baseT is a crappy low end one! (I'm running an affected kernel.) Tue, 23 Sep 2008 21:09:00 GMT donotreply@osnews.com (sbergman27) Comments RE: Tidbits http://osnews.com/thread?331206 http://osnews.com/thread?331206 Yes, as the MDV notification says, don't use ibautil.exe, it's really not a good idea. A BIOS flash apparently should usually fix it. If it doesn't, you should return to the manufacturer, unless you happened to take a backup of the good EEPROM data (we're all in the habit of backing up our EEPROMs, right? :>) Tue, 23 Sep 2008 23:05:00 GMT donotreply@osnews.com (AdamW) Comments RE[2]: Tidbits http://osnews.com/thread?331217 http://osnews.com/thread?331217 I'm going to be now. I got hit by this in an Ubuntu alpha, and just don't have time to RMA until school gets out for summer.

I think the big issue is how some distributors are responding this. Every ISO with this issue should be pulled immediately, and new ones posted with either a fix or the module removed, not just blacklisted. There's a debate about this in the Ubuntu bug report right now.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555 Wed, 24 Sep 2008 02:55:00 GMT donotreply@osnews.com (Ethyriel) Comments RE[3]: Tidbits http://osnews.com/thread?331218 http://osnews.com/thread?331218 Did you try just reflashing the BIOS? That should fix it. Wed, 24 Sep 2008 03:06:00 GMT donotreply@osnews.com (AdamW) Comments RE[4]: Tidbits http://osnews.com/thread?331219 http://osnews.com/thread?331219 I'm going to have to see about flashing with an old BIOS since I'm at the latest, and Lenovo's utility won't let me reflash the current version.

I've heard that a BIOS flash isn't working for everyone. Wed, 24 Sep 2008 03:14:00 GMT donotreply@osnews.com (Ethyriel) Comments RE[5]: Tidbits http://osnews.com/thread?331220 http://osnews.com/thread?331220 Yeah, that's not working for me. Wed, 24 Sep 2008 03:48:00 GMT donotreply@osnews.com (Ethyriel) Comments RE[6]: Tidbits http://osnews.com/thread?331226 http://osnews.com/thread?331226 Ah. That's a pain. :\ Wed, 24 Sep 2008 04:53:00 GMT donotreply@osnews.com (AdamW) Comments RE[3]: Tidbits http://osnews.com/thread?331359 http://osnews.com/thread?331359 Hmm, interesting :p


Jeffrey, we can't afford to do that; we need to be able to test with the Alpha CDs on the wide variety of hardware not affected by this bug, or our development schedules for 8.10 will be seriously compromised. However, I'd be happy to add a warning to the cdimage web pages. Can anyone suggest some text?
 Thu, 25 Sep 2008 00:14:00 GMT donotreply@osnews.com (wannabe geek) Comments