Well it seems the patch only enables write protection but it does not really fix the root cause of the problem. Also it does not enable already defect chips to be recognized again.
http://git.kernel.org/?p=linux/kerne...c6ebbee3f9b3a7
Phoronix: Intel Provides Temporary e1000e Fix
In the Linux 2.6.27 kernel code was a rather serious regression where a faulty driver is killing Intel network hardware. Specifically the e1000 and e1000e network adapters were getting their EEPROM corrupted by the driver, which renders the network interface permanently inoperable unless that non-volatile memory can be restored...
http://www.phoronix.com/vr.php?view=Njc1OQ
Well it seems the patch only enables write protection but it does not really fix the root cause of the problem. Also it does not enable already defect chips to be recognized again.
http://git.kernel.org/?p=linux/kerne...c6ebbee3f9b3a7
good idea by the kernel developers!
they should start to randomly insert drivers that brick you hardware so the companies suddenly raise the funds to fix drivers... maybe that will help with the opensource ati driver development![]()
Last edited by Pfanne; 10-02-2008 at 10:26 AM.
Sad part is, if this had been a Mac or a AMD product the tech sites would have made this a world headline, but because it's a intel it's a mere footnote elsewhere.
Honestly, I don't understand why this bug made it past the very early stages of the release cycle. It seems like a bug of this severity should trigger a rollback to earlier code as soon as it is discovered. Something like this should never make it into a Linux kernel RC.
SO now that this bug came to light and is being investigated...that's a good thing, but who should be using RC kernels anyway?