From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754182AbYI3WIS (ORCPT ); Tue, 30 Sep 2008 18:08:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753318AbYI3WIH (ORCPT ); Tue, 30 Sep 2008 18:08:07 -0400 Received: from www.tglx.de ([62.245.132.106]:35197 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753301AbYI3WIG (ORCPT ); Tue, 30 Sep 2008 18:08:06 -0400 Date: Wed, 1 Oct 2008 00:07:51 +0200 (CEST) From: Thomas Gleixner To: "Brandeburg, Jesse" cc: Linus Torvalds , Jiri Kosina , Linux Kernel Mailing List Subject: RE: Linux 2.6.27-rc8 In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52064B1CE4@orsmsx418.amr.corp.intel.com> Message-ID: References: <36D9DB17C6DE9E40B059440DB8D95F52064B1CE4@orsmsx418.amr.corp.intel.com> User-Agent: Alpine 1.10 (LFD 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 On Mon, 29 Sep 2008, Brandeburg, Jesse wrote: > Linus Torvalds wrote: > > What's the magic to trigger it? I've got a laptop with that e1000e > > chip in it, and am obviously running a recent kernel on it. Do people > > have a handle on it? Is it actually verified to be kernel-related, > > and not related to the X server etc? > > my current status mail was posted earlier today to lkml from this > address, since then we've had a local reproduction and are going for > number two. The reproduction seems racy, i.e. it doesn't happen every > time, so we put it in a loop doing detect, check eeprom, detect, etc, > and we'll see if it fails. > > Reproduction seems to consistently be around X probing time, no firm > leads yet. As for Intel we have keithp and jbarnes as well as arjan, > auke, myself and a few others involved. > > We have some patches to lock the nvm down, we'll be posting those > tonight and tomorrow, I also have some debug logic (and fixes) to help > prove that we don't think it's a race in e1000e. Can we get the simple debug patches including the fixes which resulted from them pushed upstream ASAP ? Thanks, tglx