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: <alpine.LNX.1.10.0810010935560.4022@jikos.suse.cz>
Date:	Wed, 1 Oct 2008 17:37:20 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	"Allan, Bruce W" <bruce.w.allan@...el.com>
cc:	Krzysztof Halasa <khc@...waw.pl>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Subject: RE: Linux 2.6.27-rc8

On Tue, 30 Sep 2008, Allan, Bruce W wrote:

> > > > So far it seems to be that you need 1) something close to xorg 7.4 
> > > > and 2) 2.6.27-rcX kernel to trigger it. Not every system having 
> > > > e1000e is affected.
> > > And this e1000e must be ICH*, right? I.e. not a separate e1000e 
> > > chip/card?
> > So far all the affected systems I am aware of were ICH.
> Ditto here, i.e. we have no similar reports on other parts.

We have received another report [1] a few hours ago, which really looks 
very much like the very same corruption, but it happened on system with 
nVidia card, for the first time whatsoever! So it now really looks like 
that we could rule out at least the xorg Intel driver, if this is really 
the same bug. Now go guess.

I am trying to get more information about the system in question.

[1] https://bugzilla.novell.com/show_bug.cgi?id=425480#c105

-- 
Jiri Kosina
SUSE Labs
--
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/