| 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
| ||
|
Date: Wed, 1 Sep 2010 19:13:41 +0100 From: Ken Moffat <zarniwhoop@...world.com> To: Martin Steigerwald <Martin@...htvoll.de> Cc: linux-kernel@...r.kernel.org Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes On Wed, Sep 01, 2010 at 06:10:24PM +0200, Martin Steigerwald wrote: > Am Mittwoch 01 September 2010 schrieb Ken Moffat: > > > > While you are bisecting, don't believe the version in Makefile. I > > got similarly freaked out a couple of years ago - if I understood > > correctly, it's something to do with when a change was created. > > > > The key point is that during bisection the apparent version *can* > > go back to a version that appears to be before the initial "good" > > kernel. > > I verified the version by running git log after doing the skip. And it was > just 300 lines after Linus commited 2.6.33-rc2. Can git log be showing > incorrect results during a bisect? > > Thanks, I suggest you go with the versions that git bisect selects. I appreciate that it takes you a long time to build and test each kernel, but hopefully you can reach a stage where the bad commit is identified. I think I've seen people report that an old commit was identified as causing a problem, and I also think that in those cases the problem was exposed by a later commit. ken -- das eine Mal als Tragödie, das andere Mal als Farce -- 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/
Powered by blists - more mailing lists