lkml.org 
[lkml]   [2008]   [Nov]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: 2.6.28-rc4: BUG: spinlock lockup on CPU#0
From
From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Wed, 12 Nov 2008 02:32:30 +0300

> It is on sparc64 (Ultra 10). 2.6.28-rc4-00011-g3ad4f59
>
> BUG: spinlock lockup on CPU#0, metalog/1322, 00000000007f1430
> Kernel panic - not syncing: Aiee, killing interrupt handler!
>
> It seems Sysrq does not work.
>
> David, how can I provide more info before I reboot it ?
>
> Full dmesg:

Hmm, this BUG message should have given you a register dump and a
backtrace.

Can you give it a "Alt-SysRQ-p" and show the output?

Actually, if you got this over a serial console or
similar, you're not getting the register dump because
the console loglevel is filtering them out.

If that's what's happening, reboot with "ignore_loglevel"
(I always boot with this option, by adding it to the
default kernel command line options in /etc/silo.conf)

Also, in situations where the system is already booted and
you want to see things like the Alt-SysRQ-p register dumps
on the console, you'll need to type something like
"Alt-SysRQ-8" to bump the console log level.


\
 
 \ /
  Last update: 2008-11-12 00:51    [W:0.047 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site