netdev - Re: TSC unstable due to TSC halts in idle?

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: <Pine.LNX.4.64.1005151139280.16599@ask.diku.dk>
Date:	Sat, 15 May 2010 11:54:15 +0200 (CEST)
From:	Jesper Dangaard Brouer <hawk@...u.dk>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	john stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>,
	"Brown, Len" <len.brown@...el.com>,
	"Li, Shaohua" <shaohua.li@...el.com>, "hawk@...x.dk" <hawk@...x.dk>
Subject: Re: TSC unstable due to TSC halts in idle?


On Fri, 14 May 2010, Suresh Siddha wrote:
> On Fri, 2010-05-14 at 15:28 -0700, john stultz wrote:
>> On Fri, May 14, 2010 at 1:13 PM, Jesper Dangaard Brouer <hawk@...u.dk> wrote:
>>> I want to know, if its safe to enable the TSC clocksource, when the
>>> kernel reports:
>>>  "Marking TSC unstable due to TSC halts in idle"
>>>
>>> The system selects HPET (in current_clocksource), but I can still see
>>> TSC as an available clocksource (in
>>> /sys/devices/system/clocksource/clocksource0/available_clocksource).
>>>
>>> Is it safe to enable TSC manually (by changing current_clocksource)?
>>> (my workload is 10Git/s routing, cannot survive with a slow clock)
>>>
>>>
>>> Any trick to avoid this? (e.g. kernel config setting, or a /sys/ setting
>>> which changes the minimum P-state?)
>>
>> Might try booting with the max-cstate=1 option.
>
> Jesper mentioned that it is xeon 5550. TSC's for that processor doesn't
> stop in idle.

Thanks, then it should be safe to force using TSC, even on this older 
kernel.


> Perhaps he is using an older kernel which doesn't detect this fact. 
> Jesper, more recent kernels should be able to use TSC as the 
> clocksource.

Guess this it the problem. As I'm running a standard Debian compiled 
kernel 2.6.26-2-amd64 (which comes with Debian lenny).  I'm not going to 
run with this kernel in production, as it doesn't have multiqueue support 
and doesn't support the NICs I'm using.

I'm already annoyed with this old kernel, as it doesn't support any of the 
NICs in the machine, not even the build in NICs in the HP370 G6 server.

I'll boot a new kernel on the machine Monday, and I'll complain if it 
didn't solve the issue, else consider this issue solved "in a newer kernel 
version".

Cheers,
   Jesper Brouer

--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html