public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Hofmann <markus@gofurther.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.2 - System clock runs too fast
Date: Tue, 10 Feb 2004 13:32:26 +0100	[thread overview]
Message-ID: <200402101332.26552.markus@gofurther.de> (raw)

Hello together

I've a problem with my system clock. It runs too fast. In realtime 5 minutes 
my notebook runs 8 minutes. The BIOS-Time doesn't run.
With kernel 2.4.24 everything is ok but when I boot my new 2.6.2 the clock 
runs.

Could it be that the compiled speedstepping caused this problem?
Or is there an another causing?

My system: IBM A31p, Kernel 2.6.2, Debian unstable

I already tried "adjtimex --adjust", but I only get the following lines:

--------------
                                           --- current ---    -- suggested --
cmos time     system-cmos       2nd diff    tick      freq     tick      freq
1076412437     3618.069962    3618.069962   10000 -31571705
1076412444     3620.461976       2.392014   10000 -31571705
1076412451     3622.920983       2.459007   10000 -31571705     7536   1149088
1076412458     3625.488963       2.567980   10000 -31571705     7427   1326036
1076412467     3629.007896       3.518933   10000 -31571705     6476   1637419
adjtimex: Invalid argument
---------------

I hope someone can help me!

regards 
Markus

             reply	other threads:[~2004-02-10 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 12:32 Markus Hofmann [this message]
2004-02-10 19:48 ` 2.6.2 - System clock runs too fast 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
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=200402101332.26552.markus@gofurther.de \
    --to=markus@gofurther.de \
    --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