linux-kernel - Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1163014620.8335.46.camel@localhost.localdomain>
Date:	Wed, 08 Nov 2006 20:36:59 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andreas Mohr <andi@...x01.fht-esslingen.de>
Cc:	Ingo Molnar <mingo@...e.hu>, Len Brown <lenb@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required)
	[2.6.18-rc4-mm1]

On Tue, 2006-11-07 at 23:27 +0100, Andreas Mohr wrote:
> I applied the patch, the changes *are* in the tree and I did create and
> install a new image (with CONFIG_NO_HZ re-enabled and C1 hard-wiring removed),
> but it failed again, completely. The usual hang during boot with
> keyboard activity required, and then it didn't even manage to finish booting
> (I probably was too slow in generating the necessary amount of events).
> 
> Let me think a bit about that stuff, maybe I'll be able to figure out what's
> happening on my system. Or any other ideas?
> (since I would like to somehow get this resolved without less than perfect
> workarounds if possible)

Yes, I'm going to drop the detection as it can never be perfect and
enforce the PIT usage on UP boxen, as it seems that the lapic / BIOS
crap is more or less unfixable. Working on a patch against rc5-mm1 right
now.

	tglx


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