From owner-freebsd-current Sun Nov 29 09:27:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15770 for freebsd-current-outgoing; Sun, 29 Nov 1998 09:27:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iworks.interworks.org (iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15763; Sun, 29 Nov 1998 09:27:11 -0800 (PST) (envelope-from deischen@iworks.interworks.org) Received: (from deischen@localhost) by iworks.interworks.org (8.8.7/8.8.7) id LAA00207; Sun, 29 Nov 1998 11:40:48 -0600 (CST) Date: Sun, 29 Nov 1998 11:40:48 -0600 (CST) From: "Daniel M. Eischen" Message-Id: <199811291740.LAA00207@iworks.interworks.org> To: bde@zeta.org.au, majordom@FreeBSD.ORG Subject: Re: kern_clock.c (was: video mode switching has gone south) Cc: current@FreeBSD.ORG, elias@cnetworks.net, green@unixhelp.org, phk@FreeBSD.ORG, seggers@semyam.dinoco.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. Well, it affects my laptop also (Intel Pentium 200MHz MMX). I do not run xntpd, but I am running the kernel at HZ=1000. Dan Eischen deischen@iworks.InterWorks.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message