From mboxrd@z Thu Jan 1 00:00:00 1970 From: Krzysztof Halasa Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM Date: Thu, 25 Sep 2008 21:23:11 +0200 Message-ID: References: <20080923.150722.141587696.davem@davemloft.net> <9929d2390809231512w160d221axa2923a6b293a041@mail.gmail.com> <20080923.211215.193696086.davem@davemloft.net> <21d7e9970809241722w7c3bb6a5w1af5801b7380169d@mail.gmail.com> <21d7e9970809241722w7c3bb6a5w1af5801b7380169d@mail.gmail.com> <200809250401.54818.elendil@planet.nl> Mime-Version: 1.0 Return-path: In-Reply-To: (Jiri Kosina's message of "Thu\, 25 Sep 2008 19\:24\:57 +0200 \(CEST\)") Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jiri Kosina Cc: Frans Pop , airlied@gmail.com, Jeff Garzik , davem@davemloft.net, Andrew Morton , jeffrey.t.kirsher@intel.com, david.vrabel@csr.com, rjw@sisk.pl, linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org, chrisl@vmware.com, Ingo Molnar , jbarnes@virtuousgeek.org, jesse.brandeburg@gmail.com Jiri Kosina writes: > Still, what confuses me a little bit -- the EEPROM of the card is set to > all 0xff, once the corruption happens. Isn't that a quite a coincidence, > that bytes representing "nothing" in this context are used? Perhaps the entire chip has been erased with the "ERAL" (erase all) command. Requires previously issued EWEN (erase/write enable). Each command seems to require several writes to the EEPROM control register. -- Krzysztof Halasa