Date: Thu, 09 Mar 2006 07:42:24 -0800 From: othermark <atkin901@yahoo.com> To: freebsd-current@freebsd.org Subject: Re: Still seeing "calcru: runtime went backwards" messages Message-ID: <dupid0$itf$1@sea.gmane.org> References: <47d0403c0603012213o32b6d6d0m6ab4207de9134577@mail.gmail.com> <17030.1141292439@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote:
> I've updated the calibration code to be much more precise, let me know
> if this helps or not.
[last minute edit: I see you just updated kern_resource for slop. I'll try
it..]
I'm still getting calcru messages. They are much less prevalent now, but
still occur in two instances. I no longer get the em watchdog problems
that were occuring before this checkin.
- On bootup, where seemingly the same processes report them each time (I
haven't verified this for sure).
- During NFS operations
[root@moby kern]$ cat kern_exit.c |grep FBSD
__FBSDID("$FreeBSD: src/sys/kern/kern_exit.c,v 1.285 2006/02/22 18:57:49 jhb
Exp $");
[root@moby kern]$ cat kern_resource.c |grep FBSD
__FBSDID("$FreeBSD: src/sys/kern/kern_resource.c,v 1.156 2006/02/22 16:58:48
jhb Exp $");
[root@moby ~]$ dmesg -a |grep "calcru: "
calcru: runtime went backwards from 7409 usec to 7408 usec for pid 590
(smartd)
calcru: runtime went backwards from 316 usec to 315 usec for pid 541 (nfsd)
calcru: runtime went backwards from 28662 usec to 28661 usec for pid 539
(nfsd)
calcru: runtime went backwards from 255 usec to 254 usec for pid 296
(moused)
calcru: runtime went backwards from 520379 usec to 520349 usec for pid 40
(pagezero)
calcru: runtime went backwards from 21912 usec to 21911 usec for pid 18
(swi5: +)
calcru: runtime went backwards from 3915038 usec to 3915033 usec for pid
4975 (md0)
calcru: runtime went backwards from 731718 usec to 731717 usec for pid 865
(sh)
calcru: runtime went backwards from 711134 usec to 711133 usec for pid 782
(bash)
calcru: runtime went backwards from 18702 usec to 18701 usec for pid 773
(login)
calcru: runtime went backwards from 1286171 usec to 1286169 usec for pid 48
(nfsiod 3)
calcru: runtime went backwards from 1294673 usec to 1294671 usec for pid 47
(nfsiod 2)
calcru: runtime went backwards from 1314046 usec to 1314044 usec for pid 46
(nfsiod 1)
calcru: runtime went backwards from 1368574 usec to 1368572 usec for pid 45
(nfsiod 0)
[root@moby ~]$ sysctl -a |grep timecounter
kern.timecounter.tick: 1
kern.timecounter.choice: TSC(800) HPET(-200) ACPI-safe(1000) i8254(0)
dummy(-1000000)
kern.timecounter.hardware: ACPI-safe
kern.timecounter.nsetclock: 3
kern.timecounter.ngetmicrotime: 9681737
kern.timecounter.ngetnanotime: 0
kern.timecounter.ngetbintime: 0
kern.timecounter.ngetmicrouptime: 23989400
kern.timecounter.ngetnanouptime: 1527575
kern.timecounter.ngetbinuptime: 394810
kern.timecounter.nmicrotime: 31466497
kern.timecounter.nnanotime: 6184341
kern.timecounter.nbintime: 37652932
kern.timecounter.nmicrouptime: 246038910
kern.timecounter.nnanouptime: 67
kern.timecounter.nbinuptime: 285816753
kern.timecounter.stepwarnings: 0
kern.timecounter.smp_tsc: 0
--
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dupid0$itf$1>