Date: Tue, 27 Feb 2001 08:49:10 -0600 From: "Thomas T. Veldhouse" <veldy@veldy.net> To: "Alexandr A. Listopad" <laa@laa.zp.ua> Cc: <freebsd-stable@FreeBSD.ORG> Subject: Re: microuptime() went backwards (50596.915024 -> 50596.895202) Message-ID: <005301c0a0cc$726db9a0$3028680a@tgt.com> References: <008401c0a014$4e1c1ff0$3028680a@tgt.com> <20010227092732.A692@laa.zp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
There is nothing in LINT about this. What is it that you are referring too? Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Alexandr A. Listopad" <laa@laa.zp.ua> To: "Thomas T. Veldhouse" <veldy@veldy.net> Cc: <freebsd-stable@FreeBSD.ORG> Sent: Tuesday, February 27, 2001 1:27 AM Subject: Re: microuptime() went backwards (50596.915024 -> 50596.895202) > On Mon, Feb 26, 2001 at 10:51:02AM -0600, Thomas T. Veldhouse wrote: > > I seem to have a problem unique to my Athlon system. I noticed this problem > > begin somewhere around 4.2-STABLE. The message: > > > > microuptime() went backwards (50596.915024 -> 50596.895202) > > > > is repeated thousands of times and floods my syslog when the system under > > load (currently during a buildworld). The times vary of course. > > > > What changes have been made relatively recently to cause this error? This > > seems to be a problem for either Classic Athlons or it has also been > > speculated by a couple to be VIA KX133 related. > > > > Please advise. > > see LINT for details [search for microuptime]. > > -- > Laa > 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?005301c0a0cc$726db9a0$3028680a>