Date: Mon, 30 Nov 1998 23:08:52 +0800 From: Peter Wemm <peter@netplex.com.au> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Mike Smith <mike@smith.net.au>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_clock.c Message-ID: <199811301508.XAA11566@spinner.netplex.com.au> In-Reply-To: Your message of "Mon, 30 Nov 1998 15:31:46 %2B0100." <12215.912436306@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote: > In message <199811301410.GAA03905@dingo.cdrom.com>, Mike Smith writes: > >> In message <199811301338.FAA03590@dingo.cdrom.com>, Mike Smith writes: > >> >> phk 1998/11/29 12:31:03 PST > >> >> > >> >> Modified files: > >> >> sys/kern kern_clock.c > >> >> Log: > >> >> Make the previous behaviour the default, add a sysctl which you > >> >> can set if your hw/sw produces the "calcru negative..." message. > >> > > >> >The sysctl should be automatically set by the "calcru negative ..." > >> >detection code. > >> > >> No, because at that time you clock has already been warped out of > >> shape. People need to know and be aware that their sw/hw has a problem. > > > >Since we can't do this except by screwing up, and for that one time you > >can fudge things so that they're not fatal, I think this is a better > >approach. > > No. I have no way from the kernel to make the change persistent, so > it would have to mess up once per boot. I've come in late, so please forgive me if I'm missing something.. Why is repeating: calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... calcru: negative time .... [.. etc etc ...] over and over again better than doing this once: calcru: negative time .... WARNING: switching timecounter to slightly slower method. Set the sysctl 'kern.timecounter.method' 1 at boot to make this permanent (see /etc/rc.conf). I know what I'd prefer, and I know which one will generate less bug reports and PR's. After all, we stop printing 'stray interrupt' messages after the first few etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811301508.XAA11566>