> > Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> >10412, -694583121)y > > > > this is bad.. right ? :-) > > Well, at any rate it looks very funny. If this is a laptop, try > building a kernel without apm and see if that helps. It only helps "hide" the problem. There's either *extremely* bogus data coming in, or an arithmetic or sequencing error that's allowing a corrupt timecounter to be seen. It might help to see the negative number as hex... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- microuptime() went backwards Steve Ames
- Re: microuptime() went backwards John Baldwin
- Re: microuptime() went backwards Greg Lehey
- Re: microuptime() went backwards John Baldwin
- Re: microuptime() went backwards Greg Lehey
- Re: microuptime() went backwa... Kenneth Wayne Culver
- Re: microuptime() went ba... Greg Lehey
- Re: microuptime() wen... Kenneth Wayne Culver
- Re: microuptime() wen... Greg Lehey
- Re: microuptime() wen... Kenneth Wayne Culver
- Re: microuptime() wen... Mike Smith
- Re: microuptime() wen... Greg Lehey
- Re: microuptime() wen... Poul-Henning Kamp
- Re: microuptime() wen... Mike Smith
- Re: microuptime() wen... Kenneth Wayne Culver
- Re: microuptime() went backwards Siobhan Patricia Lynch
- Re: microuptime() went backwards Valentin Nechayev
- Re: microuptime() went backwards / SHMSEG John Toon
- Re: microuptime() went backwards Valentin Nechayev
- Re: microuptime() went backwards John Baldwin
- Re: microuptime() went backwards Bruce Evans