From: Markus Hofmann <markus@gofurther.de>
To: john stultz <johnstul@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.2 - System clock runs too fast
Date: Mon, 23 Feb 2004 14:13:27 +0100 [thread overview]
Message-ID: <200402231413.27757.markus@gofurther.de> (raw)
In-Reply-To: <1076524588.795.28.camel@cog.beaverton.ibm.com>
Hello John
After a recompiling kernel my system clock runs now again too slow. Your patch
helps with a fast running clock but not with a slow clock. Do you have an
idea what to do now?!?
best wishes
Markus
Am Mittwoch, 11. Februar 2004 19:36 schrieb john stultz:
> On Wed, 2004-02-11 at 01:07, Markus Hofmann wrote:
> > Thank you for answering.
> > In the meantime I heard that apm could cause this problem. I tested this
> > by compiling acpi. The result was that the clock runs normal with acpi.
> > But I want to use apm. So I removed the acpi and now the system clock is
> > too slow with only apm.
> >
> > I think this is a very curious thing! :-(
>
> Indeed, normally its ACPI that causes more problems. That's a new one.
>
> I'd be curious how this drift changes using the attached patch.
>
> thanks
> -john
>
> ===== arch/i386/kernel/timers/timer_tsc.c 1.35 vs edited =====
> --- 1.35/arch/i386/kernel/timers/timer_tsc.c Wed Jan 7 00:31:11 2004
> +++ edited/arch/i386/kernel/timers/timer_tsc.c Tue Jan 20 13:22:54 2004
> @@ -226,7 +226,7 @@
> delta += delay_at_last_interrupt;
> lost = delta/(1000000/HZ);
> delay = delta%(1000000/HZ);
> - if (lost >= 2) {
> + if (0 && (lost >= 2)) {
> jiffies_64 += lost-1;
>
> /* sanity check to ensure we're not always losing ticks */
next prev parent reply other threads:[~2004-02-23 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 12:32 2.6.2 - System clock runs too fast Markus Hofmann
2004-02-10 19:48 ` john stultz
2004-02-11 9:07 ` Markus Hofmann
2004-02-11 18:36 ` john stultz
2004-02-20 12:13 ` Markus Hofmann
2004-02-23 13:13 ` Markus Hofmann [this message]
2004-02-23 20:31 ` john stultz
2004-03-02 14:15 ` Markus Hofmann
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=200402231413.27757.markus@gofurther.de \
--to=markus@gofurther.de \
--cc=johnstul@us.ibm.com \
--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