DragonFly BSD
DragonFly bugs List (threaded) for 2004-07
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Problems with clock on 1.1-CURRENT

From: Freddie Cash <fcash-ml@xxxxxxxxxx>
Date: Tue, 27 Jul 2004 20:34:36 -0700

On July 20, 2004 09:20 am, Freddie Cash wrote:
> >     I'll do you one better... I just committed some in-kernel timer
> >     diagnostics.  The kernel will now unconditionally report its
> > timer calibration at boot (dmesg | fgrep clock), and, even better,
> > I added a sysctl which will dump the current 8254 timer 2 counter
> > which is used as a basis for system timing, and it will even throw
> > in the TSC if there is one.

> >     So if you cvsup, update, compile up a new kernel and reboot, we
> >     can hopefully diagnose some of these issues.

> Building world now.  I'll post results of the script in about an hour
> or so after everything is updated and running again.

I cvsup'd the source Tuesday or Wednesday of last week (around the 
20th), rebuilt the world and kernel, and have not been able to 
reproduce the clock going crazy.

I've tried running multiple buildworlds concurrently.  I've tried 
starting XFree86.  I've tried starting KDE (locks the system up solid, 
requiring a hard reboot).  I've tried all the things that used to 
trigger the clock going crazy, and I have not been able to get it to do 

This in on the Celeron laptop.  Haven't had a chance to test it on the 
P166 yet (been laid up with food poisoning and getting my wisdom teeth 
yanked out).  So far, things seem to be chugging along quite nicely.

I had to restore FreeBSD 5.x on the Celeron laptop in order to get some 
things done for work, but I should be able to get it dual-booting with 
DFly on the weekend.

Freddie Cash, CCNT CCLP        Helpdesk / Network Support Tech.
School District 73             (250) 377-HELP [377-4357]

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]