From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Date: Wed, 24 Sep 2008 22:28:45 -0400 Message-ID: <48DAF75D.4050908@garzik.org> References: <20080923.150722.141587696.davem@davemloft.net> <9929d2390809231512w160d221axa2923a6b293a041@mail.gmail.com> <20080923.211215.193696086.davem@davemloft.net> <21d7e9970809241722w7c3bb6a5w1af5801b7380169d@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Jiri Kosina Cc: Dave Airlie , David Miller , Andrew Morton , jeffrey.t.kirsher-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, david.vrabel-kQvG35nSl+M@public.gmane.org, rjw-KKrjLPT3xs0@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, chrisl-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org, Ingo Molnar , jbarnes-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org, jesse.brandeburg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 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 > 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