Date: Tue, 30 Jun 1998 20:23:02 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: John Hay <jhay@mikom.csir.co.za> Cc: freebsd-smp@FreeBSD.ORG Subject: Re: time problem? Message-ID: <15031.899230982@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 30 Jun 1998 20:15:28 %2B0200." <199806301815.UAA19361@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
>I followed Tony Li's advice and started ntpd again on the machine with >no local reference clocks and the machine has now been up for more than >24 hours with no jumps at all, so it looks like it is calling nanotime() >from within the sio interrupt that causes the problems. :-( yes, that may not be entirely safe to do according to Bruce. >So what are my options then? Can I somehow run the sio interrupts at >a lower priority? I would really prefer to have the pps signal on the >serial port, because the port is already used to read the serial stream >from the GPS. I don't know :-) You're entering territory here where I have not yet managed to venture... I pressume you havn't used the PPS_SYNC stuff in the kernel (if not: don't!) And it doesn't happen if you run !SMP with the TSC timecounter, right ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15031.899230982>