Re: Problems with clock on 1.1-CURRENT

["Freddie Cash" <fcash-ml@xxxxxxxxxx>]

> Freddie Cash wrote:
>> I've installed 1.0 via the 1.0a installer CD.  CVSup'd to the latest
>> sources yesterday afternoon.  Everything works nicely except for one
>> major problem:  under a "heady load", the clock will go crazy (30
>> seconds on the laptop is less than 1 second on the wall clock) and
>> processes will go into hyperspeed.  "Heavy load" is compiling the
>> world (P166) or loading KDE (Celeron).  Once the clock goes crazy,
>> the laptops are useless and must be rebooted to reset the clock.

> A number of people have reported this bug; it looks like it's a
> problem with the timer code.  I haven't tried this myself, but it may
> be possible to use ntp to resync until the cause is found.

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.
School District 73             (250) 377-HELP [377-4357]
fcash-ml@xxxxxxxxxx