From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
kernel-testers@vger.kernel.org, rjw@sisk.pl
Subject: Re: 2.6.28-rc4: BUG: spinlock lockup on CPU#0
Date: Tue, 11 Nov 2008 15:49:02 -0800 (PST) [thread overview]
Message-ID: <20081111.154902.11426409.davem@davemloft.net> (raw)
In-Reply-To: <20081111233230.GC12456@orion>
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.
next prev parent reply other threads:[~2008-11-11 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 23:32 2.6.28-rc4: BUG: spinlock lockup on CPU#0 Alexander Beregalov
2008-11-11 23:49 ` David Miller [this message]
[not found] ` <20081111.154902.11426409.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-11-12 0:09 ` Alexander Beregalov
[not found] ` <a4423d670811111609l37dcfe6bme277692b5206b5ec-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-12 0:15 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081111.154902.11426409.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox