[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48DCCC5F.8040609@linux.intel.com>
Date: Fri, 26 Sep 2008 04:49:51 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Jiri Kosina <jkosina@...e.cz>
CC: "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
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.
--
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