From owner-freebsd-bugs Tue Apr 25 1:40: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E8B1637BCC0 for ; Tue, 25 Apr 2000 01:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id BAA70268; Tue, 25 Apr 2000 01:40:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 25 Apr 2000 01:40:02 -0700 (PDT) Message-Id: <200004250840.BAA70268@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Kees Hendrikse Subject: Re: kern/17842: Erratic user time reports for long running processes Reply-To: Kees Hendrikse Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/17842; it has been noted by GNATS. From: Kees Hendrikse To: sheldonh@uunet.co.za (Sheldon Hearn) Cc: ech@echelon.nl (mailarchief Echelon) Subject: Re: kern/17842: Erratic user time reports for long running processes Date: Mon, 24 Apr 2000 02:12:02 +0200 (METDST) Hi Sheldon, > Excellent! Let me know what you find. FreeBSD 4.0 doesn't trigger the "ANOMALY" output lines, but it exhibits an interesting variation of the same problem: it just stops increasing ru.ru_utime.tv_sec: (...) ce=459822 cu=378572 ce=459938 cu=378688 ce=460054 cu=378803 ce=460170 cu=378919 ce=460285 cu=379034 ce=460401 cu=379150 ce=460517 cu=379265 <--- that's all folks.... ce=460633 cu=379265 ce=460748 cu=379265 ce=460864 cu=379265 (...) ce=545783 cu=379265 ce=545899 cu=379265 ce=546015 cu=379265 ce=546130 cu=379265 ce=546246 cu=379265 The program is still running... top shows: last pid: 9456; load averages: 1.00, 1.00, 1.00 up 6+07:57:54 01:42:24 15 processes: 2 running, 13 sleeping CPU states: 0.4% user, 98.1% nice, 0.4% system, 1.2% interrupt, 0.0% idle Mem: 4156K Active, 4072K Inact, 3500K Wired, 1576K Cache, 1023K Buf, 1052K Free Swap: 64M Total, 60K Used, 64M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 162 root 103 20 804K 236K RUN 129.5H 97.22% 97.22% pointless (...) /proc/162/status confirms the output of "pointless": # cd /proc/162 # for i in 1 2 3 4 5 > do > cat status > sleep 2 > done pointless 162 1 162 0 12,0 noflags 955986493,95119 379265,687860 16922,998963 nochan 0 0 0,0,0,2,3,4,5,20,31 - pointless 162 1 162 0 12,0 noflags 955986493,95119 379265,687860 16923,228881 nochan 0 0 0,0,0,2,3,4,5,20,31 - pointless 162 1 162 0 12,0 noflags 955986493,95119 379265,687860 16923,619831 nochan 0 0 0,0,0,2,3,4,5,20,31 - pointless 162 1 162 0 12,0 noflags 955986493,95119 379265,687860 16924,10718 nochan 0 0 0,0,0,2,3,4,5,20,31 - pointless 162 1 162 0 12,0 noflags 955986493,95119 379265,687860 16924,401572 nochan 0 0 0,0,0,2,3,4,5,20,31 - ^^^^^^^^^^^^^ What baffles me most: why stop counting at 379265,687860 seconds? -- Kees Hendrikse | email: kees@echelon.nl | web: www.echelon.nl ECHELON consultancy and software development | phone: +31 (0)53 48 36 585 PO Box 545, 7500AM Enschede, The Netherlands | fax: +31 (0)53 43 36 222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message