From: john stultz <johnstul@us.ibm.com>
To: jean-philippe francois <jp.francois@cynove.com>
Cc: Lin Ming <lin@ming.vg>,
venki@google.com, "H. Peter Anvin" <hpa@zytor.com>,
linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
jslaby@suse.cz
Subject: Re: System time drifts when processor idle.
Date: Fri, 27 Aug 2010 11:11:48 -0700 [thread overview]
Message-ID: <1282932708.1946.8.camel@work-vm> (raw)
In-Reply-To: <AANLkTikWTLeDLbWWi-LJDD5SRAFN60v5065Vc_wGoY5N@mail.gmail.com>
On Fri, 2010-08-27 at 16:12 +0200, jean-philippe francois wrote:
> My Timekeeping bug is still present, here is an updated script and log.
> I am willing to make test, but I don't know what kind of debugging
> info is needed.
>
> cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> hpet acpi_pm
> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> hpet
Huh. hpet was not what I would have expected.
So first, two experiments:
1) Does booting with "clock=acpi_pm" cause the issue to disappear?
2) Does booting with "nohz=off" cause the issue to disappear?
Venkatesh: You have any experience with HPETs that halt in idle?
thanks
-john
next prev parent reply other threads:[~2010-08-27 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=ivkOHRYwLy5FDg3RnK18+opjGd9XsxC7yZqi7@mail.gmail.com>
2010-08-21 3:58 ` System time drifts when processor idle Lin Ming
2010-08-23 8:46 ` jean-philippe francois
2010-08-23 22:17 ` john stultz
2010-08-24 7:08 ` jean-philippe francois
2010-08-27 14:12 ` jean-philippe francois
2010-08-27 18:11 ` john stultz [this message]
2010-08-28 0:10 ` Venkatesh Pallipadi
2010-08-28 1:09 ` john stultz
2010-08-28 12:45 ` jean-philippe francois
2010-08-28 15:19 ` Venkatesh Pallipadi
2010-09-02 11:45 ` jean-philippe francois
2010-08-30 8:03 ` jean-philippe francois
2010-09-03 12:23 ` jean-philippe francois
2010-09-09 17:42 ` john stultz
2010-09-13 13:04 ` jean-philippe francois
2010-12-06 12:55 ` jean-philippe francois
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=1282932708.1946.8.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=hpa@zytor.com \
--cc=jp.francois@cynove.com \
--cc=jslaby@suse.cz \
--cc=lin@ming.vg \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venki@google.com \
/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