From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: has the i915 "black screen" boot issue returned?
Date: Fri, 28 Jan 2011 09:29:53 +0000 [thread overview]
Message-ID: <0d30dc$kt3gd6@orsmga001.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101280421430.2739@localhost6.localdomain6>
On Fri, 28 Jan 2011 04:24:17 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> On Fri, 28 Jan 2011, Chris Wilson wrote:
>
> > Well, we have two endpoints, so let git attack:
> >
> > $ git bisect start
> > $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5
> > $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e
> >
> > That shouldn't take more than a few recompiles to identify the
> > troublemaker.
>
> ok, i can get to that in a bit. might take a while since this
> system is not exactly a screamer but i'm curious -- have you heard no
> other reports of people running into this issue? i'm going to be
> embarrassed if it turns out it's something *i've* done but, at this
> point, it seems fairly reproducible.
This is the first I'm aware of. It could just be the tip of the iceberg...
> are there any kernel command-line parms i might try that would be
> informative? anything involving modesetting?
Sure: add drm.debug=0xe to your boot parameters (or to your modprobe
conf).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-28 9:29 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
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 [this message]
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='0d30dc$kt3gd6@orsmga001.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