[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200809261052.38966.jbarnes@virtuousgeek.org>
Date: Fri, 26 Sep 2008 10:52:34 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Jiri Kosina <jkosina@...e.cz>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
LKML <linux-kernel@...r.kernel.org>, agospoda@...hat.com,
"Ronciak, John" <john.ronciak@...el.com>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
"Graham, David" <david.graham@...el.com>, kkiel@...e.de,
tglx@...utronix.de, chris.jones@...onical.com,
arjan@...ux.jf.intel.com
Subject: Re: e1000e NVM corruption issue status
On Friday, September 26, 2008 4:49 am Arjan van de Ven wrote:
> 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.
I'm spinning a new one now with some debug output, stay tuned (just gotta boot
my test box).
--
Jesse Barnes, Intel Open Source Technology Center
--
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