On Tue, 2014-12-09 at 22:51 +0000, Toni Mueller wrote: > > > Hi Ben, > > On Tue, Dec 09, 2014 at 06:11:09PM +0000, Ben Hutchings wrote: > > Also, this is assigned to linux-image-3.16-0.bpo.3-686-pae but the > > screenshot you attached shows that package being newly installed. > > Therefore it is not the kernel you were running at the time you first > > saw this problem. > > > > Did you subsequently boot into that kernel? > > yes, the problem occurred with the 3.16-bpo kernel several times, basically > each time I tried to run it, but so far never that early. > Today the machine just locked up this way during or shortly after boot (I did > not have a console for it when it happened). > > Should I create another screen shot when the problem happens next time? I don't think a screen shot will provide enough information. > > We would need a more complete kernel log. You could use an emulated > > serial console to get this. > > What exactly do you want? I mean, at this point I am almost confident to > unfortunately reproduce the problem soonish. 1, Enable an emulated serial port for the VM, with output going to a file. 2. Enable a serial console on the kernel command line. 3. Set sysctl kernel.printk=7 (i.e. send all non-debug logging to the console). 4. Do whatever you have to do, to reproduce the hang. Then send us the file with the console output. > > How much memory does this VM have? Does it have a swap file? > > <memory unit='KiB'>1638400</memory> > > It has a swap partition, but no separate swap file. Sorry, I meant swap partition. Anyway, it is not very small which was one possibility I had thought of. Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa.
Attachment:
signature.asc
Description: This is a digitally signed message part