From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <536e347f7c2fe951277441d936cfa9bc@vitanuova.com>
To: 9fans@cse.psu.edu
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] odd clock behaviour
Date: Thu, 13 Mar 2003 14:25:37 +0000
Topicbox-Message-UUID: 7f642cbc-eacb-11e9-9e20-41e7f4b1d025

has anyone else experienced odd clock behaviour on their plan 9
system?

i'm running on an IBM Thinkpad (T22), and occasionally (not always) i
get the clock running much faster than it should (#r/rtc still gives
the correct time)

as an example (i ran this a few minutes ago):
% echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1047563747 1047629025 1047629025597639124 41354973397504 305454592
1047563792 1047629508 1047629508199623282 41502386389760 305454592
% % echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1047563991 1047632392 1047632392826308124 42383508857344 305454592
1047564039 1047632728 1047632728118785531 42485925484288 305454592
% % % echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1047564093 1047633210 1047633210610709377 42633304858112 305454592
1047564136 1047633742 1047633742398391924 42795741847808 305454592
%

i.e.  /dev/time advanced by 483, 336 and 532 seconds respectively,
while #r/rtc advanced by 45, 48 and 43 seconds respectively,
all for a nominally 100 second sleep!

the power has been plugged in continuously (i.e.  it shouldn't have
invoked any funny power-saving clock changing).

this leads to some odd effects on the user interface, not to mention
the fact that date(1) now thinks it's 11:18am tomorrow...

  cheers,
    rog.