From: Arjan van de Ven <arjan@linux.intel.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
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: Fri, 26 Sep 2008 04:49:51 -0700 [thread overview]
Message-ID: <48DCCC5F.8040609@linux.intel.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0809260812130.14480@pegasus.suse.cz>
Jiri Kosina wrote:
> On Thu, 25 Sep 2008, Brandeburg, Jesse wrote:
>
>> 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.
>
> Thanks. Also Jesse Barnes' patch shouldn't be forgotten, could you please
> add it to that lineup?
>
> http://marc.info/?l=linux-kernel&m=122237193628087&w=2
>
can we (for now) also stick a WARN_ON() into that failure path? that way we can at least
catch if/when this happens more visibly..... if it happens consistently in say the new distros
we can be more confident that we're down the right path in diagnosing the issue.
next prev parent reply other threads:[~2008-09-26 11:50 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 [this message]
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
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=48DCCC5F.8040609@linux.intel.com \
--to=arjan@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox