mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.37-rc2 breaks i915 graphics
Date: Sun, 21 Nov 2010 18:34:23 +0000	[thread overview]
Message-ID: <20101121183423.0f7c1872@laptop.homenet> (raw)
In-Reply-To: <0d30dc$k822nk@orsmga001.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1842 bytes --]

On Sun, 21 Nov 2010 10:30:43 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> 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

First an additional datum point: 2.6.37-rc1 works normally, so the bug
is something introduced between 2.6.37-rc1 and 2.6.37-rc2 (to that
extent it may be related to this bug which reports a similar phenomenon:
http://lkml.org/lkml/2010/11/21/23 ).

Attached is the dmesg output from a successful cold boot with
2.6.37-rc2, an unsuccessful cold boot and an unsuccessful warm boot,
each with drm.debug=0xe.

I can't provide the output of intel_reg_dumper:  I can't compile the
latest intel-gpu-tools from git (missing declaration/definition of
I915_EXE_BLT).  Probably something in a relevant library is too old.

Chris

[-- Attachment #2: dmesg-2.6.37-rc2.succeed.gz --]
[-- Type: application/x-gzip, Size: 11791 bytes --]

[-- Attachment #3: dmesg-2.6.37-rc2.cold.fail.gz --]
[-- Type: application/x-gzip, Size: 13207 bytes --]

[-- Attachment #4: dmesg-2.6.37-rc2.warm.fail.gz --]
[-- Type: application/x-gzip, Size: 13135 bytes --]

  reply	other threads:[~2010-11-21 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 10:23 Chris Vine
2010-11-21 10:30 ` Chris Wilson
2010-11-21 18:34   ` Chris Vine [this message]
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=20101121183423.0f7c1872@laptop.homenet \
    --to=chris@cvine.freeserve.co.uk \
    --cc=chris@chris-wilson.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

all inboxes | Powered by JetHome®