linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Clock drift on an iBook2
Date: Tue, 17 Jul 2001 13:04:25 -0400	[thread overview]
Message-ID: <20010717130425.G22214@localhost.localdomain> (raw)
In-Reply-To: <20010717165032.5490@smtp.adsl.oleane.com>; from benh@kernel.crashing.org on Tue, Jul 17, 2001 at 06:50:32PM +0200

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Benjamin Herrenschmidt spake unto us the following wisdom:
> >I have a new iBook2 and I'm having *severe* clock drift problems -- on
> >the order of several seconds gained per minute.  I'd like to get this
> >taken care of, and it seems to be a linux problem as OSX appears to
> >have a stable clock.
> 
> Are you using MOL or do you experience this with nothing special running ?

Nothing special...   I tried using ntpd to fix the problem, but it
didn't seem to be able to set the system time and I'm not sure why.

> Do you have the same issue if you disable powersave_nap (/proc/sys/
> kernel/powersave_nap) ?

Yes, it seems to make no difference.  (~4s of drift in 3 minutes
either way, according to the tests I just did)

> The TB is calibrated using the VIA, if we don't have a correct VIA frequency
> or if the calibration routine is slightly off, that may also explain the
> problem.

Looking into your next email regarding the VIA...
Ethan

-- 
If I've told you once, I've told you once
And once is all that you needed.
		-- The Refreshments, "Carefree"

[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]

  parent reply	other threads:[~2001-07-17 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 14:27 Clock drift on an iBook2 Ethan Blanton
2001-07-17 16:50 ` Benjamin Herrenschmidt
2001-07-17 16:52   ` Benjamin Herrenschmidt
2001-07-17 17:32     ` Ethan Blanton
2001-07-17 17:04   ` Ethan Blanton [this message]
2001-07-17 17:14     ` Tom Rini
2001-07-17 17:16       ` Ethan Blanton

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=20010717130425.G22214@localhost.localdomain \
    --to=eblanton@cs.ohiou.edu \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).