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: Fri, 20 Jun 2008 12:17:22 +0200 From: Ingo Molnar <mingo@...e.hu> To: Kevin Winchester <kjwinchester@...il.com> Cc: Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Yinghai Lu <yhlu.kernel@...il.com>, "Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz> Subject: Re: Bisecting tip/auto-x86-next? * Kevin Winchester <kjwinchester@...il.com> wrote: > Hi, > > I am trying to track down a problem I reported here: > > http://lkml.org/lkml/2008/6/11/431 [ GART related bootup crash. ] > None or you were cc'd on the original report because I had no idea of > the source of the issue. However, I have now narrowed down the > problem to the auto-x86-next tree. Thus I did something like: > > $ git bisect start > $ git bisect good linus/master > $ git bisect bad tip/auto-x86-next ok, in that case you can use tip's topical structure and probably bisect purely x86/gart, which has all x86 gart changes. I.e. do something like this: git-checkout tip/x86/gart build and boot that kernel, if it fails and mainline works then do: git-bisect reset git-bisect start git-bisect good linus/master git-bisect bad tip/x86/gart this should drastically reduce the number of bisection steps needed, to 3 or 4 iterations. Ingo -- 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