From owner-freebsd-stable Mon Oct 23 0:27:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from us66.grant.org (us66.grant.org [213.39.2.177]) by hub.freebsd.org (Postfix) with ESMTP id 5F14F37B4CF for ; Mon, 23 Oct 2000 00:27:18 -0700 (PDT) Received: from splat.grant.org (splat [213.39.2.179]) by us66.grant.org (8.9.3+Sun/8.9.1) with ESMTP id JAA15413; Mon, 23 Oct 2000 09:27:10 +0200 (MET DST) Received: (from mgrant@localhost) by splat.grant.org (8.9.3+Sun/8.9.1) id JAA04525; Mon, 23 Oct 2000 09:27:05 +0200 (MET DST) Date: Mon, 23 Oct 2000 09:27:05 +0200 (MET DST) Message-Id: <200010230727.JAA04525@splat.grant.org> From: Michael Grant To: Patrick Hartling Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System clock out of control Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This says something! If you don't have this problem with a GENERIC kernel, then the thing to try (yes, I know this is tedious) is to start adding/removing things one-by-one from GENERIC until it looks like the kernel that fails. This should make it obvious what is causing it to do this and that would be very helpful info indeed! -Mike Patrick Hartling wrote: > I tried adding these options, but it unfortunately didn't help. Now > the CPU is being reported as running at 18.08 MHz. I have played around > with some of the Cyrix-specific options in LINT that are not noted as > being dangerous, but nothing is helping. :( What I really don't > understand is how GENERIC works fine with no extra options. I must be > missing something simple... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message