I always used to get this when I ran console screen saver kernel modules
(like firesaver and the like). I noticed that when those were running,
the system spent almost all of its time servicing interrupts. If I had to
guess, in my particular case, it was so busy servicing whatever interrupts
were caused/generated by the running of the screen saver, that it was
missing the RTC (real time clock) interrupts.

Just a guess based on my experiences.

On Fri, 15 Mar 2002, Florin MANAILA wrote:

> Hi all,
> I receve some strange error on my FreeBSD 4.5 :
>
>
> /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)
>
> etc.
>
> ????? What's this strange error ????
>
> My system wen I receve this error is work very , very slow , but all
> traffic that is make from an ether to anoter (from xl0 to xl1) is OK
> This system is a firewall/gateway freebsd-router with 200 CPU Pentium
> MMX
>
>
> To Unsubscribe: send mail to majordomoFreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>

/-------------------------------------------------------------------------/
"Deep" is a word like "theory" or "semantic" -- it implies all sorts of
marvelous things. It's one thing to be able to say "I've got a
theory", quite another to say "I've got a semantic theory", but, ah,
those who can claim "I've got a deep semantic theory", they are truly
blessed.
                -- Randy Davis

                https://ephemeron.org:4300/~bigby/pgp_key.txt
/-------------------------------------------------------------------------/

To Unsubscribe: send mail to majordomoFreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]