Linked by Thom Holwerda on Tue 23rd Sep 2008 20:36 UTC, submitted by AdamW
Linux I'm generally not very fond of reporting on security breaches or bugs, but OSNews reader and Mandriva employee Adam Williamson warned us of a pretty serious bug in pre-releases of the Linux kernel. "A major bug has been found in the e1000e module (which supports some Intel onboard ethernet adapters) in Linux kernel 2.6.27 pre-releases (up to and including 2.6.27rc7). It can cause the EEPROM of the adapter to become corrupted, rendering it non-functional. This may affect current pre-releases of distributions. Mandriva has posted a detailed notification about the issue, as has SUSE." So, watch out.
Order by: Score:

Sorry, couldn't resist...
by fretinator on Tue 23rd Sep 2008 21:01 UTC
fretinator
Member since:
2005-07-06

All your 1000-baseT are belong to us.

Tidbits
by sbergman27 on Tue 23rd Sep 2008 21:09 UTC
sbergman27
Member since:
2005-07-24

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.)

RE: Tidbits
by AdamW on Tue 23rd Sep 2008 23:05 UTC in reply to "Tidbits"
AdamW Member since:
2005-07-06

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? :>)

RE[2]: Tidbits
by Ethyriel on Wed 24th Sep 2008 02:55 UTC in reply to "RE: Tidbits"
Ethyriel Member since:
2005-07-07

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

RE[3]: Tidbits
by AdamW on Wed 24th Sep 2008 03:06 UTC in reply to "RE[2]: Tidbits"
AdamW Member since:
2005-07-06

Did you try just reflashing the BIOS? That should fix it.

RE[4]: Tidbits
by Ethyriel on Wed 24th Sep 2008 03:14 UTC in reply to "RE[3]: Tidbits"
Ethyriel Member since:
2005-07-07

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.

RE[5]: Tidbits
by Ethyriel on Wed 24th Sep 2008 03:48 UTC in reply to "RE[4]: Tidbits"
Ethyriel Member since:
2005-07-07

Yeah, that's not working for me.

RE[6]: Tidbits
by AdamW on Wed 24th Sep 2008 04:53 UTC in reply to "RE[5]: Tidbits"
AdamW Member since:
2005-07-06

Ah. That's a pain. :\

RE[3]: Tidbits
by wannabe geek on Thu 25th Sep 2008 00:14 UTC in reply to "RE[2]: Tidbits"
wannabe geek Member since:
2006-09-27

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?