Date: Mon, 23 Oct 2000 11:24:41 -0500 From: Patrick Hartling <patrick@137.org> To: Blaz Zupan <blaz@amis.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: System clock out of control Message-ID: <20001023162441.194C55E0C@tomservo.vrac.iastate.edu> In-Reply-To: "Mon, 23 Oct 2000 17:37:48 %2B0200." <Pine.BSF.4.21.0010231737100.83266-100000@titanic.medinet.si>
next in thread | previous in thread | raw e-mail | index | archive | help
Blaz Zupan <blaz@amis.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023162441.194C55E0C>