From: Michael Tokarev <mjt@tls.msk.ru>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: tickless/dynticks + cpufreq = tsc unstable
Date: Sat, 26 Jan 2008 02:02:46 +0300 [thread overview]
Message-ID: <479A6A96.7060805@msgid.tls.msk.ru> (raw)
Is it normal that once I enable cpufreq on
a tickless system, it spews a warning:
Clocksource tsc unstable (delta = -288201154 ns)
?
It's an old problem, and I was thinking about
differences between x86-64 (it worked there) and
i386 kernels. But with 2.6.24, x86-64 can run
tickless as well, and once I enable this mode,
and load dynamic cpufreq governor, the above message
gets printed too.
The system is amd x2-64, all kernels since tickless
has been introduced.
I'm not sure if it's really something to worry about --
probably not, as this system has hpet. But on another
system, Intel-based, where there was no hpet and jiffies
clocksourse gets selected instead, there were some...
issues still (I don't remember offhand which ones, will
check the next week with new kernel).
Thanks!
/mjt
next reply other threads:[~2008-01-25 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 23:02 Michael Tokarev [this message]
2008-01-25 23:29 ` Lee Revell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=479A6A96.7060805@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome