From: Ondrej Zary <linux@rainbow-software.org>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: regression: 2.6.35-rc1 hangs on i865G with KMS
Date: Sat, 5 Jun 2010 13:44:29 +0200 [thread overview]
Message-ID: <201006051344.30836.linux@rainbow-software.org> (raw)
In-Reply-To: <87vd9yjpj4.fsf@pollan.anholt.net>
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.
I don't like that place - from 13 bugs I have reported there, 11 are still
open :( I even provided a patch for one and nobody cares...
Bisect reveals two possible bad commits:
386516744ba45d50f42c6999151cc210cb4f96e4
drm/fb: fix fbdev object model + cleanup properly
or
8be48d924c307e72e3797ab5bde81b07a1ccc52d
drm/kms/fb: move to using fb helper crtc grouping instead of core crtc list
It depends on the last step of bisection - that kernel hangs but in a
different way - the monitor has no signal (in every other case, the monitor
was just blank).
Reverting these commits is not possible.
--
Ondrej Zary
next prev parent reply other threads:[~2010-06-05 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 20:01 regression: 2.6.35-rc1 hangs on i865G with KMS Ondrej Zary
2010-06-05 0:23 ` Eric Anholt
2010-06-05 11:44 ` Ondrej Zary [this message]
2010-06-05 20:28 ` Ondrej Zary
2010-06-06 9:04 ` Dave Airlie
2010-06-06 9:04 ` Dave Airlie
2010-06-06 10:20 ` Ondrej Zary
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=201006051344.30836.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.