public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: regression: 2.6.35-rc1 hangs on i865G with KMS
Date: Sun, 6 Jun 2010 12:20:13 +0200	[thread overview]
Message-ID: <201006061220.15579.linux@rainbow-software.org> (raw)
In-Reply-To: <AANLkTinLPi93TvXcudNKPPWQaiD6xUrqvEESoxHnlIif@mail.gmail.com>

On Sunday 06 June 2010 11:04:44 Dave Airlie wrote:
> On Sun, Jun 6, 2010 at 6:28 AM, Ondrej Zary <linux@rainbow-software.org> 
wrote:
> > On Saturday 05 June 2010 02:23:27 Eric Anholt wrote:
> >> On Fri, 4 Jun 2010 22:01:28 +0200, Ondrej Zary 
<linux@rainbow-software.org> wrote:
> >> > Hello,
> >> > I'm testing 2.6.35-rc1 kernel on Asus P4P800-VM (i865G chipset). After
> >> > loading i915 module, the screen goes blank and the kernel hangs
> >> > completely (same with 2.6.35-rc1-git2). This does not happen with
> >> > "i915.modeset=0" parameter.
> >> >
> >> > This problem does not appear with 2.6.34. Is this a known regression?
> >>
> >> Not known as far as I know -- we'd enjoy a bisect with a bug report on
> >> bugs.freedesktop.org.
>
> Can you try the attached patch?

Thanks, applied it on 2.6.35-rc2 and it seems to work fine.


-- 
Ondrej Zary

      reply	other threads:[~2010-06-06 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201006042201.29872.linux@rainbow-software.org>
     [not found] ` <87vd9yjpj4.fsf@pollan.anholt.net>
2010-06-05 20:28   ` regression: 2.6.35-rc1 hangs on i865G with KMS Ondrej Zary
2010-06-06  9:04     ` Dave Airlie
2010-06-06 10:20       ` Ondrej Zary [this message]

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=201006061220.15579.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    /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