Date: Tue, 20 May 2003 02:05:00 +0530 From: Shantanu Mahajan <freebsd@dhumketu.cjb.net> To: Christopher Rosado <chris@tophnet.net> Cc: freebsd-questions@freebsd.org Subject: Re: mircouptime()??? Message-ID: <20030519203500.GB37777@dhumketu.homeunix.net> In-Reply-To: <200305190403.24229.chris@topher.gintera.net> References: <20030518213036.GA1513@dhumketu.homeunix.net> <200305190403.24229.chris@topher.gintera.net>
next in thread | previous in thread | raw e-mail | index | archive | help
+-- Christopher Rosado [19-05-03 04:04 -0600]: | On Sunday 18 May 2003 03:30 pm, Shantanu Mahajan wrote: | | > Hi! | > I got the following msg. | > | > microuptime() went backwards (14208.429157 -> 13513.043743) | | You have an AMD CPU, and you have APM enabled in your kernel, would be my | guess (since I suffered from this exact problem when first switching to | FreeBSD). Hey, that's the correct guess. | | > what does it mean? should i have to worry? | | Yes, you do need to worry - your machine will eventually do an unclean reboot, yes that happens, but i never thought in that direction. | depending on how much you tax it. I lost a hard drive while I was trying to | fix this problem, due to many unclean spontaneous reboots. | | You need to *immediately* build a new kernel with absolutely nothing | APM-related enabled. Commenting out, or removing, the "device apm0" line and | rebuilding the kernel should be sufficient. Once you do that, you'll be | fine... just don't expect to be able to take advantage of APM (not that big | of a deal anyway). Rt. now compiling the kernel. Will let you know abt. future development. | | -- | Christopher Rosado | "Liberalism leads to loss of liberty." - Me Thanks a lot. Regards, Shantanu -- Madness has no purpose. Or reason. But it may have a goal.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030519203500.GB37777>