From owner-freebsd-stable Mon Oct 23 8:37:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id B021F37B4C5 for ; Mon, 23 Oct 2000 08:37:49 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id A07D95D21; Mon, 23 Oct 2000 17:37:48 +0200 (CEST) Date: Mon, 23 Oct 2000 17:37:48 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Patrick Hartling Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System clock out of control In-Reply-To: <20001023142346.0823B5E0C@tomservo.vrac.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > } > 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! > > I have started this process, but I have only gotten through one iteration > because I got too tired to work on it last night. ;) Let me help you: try adding back "device apm". It helped me with a simmilar problem on some different hardware. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message