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
Subject: Re: i915 black screen introduced by ACPI changes
Date: Tue, 19 Feb 2013 10:08:49 -0800 [thread overview]
Message-ID: <20130219100849.72d2330b@jbarnes-desktop> (raw)
In-Reply-To: <CANeU7QmbzX4Tx1Dtu6xOiYzr6h6_8tPQvVG32Wvkt=5wAwEEAg@mail.gmail.com>
On Sun, 17 Feb 2013 20:43:47 -0800
Chris Li <lkml@chrisli.org> wrote:
> My Lenovo Y580 laptop with FC18 start to get black screen after the kernel
> upgrade to 3.7.xxx
>
> The black screen happens about the time kernel switch to using VT console.
> At the point of black screen, no response of cap locks key led no network
> connection. The machine seems dead.
Can you set up netconsole and see if you can get any output from the
boot, if we're lucky maybe you'll see a panic...
> The CPU is i7 and it has two video card. The Intel build-in video card
> and Gtx 660M Nvidia card.
>
> This is very annoying. I did some poking around it:
> - It was fine on the FC18 3.6.xxx kernel before the upgrade.
> - The black screen exists with FC18 3.7.xxx kernel
> - The black screen also exists in latest tip of linux-2.6.
> - Switch to multi-user mode booting does not get rid of the black screen.
> - Get rid of the "rhrb quit" does not help either.
> - When the black screen happen, cap lock LED does not response to cap locks.
> - No networking when black screen happen. The only thing to do is
> reboot the system.
> - Adding "i915.modeset=0" will allow the kernel to boot into GUI login. However,
> logout of X will cause the machine to hang similar to the black screen.
> - Suspend and resume will get stuck at the black screen with"i915.modeset=0".
> - Kernel console and X is using the Intel driver for display.
I don't know about the ACPI change mentioned, but ACPI is involved in
dual-GPU configurations. Maybe the change affected the default
behavior and pointed more functions at the nVidia device rather than
the Intel?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-02-19 18:08 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 [this message]
2013-02-19 20:18 ` Chris Li
2013-02-19 20:52 ` Jesse Barnes
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=20130219100849.72d2330b@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 \
/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®