Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753820AbYJCVpW (ORCPT ); Fri, 3 Oct 2008 17:45:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753117AbYJCVpK (ORCPT ); Fri, 3 Oct 2008 17:45:10 -0400 Received: from styx.suse.cz ([82.119.242.94]:53898 "EHLO mail.suse.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752834AbYJCVpJ (ORCPT ); Fri, 3 Oct 2008 17:45:09 -0400 Date: Fri, 3 Oct 2008 23:45:07 +0200 (CEST) From: Jiri Kosina To: Jesse Barnes cc: David Miller , jesse.brandeburg@intel.com, linux-kernel@vger.kernel.org, linux-netdev@vger.kernel.org, kkeil@suse.de, agospoda@redhat.com, arjan@linux.intel.com, david.graham@intel.com, bruce.w.allan@intel.com, john.ronciak@intel.com, Thomas Gleixner , chris.jones@canonical.com, tim.gardner@intel.com, airlied@gmail.com, Olaf Kirch , Linus Torvalds Subject: Re: [RFC PATCH 02/12] On Tue, 23 Sep 2008, David Miller wrote: In-Reply-To: <200810031429.22598.jbarnes@virtuousgeek.org> Message-ID: References: <20080930030825.22950.18891.stgit@jbrandeb-bw.jf.intel.com> <200810021523.45884.jbarnes@virtuousgeek.org> <20081003.134634.240211201.davem@davemloft.net> <200810031429.22598.jbarnes@virtuousgeek.org> User-Agent: Alpine 1.10 (LNX 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1301 Lines: 36 On Fri, 3 Oct 2008, Jesse Barnes wrote: > Ok, thanks. You'll have to check Linus' tree for sanity though, he just > merged a variant on my patch for 2.6.27. See > b5ff7df3df9efab511244d5a299fce706c71af48 and yell if it broke something > for you. Karsten has been testing kernel with these three patches from the series applied: e1000e: reset swflag after resetting hardware e1000e: fix lockdep issues e1000e: debug contention on NVM SWFLAG This was done on a hardware which previously triggered the bug in just a few test iterations in quite a reliable way. Now, with these patches applied, the EEPROM corruption didn't happen after several tens of iterations. Please note, that the patch that disables the writes to EEPROM on hardware level was *not* involved in this testing. Therefore it currently seems that these three patches really address the race condition issue that was present in the e1000e driver. It is still not clear why the bug started triggering all of a sudden for so many people though. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/