I was hit by this bug on a Thinkpad T61p. Fortunately I have a copy of the eeprom from a previous ethtool dump, but the data is quite useless without some restore method.
Posted Oct 16, 2008 20:31 UTC (Thu) by proski (subscriber, #104)
[Link]
Did you have CONFIG_DYNAMIC_FTRACE enabled? That's really the first question we should be asking to make sure that we don't have other issues affecting e1000e hardware.
EEPROM restore utility?
Posted Oct 16, 2008 21:06 UTC (Thu) by kalbakk (guest, #54118)
[Link]
yeah, CONFIG_DYNAMIC_FTRACE was enabled.
It's even worse now. Stupid me, taking advice from some random guy on Ubuntu launchpad: "Try diagnostic with the Windows driver."
I ran the hardware diagnostic in the Windows driver. EEPROM verified ok, but 'register test' failed. Then the card died, now it doesn't even init on the PCI bus. lspci shows no sign of it. Guess I'll just return the damn laptop.
EEPROM restore utility?
Posted Oct 19, 2008 3:46 UTC (Sun) by sbergman27 (guest, #10767)
[Link]
"""
Then the card died, now it doesn't even init on the PCI bus. lspci shows no sign of it. Guess I'll just return the damn laptop.
"""
Think about that next time you complain about a problem and someone "responds" by asking you where you were when the project was asking for beta testers. Tell them just how dangerous testing can be. Good thing you were in warranty. Which brings up another question. The vendor likely sold the machine with an OS that did not destroy the hardware. What should their options be?
random advice :(
Posted Nov 20, 2008 21:36 UTC (Thu) by gvy (guest, #11981)
[Link]
Hope you're at least not going to listen anymore to win-advice of random guys on *shrug* launchpads...