From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
dri-devel@lists.freedesktop.org
Subject: Re: has the i915 "black screen" boot issue returned?
Date: Thu, 27 Jan 2011 10:15:01 +0000 [thread overview]
Message-ID: <b9dded$hp9kfu@orsmga002.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101260634300.10774@localhost6.localdomain6>
On Wed, 26 Jan 2011 06:37:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
>
> after suffering through the i915 "black screen" issue for a while,
> it was a relief that it finally seemed to be resolved with 2.6.37 or
> something in tha vicinity. but i just built and booted a 2.6.38-rc2+
> kernel on my ubuntu 10.10 system and it once again boots to a black
> screen.
>
> is this a new known issue? has anyone else seen this?
It all depends. There is a new ACPI backlight issue causing grief, aside
from that and lingering issues with the legacy backlight combination mode,
I don't think there was a new i915 KMS regression. (We had regressions
elsewhere and finally fixed up a few old regressions for UMS and DRI1 and
various other OOPS-on-boot. And suspend is a bit hit and miss.)
For extra fun, it appears that sched_autocgroup can trigger a leak of
pinned bo eventually hitting a BUG. That's one I'm keen to reproduce.
Without knowing your chipset and seeing a dmesg, I can only guess which
problem you are most likely to have hit.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-27 10:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 11:37 has the i915 "black screen" boot issue returned? Robert P. J. Day
2011-01-27 10:15 ` Chris Wilson [this message]
2011-01-27 10:37 ` Robert P. J. Day
2011-01-27 11:47 ` Robert P. J. Day
2011-01-27 11:56 ` Chris Wilson
2011-01-27 12:12 ` Robert P. J. Day
2011-01-27 12:17 ` Chris Wilson
2011-01-27 12:27 ` Robert P. J. Day
2011-01-27 13:00 ` Robert P. J. Day
2011-01-27 13:42 ` Robert P. J. Day
2011-01-27 13:52 ` Chris Wilson
2011-01-27 13:55 ` Robert P. J. Day
2011-01-27 14:07 ` Chris Wilson
2011-01-27 14:13 ` Robert P. J. Day
2011-01-27 18:40 ` Robert P. J. Day
2011-01-27 21:39 ` Robert P. J. Day
2011-01-27 22:33 ` Robert P. J. Day
2011-01-28 8:59 ` Chris Wilson
2011-01-28 9:24 ` Robert P. J. Day
2011-01-28 9:29 ` Chris Wilson
2011-01-28 13:53 ` has the i915 "black screen" boot issue returned? [BISECTED] Robert P. J. Day
2011-01-28 14:02 ` Chris Wilson
2011-01-28 14:10 ` Robert P. J. Day
2011-01-28 14:32 ` Robert P. J. Day
2011-01-28 14:36 ` Chris Wilson
2011-01-28 14:51 ` Robert P. J. Day
2011-01-28 15:04 ` Chris Wilson
2011-01-28 15:08 ` Robert P. J. Day
2011-01-28 15:11 ` Chris Wilson
2011-01-28 15:27 ` Robert P. J. Day
2011-01-28 15:39 ` Chris Wilson
2011-01-28 15:54 ` Robert P. J. Day
2011-01-28 16:03 ` Chris Wilson
2011-01-28 16:23 ` Robert P. J. Day
2011-01-28 16:30 ` Chris Wilson
2011-01-28 18:38 ` Robert P. J. Day
2011-01-29 10:02 ` Robert P. J. Day
2011-02-01 12:05 ` Robert P. J. Day
2011-02-01 12:12 ` Chris Wilson
2011-02-01 12:56 ` Robert P. J. Day
2011-01-28 16:30 ` Robert P. J. Day
2011-01-28 20:12 ` Rafael J. Wysocki
2011-01-28 20:21 ` Robert P. J. Day
2011-01-28 20:46 ` Robert P. J. Day
2011-01-28 11:35 ` has the i915 "black screen" boot issue returned? Robert P. J. Day
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='b9dded$hp9kfu@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=rpjday@crashcourse.ca \
/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