linux-kernel - Re: Clocksource tsc is always unstable with 2.6.25-* kernels and CONFIG_NO

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: <20080225121440.32810c91.akpm@linux-foundation.org>
Date:	Mon, 25 Feb 2008 12:14:40 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Gabriel C <nix.or.die@...glemail.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Gabriel C <crazy@...galware.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Clocksource tsc is always unstable with 2.6.25-* kernels and
 CONFIG_NO_HZ=y on my box

On Sun, 24 Feb 2008 01:31:21 +0100 Gabriel C <nix.or.die@...glemail.com> wrote:

> Hi,
> 
> I noticed tsc is always marked unstable on my box with 2.6.25* , 2.6.24 is fine.
> 
> ...
> 
> [    0.825760] ACPI: PCI Interrupt 0000:03:0e.0[A] -> GSI 22 (level, low) -> IRQ 22
> [    0.805755] Switched to high resolution mode on CPU 1
> [    0.794244] Switched to high resolution mode on CPU 2
> [    0.766968] Switched to high resolution mode on CPU 3
> [    1.083944] Switched to high resolution mode on CPU 0
> [   15.388792] Clocksource tsc unstable (delta = 9373391604 ns)
> [   15.714648] Time: acpi_pm clocksource has been installed.
> 
> ...
> 
> Booting nohz=off fixes that.
> 
> Another strange thing is when I try to boot that kernel with clocksource=acpi_pm it just hangs.
> 
> config is attached.
> 
> Please let me know if you need more infos / want me to try patches or anything else.
> 
> 

I suppose we should consider this a regression.  If only because acpi_pm is
slower.  But mainly because (afaik) this change was not intentional.
--
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/