From owner-freebsd-stable Thu Apr 8 7: 6:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 817FC15A77 for ; Thu, 8 Apr 1999 07:06:37 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA24118; Thu, 8 Apr 1999 23:04:31 +0900 (JST) Message-ID: <370CB613.EB3A544C@newsguy.com> Date: Thu, 08 Apr 1999 22:58:43 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mark Powell Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Real time clock problem in 3.1-STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Powell wrote: > > Something to do with the kernel not understanding the Real Time Clock > hardware properly? Checking through the ntp logs I note that for one time > whilst the machine was up the time was getting set correctly. However, > after the next reboot the clock was drifting again. There is one sysctl that is related to the clock. You'll find a reference to it in LINT, I *think* near the APM stuff. I suggest you try tweaking this sysctl. As for securelevel and lack of APM in your BIOS, your response indicates the problem isn't related to either. This is as far as I can help you. If the sysctl stuff doesn't help, either someone else steps up, or I suggest you file a PR. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "nothing better than the ability to perform cunning linguistics" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message