From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: 2.6.28-rc4: BUG: spinlock lockup on CPU#0 Date: Tue, 11 Nov 2008 16:15:09 -0800 (PST) Message-ID: <20081111.161509.104851175.davem@davemloft.net> References: <20081111233230.GC12456@orion> <20081111.154902.11426409.davem@davemloft.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: Text/Plain; charset="us-ascii" To: a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rjw-KKrjLPT3xs0@public.gmane.org From: "Alexander Beregalov" Date: Wed, 12 Nov 2008 03:09:54 +0300 > 2008/11/12 David Miller : > > From: Alexander Beregalov > > 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? > No, sysrq does not work, even Stop-A does not work now. > How could it be. The cpu stuck on the spinlock has interrupts disabled, but this is the cpu that services console interrupts. That's how it could be.