linux-kernel - Re: 2.6.23-rt1 lockup after loading HAL deamon

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: <20071013055922.GB26370@elte.hu>
Date:	Sat, 13 Oct 2007 07:59:22 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Rok Markovic <kernel@...ardia.eu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: 2.6.23-rt1 lockup after loading HAL deamon

* Rok Markovic <kernel@...ardia.eu> wrote:

> I enabled netconsole but I am affraid that it won't help. In 
> attachment I am sending complete log over netconsole. While I was 
> trying to make everything, I got a lockup on linux-2.6.23-rc8, but I 
> am not sure into this. But all lockups happend in VGA console mode. 
> Any ideas.

hm:

[  104.224904] oprofile: using NMI interrupt.

could you disable CONFIG_OPROFILE? Maybe it interferes with the NMI 
watchdog?

how does /proc/interrupts look like shortly after bootup? Does a simple 
"intentional lockup" piece of code, which provokes a hard lockup from 
user-space, get properly zapped by the NMI watchdog (within a minute or 
so):

# cat > lockup.c

int main(void)
{
	iopl(3);
	for (;;)
		asm("cli");
}
Ctrl-D
# make lockup
# ./lockup
<hard hang>

the NMI watchdog should produce a console message similar to:

 BUG: NMI Watchdog detected LOCKUP on CPU0, eip bff12345, registers:
 ...

( if you test ./lockup and get the message properly then i'd suggest a 
  new reboot - i think we inhibit further console output after an NMI 
  printout. )

	Ingo
-
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/