From: Karsten Keil <kkeil@suse.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: e1000e NVM corruption issue status
Date: Fri, 26 Sep 2008 16:23:34 +0200 [thread overview]
Message-ID: <20080926142334.GA554@pingi.kke.suse.de> (raw)
In-Reply-To: <Pine.WNT.4.63.0809251857360.1736@jbrandeb-desk.amr.corp.intel.com>
On Thu, Sep 25, 2008 at 07:01:21PM -0700, Brandeburg, Jesse wrote:
> > We have a series of kernel patches that I will reply to this mail with
> > that may help users willing to test.
>
> this is the current set of patches that I have to help us debug
> and/or fix e1000e issues found during this debug effort for
> the corrupt NVM. the "drop stats lock" - "reset swflag" patches allow
> Thomas' patch for a mutex in the SWFLAG acquire function to run without
> any errors.
>
> the patches are not probably production quality, but seem to work
> for myself and thomas on at least a couple of machines.
>
> The non-debug aspects of the patches will likely be pushed later.
>
> At this point I do not believe any of these patches will fix the
> NVM corruption issue, but will add to the ability of any tester
> to help find the issue, and reduce the chance that it is any issue we
> (now) know about.
>
A kernel with this these patches load the e1000e driver fine on
a test machine which has a OK NVM checksum.
But it freeze on one machine which has a wrong checksum.
On this machine the NVM seems to be OK, but the NVM valid bit
is cleared. If I would set this bit, the NVM checksum would be OK
again. This is the T61 notebook which did show this error after
openSUSE 11.1 Beta1 install after a reboot during X setup.
--
Karsten Keil
SuSE Labs
ISDN and VOIP development
SUSE LINUX Products GmbH, Maxfeldstr.5 90409 Nuernberg, GF: Markus Rex, HRB 16746 (AG Nuernberg)
next prev parent reply other threads:[~2008-09-26 14:23 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 ` 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 [this message]
2008-09-26 5:44 ` Jesse Brandeburg
2008-09-26 7:19 ` Karsten Keil
2008-10-18 19:13 ` James Courtier-Dutton
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=20080926142334.GA554@pingi.kke.suse.de \
--to=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome