On Wed, 2013-03-06 at 01:49 +0400, vitalif@yourcmc.ru wrote: > >> >It means nothing very much. How about the stack trace *before* > >> this > >> >line: > >> > >> The problem is that the maximum available VESA mode is 1400x1050 on > >> my laptop and the stack is very long, and obviously I can't scroll > >> it after a kernel panic :-) > >> How can I get to previous lines of it? :-) > > > > There is netconsole: > > https://www.kernel.org/doc/Documentation/networking/netconsole.txt > > > > Although that might not work while suspending. Serial console would > > probably work if the computer has a serial port. If neither of those > > works then you might be able to use a video recording and freeze- > > frame. > > Yeah, the netconsole doesn't work during suspend - I've just checked, > the last line it prints is "Freezing remaining freezable tasks ... > (elapsed 0.01 seconds) done." > > However the 1st time I tried to use netconsole the suspend surprisingly > worked with 3.8 :-) the second time it returned back. So it seems the > bug also isn't 100% reproducible. > > The computer has no serial port. > > And the video is also not an option - I've tried to film it with 60fps > ContourHD, it seems the stack trace is printed very fast. > > It would be good to have some delay after printing each line of stack > trace in the kernel - is there such an option? No, but I think this kernel parameter will help: pause_on_oops= Halt all CPUs after the first oops has been printed for the specified number of seconds. This is to be used if your oopses keep scrolling off the screen. (How have I not noticed this in all the years I've been crashing kernels?!) Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.
Attachment:
signature.asc
Description: This is a digitally signed message part