Re: microuptime() went backwards

2004-04-23 Thread Vijay
On Fri, 2004-04-23 at 11:34, hugle wrote: Hello all. SOmetimes I see such messages in dmesg. perl# dmesg uptime() went backwards (1574174.333073 - 1573478.944788) Is your system clock working fine ? what they mean? and what causes them to appear ? is it good or bad?? :) --- Vijay

Re: microuptime() went backwards

2004-04-23 Thread Jez Hancock
On Fri, Apr 23, 2004 at 09:04:56AM +0300, hugle wrote: SOmetimes I see such messages in dmesg. perl# dmesg uptime() went backwards (1574174.333073 - 1573478.944788) what they mean? and what causes them to appear ? is it good or bad?? :) I'd always presumed these messages occured on my

Re: microuptime() went backwards

2004-04-23 Thread Matthew Seaman
On Fri, Apr 23, 2004 at 01:13:11PM +0100, Jez Hancock wrote: On Fri, Apr 23, 2004 at 09:04:56AM +0300, hugle wrote: SOmetimes I see such messages in dmesg. perl# dmesg uptime() went backwards (1574174.333073 - 1573478.944788) what they mean? and what causes them to appear ? is

Re: microuptime() went backwards

2004-04-23 Thread Peter Elsner
At 01:04 AM 4/23/2004, you wrote: Hello all. SOmetimes I see such messages in dmesg. perl# dmesg uptime() went backwards (1574174.333073 - 1573478.944788) what they mean? and what causes them to appear ? is it good or bad?? :) -- Best regards,Hugle ___

Re: microuptime() went backwards

2004-04-23 Thread Danny MacMillan
On Fri, 23 Apr 2004 13:41:18 +0100, Matthew Seaman [EMAIL PROTECTED] wrote: On Fri, Apr 23, 2004 at 01:13:11PM +0100, Jez Hancock wrote: On Fri, Apr 23, 2004 at 09:04:56AM +0300, hugle wrote: SOmetimes I see such messages in dmesg. perl# dmesg uptime() went backwards (1574174.333073 -

Re: microuptime() went backwards

2003-01-19 Thread bastill
Quoting talon [EMAIL PROTECTED]: re microuptime. My guess is that you will get 10^7 replies to this chestnut! :-) 1. Reconfigure your kernel by deleting all reference to APM, Leaving it in the default disabled state will not be enough. 2. Remove APM from your BIOS settings. IIRC that's about

Re: microuptime() went backwards

2003-01-19 Thread talon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | Quoting talon [EMAIL PROTECTED]: | re microuptime. | | My guess is that you will get 10^7 replies to this chestnut! :-) Ok Thanks Heaps .. Il definately do that! Thanks Again Jason FreeBSD Rox My Sox :) -BEGIN PGP

Re: microuptime went backwards ??

2002-12-03 Thread Christopher Rosado
On Tue, 03 Dec 2002 16:49:48 -0800 Bertrand Habib [EMAIL PROTECTED] wrote: BH Dear all, BH BH writing on ata disk, i get full screens of BH microuptime() went backwards ( nnn.nn - mmm.m ) Sounds like an AMD Athlon. BH with mmm.m being less than nnn.n (i.e backwards ) BH

Re: microuptime went backwards ??

2002-12-03 Thread Bertrand Habib
BH microuptime() went backwards ( nnn.nn - mmm.m ) Sounds like an AMD Athlon. Yes Disable power management in your BIOS. Nop! It was disabled and this brough me to the microuptime problem. After having re-enabled it (i.e: ACPI enable, APM enable), it seams to work. Also, I

Re: microuptime went backwards ??

2002-12-03 Thread bastill
Quoting Bertrand Habib [EMAIL PROTECTED]: BH microuptime() went backwards ( nnn.nn - mmm.m ) Sounds like an AMD Athlon. Yes Disable power management in your BIOS. Nop! It was disabled and this brough me to the microuptime problem. After having re-enabled it (i.e: ACPI

Re: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-16 Thread Brian Astill
On Wednesday 16 October 2002 04:20, Hartmann, O. wrote: On Tue, 15 Oct 2002, Andy Knapp wrote: No, on our servers I disabled APM by default because it triggered trouble in the past on several SMP machines. And why APM on every-time-up servers? No, definitely no APM facilities in kernel or

Re: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-15 Thread Tom Snell
Hartmann, O. wrote: Hello. Is this subject of a bug report? While calculating numerical simulations and heavy load one of our P4 systems showed up this: microuptime() went backwards (57243.730002 - 57243.730001) dmesgout of the system follows as attachment. -- MfG O. Hartmann [EMAIL

RE: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-15 Thread Andy Knapp
: microuptime() went backwards, FreeBSD 4.7-RELEASE Hartmann, O. wrote: Hello. Is this subject of a bug report? While calculating numerical simulations and heavy load one of our P4 systems showed up this: microuptime() went backwards (57243.730002 - 57243.730001) dmesgout of the system follows

RE: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-15 Thread Hartmann, O.
Snell :Sent: Tuesday, October 15, 2002 12:27 PM :To: Hartmann, O.; [EMAIL PROTECTED] :Subject: Re: microuptime() went backwards, FreeBSD 4.7-RELEASE : : :Hartmann, O. wrote: : :Hello. : :Is this subject of a bug report? : :While calculating numerical simulations and heavy load one of our P4 :systems

RE: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-15 Thread Andy Knapp
Snell'; [EMAIL PROTECTED] Subject: RE: microuptime() went backwards, FreeBSD 4.7-RELEASE On Tue, 15 Oct 2002, Andy Knapp wrote: This machine has a highly customized kernel ... :I've actually had this problem before, and I am pretty sure that it is a :problem with the apm line in the generic

RE: microuptime() went backwards, FreeBSD 4.7-RELEASE

2002-10-15 Thread Hartmann, O.
: [EMAIL PROTECTED] ::[mailto:[EMAIL PROTECTED]] On Behalf Of Tom Snell ::Sent: Tuesday, October 15, 2002 12:27 PM ::To: Hartmann, O.; [EMAIL PROTECTED] ::Subject: Re: microuptime() went backwards, FreeBSD 4.7-RELEASE : : ::Hartmann, O. wrote: : :Hello. : :Is this subject of a bug :report? : :While