Thanks...I was just going to post that the rt kernel works.
Code:~$ uname -a Linux tikal 2.6.26-1-rt #1 SMP PREEMPT RT Fri Aug 29 12:39:10 UTC 2008 x86_64 GNU/Linux ~$ dpkg -l | grep 2.6.26 ii linux-headers-2.6.26-1-rt 2.6.26-1.15 Linux kernel headers for version 2.6.26 on Ingo Molnar' ii linux-headers-rt 126.96.36.199.5 Rt Linux kernel headers ii linux-image-2.6.26-1-rt 2.6.26-1.15 Linux kernel image for version 2.6.26 on Ingo Molnar's
If it because of the bug, it means that your ethernet firmware reads:
ff ff ff ff ff ff
And nothing will make that work again, aside from possibly a BIOS reflash, although that has mixed results: working vs bricking
AMD Athlon 3000 @2.0Ghz / MSI K8T Neo K8T800 / 2 GB Corsair DDR RAM / Nvidia GeForce 6600GT (256MB) / Samsung 226BW @ 1600x1050 / 120GB/320GB PATA.
Scruffy, just blacklisting.
According to the posts on LKML intel is working on a utility that will allow reflashing of eeproms.
Guys, i think you need to reword the title of this thread, i read this as a bug causing corruption of network traffic on these cards & not as a possible eeprom getting flushed.
I would replace corruption with bricking in the subject line.
The information on how to know if you're affected seems to be incomplete.
My eth0 info is:
Am I affected or does the "driver" field actually spell "e1000e" on those cards?Code:driver: e100 version: 3.5.23-k4-NAPI firmware-version: N/A bus-info: 0000:08:08.0
Thanks for the detailed helps.
I have kernel 2.6.27-2, am I affected? I dont currently use this card, so there is no way for me to know. I've just backup the eeprom, and it reads like this:
Code:0x0000 00 17 31 52 3f d0 30 0b 46 f7 57 00 ff ff ff ff 0x0010 ff ff ff ff 6b 02 c2 81 43 10 9a 10 86 80 df 80 0x0020 00 00 00 20 54 7e 00 00 14 00 da 00 04 00 00 27 0x0030 c9 6c 50 31 32 07 0b 04 84 29 00 00 00 f0 06 07 0x0040 08 10 00 00 04 0f ff 7f 01 4d ff ff ff ff ff ff 0x0050 14 00 1d 00 14 00 1d 00 af aa 1e 00 00 00 1d 00 0x0060 00 01 00 40 1c 12 07 40 ff ff ff ff ff ff ff ff 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 7f 1d
2.6.27-2 boots and runs with ethernet working, for me. 2.6.27-4 has the module blacklisted -- no networking.
Intel Core i7-950 / Asus P6X58D-E / Nvidia GTX480 / siduction 64-bit on OCZ Revodrive SSD / KDE4.10.2/ Kubuntu 13.04