[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080923.150722.141587696.davem@davemloft.net>
Date: Tue, 23 Sep 2008 15:07:22 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: airlied@...il.com
Cc: jkosina@...e.cz, david.vrabel@....com, rjw@...k.pl,
linux-kernel@...r.kernel.org, kernel-testers@...r.kernel.org,
chrisl@...are.com
Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
From: "Dave Airlie" <airlied@...il.com>
Date: Wed, 24 Sep 2008 07:09:09 +1000
> On Wed, Sep 24, 2008 at 7:05 AM, David Miller <davem@...emloft.net> wrote:
> > From: Jiri Kosina <jkosina@...e.cz>
> > Date: Tue, 23 Sep 2008 16:29:16 +0200 (CEST)
> >
> >> On Mon, 22 Sep 2008, David Miller wrote:
> >>
> >> > So I went through the changes from 2.6.27-rc5 until the SHA1
> >> > ID ec0c15afb41fd9ad45b53468b60db50170e22346 and there were
> >> > definitely no E1000 or E1000E changes during that time.
> >>
> >> Some recent comments on [1] seem to indicate that this is somehow coupled
> >> into prior problems/panics with Intel graphics.
> >
> > My current suspicion in all of this is either the GEM kernel patches
> > or recent X server.
> >
>
> I don't think OpenSUSE was shipping any of the GEM bits.
Good data point, can someone confirm this? Also, what X server version
is the effected OpenSUSE shipping?
--
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