9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] odd clock behaviour
Date: Thu, 20 Mar 2003 18:07:02 +0000	[thread overview]
Message-ID: <3859f4b0b3967a65f80798d1eef75e10@vitanuova.com> (raw)

i just found my machine in the odd timer state again, so have
the opportunite to play with it a bit more...

presotto:
> Try setting the variable i8253dotimerset to 0 (it's now set to 1).
>	echo off > '#P'/i8253timerset

presumably i should do this at boot time, but i'd never know for sure
whether i'd nailed the problem because it presents itself so rarely.

anyway, it doesn't seem to fix much at run time.  it does change stuff
though:

% echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1048176273 1048211930 1048211930303113804 14857013246208 305454592
1048176320 1048212205 1048212205836287972 14941176119552 305454592
% echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1048176368 1048212488 1048212488976582421 15027662622720 305454592
1048176414 1048212763 1048212763054236813 15111380900864 305454592
% echo -n off > '#P'/i8253timerset
% echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1048176621 1048213988 1048213988275370902 15485630322688 305454592
1048176798 1048214298 1048214298823858727 15580488784384 305454592
% % echo `{cat '#r/rtc'; cat /dev/time; }; sleep 100; echo `{cat '#r/rtc'; cat /dev/time; }
1048176875 1048214418 1048214418231644733 15616962440960 305454592
1048177053 1048214695 1048214695742160153 15701729302272 305454592
%

i.e. before the change, sleep 100 was sleeping for 45 realtime seconds
for 275 seconds elapsed in /dev/time.

after changing i8253timeset, sleep 100 sleeps for 178 realtime seconds
for 277 seconds elapsed in /dev/time.

the timer was running normally when i booted the machine up.

on boot, my processor is reported as a 
996MHz GenuineIntel PentiumIII/Xeon (cpuid: AX 0x068A DX 0x383F9FF)

i had a look in my bios settings for stuff that could be influencing
the timers at runtime.

what we've got (i'm running it on AC):

	Power Mode for AC		Maximum Performance
	(which presumably chooses "Fixed Max" out of the options
	for processor speed of "Fixed Max/Medium/Slow", "Auto Medium/Slow")

	SpeedStep Technology	Automatic
	(which says it's "Maximum Performance" on AC, i.e. always at high speed)

	CPU power management	Automatic
	(says: "enables or disables the power saving feature that stops
	the microprocessor clock automatically when there are no system
	activities.")

the last one seems like a possible culprit, i guess.



             reply	other threads:[~2003-03-20 18:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 18:07 rog [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-13 18:58 rog
2003-03-13 19:15 ` David Presotto
2003-03-13 19:25   ` Russ Cox
2003-03-13 18:43 David Presotto
2003-03-13 18:06 rog
2003-03-13 14:43 rog
2003-03-13 14:25 rog
2003-03-13 14:30 ` Fco.J.Ballesteros
2003-03-13 15:40 ` Russ Cox
2003-03-13 16:22 ` Sam
2003-03-13 16:26   ` David Presotto
2003-03-13 17:06     ` Russ Cox
2003-03-13 17:50       ` Fco.J.Ballesteros
2003-03-13 18:39 ` Dan Cross
2003-03-13 18:40 ` Dan Cross

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=3859f4b0b3967a65f80798d1eef75e10@vitanuova.com \
    --to=rog@vitanuova.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).