linux-kernel - Re: Regression in TSC unstable -- confirmed

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: <200905110226.50115.elendil@planet.nl>
Date:	Mon, 11 May 2009 02:26:48 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-kernel@...r.kernel.org
Cc:	Steven Rostedt <rostedt@...dmis.org>, len.brown@...el.com,
	mingo@...e.hu, tglx@...utronix.de, johnstul@...ibm.com
Subject: Re: Regression in TSC unstable -- confirmed

I'm seeing the same issue with 2.6.30-rc5 (not tested previous RCs on that 
box) on a system for which TSC has always been usable.

$ dmesg | grep TSC
Fast TSC calibration using PIT
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Marking TSC unstable due to TSC halts in idle

The last line is new with 2.6.30. After reverting a71e4917dc0 the TSC 
works fine again.

The system has a Intel D945GCZ mainboard with dual core Pentium D 
(3.20GHz) processor running x86_64 and Debian Lenny.

Cheers,
FJP

(Thanks to Steven for doing the bisection.)
--
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/