Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Sep 1997 12:45:37 -0700
From:      Wayne Scott <wscott@ichips.intel.com>
To:        freebsd-smp@freebsd.org
Subject:   SMP kernel loses timer interrupts
Message-ID:  <199709241945.MAA06356@pdxlx008.jf.intel.com>

next in thread | raw e-mail | index | archive | help

This is probably obvious when you think about it, but I am finding
that when I run a SMP kernel under heavy load I lose a lot of timer
interrupts.

I started running xntpd the other night and it locked on a tracked 
our GPS reciever very closly.  But during the day when I started 
using the machine for very heavy cpu work I found that xntpd
was totally unable to keep the clock synchronized.

Sep 24 11:04:38 pdxlx008 xntpd[842]: Previous time adjustment didn't complete
Sep 24 11:20:18 pdxlx008 xntpd[842]: time reset (step) 3.634986 s
Sep 24 11:27:46 pdxlx008 xntpd[842]: time reset (step) 1.293589 s
Sep 24 11:35:14 pdxlx008 xntpd[842]: time reset (step) 1.291778 s
Sep 24 11:42:42 pdxlx008 xntpd[842]: time reset (step) 0.858847 s
Sep 24 11:50:10 pdxlx008 xntpd[842]: time reset (step) 1.226982 s
Sep 24 11:57:38 pdxlx008 xntpd[842]: time reset (step) 1.285231 s
Sep 24 12:05:06 pdxlx008 xntpd[842]: time reset (step) 1.092863 s
Sep 24 12:12:34 pdxlx008 xntpd[842]: time reset (step) 1.336681 s
Sep 24 12:18:58 pdxlx008 xntpd[842]: time reset (step) 0.861123 s
Sep 24 12:26:00 pdxlx008 xntpd[842]: Previous time adjustment didn't complete

If fact on two occasions xntpd got so confused that it just stopped my
system clock.  The date was 4:51:36 for 12 hours.  'gmake' really
doesn't work well when time stops.

I hope this will be fixed when FreeBSD support multiple kernel locks.

I am current running with the 8/27 kernel.  I also tried the ~9/11
kernel.

-Wayne




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709241945.MAA06356>