From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Li <lkml@chrisli.org>
Cc: linux-kernel@vger.kernel.org, robert.moore@intel.com,
feng.tang@intel.com, len.brown@intel.com, daniel.vetter@ffwll.ch,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: i915 black screen introduced by ACPI changes
Date: Tue, 19 Feb 2013 12:52:17 -0800 [thread overview]
Message-ID: <20130219125217.6b6f55ff@jbarnes-desktop> (raw)
In-Reply-To: <CANeU7QmJb+yUGu9mVgq=_pHhvpPu6ORrikm=E6PkuHpOz9OREA@mail.gmail.com>
On Tue, 19 Feb 2013 12:18:45 -0800
Chris Li <lkml@chrisli.org> wrote:
> Secondly, the one clue is that, setting "i915.modeset=0" alone will allow
> the kernel to boot into X GUI login. It seems that the mode switch alone in
> i915 can trigger the black screen. It is consistent with kernel lockup when I
> logout of X desktop, where X want to reset the screen.
>
> Instead of guess which driver were at fault, can you suggest some experiment
> to confirm or denial which driver is at fault?
Well it definitely sounds i915 related. I was just thinking that if
certain bits were routed to the nvidia chip instead of the i915 one,
the i915 driver may get confused and panic.
For debugging, you could modify the modeset_init function in i915_dma.c
and make it return early with an error. You could use that to narrow
down which part of init was failing.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-02-19 20:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 4:43 Chris Li
2013-02-19 18:08 ` Jesse Barnes
2013-02-19 20:18 ` Chris Li
2013-02-19 20:52 ` Jesse Barnes [this message]
2013-02-20 7:17 ` Chris Li
2013-02-20 10:57 ` Daniel Vetter
2013-02-20 19:29 ` Chris Li
2013-02-20 19:33 ` Chris Li
2013-02-20 19:37 ` Chris Li
2013-02-20 19:45 ` Chris Li
2013-02-20 20:01 ` Chris Li
2013-02-20 20:19 ` Daniel Vetter
2013-02-20 20:23 ` Chris Li
2013-02-20 20:43 ` Chris Li
2013-02-20 21:04 ` Chris Li
2013-02-22 22:42 ` Chris Li
2013-03-04 17:11 ` Chris Li
2013-03-04 17:49 ` Daniel Vetter
2013-03-04 17:50 ` Daniel Vetter
2013-03-04 23:16 ` Chris Li
2013-03-04 23:33 ` Chris Li
2013-03-11 13:16 ` [Intel-gfx] " Jani Nikula
2013-03-14 20:10 ` Chris Li
2013-03-14 20:49 ` Chris Li
2013-03-15 7:29 ` Jani Nikula
2013-03-15 9:00 ` Chris Li
2013-03-15 9:06 ` Chris Li
2013-03-15 9:33 ` Chris Li
2013-03-19 8:13 ` Chris Li
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=20130219125217.6b6f55ff@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel.vetter@ffwll.ch \
--cc=feng.tang@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@chrisli.org \
--cc=robert.moore@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®