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] [day] [month] [year] [list]

Message-ID: <4640C589.7010105@rtr.ca>
Date:	Tue, 08 May 2007 14:46:33 -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

Mark Lord wrote:
> Thomas Gleixner wrote:
>> ..
>> I try to come up with something, but I'm travelling tomorrow, so it
>> might be not before end of week.
> 
> Thanks, Thomas.
> 
> I believe we definitely want to nail this down before 2.6.22-final,
> but there's a good workaround in the interim (CONFIG_DETECT_SOFTLOCKUP=y)
> and we've got at least a couple of months 'till then.
> 
> I think I may have fiddled with the RTC config, so I'll compare with my
> old config and see what changed.

Okay.  I turned on CONFIG_COMPAT_VDSO=y and now the system fails to start up
in the same way/place as before.

Rebuilding again with CONFIG_COMPAT_VDSO not set, and all is as "well" as
before -- system starts up so long as CONFIG_DETECT_SOFTLOCKUP=y is given.

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/