linux-kernel - Re: FYI: e1000e: corruption, Lenovo/IBM are replacing my MB.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <48E54978.8040209@devnull.org>
Date:	Fri, 03 Oct 2008 00:21:44 +0200
From:	Niel Lambrechts <niel.lambrechts@...il.com>
To:	"linux.kernel" <linux-kernel@...r.kernel.org>
Subject: Re: FYI: e1000e: corruption, Lenovo/IBM are replacing my MB.

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/