linux-kernel - Re: kernel 2.6.37-rc2 breaks i915 graphics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101126102341.6d4188af@schatten.dmk.lab>
Date:	Fri, 26 Nov 2010 10:23:41 +0100
From:	Florian Mickler <florian@...kler.org>
To:	Chris Vine <chris@...ne.freeserve.co.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: kernel 2.6.37-rc2 breaks i915 graphics

On Sun, 21 Nov 2010 18:34:23 +0000
Chris Vine <chris@...ne.freeserve.co.uk> wrote:

> On Sun, 21 Nov 2010 10:30:43 +0000
> Chris Wilson <chris@...is-wilson.co.uk> wrote:
> 
> > On Sun, 21 Nov 2010 10:23:44 +0000, Chris Vine
> > <chris@...ne.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 trimmed the failure boot logs to the stuff before suspending, in
order to only compare the boot sequence. 

Looks like only in failure case there are "pipe b
underrun" reported...
In success case, no "pipe b underrun" is reported. 

Also in success case connectors are probed much more often:

$ grep drm:drm_helper_probe_single_connector_modes dmesg-2.6.37-rc2.succeed  | wc -l
76
$ grep drm:drm_helper_probe_single_connector_modes dmesg-2.6.37-rc2.*.fail  | wc -l
32
$ grep drm:drm_helper_probe_single_connector_modes dmesg-2.6.37-rc2.cold.fail  | wc -l
16


I could not spot any other differences both failure modes have in common against the success case.

If Chris (Wilson) doesn't yet know what could be the bug a bisection 
between 2.6.37-rc1 and rc2 might be helpful. 

 
> 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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/