linux-kernel - Re: [bisected] i915 regression in post 2.6.36 kernels

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <201011102339.36590.johannes.hirte@fem.tu-ilmenau.de>
Date:	Wed, 10 Nov 2010 23:39:35 +0100
From:	Johannes Hirte <johannes.hirte@....tu-ilmenau.de>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [bisected] i915 regression in post 2.6.36 kernels

On Wednesday 10 November 2010 08:46:40 Chris Wilson wrote:
> On Wed, 10 Nov 2010 08:02:19 +0100, Johannes Hirte <johannes.hirte@....tu-ilmenau.de> wrote:
> > With the latest kernel, I don't get any windows in KDE displayed. After
> > starting kdm, I get the background picture and the mouse cursor but not the
> > login window. I can login blindly and a ps on console shows me that the
> > expected KDE processes are started but still nothing is displayed. 
> > I've bisected this to:
> > 
> > 5c12a07e8073295ce8b57a822f811ac34e4f8420 is the first bad commit
> > commit 5c12a07e8073295ce8b57a822f811ac34e4f8420
> > Author: Chris Wilson <chris@...is-wilson.co.uk>
> > Date:   Wed Sep 22 11:22:30 2010 +0100
> > 
> >     drm/i915: Drop ring->lazy_request
> >     
> >     We are not currently using it as intended, so remove the complication.
> > 
> >     Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
> 
> May I ask you to recheck your bisection, since that was later reverted.
> -Chris

Did so. I've started with v2.6.36 for bisect good and 
f6614b7bb405a9b35dd28baea989a749492c46b2 for bisect bad (was HEAD) in this
case. Again I ended in 5c12a07e8073295ce8b57a822f811ac34e4f8420 as the first
bad commit. The regression was introduced there, as the commit before is fine.
If it was reverted, the regression should be fixed by this. But I don't find
neither the fix/revert nor the reintroduction of the regression.

regrards,
  Johannes
--
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/