From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753966AbYIYQJ0 (ORCPT ); Thu, 25 Sep 2008 12:09:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752794AbYIYQJQ (ORCPT ); Thu, 25 Sep 2008 12:09:16 -0400 Received: from outbound-mail-13.bluehost.com ([69.89.18.113]:60142 "HELO outbound-mail-13.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752747AbYIYQJP (ORCPT ); Thu, 25 Sep 2008 12:09:15 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-Identified-User; b=eOmC3dIxFhzECvRREegSh9mTouQl/ouVY4Q+ybUMgfe74OfKwHMfXnnVb6xp8yn0u49rWs5qmSJDNh7niJwFd4apZkxrk3GFbMFYw4WR4Hb0GnjCKGcreYbwdF5ysVNN; From: Jesse Barnes To: Jiri Kosina Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Date: Thu, 25 Sep 2008 09:08:36 -0700 User-Agent: KMail/1.9.9 Cc: David Miller , jeffrey.t.kirsher@intel.com, airlied@gmail.com, david.vrabel@csr.com, rjw@sisk.pl, linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org, chrisl@vmware.com, Ingo Molnar , jesse.brandeburg@intel.com, Karsten Keil References: <20080923.150722.141587696.davem@davemloft.net> <200809241726.58628.jbarnes@virtuousgeek.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809250908.37676.jbarnes@virtuousgeek.org> X-Identified-User: {642:box128.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 75.111.27.49 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, September 24, 2008 5:33 pm Jiri Kosina wrote: > On Wed, 24 Sep 2008, Jesse Barnes wrote: > > That said, adding a check to the x86 code would be a good thing to do; > > I'll hack up a patch tomorrow unless someone beats me to it. > > The problem here is that what we desperately need first is a method to > restore the original EEPROM contents after it gets corrupted (David Airlie > has, sadly, apparently bricked his notebook while trying to do so). > Without this, we can put a lot of debugging/protecting patches into the > kernel, but we won't be able to succesfully verify anything, because > testing wouldn't be possible. > > Added Jesse and Karsten to CC, as they are working on such a tool right > now, as far as I know. I should be able to test the mmap fix independently of the e1000 breakage at least... lemme try it out now... -- Jesse Barnes, Intel Open Source Technology Center