> Not really, but the values are making *huge* jumps back and forth, so
> it's not just a matter of missing some interrupts in your case.
>
> > Is this really a problem? how can I squelch it?
>
> It does seem to be a problem. It may be a hardware problem with your
> timekeeping source. Try chan
Jason <[EMAIL PROTECTED]> writes:
> and I see
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE
> but this info seems to only apply to 4.x.
Not really, but the values are making *huge* jumps back and forth, so
it's not just a matter of missing some interrup
hey folks..
Im running on a compaq proliant dual 733Mhz computer with 1 gig o memory..
I was running 5.4-STABLE a few weeks ago with no problem.. I did a make world
about a
week ago, and now I see lots of messages in syslog..
Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from
On Monday, 2 July 2001 at 15:45:06 -0600, John R. Shannon wrote:
> I'm also experiencing the lockups; 4 today since CVSUPing stable this AM.
>
> /var/run/dmesg.boot:
*sigh* We really need to update our documentation. dmesg was once
important. In this case it's irrelevant. Can you find any
co
