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


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

> 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?

no good ideas :-( I suspect this one:

  [  185.600900] hdc: lost interrupt

was a side-effect of lockup.c too?

does the lockup go away if you boot with maxcpus=1?

	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/