Hey On Sun, Sep 30, 2012 at 10:57 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: > Hi Stefan, > > Stefan Ott wrote: > >> Is there anything I can do to help debug this, other than building & >> trying dozens of kernel versions to try and find the "bad" commit? > > I haven't looked closely into this report, but here are two quick > ideas: > > A. Have you tried the 3.5.y kernel from experimental? If it works, > we can try to find the patch that fixes the bug and apply the same > to wheezy. If it doesn't work, that information will make it much > easier for us to get help from upstream.
I've been using the 3.5-trunk-686-pae kernel for about a week now and so far there haven't been any further incidents - it might just be a lucky coincidence but considering how often it happened with the wheezy kernel I'm inclined to say that the upgrade fixed the issue. Do you have a particular commit in mind that might be responsible? If so I could try building a patched kernel. cheers -- Stefan Ott http://www.ott.net/ "You are not Grey Squirrel?" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
