From: "Myron Cheung" <onyx.peridot@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] incorrect system time
Date: Sat, 25 Nov 2006 03:24:33 +0000 [thread overview]
Message-ID: <95dfc7de0611241924x4aed79f3v701593e2dc2ae7fa@mail.gmail.com> (raw)
In-Reply-To: <13426df10611241913h18b1c943kdf98ed8079088c80@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
By the way, I also tried the most recent version of plan9.iso on a Dell PC
(celeron 2.8GHZ), the clock comes up correct.
On 11/25/06, ron minnich <rminnich@gmail.com> wrote:
>
> On 11/24/06, Myron Cheung <onyx.peridot@gmail.com> wrote:
> > I downloaded the plan9.iso a few days ago, and when I load it up in
> qemu,
> > the system time is off by more than 6 years. However, I never had this
> > problem when I ran an older version of plan9 (about 3 years older). I
> > searched through the archive of 9fans, and there were some mention of a
> > similar clock drift problem on other platforms. Anyways, I checked
> /dev/rtc
> > and /dev/time. It appears that /dev/rtc is correct while /dev/time is
> way
> > off. If I do "cat /dev/rtc > /dev/time", the clock gets reset to its
> > correct value, but after a few minutes, it reverts back to an incorrect
> > value.
>
> I am still seeing the same problem. I think I fixed this in Xen by
> taking the clock interrupt but always picking up the value of the time
> from the rtc, but I am not sure. But there is definitely a problem
> here.
>
> ron
>
[-- Attachment #2: Type: text/html, Size: 1534 bytes --]
next prev parent reply other threads:[~2006-11-25 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 2:59 Myron Cheung
2006-11-25 3:13 ` ron minnich
2006-11-25 3:24 ` Myron Cheung [this message]
2006-11-26 16:23 ` Russ Cox
2006-11-26 21:19 ` Myron Cheung
2006-11-26 22:18 ` Russ Cox
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=95dfc7de0611241924x4aed79f3v701593e2dc2ae7fa@mail.gmail.com \
--to=onyx.peridot@gmail.com \
--cc=9fans@cse.psu.edu \
/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).