linux-kernel - Re: BUG: soft lockup detected on CPU#1!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1153747232.4002.81.camel@localhost.localdomain>
Date:	Mon, 24 Jul 2006 09:20:32 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jochen Heuer <jogi-kernel@...netzork.ping.de>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	nathans@....com, xfs@....sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!

On Sat, 2006-07-22 at 00:53 +0200, Jochen Heuer wrote:

> 
> Is there anything I can test? Disable irq balancing? Disabling preemption did
> not help. Disabling IO-APIC? What can I do to help isolate the problem because
> it really is annoying and I don't like pushing the reset button. Because if the
> system locks up *really* nothing works. The screen is frozen, no mouse, no
> keyboard, no sys-rq, no network ... nothing.

Jochen, have you tried to enable NMI?  Make sure you have Local APIC
enabled (you should since it's SMP), and on your kernel command line (in
Grub) add "lapic nmi_watchdog=2". (lapic isn't really needed, but I
always add it so I don't forget to when working on UP machines).

Run it again, and if it locks up hard, which probably means its spinning
somewhere with interrupts disabled, the NMI will trigger and should give
you another dump of where it's locked up.

-- Steve

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/