Date: Fri, 15 Mar 2002 11:29:32 -0500 (EST) From: Matt Piechota <piechota@argolis.org> To: Rasputin <rasputin@shikima.mine.nu> Cc: Florin MANAILA <florin.manaila@softnet.ro>, <security@FreeBSD.ORG> Subject: Re: !!! Syslog message !!! Message-ID: <20020315112506.T8772-100000@cithaeron.argolis.org> In-Reply-To: <20020315121253.A20726@shikima.mine.nu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Mar 2002, Rasputin wrote: > > /kernel: microptime () went backwords (29281.21038151 -> 29281.820797) > > /kernel: microptime () went backwords (29281.21038151 -> 29281.639506) > > /kernel: microptime () went backwords (29281.21038151 -> 29281.639505) > > /kernel: microptime () went backwords (29281.21038151 -> 29281.639507) > > Search the mailing list archives - saw a lot of posts about this a > year or so back. Can't remember the fix, though. The usual answer is disable APM in your kernel. If that doesn't work (and it didn't for one of my machines), you might just have an iffy clock chip (or processor[0]). For me disabling apm helped, but didn't fix the problem completely. This isn't really a security issue in any case, and we shouldn't be discussing it here. [0] I switched the processor from a AMD K62-350 to a AMD K63-450 and the problem went away. So either the processor was funky, or the board wasn't stable at 350, but was at 450. -- Matt Piechota To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020315112506.T8772-100000>