linux-kernel - Re: i915 completely unusable in 2.6.38.x

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: <20110425210323.GA23418@kroah.com>
Date:	Mon, 25 Apr 2011 14:03:23 -0700
From:	Greg KH <greg@...ah.com>
To:	Melchior FRANZ <melchior.franz@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: i915 completely unusable in 2.6.38.x

On Mon, Apr 25, 2011 at 10:10:46PM +0200, Melchior FRANZ wrote:
> * Boris B. Zhmurov -- Monday 25 April 2011:
> > After upgrading RHEL6 to 2.6.28.x kernel, I have spontaneous "GPU hung"
> > 5-6 times per day.
> > xorg-x11-drv-intel-2.11.0-7.el6.i686 driver for Xorg.
> 
> JFTR, and although it seems to be a totally different problem with i915
> (or rather gm45), the whole 2.6.38.* series is also of limited use on my
> notebook, as described in this error message:
> 
>    https://bugzilla.kernel.org/show_bug.cgi?id=31522
> 
> I'm still using 2.6.38-rc8 (with SuSE 11.4/tumbleweed) on this machine
> (Acer TravelMate 5735Z-452G32Mnss), because that's the last version that
> supported KMS on my chipset. This older version works ok, so there's no
> reason to complain, but I'm still a bit suprised about that regression.

I don't understand, .38 should work as it has the above fix in it,
right?

Otherwise, what should be done for the .38-stable tree?

confused,

greg k-h
--
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/