linux-kernel - e1000e NVM corruption issue status (updated 29-Sept-2008)

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]

Date:	Mon, 29 Sep 2008 11:22:38 -0700 (Pacific Daylight Time)
From:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To:	LKML <linux-kernel@...r.kernel.org>
cc:	Karsten Keil <kkeil@...e.de>, Jiri Kosina <jkosina@...e.cz>,
	chris.jones@...onical.com, tim.gardner@...onical.com,
	agospoda@...hat.com, arjan@...ux.jf.intel.com,
	"Graham, David" <david.graham@...el.com>,
	"Ronciak, John" <john.ronciak@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Allan, Bruce W" <bruce.w.allan@...el.com>
Subject: e1000e NVM corruption issue status (updated 29-Sept-2008)

Here is my latest information regarding this bug.

Problem: some users report that with many of the latest beta distros, 
during a reboot when e1000e loads it says "NVM checksum is not valid" and 
the driver fails to load.

updated hardware affected list:
laptops and desktops with 82566 or 82567 based LAN parts, which are 
machines with the ICH8, ICH9, ICH10R chipsets and a variety of processors. 
The machines I know of that have reported the issue include

Lenovo X300
HP 2510p
Intel DP35JO
Lenovo T61 (possibly)
Lenovo X61 (possibly)
Intel DG45ID

We received a system that had been corrupted and are doing forensics on it 
before we start running tries at a reproduction.

Many other systems are currently attempting reproduction here at Intel, 
but we don't have a solid repro here yet.

Novell's SuSE engineers report they have reproduced on at least one 
machine by repeatedly running the install of SuSE beta 1 through stage 2 
install, then rebooting.

Intel's current efforts include:
a) reproduction
b) patch set to prevent corruption of gigabit region in flash by setting 
   protection registers
c) patch to set_memory_ro our memory mapped flash configuration registers
d) debug patches for e1000e, including loading the driver even if 
   checksum fails.
e) patch to allow e1000e to restore the nvm's gigabit region from a 
   previously saved image.

Bandaiding over this image with patches b) c) *might* prevent any more 
corruptions but won't probably find the bug.

Also of note, a patch was posted from Tim Gardner to iounmap the BAR1 of 
e1000e devices when it is not in use but we believe that patch to be 
functionally the same (but not as useful) as the patch c) above.

Jesse
--
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/