linux-kernel - Re: 2.6.35-rc[1-5] + Radeon-kms: 3D graphic performance

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] [day] [month] [year] [list]

Message-ID: <20100724124913.0bbd9a06@schatten.dmk.lab>
Date:	Sat, 24 Jul 2010 12:49:13 +0200
From:	Florian Mickler <florian@...kler.org>
To:	trapdoor6@...il.com, LKML <linux-kernel@...r.kernel.org>
Cc:	Alex Deucher <alexdeucher@...il.com>
Subject: Re: 2.6.35-rc[1-5] + Radeon-kms: 3D graphic performance

On Fri, 23 Jul 2010 01:21:24 +0100
trapDoor <trapdoor6@...il.com> wrote:

> Hi Alex,
> This is with regard to thread 'Blank (disconnected) screen during boot
> with latest 2.6.35-rcX kernels'.
> 
> You asked me in your last e-mail if I could do a bisect to find out
> what caused a regression I mentioned about - in 3D graphic performance
> in kernels 2.6.35-rc + radeoon-kms. I started the bisect but
> unfortunately I haven't finished due to some problems I came across
> and I'm not sure if I can continue it. I'm pointing below how the
> bisect went and - if you'd like to take a look - at the last point I
> explained why I stopped.
> 
> I did notice some pattern during this unfinished bisect though. And I
> think it may narrow down the regression to its source.
> 
> 
> 

Hi Alex!

I just pasted your good/bad results in my git and did look at it with

git bisect visualize


What I would do in your case is to try
612e06ce9c7884 radeon: Fix locking in power management paths

as that is the one just before your suspected bad commit. 

Definitely(well 98% certainty) you can skip any powerpc-commits that
are left as undecided... just try some commits in the drm/radeon range
there to either validate or invalidate your suspicion about f81f202402
(one of the vblank ones)

You can just do 'git reset --hard [commit you like to try]' to change
the commit you want to try next. (or use git bisect skip) 

Cheers,
Flo

p.s.: oh and of course trying the patches suggested by alex in the
other mail first is probably a wise thing to do...
--
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/