On Thursday,  7 September 2000 at 17:48:06 -0700, John Baldwin wrote:
> Greg Lehey wrote:
>> On Thursday,  7 September 2000 at 17:28:02 -0700, John Baldwin wrote:
>>> Steve Ames wrote:
>>>> Just upgraded to -CURRENT as of about noon (EST) today. At reboot
>>>> I got a lot of these:
>>>> microuptime() went backwards (1.7682417 -> 1.997434)
>>>> I recall reading in -current earlier this week that someone was
>>>> looking for victims getting this. What further information can I provide?
>>> This is a SMPng issue on UP machines.
>> Yes, but it's not the only cause.  We've also seen it on pre-SMPng
>> stuff, and Athlons seem to be particularly capable of doing it.  phk
>> is looking at it at the moment, and he has an idea what's causing it.
>> I'd guess, however, that this *is* the SMPng problem.  It's subtly
>> different from other manifestations in that the first time typically
>> has 7 digits after the decimal point.
> Most definitely an SMPng issue.  If you take a SMP machine and compile a UP
> and an SMP kernel on it, the SMP kernel will boot fine, whereas the UP kernel
> will generate these warnings.

The point I'm making is that we've had these problems before SMPng,
and that you can't automatically assume that it's SMPng just because
you get the messages.  On the other hand, the 7 digits seem to be a
pretty reliable signature.

Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to