linux-kernel - Re: Linux 2.6.27-rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <21d7e9970809291939r51a728c8ye865e19dffac5bd6@mail.gmail.com>
Date:	Tue, 30 Sep 2008 12:39:03 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Jiri Kosina" <jkosina@...e.cz>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	jesse.brandeburg@...el.com
Subject: Re: Linux 2.6.27-rc8

On Tue, Sep 30, 2008 at 12:21 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
>
> 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
> fine).

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.

Dave.
--
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/