[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0810010006470.5549@apollo.tec.linutronix.de>
Date: Wed, 1 Oct 2008 00:07:51 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Jiri Kosina <jkosina@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: Linux 2.6.27-rc8
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists