linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Torben Mathiasen <torben@kernel.dk>
To: akuster@mvista.com
Cc: Torben Mathiasen <torben@kernel.dk>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: RTC drift on Walnut?
Date: Mon, 9 Jul 2001 18:17:20 +0200	[thread overview]
Message-ID: <20010709181719.A798@fry> (raw)
In-Reply-To: <3B4971C3.2ADEAF79@mvista.com>; from akuster@mvista.com on Mon, Jul 09, 2001 at 01:56:35AM -0700


tn Mon, Jul 09 2001, akuster@mvista.com wrote:
> Torben Mathiasen wrote:
> >
> > Hi,
> >
> > I'm seeing a rather large drift of the RTC on a Walnut system. I haven't
> > got the exact numbers, but its something like 20mins in 24 hours.
> > This is with the montavista 2.4.2 kernel.
> >
> > Has anyone seen this before?
> >
> > Thanks in advance,
> >
> > Torben
> >
>
> Torben;
>
> I am not sure.  I will have to check, I will let you know tomorrow.

Thanks. I'm pretty sure its kernel related, I bet something's wrong in
arch/ppc/kernel/time.c. The kernel just reads the RTC at startup, and maintains
the system clok via the timer-interrupts. Coming to think of it, I'm not sure
if the hardware RTC drifts, or if its just the kernel 'software' clock. Will
check on that.

Maybe we're turning ints off for too long somewhere...

Thanks,
Torben

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-09 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 20:09 RTC drift on Walnut? Torben Mathiasen
2001-07-09  8:56 ` akuster
2001-07-09 16:17   ` Torben Mathiasen [this message]
2001-07-10 16:43     ` Armin Kuster
2001-07-10 17:25       ` Torben Mathiasen
  -- strict thread matches above, loose matches on Subject: below --
2001-07-10 17:29 Wright, David
2001-07-10 17:45 ` Torben Mathiasen
2001-07-13  0:12   ` Mark A. Greer
2001-07-13  0:15   ` Mark A. Greer

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=20010709181719.A798@fry \
    --to=torben@kernel.dk \
    --cc=akuster@mvista.com \
    --cc=linuxppc-embedded@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).