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: <47109008.5090405@kanardia.eu>
Date:	Sat, 13 Oct 2007 11:29:44 +0200
From:	Rok Markovic <kernel@...ardia.eu>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.23-rt1 lockup after loading HAL deamon

Hi

I have recompiled kernel with OPROFILE disabled. I am sending in
attachment /proc/interrupts (i ran it 3 times with 2 sec delay) and
netconsole log. Lockup in the lock is software made with ./lockup.
The kernel still locks 4-5minutes after boot without any further
messages (waited more than 2 minutes). Any ideas?


Rok


Ingo Molnar wrote:
> 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):
> 
> 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
> 
> 



View attachment "interrupts.log" of type "text/x-log" (2602 bytes)

View attachment "kernel.log" of type "text/x-log" (27166 bytes)