linux-kernel - Re: Panic 2.6.24-3 NMI Watchdog detected LOCKUP on CPU 0

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.1.00.0803011527410.11084@apollo.tec.linutronix.de>
Date:	Sat, 1 Mar 2008 15:29:03 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ed Tomlinson <edt@....ca>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Panic 2.6.24-3 NMI Watchdog detected LOCKUP on CPU 0

On Sat, 1 Mar 2008, Ed Tomlinson wrote:
> Hi,
> 
> I have been seeing these since I installed .24 kernels.  It does not seem to matter if I change the clocksource from tsc
> to apci_pm.  Its happened with all .24 kernels I have tried starting with stock 2.6.24 upto 2.6.24-gentoo-r2 + 2.6.24-3
> 
> Ideas?

Questions first. Is there a particular reason to use idle=poll ?

Idea: does the patch below help ?

Thanks,
	tglx

---

 arch/x86/kernel/process_64.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

Index: linux-2.6.24/arch/x86/kernel/process_64.c
===================================================================
--- linux-2.6.24.orig/arch/x86/kernel/process_64.c
+++ linux-2.6.24/arch/x86/kernel/process_64.c
@@ -212,14 +212,13 @@ void cpu_idle (void)
 	current_thread_info()->status |= TS_POLLING;
 	/* endless idle loop with no priority at all */
 	while (1) {
+		tick_nohz_stop_sched_tick();
 		while (!need_resched()) {
 			void (*idle)(void);
 
 			if (__get_cpu_var(cpu_idle_state))
 				__get_cpu_var(cpu_idle_state) = 0;
 
-			tick_nohz_stop_sched_tick();
-
 			rmb();
 			idle = pm_idle;
 			if (!idle)
--
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/