From: Woody Suwalski <terraluna977@gmail.com>
To: Keith Packard <keithp@keithp.com>, "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regression: i915 blank issue on kernel 3.1.0-rc3
Date: Sun, 25 Sep 2011 10:23:37 -0400 [thread overview]
Message-ID: <4E7F3969.2050308@gmail.com> (raw)
In-Reply-To: <yun4o05xkgl.fsf@aiko.keithp.com>
Keith Packard wrote:
> On Wed, 21 Sep 2011 19:02:05 -0400, Woody Suwalski<terraluna977@gmail.com> wrote:
>
>> Chris, I do not know if it is i915 driver or X'drm or what..
>> Problem exists on 3.1.0, no problem on 3.0.3
> Any way you could narrow it down a bit more? A bisect should sort it out
> pretty quickly, given that you've got working code in 3.0 and
> not-working code in 3.1-rc. You can start by manually bisecting across the
> 3.1 release candidates, and then narrow it down from there by bisecting
> only across the drivers/gpu/drm/i915 directory.
>
I see that now more people are reporting a blanker problem. I guess
kernel.org downtime is really impacting testing...
Anyway, for Eeepc reverting the
aaa6fd2a004147bf32fce05720938236de3361d9
seems to be fixing the issue. Which is not of course the way we want to go ;-(
Woody
next prev parent reply other threads:[~2011-09-25 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 23:02 i915 blank issue on kernel 3.1.0 Woody Suwalski
2011-09-22 4:35 ` Keith Packard
2011-09-25 13:15 ` Regression: i915 blank issue on kernel 3.1.0-rc3 Woody Suwalski
2011-09-25 14:23 ` Woody Suwalski [this message]
2011-09-25 20:27 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2011-09-25 13:37 Alex Davis
2011-10-03 21:10 ` Alex Davis
2011-10-04 19:32 ` Keith Packard
2011-10-05 19:59 ` Alex Davis
2011-10-05 20:16 ` Keith Packard
2011-10-05 21:20 ` Alex Davis
2011-10-05 21:42 ` Keith Packard
2011-10-05 21:59 ` Alex Davis
2011-10-06 22:00 ` Alex Davis
2011-09-25 21:13 Alex Davis
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=4E7F3969.2050308@gmail.com \
--to=terraluna977@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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