linux-kernel - Re: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES

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: <463910BF.9050103@rtr.ca>
Date:	Wed, 02 May 2007 18:29:19 -0400
From:	Mark Lord <lkml@....ca>
To:	tglx@...utronix.de
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Walker <dwalker@...sta.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of	CONFIG_NO_HZ,
 CONFIG_HIGH_RES_TIMERS

Oh crap.  It's back.

I don't know what's different from before,
but the system now locks up again exactly the same way,
even with the lock contention fix applied.

With or without CONFIG_PROVE_LOCKING=y in the config.

I've gotta get some work done here (this is my primary development machine),
so it's back to CONFIG_DETECT_SOFTLOCKUP=y for a while.

If anyone has a patch to dump out state/whatever just before that
last message that preceeds all lockups, then pass it along and
I'll queue it up for testing as soon as I can.

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