linux-kernel - Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48DAF75D.4050908@garzik.org>
Date:	Wed, 24 Sep 2008 22:28:45 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	Dave Airlie <airlied@...il.com>,
	David Miller <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	jeffrey.t.kirsher@...el.com, david.vrabel@....com, rjw@...k.pl,
	linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
	chrisl@...are.com, Ingo Molnar <mingo@...e.hu>,
	jbarnes@...tuousgeek.org, jesse.brandeburg@...il.com
Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

Jiri Kosina wrote:
> On Thu, 25 Sep 2008, Dave Airlie wrote:
> 
>> Well I'm out of the race, my attempts to re-write my eeprom using an 
>> eeprom from an equivalent laptop have totally failed and my BIOS won't 
>> boot anymore - so my laptop is == a brick.
> 
> Uh oh. Shouldn't we put something like the patch below in Linus' tree 
> unless we get this sorted out? Otherwise more and more people who use -rc 
> kernels will run into this, and will get their hardware [hopefully 
> temporarily, but not all users are able to re-flash their network card 
> EEPROMs, right] bricked.
> 
> I know that it is quite aggressive and is going to disable wired 
> networking on a lot of systems that have been functioning properly, 
> therefore RFC ...
> 
> 
> 
> From: Jiri Kosina <jkosina@...e.cz>
> Subject: [PATCH] [RFC] E1000E: temporarily disable e1000e driver
> 
> E1000E: temporarily disable e1000e driver

That seems a bit drastic, particularly when the debugging was beginning 
to point to another culprit.

We have equal case at this point to disable r8169 and i915_drm, no?

	Jeff




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