From: Niel Lambrechts <niel.lambrechts@gmail.com>
To: "linux.kernel" <linux-kernel@vger.kernel.org>
Subject: Re: FYI: e1000e: corruption, Lenovo/IBM are replacing my MB.
Date: Fri, 03 Oct 2008 00:21:44 +0200 [thread overview]
Message-ID: <48E54978.8040209@devnull.org> (raw)
In-Reply-To: <biEx3-1ZX-17@gated-at.bofh.it>
On 10/03/2008 12:10 AM, Kok, Auke wrote:
> your mac address certainly still looks ok, and from quickly browsing this eeprom
> content certainly looks valid. (most eeproms indeed END in all 0xff bytes).
Thanks for clarifying that, I suspected it to be the case, but wanted
confirmation since it is a new company laptop :O
The first thing I did was to reboot in 2.6.25 and verify the ethernet -
it was fully functional via DHCP.
Also to me, the MAC address seems fine:
linux-7vph:/ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:1C:25:95:93:EC
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Memory:fc200000-fc220000
(Right now, I'm using iwlagn, not ethernet)
> does the e1000e driver still load? do you get 'bad eeprom checksum' errors on boot?
Well it loads fine now, but this is after I have switched back to 2.6.26.5.
Too scared to try 2.6.27 again, but I definitely saw a boot message in
an asterisk surrounded block that said something about NVRAM checksum(?)...
>From some of the earlier posts I read that this bug surfaced on s2ram /
s2disk, not sure if there are other corruption "triggers".
Regards,
Niel
next parent reply other threads:[~2008-10-02 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] <biyi4-2jF-23@gated-at.bofh.it>
2008-10-02 21:47 ` FYI: e1000e: corruption, Lenovo/IBM are replacing my MB Niel Lambrechts
2008-10-02 22:02 ` Kok, Auke
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=48E54978.8040209@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