From owner-freebsd-stable Mon Oct 23 9:24:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 235BE37B479 for ; Mon, 23 Oct 2000 09:24:49 -0700 (PDT) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id B492C68; Mon, 23 Oct 2000 11:24:48 -0500 (CDT) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 194C55E0C; Mon, 23 Oct 2000 11:24:41 -0500 (CDT) To: Blaz Zupan Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System clock out of control In-reply-to: "Mon, 23 Oct 2000 17:37:48 +0200." Date: Mon, 23 Oct 2000 11:24:41 -0500 From: Patrick Hartling Message-Id: <20001023162441.194C55E0C@tomservo.vrac.iastate.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan wrote: } > } > 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. That fixed it. Thanks, Blaz! So now I have to wonder why this fixed the problem? Is this a sign of some other problem, or is it just something that is an issue with non-Intel i386 hardware? -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message