From: Chris Wilson <chris@chris-wilson.co.uk>
To: Chris Vine <chris@cvine.freeserve.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.37-rc2 breaks i915 graphics
Date: Sun, 21 Nov 2010 10:30:43 +0000 [thread overview]
Message-ID: <0d30dc$k822nk@orsmga001.jf.intel.com> (raw)
In-Reply-To: <20101121102344.7c590b99@laptop.homenet>
On Sun, 21 Nov 2010 10:23:44 +0000, Chris Vine <chris@cvine.freeserve.co.uk> wrote:
> Hi,
>
> With kernel 2.6.37-rc2, i915 graphics usually fails on boot-up after
> modesetting with my Lenovo S12 netbook which uses the Intel 945GME
> Express Integrated Graphics Controller. It displays up to the point at
> which modesetting takes place and then usually goes blank.
>
> There may be some kind of race at work here: first, sometimes (maybe 1
> times in 4) graphics comes up correctly on a first cold boot, but I
> have never managed to get it to come up on a warm reboot. Secondly,
> graphics can be restored when I know (but cannot see) that boot-up has
> concluded, simply by suspending the laptop and then resuming. Resuming
> the laptop after a suspend always brings up the graphics correctly.
Add drm.debug=0xe to your boot commandline and compare if there is any
difference between a successful cold boot, a broken cold boot and a warm
boot. Similarly, comparing the output of intel_reg_dumper after each
should yield a few clues as to what stage in the boot process we fail.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-21 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 10:23 kernel 2.6.37-rc2 breaks i915 graphics Chris Vine
2010-11-21 10:30 ` Chris Wilson [this message]
2010-11-21 18:34 ` Chris Vine
2010-11-22 8:36 ` Boaz Harrosh
2010-11-26 9:23 ` Florian Mickler
2010-11-26 13:34 ` Zdenek Kabelac
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$k822nk@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=chris@cvine.freeserve.co.uk \
--cc=linux-kernel@vger.kernel.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