Problems with clock on 1.1-CURRENT

[Matthew Dillon]

:Re-syncing the clock is not the problem.  :)  Having a CPU that is
:running at hyperspeed and causing heat problems is.  When the system
:clock starts running faster, the whole system starts running faster. 
:I've watched the P166 run through a buildworld in very little time
:(around 30 minutes wall time).  The resulting binaries don't work,
:though.  Not to mention the system becomes unusable as things like
:screensaver timeouts are in the sub-minute (wall time) range.
:
:Once the clock is out-of-sync like that, the only solution is to
:reboot the system.  Otherwise, heat buildup will most likely kill it.
:
:-- 
:Freddie Cash, CCNT CCLP        Helpdesk / Network Support Tech.
    
    Well, I'm pretty sure it isn't running at hyperspeed.  A pentium 
    166 doesn't really have any low power / clock enhancement modes
    that DragonFly could twiddle anyway.

    But the clock issue is one I'd like to solve.  There's something
    going on somewhere but I haven't yet been able to reproduce it
    the problem.

    When you are experiencing the clock issue are you doing anything that
    might trigger BIOS calls, such as video bios calls or ACPI events
    (sleep mode, that sort of thing) ?  Or does it appear to solely be 
    triggered by a heavy load?

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>