On Fri, 2012-01-06 at 13:56 +0000, Simon McVittie wrote:
> Package: linux-2.6
> Version: 3.1.6-1
> Severity: normal
>
> When left idle, my laptop sometimes (a couple of times a day?) goes into a
> "stuck" state with a crash dump printed to the framebuffer console and the
> caps lock LED flashing. Sometimes the speaker plays a continuous tone.
> I believe this is a kernel panic, but the crash dump is more than one
> screenful, so I can't see the beginning of the message.
>
> While in this state, no input works, including the magic SysRq key.
Right, after a panic the keyboard driver is stopped.
> This sometimes happens while the screen is blanked, in which case I can't
> photograph the crash dump.
>
> This also affects the 3.0.0-2-amd64 kernel, although subjectively it
> seems to be less frequent on this kernel. I haven't tried older kernels
> since this problem started a few days ago; it's also possible that it's a
> hardware error that recently appeared, or something triggered by (say) a
> newer X driver (I'd used 3.0 and 3.1 successfully for a while before this
> started appearing).
>
> Selected information from the 3.0 crash dump, transcribed from a photo
> (may contain errors):
>
> > pid 0, swapper
> > Tainted: G D
[...]
The 'D' flag means that there was a previous failure ('BUG' or 'Oops').
Please send a log of that (which will say 'Not tainted'). It might have
happened immediately before or it might have happened much earlier in
which case it's probably in /var/log/messages.
If the first failure doesn't appear in /var/log/messages then use
netconsole or a serial console to capture it.
Ben.
--
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.
Attachment:
signature.asc
Description: This is a digitally signed message part