Hi, nice to finally see some activity on this :)
> > What do you recommend next? > > Nice. That narrows it down to one of 104 patches, which means > 7 rounds of bisection would narrow it down to a single patch: [...] > > If you go through step 5 enough times, it will reveal the "first bad > commit". If you get bored before then, running "git bisect log" will > produce a log of the versions you have tested to allow someone else to > pick up where you left off. If the gitk package is installed, at any > step you can run "git bisect visualize" to watch the regression range > narrowing. I can confirm that on my system, the bug does not appear with 2.6.37 either. I am currently building upstream 2.6.38-rc6, and maybe I can do some of the bisecting rounds later today. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
