[ltp] (fwd): Help for those who got their e1000 corrupted
umesh b
linux-thinkpad@linux-thinkpad.org
Sun, 19 Oct 2008 08:28:31 +0000
------=_Part_105714_9310574.1224404911813
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Fri, Oct 17, 2008 at 4:31 PM, Henrique de Moraes Holschuh <hmh@hmh.eng.br
> wrote:
> Since it DOES apply to some ThinkPads, and ThinkPad users are the sort of
> crowd who do run -rc kernels...
>
> The MAC is written in a label somewhere in the ThinkPad.
>
> The NVM copy and PCI ID information you can ask here from someone that has
> the same ThinkPad (remember: you have to supply also the full model number,
> and you should use an NVM from the closest machine you can. Don't use one
> from the X60s on the X60, or one from an old-model T60 with the new-model
> T60...).
>
> --
> "One disk to rule them all, One disk to find them. One disk to bring
> them all and in the darkness grind them. In the Land of Redmond
> where the shadows lie." -- The Silicon Valley Tarot
> Henrique Holschuh
>
>
> ---------- Forwarded message ----------
> From: Karsten Keil <kkeil@suse.de>
> To: linux-kernel@vger.kernel.org
> Date: Fri, 17 Oct 2008 15:59:10 +0200
> Subject: e1000e EEPROM corruption
> Hi,
>
> so after this ugly bug is finally fixed, here maybe left some victims of
> this bug.
>
> If here is still sombody who need help to recover from this issue,
>
> I can probably help him, I successful recovered all machines on our side,
> even one which do not longer show the NIC via lspci, so the only restiction
> is, that the machine still boots and we have a NVM image of a similar
> machine.
> You should know the PCI ids of the NIC from the time before it crashed and
> the MAC address.
>
> --
>
> Is the problem really solved? I could see one more mail in lkml regarding
this issue wih 2.6.27. Laptop was a R61.
http://lkml.org/lkml/2008/10/18/88
Regards
Umesh
------=_Part_105714_9310574.1224404911813
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Oct 17, 2008 at 4:31 PM, Henrique de Moraes Holschuh <span dir="ltr"><<a href="mailto:hmh@hmh.eng.br" target="_blank">hmh@hmh.eng.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Since it DOES apply to some ThinkPads, and ThinkPad users are the sort of<br>
crowd who do run -rc kernels...<br>
<br>
The MAC is written in a label somewhere in the ThinkPad.<br>
<br>
The NVM copy and PCI ID information you can ask here from someone that has<br>
the same ThinkPad (remember: you have to supply also the full model number,<br>
and you should use an NVM from the closest machine you can. Don't use one<br>
from the X60s on the X60, or one from an old-model T60 with the new-model<br>
T60...).<br>
<br>
--<br>
"One disk to rule them all, One disk to find them. One disk to bring<br>
them all and in the darkness grind them. In the Land of Redmond<br>
where the shadows lie." -- The Silicon Valley Tarot<br>
<font color="#888888"> Henrique Holschuh<br>
</font><br><br>---------- Forwarded message ----------<br>From: Karsten Keil <<a href="mailto:kkeil@suse.de" target="_blank">kkeil@suse.de</a>><br>To: <a href="mailto:linux-kernel@vger.kernel.org" target="_blank">linux-kernel@vger.kernel.org</a><br>
Date: Fri, 17 Oct 2008 15:59:10 +0200<br>Subject: e1000e EEPROM corruption<br>Hi,<br>
<br>
so after this ugly bug is finally fixed, here maybe left some victims of<br>
this bug.<br>
<br>
If here is still sombody who need help to recover from this issue,<br>
<br>
I can probably help him, I successful recovered all machines on our side,<br>
even one which do not longer show the NIC via lspci, so the only restiction<br>
is, that the machine still boots and we have a NVM image of a similar<br>
machine.<br>
You should know the PCI ids of the NIC from the time before it crashed and<br>
the MAC address.<br>
<br>
--<br>
<br></blockquote></div>Is the problem really solved? I could see one more mail in lkml regarding this issue wih <a href="http://2.6.27." target="_blank">2.6.27.</a> Laptop was a R61.<br><a href="http://lkml.org/lkml/2008/10/18/88">http://lkml.org/lkml/2008/10/18/88</a><br>
<br>Regards<br>Umesh<br></div>
------=_Part_105714_9310574.1224404911813--