From: Thomas Gleixner <tglx@linutronix.de>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Linux 2.6.27-rc8
Date: Wed, 1 Oct 2008 00:07:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0810010006470.5549@apollo.tec.linutronix.de> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52064B1CE4@orsmsx418.amr.corp.intel.com>
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
next prev parent reply other threads:[~2008-09-30 22:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 22:39 Linus Torvalds
2008-09-29 23:09 ` david
2008-09-29 23:33 ` Jiri Kosina
2008-09-30 1:56 ` Linus Torvalds
2008-09-30 1:59 ` Dave Airlie
2008-09-30 2:06 ` Arjan van de Ven
2008-09-30 2:23 ` Linus Torvalds
2008-09-30 2:24 ` Linus Torvalds
2008-09-30 12:06 ` Alan Cox
2008-09-30 3:42 ` Brandeburg, Jesse
2008-09-30 12:05 ` Alan Cox
2008-09-30 2:21 ` Linus Torvalds
2008-09-30 2:39 ` Dave Airlie
2008-09-30 3:19 ` Arjan van de Ven
2008-09-30 7:11 ` Jiri Kosina
2008-09-30 7:58 ` Eric Piel
2008-09-30 16:28 ` Luiz Fernando N. Capitulino
2008-09-30 18:27 ` Herton Ronaldo Krzesinski
2008-09-30 2:30 ` Brandeburg, Jesse
2008-09-30 22:07 ` Thomas Gleixner [this message]
2008-09-30 7:06 ` Jiri Kosina
2008-09-30 14:09 ` Krzysztof Halasa
2008-09-30 14:11 ` Jiri Kosina
2008-09-30 15:48 ` Allan, Bruce W
2008-10-01 15:37 ` Jiri Kosina
2008-09-30 7:43 ` Typo bug [Re: Linux 2.6.27-rc8] J.A. Magallón
2008-09-30 7:55 ` Ingo Molnar
2008-09-30 8:02 ` J.A. Magallón
2008-09-30 8:05 ` Ingo Molnar
2008-10-01 21:33 ` Domenico Andreoli
2008-10-02 5:27 ` Willy Tarreau
2008-10-02 9:26 ` Ingo Molnar
2008-10-02 9:45 ` Domenico Andreoli
2008-09-30 18:47 ` H. Peter Anvin
2008-09-30 19:30 ` Yinghai Lu
2008-09-30 19:59 ` H. Peter Anvin
2008-09-30 21:35 ` Yinghai Lu
2008-09-30 21:37 ` H. Peter Anvin
2008-09-30 21:42 ` Yinghai Lu
2008-09-30 22:02 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.10.0810010006470.5549@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=jesse.brandeburg@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®