public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Melchior FRANZ <melchior.franz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i915 completely unusable in 2.6.38.x
Date: Mon, 25 Apr 2011 14:03:23 -0700	[thread overview]
Message-ID: <20110425210323.GA23418@kroah.com> (raw)
In-Reply-To: <201104252210.46523@rk-nord.at>

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

  reply	other threads:[~2011-04-25 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25  9:14 i915 completely unusable in 2.6.38.x Boris B. Zhmurov
2011-04-25  9:15 ` Boris B. Zhmurov
2011-04-25 20:10 ` Melchior FRANZ
2011-04-25 21:03   ` Greg KH [this message]
2011-04-26  7:59     ` Melchior FRANZ
2011-04-26 10:31       ` Boris B. Zhmurov
2011-04-26 18:04       ` Melchior FRANZ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110425210323.GA23418@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=melchior.franz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox