From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <95dfc7de0611241859i3c9a443bu40aaeba5116d6275@mail.gmail.com>
Date: Sat, 25 Nov 2006 02:59:36 +0000
From: "Myron Cheung" <onyx.peridot@gmail.com>
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_99465_10942067.1164423576152"
Subject: [9fans] incorrect system time
Topicbox-Message-UUID: e68bce8a-ead1-11e9-9d60-3106f5b1d025

------=_Part_99465_10942067.1164423576152
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 just wonder why I never had this problem with the older version of
plan9.  If both versions show similar behavior, I would be more inclined to
put the blame on qemu.

I shall much appreciate any insight from a more experienced user of
developer of plan9.

------=_Part_99465_10942067.1164423576152
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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.&nbsp; However, I never had this problem when I ran an older version of plan9 (about 3 years older).&nbsp; I searched through the archive of 9fans, and there were some mention of a similar clock drift problem on other platforms.&nbsp; Anyways, I checked /dev/rtc and /dev/time.&nbsp; It appears that /dev/rtc is correct while /dev/time is way off.&nbsp; If I do &quot;cat /dev/rtc &gt; /dev/time&quot;, the clock gets reset to its correct value, but after a few minutes, it reverts back to an incorrect value.&nbsp; I just wonder why I never had this problem with the older version of plan9.&nbsp; If both versions show similar behavior, I would be more inclined to put the blame on qemu.&nbsp;
<br><br>I shall much appreciate any insight from a more experienced user of developer of plan9.<br>

------=_Part_99465_10942067.1164423576152--