Date: Mon, 29 Jul 2002 15:35:28 -0400 From: "David E. Cross" <crossd@cs.rpi.edu> To: joerch <helix@mayn.de> Cc: "David E. Cross" <crossd@cs.rpi.edu>, freebsd-hackers@freebsd.org, crossd@cs.rpi.edu Subject: Re: microuptime? Message-ID: <200207291935.g6TJZSe22496@monica.cs.rpi.edu> In-Reply-To: Message from joerch <helix@mayn.de> of "Mon, 29 Jul 2002 17:21:23 -0000." <20020729172123.C2113@mayn.de> References: <200207291438.g6TEcVu07763@jenolen.cs.rpi.edu> <20020729172123.C2113@mayn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > # Power management support (see LINT for more options) > > device apm0 at nexus? flags 0x20 # Advanced Power Management > > delete this line and build a new kernel. > > i got the same problem here with an amd 750mhz and epox mainboard. > > after i build a new kernel, the microuptime message disappeared. No go. I still have microuptime go backwards by 4 _seconds_. My next step is to try a UP kernel build, but I already know that will likely fix it :I I really want to know why this came up again, and if it means I fried something. Could someone point me at documentation on the PIIX timecounter method, perhaps if I understood how this clock worked I could understand what is not working correctly. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207291935.g6TJZSe22496>