Thought I would use my old K7 600 MHz and 7KXA mobo as a gateway since my old K6-2
died,
and have run into a common problem when I installed 4.9.
When under high IO (network or CPU use) I get the "microuptime() went backwards"
flooding my screen, and syslog logging it making
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 ->
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
___
functionality into the main ntpd(8) -- so 'ntpq -q' is meant to be
functionally equivalent to ntpdate. Even so, it's not clear to me
that the 'step the clock' mode of operation is available from 'ntpd
-q'.
The OP's original query about 'microuptime w
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 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?? :)
---
Vij
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
___
[EMAIL PROTECTED] mailing list
-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 PG
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All ...
I have a slight problem with a box that i am looking after.
Any tips would be appreciated.
logfile /var/log/messages -- very tiny sample
Jan 20 14:06:22 gateway /kernel: microuptime() went backwards
(164603.803615 -> 163908.386002)
Quoting Christopher Rosado <[EMAIL PROTECTED]>:
>
> On Wed, 4 Dec 2002 14:41:50 +1030
> [EMAIL PROTECTED] wrote:
>
> BCA> Makes no difference. As Greg Lehey explained earlier the only
> BCA> solution is to delete all reference to APM in your kernel config file.
>
> He did? I see no such me
On Wed, 4 Dec 2002 14:41:50 +1030
[EMAIL PROTECTED] wrote:
BCA> Makes no difference. As Greg Lehey explained earlier the only
BCA> solution is to delete all reference to APM in your kernel config file.
He did? I see no such message from him in this thread.
BCA> "Disabled" means "still th
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
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
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.mm
Dear all,
writing on ata disk, i get full screens of
"microuptime() went backwards ( nnn.nn -> mmm.m )"
with mmm.m being less than nnn.n (i.e backwards )
Broken hardware ?
Wo may help me to interpret this message and, eventualy, correct that issue ?
Many thanks i
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 o
:>Cc: 'Tom 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 pr
'Tom 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 t
rom: [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.
:>&
ED]
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 showed up this:
>microuptime() went backwards (57243.730002 -> 5
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 attachm
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 PROTEC
23 matches
Mail list logo