From owner-freebsd-current Sun Nov 29 08:39:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12033 for freebsd-current-outgoing; Sun, 29 Nov 1998 08:39:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gravy.kishka.net (dyn-3.blackbox-2.netaxs.com [207.106.60.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12027; Sun, 29 Nov 1998 08:39:20 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (gravy.kishka.net [10.0.0.1]) by gravy.kishka.net (8.9.1/8.8.8) with ESMTP id LAA00310; Sun, 29 Nov 1998 11:38:32 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sun, 29 Nov 1998 11:38:31 -0500 (EST) From: Bryan Liesner To: Bruce Evans cc: elias@cnetworks.net, seggers@semyam.dinoco.de, current@FreeBSD.ORG, green@unixhelp.org, phk@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) In-Reply-To: <199811291450.BAA24073@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, Bruce Evans wrote: <> It actually sleeps for an average of about half a second. <> <> Everything that uses get{micro,nano}{,up}time (mainly timeouts) is broken <> because the time reported by these functions now lags the actual time <> by up to about 1 second. <> <> Ignore the `force' flag to go back to the previous brokenness which <> affects relatively few systems. <> <> Bruce After running a kernel compiled with kern_clock.c revision 1.85 I noticed some problems: Switching to X is sluggish and takes a few seconds where it used to be almost instantaneous. While running X, xlock's screen savers slow down to a crawl, and hitting a key to stop the screen saver can take up to ten seconds. I run xntpd, and got a large amount of "the previous time adjustment did not complete" errors. My system is running a Cyrix 686MX PR266, so this doesn't seem to be limited to the AMD processors. Applying the patch to ignore the 'force' flag seems to have cleared this up. Can anything "bad" happen using this patch? Is there a better solution in the works? ========================================================== = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = bleez@netaxs.com Home of the Gipper = ========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message