linux-kernel - Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related

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: <201009012126.48174.Martin@lichtvoll.de>
Date:	Wed, 1 Sep 2010 21:26:38 +0200
From:	Martin Steigerwald <Martin@...htvoll.de>
To:	Paolo Ornati <ornati@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes

Am Mittwoch 01 September 2010 schrieb Paolo Ornati:
> On Tue, 31 Aug 2010 21:53:43 +0200
> 
> Martin Steigerwald <Martin@...htvoll.de> wrote:
> > Obviously I am not interested in kernels prior 2.6.33. Should I just
> > do a "git bisect good" without trying the kernel or is there some
> > other remedy?
> 
> No. Git is right in asking you to test that commit: you are ignoring
> branches and merges.
> 
> Example
[...]
> So the commit you are testing it's like "commit A": it was done before
> (in time) v2.6.33, on a kernel based on v2.6.33-rc2, but was merged in
> Linus' tree _after_ v2.3.33.
> 
> So this this behaviour is normal :)

Thanks. That explains it. So I compile this kernel and continue bisecting 
as usual.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)