I've been seeing them a lot too on a "recent" (NOV) -current
On Wed, 19 Dec 2001, Matthew Dillon wrote: > I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks > running in parallel): > > microuptime() went backwards (44525.3954411 -> 44524.563978) > microuptime() went backwards (57425.4282241 -> 57424.766121) > microuptime() went backwards (57425.4282241 -> 57424.845844) > microuptime() went backwards (60724.4427887 -> 60724.686232) > microuptime() went backwards (60724.4427887 -> 60724.768808) > microuptime() went backwards (61685.4418845 -> 61685.102724) > microuptime() went backwards (61924.3906516 -> 61924.246151) > microuptime() went backwards (62344.3800035 -> 62344.415407) > > Anyone know what's up? > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
