on Dovecot IMAP server that kill
himself when it trap that kind of error messages.
Thank you
Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 1721
usec to 1377 usec for pid 684 (rpc.lockd)
Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 528
usec to 459 usec
related but I am a bit confused in it.
Does any guru could show me the light on how to stop those messages
if possible , this has side effects on Dovecot IMAP server that kill
himself when it trap that kind of error messages.
Thank you
Jun 8 10:16:34 mail kernel: calcru: runtime went
messages.
Thank you
Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 1721
usec to 1377 usec for pid 684 (rpc.lockd)
Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 528
usec to 459 usec for pid 678 (rpc.statd)
Jun 8 10:16:34 mail kernel: calcru: runtime went
Frank Bonnet f.bon...@esiee.fr writes:
OK thank you Antonio :-)
Also, see the FAQ entry if you haven't already.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Thanks in
2008/7/24 Dimitar Vasilev [EMAIL PROTECTED]
2008/7/24 Kris Kennaway [EMAIL PROTECTED]:
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios is as of 2005 - ami bios or something like this.
Initial
Dimitar Vasilev wrote:
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios is as of 2005 - ami
Michael Powell wrote:
Dimitar Vasilev wrote:
Hi,
I'm having calcru went backwards issues on a machine with the following
config:
MB: MSI K8D Master-F
2xOpteron 242 2.2Ghz
BIOS - от 2005-та
7-stable
areca 1120
8 disks
HDD temperature 28-29 for 1st five, 38-39 for the last 3.
bios
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time. This happens if you break to DDB for example. It can also
happen
2008/7/24 Kris Kennaway [EMAIL PROTECTED]:
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time
Dimitar Vasilev wrote:
The calcru went backwards message can have two causes:
1) Your time counter really went backwards and is too broken to use.
2) Something caused clock interrupts to be delayed for extremely long
periods of time. This happens if you break to DDB for example. It can also
On Mon, Jun 30, 2008 at 7:38 AM, Bob Johnson [EMAIL PROTECTED] wrote:
On 6/30/08, David Allen [EMAIL PROTECTED] wrote:
I've been seeing errors like the following appearing:
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
usec to 258 usec for pid 516 (devd)
[...]
Jun 30
I've been seeing errors like the following appearing:
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
usec to 258 usec for pid 516 (devd)
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 4976
usec to 4926 usec for pid 367 (pflogd)
Jun 30 03:13:57 ford kernel
I've been seeing errors like the following appearing:
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
usec to 258 usec for pid 516 (devd)
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 4976
usec to 4926 usec for pid 367 (pflogd)
Jun 30 03:13:57 ford kernel
On 6/30/08, David Allen [EMAIL PROTECTED] wrote:
I've been seeing errors like the following appearing:
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 261
usec to 258 usec for pid 516 (devd)
[...]
Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 486
usec
Hi,
can you help me on this..I attached it in this email
whats the meaning of it and how can i get rid of that??
Please...Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe,
On Fri, 25 Apr 2008 03:57 pm, Ruel Luchavez wrote:
Hi,
can you help me on this..I attached it in this email
whats the meaning of it and how can i get rid of that??
Please...Thanks
I don't believe attachments are redistributed by this
mailing list.
Best to cut and paste your error
James Long wrote:
I'm running FreeBSD RELENG_6 on a Compaq DL380 G2 dual PIII-1.4GHz with
an SMP kernel. dmesg below.
Prior to about August 12, the system had been quite stable.
Since that time, I am finding lots of calcru warnings, which often
cause system services to fail when they see
lots of calcru warnings, which often
cause system services to fail when they see unorthodox time shifts.
Section 5.19 of the handbook appears not to be current any longer,
suggesting setting kern.timecounter.method=1.
kern.timecounter.hardware=i8254 also does not improve things.
Other suggestions
I'm running FreeBSD RELENG_6 on a Compaq DL380 G2 dual PIII-1.4GHz with
an SMP kernel. dmesg below.
Prior to about August 12, the system had been quite stable.
Since that time, I am finding lots of calcru warnings, which often
cause system services to fail when they see unorthodox time shifts
Rob G. asked about calcru: negative runtime on Sun, 24 Sep 2006 13:14:27
and was not answered. Well, I too have PDSMi+ motherboards and am
getting the same error.
What is this error?
Is anyone else using the SuperMicro PDSMi+ motherboards with success?
I am running '6.1-RELEASE FreeBSD
In response to Rudy [EMAIL PROTECTED]:
Rob G. asked about calcru: negative runtime on Sun, 24 Sep 2006 13:14:27
and was not answered. Well, I too have PDSMi+ motherboards and am
getting the same error.
What is this error?
This is usually related to the following FAQ entry:
http
I see that in /var/log/messages I am getting messages like the
following...
Sep 24 13:08:36 tx kernel: calcru: negative runtime of -604849 usec
for pid 16 (yarrow)
Sep 24 13:08:36 tx kernel: calcru: negative runtime of -604842 usec
for pid 16 (yarrow)
Sep 24 13:08:38 tx kernel: calcru
I've been getting the calcru: negative time message. After
search the site I found the FAQ (5.18) that says to set this variable
sysctl kern.timecounter.method=1.
When I do that, I get sysctl: unknown old 'kern.timercounter.method'.
What is the fix/search term for 6-release??
Thanks
Jim
On 12/2/05, J. W. Ballantine [EMAIL PROTECTED] wrote:
I've been getting the calcru: negative time message. After
search the site I found the FAQ (5.18) that says to set this variable
sysctl kern.timecounter.method=1.
When I do that, I get sysctl: unknown old 'kern.timercounter.method
I running 6-RELEASE as a guest under vmware 5.5 and I'm having
problems with the clock going backwards. I'm getting the message (sample):
calcru: runtime went backwards from 10542602 usec to 10542600 usec for pid
13924
(vmware-guestd)
calcru: runtime went backwards from 11589627 usec
On 12/1/05, J. W. Ballantine [EMAIL PROTECTED] wrote:
I running 6-RELEASE as a guest under vmware 5.5 and I'm having
problems with the clock going backwards. I'm getting the message (sample):
calcru: runtime went backwards from 10542602 usec to 10542600 usec for pid
13924
(vmware-guestd
On 12/1/05, Bob Johnson [EMAIL PROTECTED] wrote:
sysctl kern.MUMBLE.timecounter=TSC
except I don't know what MUMBLE is in 6.0.
sysctl -a | grep timecounter
should reveal it, though. And if it is already TSC, try i8254,
I've seen both recommended. There are probably other
Processors and a P4
system with HyperThreading disabled and both seem to do this. Netwin is at
a loss and so am I. Any help would be greatly appreciated.
Aug 29 19:07:12 marvin kernel: calcru: runtime went backwards from 65601433
usec to 65601140 usec for pid 6406 (surgemail)
Aug 29 19:07:36 marvin
I Installed a Freebsd 5.21 with windows98SE
but exhibition this message in various program during the initialization:
calcru: negative time of -33886933 usec for pid 476 (ls) this program
exhibition this message
On Sun, Apr 10, 2005 at 08:42:30PM -0300, [EMAIL PROTECTED] wrote:
I Installed a Freebsd 5.21 with windows98SE
but exhibition this message in various program during the initialization:
calcru: negative time of -33886933 usec for pid 476 (ls) this program
exhibition this message
Kinsey [EMAIL PROTECTED] wrote:
Brian Curnow wrote:
I am new to BSD and just downloaded BSD 5.3-RELEASE.
I saw a few other posts on this issue but I didn't see any solutions.
I am getting excessive calcru: negative runtime
messages in the syslog (and the console).
According to the FAQ
I am new to BSD and just downloaded BSD 5.3-RELEASE.
I saw a few other posts on this issue but I didn't see
any solutions.
I am getting excessive calcru: negative runtime
messages in the syslog (and the console).
According to the FAQ the solution is to use sysctl and
set kern.timecounter.method
Brian Curnow wrote:
I am new to BSD and just downloaded BSD 5.3-RELEASE.
I saw a few other posts on this issue but I didn't see
any solutions.
I am getting excessive calcru: negative runtime
messages in the syslog (and the console).
According to the FAQ the solution is to use sysctl and
set
(tm) 3D processor (450.13-MHz 586-class CPU)
The biggest problem I have is that I have to boot with ACPI disabled.
With ACPI enabled I get continuous errors showing
calcru: negative runtime on pid (varies)
Google'ing for this error shows this hit
http://lists.freebsd.org/pipermail/freebsd-acpi/2004
Howdy,
For starters, uname -a gives
FreeBSD reactor.bombsession.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri
Nov 5 04:19:18 UTC 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
After an install of 5.3-Release on a freshly formatted drive, I am
getting loads of calcru errors:
calcru
Please wrap your lines around 72 characters, see:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-questions/index.html
Ricardo Santos [EMAIL PROTECTED] wrote:
Hello!
Im new to FreeBSD and there is a problem in my installation that is
repeating itself very frequently, so,
Hello!
Im new to FreeBSD and there is a problem in my installation that is repeating
itself very frequently, so, as the own OS tells to do, the output of 'uname -a' is:
FreeBSD 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
I am still unable to get rid of these on my 5.2 installation
running on AMD K6-2 450 MHz hardware.
FBSD 4.9 ran just fine on this box with nary a hiccup. I am
ruling out faulty hardware as the culprit as I test loaded 4.9
back on the system yesterday and saw not a one of the above
messages.
The
Please help if you can. I am not the only one with this problem,
I wonder if others have given up and gone back to versions
4.X...
Thank you all,
Roy
I wish there was a solution to this.. I've search for many moons.
My problem is that I can't upgrade my firewall, because I have bad RAM.
Make
I have searched high and low for help with these negative-time
calcru messages...there is scant information out there, mostly a
paragraph in the troubleshooting section of the FreeBSD docs.
Most folks following the instructions there on later versions of
FBSD seem to not be successful in getting
At 12:47 PM 1.23.2004 -0800, RA Cohen wrote:
I have searched high and low for help with these negative-time
calcru messages...there is scant information out there, mostly a
paragraph in the troubleshooting section of the FreeBSD docs.
Most folks following the instructions there on later versions
Hi,
Looks like you may have a hardware fault:
from /usr/src/sys/kern/kern_clock.c
* 0 - every tick, bad hardware may fail with calcru negative...
David
On Thu, 23 Oct 2003, Heath Volmer wrote:
Hopefully this one will get through...
I've searched exhaustively for an answer
Hi:
I just complete my first installation of FreeBSD 5.1 and I keep getting
messages scrolling on the screen which say calcru: negative time of -671171
usec for pid 10304 - message varies by pid.
Obviously I have a problem but is it hardware, setup ot hacked. I am
clueless, please help
Thanks
On Tue, Oct 14, 2003 at 04:03:48PM -0400, Peter J. Mignone wrote:
Hi:
I just complete my first installation of FreeBSD 5.1 and I keep getting
messages scrolling on the screen which say calcru: negative time of -671171
usec for pid 10304 - message varies by pid.
Obviously I have a problem
I guess this probably came up before, but I could find any helpful info
in the list's archive...
I am getting a lot of calcru: negative time of I am on 5.1
RELEASE.
I have tried troubleshooting hints but without luck.
sysctl -w kern.timecounter.method=1 gives me sysctl: unknown oid
Hi,
I'm looking for an efective solution for the calcru error.
I read many posts in many freebsd mail lists, but any solution solved the problem.
I saw the problem listed on fbsd known problems (
http://www.freebsd.org/releases/5.0R/DP1/errata.html ) and it leaded me to this list
At 11:58 PM -0500 6/3/03, Shane Kinney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 3 Jun 2003, Jimi Thompson wrote:
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIV
That web page said to enter this command (which I do not have a good
#CALCRU-NEGATIV
That web page said to enter this command (which I do not have a good
understanding of but did anyway)
# sysctl -w kern.timecounter.method=1
which I did, but apparently my 5.0 doesn't like that because it
promptly spit back:
sysctl: unknown oid 'kern.timecounter.method'
1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 3 Jun 2003, Jimi Thompson wrote:
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIV
That web page said to enter this command (which I do not have a good
understanding of but did anyway)
# sysctl -w
Jimi Thompson [EMAIL PROTECTED] writes:
That web page said to enter this command (which I do not have a good
understanding of but did anyway)
# sysctl -w kern.timecounter.method=1
which I did, but apparently my 5.0 doesn't like that because it
promptly spit back:
sysctl: unknown oid
We're trying out 5.0-RELEASE on a test machine, and all is working well (so far)
except for the continual calcru: negative time ... messages.
I found information about this in the FAQ, but 5.0 doesn't seem to have a
kern.timecounter.method oid.
I also found information in the 5.0DP1 errata
52 matches
Mail list logo
