On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > With very latest kernel I got lots of > > microuptime() went backwards (1.3624050 -> 1.998840) > > messages just before > > Mounting root from ufs:/dev/da0s1a It really does go backwards. This is caused by the giant lock preventing the clock interrupt task from running soon enough. The giant lock can also prevent the clock interrupt task from running often enough even after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does several bad things. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- recent kernel, microuptime went backwards Andrey A. Chernov
- Re: recent kernel, microuptime went backwards Bruce Evans
- Re: recent kernel, microuptime went backwa... Poul-Henning Kamp
- Re: recent kernel, microuptime went ba... Andrey A. Chernov
- Re: recent kernel, microuptime went backwa... Donn Miller
- Re: recent kernel, microuptime went backwa... John Baldwin
- Re: recent kernel, microuptime went ba... Bruce Evans
- Re: recent kernel, microuptime went ba... Poul-Henning Kamp
- Re: recent kernel, microuptime went ba... Siobhan Patricia Lynch
- Re: recent kernel, microuptime wen... Siobhan Patricia Lynch
- Re: recent kernel, microuptime wen... John Baldwin
- Re: recent kernel, microuptime went backwards Sheldon Hearn