Hello Jonathan, Thanks for your interest in my issue. I've run the following script to catch the dmesg messages :
#!/bin/sh > while /bin/true; do dmesg > ~/dmesg_logs/dmesg_$(date +%T).log; sync; > sleep 1; done You'll find attached to this email the content of the last file written when the bug occurs. If I can do anything else to help you... Dorian On Fri, Oct 26, 2012 at 1:44 PM, Didier 'OdyX' Raboud <o...@debian.org>wrote: > Hi Jonathan, > > Le jeudi, 25 octobre 2012 22.25:03, Jonathan Nieder a écrit : > > Didier Raboud wrote: > > > Tags: upstream > > > > What upstream version did you test? > > Well we only tried packaged kernels, all wheezy, unstable and experimental > exhibit this behaviour. We started to compile an upstream kernel but didn't > try yet. I tagged this bug as "upstream", considering it's probably not a > bug > of the packaging. > > > Can you get full "dmesg" output when in this state? A serial console[1] > or > > netconsole[2] might be helpful in obtaining that, or if that's not > > possible, a photograph of messages on the screen will do in a pinch. > > I'll let Dorian send that to the bug, we'll see what that gives. > > Cheers, > > OdyX >
dmesg_10:32:10.log.bz2
Description: BZip2 compressed data
