From: "Alexander Beregalov" <a.beregalov@xxxxxxxxx> Date: Wed, 12 Nov 2008 03:09:54 +0300 > 2008/11/12 David Miller <davem@xxxxxxxxxxxxx>: > > From: Alexander Beregalov <a.beregalov@xxxxxxxxx> > > 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. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
