From owner-freebsd-bugs Sun Dec 6 17:20:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27924 for freebsd-bugs-outgoing; Sun, 6 Dec 1998 17:20:02 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27878 for ; Sun, 6 Dec 1998 17:20:00 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from Unknown UID 563@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id RAA08628; Sun, 6 Dec 1998 17:20:00 -0800 (PST) Date: Sun, 6 Dec 1998 17:20:00 -0800 (PST) Message-Id: <199812070120.RAA08628@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: ortmann@sparc.isl.net Subject: Re:kern/8940:systemclockrunsextremelyslowly(andsiooverflows?) Reply-To: ortmann@sparc.isl.net Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/8940; it has been noted by GNATS. From: ortmann@sparc.isl.net To: freebsd-gnats-submit@freebsd.org, ortmann@sparc.isl.net Cc: Subject: Re:kern/8940:systemclockrunsextremelyslowly(andsiooverflows?) Date: Sun, 6 Dec 1998 19:15:20 -0600 (CST) The patch to fix an apm problem (reportedly #8280) does not affect this time problem. That is, when the following patch is applied: --- apm.c Thu Dec 3 23:09:47 1998 +++ apm.c.new Thu Dec 3 23:09:44 1998 @@ -795,7 +795,7 @@ sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; sc->cs32_limit = apm_cs32_limit - 1; if (apm_cs16_limit == 0) - apm_cs16_limit == apm_cs32_limit; + apm_cs16_limit = apm_cs32_limit; sc->cs16_limit = apm_cs16_limit - 1; sc->ds_limit = apm_ds_limit - 1; sc->cs_entry = apm_cs_entry; (sorry for the extra newlines there) ... the clock still runs slowly (or perhaps stops). This problem is still live. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message