From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Karsten Keil <kkeil@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e1000e EEPROM corruption
Date: Sat, 18 Oct 2008 19:06:13 +0200 [thread overview]
Message-ID: <20081018190613.3d0ef384@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20081017135910.GA18206@pingi.kke.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Fri, 17 Oct 2008 15:59:10 +0200
Karsten Keil <kkeil@suse.de> wrote:
> 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.
>
I need some assistance here. Machine is a Thinkpad R61 and the device
has fallen off the bus. It used to be at 00:19.0:
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 03)
I can get my hands on a NVM image from an identical machine during the
week.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-18 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 13:59 Karsten Keil
2008-10-18 17:06 ` Pierre Ossman [this message]
2011-02-22 14:46 ` Maciej Kotliński
2011-02-22 18:06 ` Henrique de Moraes Holschuh
2011-02-22 19:59 ` Maciej Kotliński
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081018190613.3d0ef384@mjolnir.drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®