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

Hi again!

I tried to boot into VGA mode with NMI watchdog=2. System loads OK,
nmi counter is increasing on both CPUs (procesor is HT), but
when I start to load the CPU (compiling kernel), system locks
without any message. Even blinking cursor disapears. I will
try to do netconsole loging, but I can't promise any results for today.

Rok


Ingo Molnar wrote:
>> I tried to recompile with those options enabled, kernel and linux 
>> boots and loads fine, but after few minutes (if i try to recompile 
>> kernel in console) the system locks completely (hard reset) without 
>> any messages. Is there anything I can do, maybe console on serial 
>> port? My new config is atached.
> 
> yes, serial console (or netconsole) output would be useful, if you can 
> solve that. Another way would be to boot with nmi_watchdog=2, do the 
> kernel recompile in a VGA text console, and wait for the lockup to 
> occur. Either you get some crash message to the text console 
> immediately, or you should get the NMI watchdog print something within a 
> minute or so. If neither happens you just get a blank hard lockup then 
> the wedge is very deep ...
> 
> (also make sure that the NMI counter in /proc/interrupts is increasing 
> on all CPUs properly, with nmi_watchdog=2. If not all CPUs/cores are 
> increasing their NMI counters once per second then the NMI watchdog wont 
> be able to print out a stackdump.)
> 
> 	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/