linux-kernel - Re: HPET causes tasks to freeze (still in 2.6.36-rc6)

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: <alpine.LFD.2.00.1010041747550.14550@localhost6.localdomain6>
Date:	Mon, 4 Oct 2010 18:31:23 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jiri Slaby <jslaby@...e.cz>
cc:	LKML <linux-kernel@...r.kernel.org>, clemens@...isch.de,
	venki@...gle.com, the arch/x86 maintainers <x86@...nel.org>
Subject: Re: HPET causes tasks to freeze (still in 2.6.36-rc6)

On Mon, 4 Oct 2010, Jiri Slaby wrote:

> Hi,
> 
> HPET as a clocksource has still issues in the latest kernels (confirmed
> in 2.6.36-rc6) at least on x86_64. Unless clocksource=jiffies,
> clocksource=tsc or nolapic_timer is used, the system is unusable. Tasks
> are not woken unless mouse is moved, key is pressed (or other hard irq
> triggered). 2.6.32 seems to be the last working.

The problem is not clocksource related, it's NOHZ related.

clocksource=jiffies, clocksource=tsc are disabling NOHZ simply because
we can not do NOHZ neither with jiffies nor with a TSC which stops in
deeper C-states.

nolapic_timer installs a dummy lapic timer so the lapic is not used,
but HPET is used instead and NOHZ is disabled as well.

So the real problem is that the hpet broadcast interrupts which are
used to work around the lapic timer stops in C3 problem are not coming
through for whatever reason.

So the question is what changed in the ACPI/idle NOHZ code which might
expose this problem.

Can we get dmesg, output of proc/timer_list and output of
/proc/acpi/processor/CPU0/power for a .32 and a non working kernel
please ?

> "My clock is seriously lagging behind. After having used hpet for 10.5
> hours now, the clock is 5.5 hours too late!"

That's probably a side effect.

> dmesg is attached. Any ideas what's still wrong with HPET?

Nothing as far as I can tell :)

Thanks,

	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/