|| ||"Dave Airlie" <airlied-AT-gmail.com>|
|| ||"Linus Torvalds" <torvalds-AT-linux-foundation.org>|
|| ||Re: Linux 2.6.27-rc8|
|| ||Tue, 30 Sep 2008 12:39:03 +1000|
|| ||"Jiri Kosina" <jkosina-AT-suse.cz>,
"Linux Kernel Mailing List" <linux-kernel-AT-vger.kernel.org>,
On Tue, Sep 30, 2008 at 12:21 PM, Linus Torvalds
> On Tue, 30 Sep 2008, Dave Airlie wrote:
>> If it is X related then its both a kernel + X server issue, the e1000e
>> driver opens the barn door, the X server drives the horses through it.
> Are you sure? There was a mandriva report abou NVM corruption on an e100
> too (that one apparently just caused PXE failure, the networking worked
Well from a purely empirical standpoint, I've been running new X
against that laptop for a long time,
and others have the same laptop, so I think its a problem with the
e1000e driver putting the card into a state which allows
X to do bad things. I think X maybe causing issues on other hw, like
e100 and some realtek.. Also when we say X I think it looks like Intel
driver interaction issues,
as I said I'm running the same stuff on my ATI gpu laptop with e1000e
and haven't had any problems.
But I'm leaving this up to Intel, I don't think HP will take it too
kindly if I keep returning my laptop.
to post comments)