[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.WNT.4.63.0809251903450.1736@jbrandeb-desk.amr.corp.intel.com>
Date: Thu, 25 Sep 2008 19:04:46 -0700 (Pacific Daylight Time)
From: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To: Chris Snook <csnook@...hat.com>
cc: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Jiri Kosina <jkosina@...e.cz>, 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 Thu, 25 Sep 2008, Chris Snook wrote:
> Brandeburg, Jesse wrote:
> > hardware affected:
> > laptops and desktops with 82566 or 82567 based LAN parts, which are machines
> > with the ICH8 and ICH9 chipsets and a variety of processors.
> > The machines I know of that have reported the issue include
> > Lenovo X300
> > HP 2510p
> > Intel DP35JO
> > Lenovo T61 (possibly)
> > Lenovo X61 (possibly)
>
> My Intel DG45ID board has an ICH10R chipset, and it also has an 82567LM, just
> as some of the affected systems. Is there some reason why ICH10 is not
> susceptible, or have we simply not seen it?
ICH10R with 82567 is also susceptible, as far as I know at this point.
--
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