From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Newall Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Date: Wed, 24 Sep 2008 15:32:23 +0930 Message-ID: <48D9D7EF.9030604@davidnewall.com> References: <20080922.185902.80812984.davem@davemloft.net> <21d7e9970809231403wf766660u39908aca70548ca7@mail.gmail.com> <20080923.150559.34795136.davem@davemloft.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080923.150559.34795136.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: David Miller Cc: airlied@gmail.com, jkosina@suse.cz, david.vrabel@csr.com, rjw@sisk.pl, linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org, chrisl@vmware.com David Miller wrote: > Right now we don't have any real leads, so data acquisition is really > important at this phase. Isn't this reliably reproducible? Assuming yes, Intel are such swell guys that you might ask them to ship a few dozen cards to you to break until you've tracked down the problem. I mean, it's a lot easier to find this sorts of fault when you can see it first hand than trying to guess from third parties' reports, isn't it? For some reasonable value of "you", that so.