kernel: calcru: runtime went backwards
Hello All since few days I get those messages into console and /var/log/messages The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu 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 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 backwards from 1928 usec to 1906 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 2241 usec to 1793 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 9373 usec to 7545 usec for pid 628 (rpcbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 556 usec to 539 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 12152 usec to 9722 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 287 usec to 229 usec for pid 143 (adjkerntz) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec to 14 usec for pid 42 (sctp_iterator) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 711 usec to 569 usec for pid 39 (irq15: ata1) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec to 40 usec for pid 36 (usb3) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec to 31 usec for pid 35 (usb2) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 1325 usec to 1060 usec for pid 23 (swi6: task queue) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 21246 usec to 20041 usec for pid 2 (g_event) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 8572 usec to 7530 usec for pid 0 (swapper) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel: calcru: runtime went backwards
This may be of help: http://forums.freebsd.org/archive/index.php/t-2805.html Cheers, Antonio 2010/6/8 Frank Bonnet f.bon...@esiee.fr: Hello All since few days I get those messages into console and /var/log/messages The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu 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 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 backwards from 1928 usec to 1906 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 2241 usec to 1793 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 9373 usec to 7545 usec for pid 628 (rpcbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 556 usec to 539 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 12152 usec to 9722 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 287 usec to 229 usec for pid 143 (adjkerntz) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec to 14 usec for pid 42 (sctp_iterator) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 711 usec to 569 usec for pid 39 (irq15: ata1) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec to 40 usec for pid 36 (usb3) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec to 31 usec for pid 35 (usb2) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 1325 usec to 1060 usec for pid 23 (swi6: task queue) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 21246 usec to 20041 usec for pid 2 (g_event) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 8572 usec to 7530 usec for pid 0 (swapper) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel: calcru: runtime went backwards
OK thank you Antonio :-) On 06/08/2010 03:11 PM, Antonio Vieiro wrote: This may be of help: http://forums.freebsd.org/archive/index.php/t-2805.html Cheers, Antonio 2010/6/8 Frank Bonnet f.bon...@esiee.fr: Hello All since few days I get those messages into console and /var/log/messages The machine is a IBM X3650 dual CPU , I've read it could be multi-cpu 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 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 backwards from 1928 usec to 1906 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 2241 usec to 1793 usec for pid 643 (ypbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 9373 usec to 7545 usec for pid 628 (rpcbind) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 556 usec to 539 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 12152 usec to 9722 usec for pid 538 (devd) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 287 usec to 229 usec for pid 143 (adjkerntz) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 18 usec to 14 usec for pid 42 (sctp_iterator) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 711 usec to 569 usec for pid 39 (irq15: ata1) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 44 usec to 40 usec for pid 36 (usb3) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 35 usec to 31 usec for pid 35 (usb2) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 1325 usec to 1060 usec for pid 23 (swi6: task queue) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 21246 usec to 20041 usec for pid 2 (g_event) Jun 8 10:16:34 mail kernel: calcru: runtime went backwards from 8572 usec to 7530 usec for pid 0 (swapper) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel: calcru: runtime went backwards
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 freebsd-questions-unsubscr...@freebsd.org
Re: calcru: runtime went backwards errors
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 03:13:57 ford kernel: calcru: runtime went backwards from 486 usec to 481 usec for pid 0 (swapper) and narrowed down the cause to openntpd. Do these errors fall into the Mostly Harmless category? It's probably just an annoyance, unless it is happening so often it causes other problems. I'll not worry then, but what's perplexing is that if time going backwards leads to confusion, why is that ntpd, as a matter of course, doesn't result in these error messages, but openntpd does? And then, why isn't anyone using openntpd getting the errors? The FreeBSD FAQ used to have a nice explanation of this, but it has been replaced by a discussion that simply assumes the problem is caused by the Intel SpeedStep implementation on your motherboard: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#Q5.24. My web searches turned a lot of noise about the above issue. Thanks for clarifying what I was reading. As for the FAQ, didn't there was one. I guess I've not needed it until now. ;-) But in general, this error can be caused by several things, including a device that is slow to respond to interrupts. One thing that often helps on SMP systems is to make sure your timecounter isn't using TSC: $ sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-100) kern.timecounter.hardware: ACPI-fast [...] Good to know, but this is an older single processor system (ACPI-safe). Seems I'll have to decide whether I drop openntpd and shuffle things around to other systems, or learn to live with the errors. Thanks to everyone that replied. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards errors
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: calcru: runtime went backwards from 588 usec to 582 usec for pid 133 (adjkerntz) Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 681 usec to 674 usec for pid 20 (swi6: task queue) Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 486 usec to 481 usec for pid 0 (swapper) and narrowed down the cause to openntpd. Do these errors fall into the Mostly Harmless category? yes. time turned backward and system get confused. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
calcru: runtime went backwards errors
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: calcru: runtime went backwards from 588 usec to 582 usec for pid 133 (adjkerntz) Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 681 usec to 674 usec for pid 20 (swi6: task queue) Jun 30 03:13:57 ford kernel: calcru: runtime went backwards from 486 usec to 481 usec for pid 0 (swapper) and narrowed down the cause to openntpd. Do these errors fall into the Mostly Harmless category? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards errors
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 to 481 usec for pid 0 (swapper) and narrowed down the cause to openntpd. Do these errors fall into the Mostly Harmless category? It's probably just an annoyance, unless it is happening so often it causes other problems. The FreeBSD FAQ used to have a nice explanation of this, but it has been replaced by a discussion that simply assumes the problem is caused by the Intel SpeedStep implementation on your motherboard: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#Q5.24. But in general, this error can be caused by several things, including a device that is slow to respond to interrupts. One thing that often helps on SMP systems is to make sure your timecounter isn't using TSC: $ sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) dummy(-100) kern.timecounter.hardware: ACPI-fast [...] - Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
calcru: runtime went backwards
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 to 11589623 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 11743728 usec to 11743726 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 12550703 usec to 12550699 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 12601970 usec to 12601968 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 13571027 usec to 13571024 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 13571027 usec to 13571024 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 13731304 usec to 13731302 usec for pid 13924 (vmware-guestd) calcru: runtime went backwards from 15674182 usec to 15674180 usec for pid 13924 (vmware-guestd) Is this bsd or vmware related, and any way to fix it? Thanks Jim Ballantine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards
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) [etc.] Is this bsd or vmware related, and any way to fix it? I don't have direct experience with this, but the reports I've seen indicate that vmware has clock problems with both FreeBSD and Linux. One suggestion is that in vmware, set host.useFastclock = FALSE in the .vmx file. Another suggestion is that in FreeBSD 6.0 you can try setting 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 possibilities (e.g. ACPI-safe seems to be the default these days) but as I said, I have no direct experience with vmware. It has also been recommended to set options HZ=1000 in your kernel configuration. Hope that helps, and if I got any of that wrong, someone please correct me! - Bob -- Spammers: please send mail to [EMAIL PROTECTED] and help me tune my spam filters! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards
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 possibilities (e.g. ACPI-safe seems to be the default these days) but as I said, I have no direct experience with vmware. In 5.x, this would be sysctl kern.timecounter.hardware=TSC but I don't know about 6.0 Good luck. - Bob -- Spammers: please send mail to [EMAIL PROTECTED] and help me tune my spam filters! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
calcru: runtime went backwards from on FreeBSD 5-STABLE SMP and Non-SMP
I am getting tons of these errors and would like to know what I can do. I have tried setting my kern.timecounter.hardware to TSC, i8254, ACPI-safe and I have even disabled the ACPI which leaves me with kern.timecounter.hardware: i8254. I am using FreeBSD 5-stable #2 with dual PIII Zeon 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 kernel: calcru: runtime went backwards from 66161646 usec to 66160290 usec for pid 6406 (surgemail) Aug 29 19:07:36 marvin kernel: calcru: runtime went backwards from 66161646 usec to 66161114 usec for pid 6406 (surgemail) Aug 29 19:07:51 marvin kernel: calcru: runtime went backwards from 66479195 usec to 66478025 usec for pid 6406 (surgemail) Aug 29 19:07:51 marvin kernel: calcru: runtime went backwards from 66479195 usec to 66478775 usec for pid 6406 (surgemail) Aug 29 19:08:29 marvin kernel: calcru: runtime went backwards from 67277563 usec to 67276508 usec for pid 6406 (surgemail) Aug 29 19:08:29 marvin kernel: calcru: runtime went backwards from 67277563 usec to 67277310 usec for pid 6406 (surgemail) Aug 29 19:08:40 marvin kernel: calcru: runtime went backwards from 67457231 usec to 67455796 usec for pid 6406 (surgemail) Aug 29 19:08:40 marvin kernel: calcru: runtime went backwards from 67457231 usec to 67456525 usec for pid 6406 (surgemail) Aug 29 19:08:40 marvin kernel: calcru: runtime went backwards from 67457231 usec to 67457192 usec for pid 6406 (surgemail) Thanks, Ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
