`system clock stops operating' problem from 4-months old system.
qhwt+dfly at les.ath.cx
Sat Jul 2 07:00:48 PDT 2005
I have three machines which have been running DragonFly-Stable
(i.e. pre-RELEASE systems) for about 124 days or so until it stopped
updating the system clock. Kernels are built from sources as of
15th of February this year. Unfortunately, I had to reboot them and
update to the latest RELEASE as they are used as production servers,
so I can't give much data for investigating possibly remaining bugs.
When I logged into these machines, date(1) shows the same time for a long
time(or probably not updating at all), and the number from
vmstat -i |grep ^clk
didn't change. I believe that the commit at 2005/03/27 11:25:10 PST
should have fixed the bug(which means RELEASE have that fix too), right?
More information about the Bugs