Re: microuptime() ...

2004-08-19 Thread Puna Tannehill
Well, I can't really voice opinion on VIA/Linux relationships and fun acronyms, but maybe give some points as to some things to check. Make sure 'apm_enable="YES"' is added to /etc/rc.conf. I got the same microuptime() error when i accidentally tapped the power swi

Re: microuptime() ...

2004-08-18 Thread Doug White
On Wed, 18 Aug 2004, Brian Astill wrote: > > Because VIA doesn't publish documentaion, and source is not > > documentation. > > I don't quite understand this response. Are you saying that the Linux > kernel team are somehow privileged cpw FBSD, so that they can avo

microuptime() went backwards

2001-08-29 Thread clemensF
k like: Wed Aug 29 16:12:25 CEST 2001 microuptime() went backwards (7633.019507 -> 7633.019407) pid 16331 (vile), uid 65534: exited on signal 6 (core dumped) cd9660: RockRidge Extension microuptime() went backwards (27387.137508 -> 27387.137407) microuptime() went bac

Re: fresh 4.3-RC: "microuptime went backwards", console lockup

2001-04-12 Thread Valentin Nechayev
Wed, Apr 11, 2001 at 11:37:35, nrh wrote about "Re: fresh 4.3-RC: "microuptime went backwards", console lockup": > This happened to me; a couple things you might try: > kern.timecounter.method=1 This is set already (in sysctl.conf), but does not help. >

Re: microuptime issues

2001-03-09 Thread Joseph Lee
On Fri, 9 Mar 2001, Odhiambo Washington wrote: > I have not seen this in the sysctl man page - so I haven't used it either. > Where can I get more info about it? Try searching the FreeBSD mailing lists. It's usually associated with the way the kernel maintains timekeeping with APM not being buil

Re: microuptime() went backwards (50596.915024 -> 50596.895202)

2001-02-27 Thread Thomas T. Veldhouse
Sent: Tuesday, February 27, 2001 1:27 AM Subject: Re: microuptime() went backwards (50596.915024 -> 50596.895202) > On Mon, Feb 26, 2001 at 10:51:02AM -0600, Thomas T. Veldhouse wrote: > > I seem to have a problem unique to my Athlon system. I noticed this problem &

Re: microuptime() going backwards

2000-06-28 Thread Wilko Bulte
Monday, 26 June 2000 at 22:56:29 +0200, Wilko Bulte wrote: > > >>> I just got tons and tons of > > >>> > > >>> Jun 26 22:06:33 freebie /kernel: microuptime() went backwards (18951.226366 -> >1 8951,199762) > > >>>

Re: microuptime() going backwards

2000-06-28 Thread Andreas Persson
;hardware on this CPU, or (more likely) a bug in the timecounter code >(since people see this on !APM systems already). Setting the sysctl kern.timecounter.method to 1 seems to have solved this on one of my 4.0-RELEASE boxes. No microuptime() messages for almost 3 weeks now. >-- >\\ Give

Re: microuptime() going backwards

2000-06-26 Thread Wilko Bulte
On Tue, Jun 27, 2000 at 12:03:49PM +1000, Greg Lehey wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Monday, 26 June 2000 at 22:56:29 +0200, Wilko Bulte wrote: > > I just got tons and tons of > > > > Jun 26 22:06:33 freebie