Posted Oct 16, 2008 7:20 UTC (Thu) by khim (subscriber, #9252)
[Link]
Now instead of destroying hardware you'll see BUG() on your screen.
Hopefully it'll allow more testing and so eventually the root cause will be
found.
e1000e
Posted Oct 16, 2008 14:32 UTC (Thu) by corbet (editor, #1)
[Link]
I was talking with an Intel developer the other day. It appears that they have a good idea of where the problem comes from, but they are holding off on saying anything until they have nailed it exactly. There may be news on that front soon.
Meanwhile, a fair amount of defensive code has gone in to ensure that the bug, when it does trigger, will not trash hardware.