From: James Courtier-Dutton <James@superbug.co.uk>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>,
agospoda@redhat.com, "Ronciak, John" <john.ronciak@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Graham, David" <david.graham@intel.com>,
kkiel@suse.de, tglx@linutronix.de, chris.jones@canonical.com,
arjan@linux.jf.intel.com
Subject: Re: e1000e NVM corruption issue status
Date: Sat, 18 Oct 2008 20:13:09 +0100 [thread overview]
Message-ID: <48FA3545.3030102@superbug.co.uk> (raw)
In-Reply-To: <Pine.WNT.4.63.0809251811330.1736@jbrandeb-desk.amr.corp.intel.com>
Brandeburg, Jesse wrote:
>
> Many of the reports seem to be related in time to a graphics crash, no one
> has been able to give us more detail about how to reproduce. We NEED HELP
> reproducing this. Steps, hints, anything. We are trying rebooting,
> suspending, opensuse, fedora, ubuntu, and several hardware platforms, etc.
>
I would suspect the ipv6 module instead of the graphics. It has a number
of bugs in it. I am just mentioning it in case it helps.
Kind Regards
James
next prev parent reply other threads:[~2008-10-18 19:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <987CEB09A2567F4A963E1E226364E2D33A685B4B@orsmsx418.amr.corp.intel.com>
2008-09-26 1:50 ` e1000e NVM corruption issue status Brandeburg, Jesse
2008-09-26 1:58 ` Chris Snook
2008-09-26 2:04 ` Brandeburg, Jesse
2008-09-26 2:01 ` Brandeburg, Jesse
2008-09-26 2:09 ` Brandeburg, Jesse
2008-09-26 7:12 ` Ingo Molnar
2008-09-26 2:09 ` Brandeburg, Jesse
2008-09-26 2:10 ` Brandeburg, Jesse
2008-09-26 2:10 ` Brandeburg, Jesse
2008-09-26 2:10 ` Brandeburg, Jesse
2008-09-26 2:11 ` Brandeburg, Jesse
2008-09-26 2:11 ` Brandeburg, Jesse
2008-09-26 2:12 ` Brandeburg, Jesse
2008-09-26 2:12 ` Brandeburg, Jesse
2008-09-26 2:13 ` Brandeburg, Jesse
2008-09-26 2:13 ` Brandeburg, Jesse
2008-09-29 15:52 ` Jiri Kosina
2008-09-29 16:20 ` Jiri Kosina
2008-09-29 16:24 ` Brandeburg, Jesse
2008-09-29 17:18 ` Jiri Kosina
2008-09-29 17:36 ` Jiri Kosina
2008-09-29 22:43 ` Jiri Kosina
2008-09-26 6:13 ` Jiri Kosina
2008-09-26 11:49 ` Arjan van de Ven
2008-09-26 17:52 ` Jesse Barnes
2008-09-26 18:23 ` Jesse Barnes
2008-09-26 18:39 ` Jesse Barnes
2008-09-26 18:43 ` Jesse Barnes
2008-09-26 18:53 ` Tim Gardner
2008-09-26 22:04 ` Krzysztof Halasa
2008-09-26 22:23 ` Brandeburg, Jesse
2008-09-27 18:45 ` Krzysztof Halasa
2008-09-27 0:05 ` Brandeburg, Jesse
2008-09-27 4:20 ` Tim Gardner
2008-09-26 14:23 ` Karsten Keil
2008-09-26 5:44 ` Jesse Brandeburg
2008-09-26 7:19 ` Karsten Keil
2008-10-18 19:13 ` James Courtier-Dutton [this message]
2008-10-18 22:49 ` Jiri Kosina
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=48FA3545.3030102@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=agospoda@redhat.com \
--cc=arjan@linux.jf.intel.com \
--cc=bruce.w.allan@intel.com \
--cc=chris.jones@canonical.com \
--cc=david.graham@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jkosina@suse.cz \
--cc=john.ronciak@intel.com \
--cc=kkiel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.