Hi Jonathan, On Mon, Feb 06, 2012 at 01:15:44AM -0600, Jonathan Nieder wrote: > Please report this upstream, following instructions from [1], and let > us know the bug number so we can track it. > > The upstream developers may ask you to bisect to find the specific > patch that introduced the problem. It works like this: > …
Thanks for the detailed walk-through. So far I tested vanilla Linux v3.2 as bad, v3.1 as good, and started the bisect (with the first half-way commit tested as bad). That means “roughly 12 steps” to go. I will report back when the upstream bug report is filed. Regards, Peter -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120207033230.GA3846@alcyone
