From: Niel Lambrechts <niel.lambrechts@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: FYI: e1000e: corruption, Lenovo/IBM are replacing my MB.
Date: Thu, 02 Oct 2008 23:47:57 +0200 [thread overview]
Message-ID: <48E5418D.3000307@devnull.org> (raw)
In-Reply-To: <biyi4-2jF-23@gated-at.bofh.it>
On 10/02/2008 05:30 PM, Lee.Mathers@tcafs.org wrote:
> Fyi, lenovo/ibm(Canada) are replacing the Motherboard on my T61 (6465-9TU)
> Intel®82566DC Gigabit Network Card. MAC ADDRR now read's FF:FF:FF:FF:FF:FF:FF:FF
>
> (wink) I did not advise them that it may have been caused by a hiccup/glitch in the Linux Kernel and/or the e1000e driver for said system.
I have not followed all of this too closely, and installed
linux-2.6.27-rc7-33 (OpenSUSE's KOTD) kernel in an attempt to get its
wireless card going. When I booted I briefly saw a NVRAM warning and my
laptop ended hanging on Firewall Initialization, without ever getting to
a login prompt.
I immediately remembered this bug, but strangely seem not to be
affected, since I could still use the card to connect to the internet
after rebooting in 2.6.26.
My laptop's a Lenovo W500 with a fairly similar card:
# lspci|grep -i ethernet
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network
Connection (rev 03)
My EEP shows
Offset Values
------ ------
0x0000 00 1c 25 95 93 ec 00 08 ff ff 83 10 ff ff ff ff
0x0010 08 10 ff ff c3 10 ee 20 aa 17 f5 10 86 80 00 00
0x0020 01 0d 00 00 00 00 05 86 20 30 00 0a 00 00 8b 8d
0x0030 02 06 40 2b 43 00 00 00 f5 10 ad ba f5 10 bf 10
0x0040 ad ba cb 10 ad ba ad ba 00 00 00 00 00 00 00 00
0x0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0060 00 01 00 40 18 13 07 40 ff ff ff ff ff ff ff ff
0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 33 cb
0x0080 20 60 1f 00 02 00 13 00 00 80 1d 00 ff 00 16 00
0x0090 dd cc 18 00 11 20 17 00 dd dd 18 00 12 20 17 00
0x00a0 00 80 1d 00 00 00 1f 00 ff ff ff ff ff ff ff ff
... all ff ...
0x0ff0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I hope it is still okay/valid!!?
Niel
next parent reply other threads:[~2008-10-02 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <biyi4-2jF-23@gated-at.bofh.it>
2008-10-02 21:47 ` Niel Lambrechts [this message]
2008-10-02 22:02 ` FYI: e1000e: corruption, Lenovo/IBM are replacing my MB Kok, Auke
[not found] <biEdH-1q1-15@gated-at.bofh.it>
[not found] ` <biEdH-1q1-13@gated-at.bofh.it>
[not found] ` <biEx3-1ZX-17@gated-at.bofh.it>
2008-10-02 22:21 ` Niel Lambrechts
2008-10-02 15:03 Lee.Mathers
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=48E5418D.3000307@devnull.org \
--to=niel.lambrechts@gmail.com \
--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