I've noticed this for a while now (since not longer after 1.4 came out
at a guess), but only today have I got an up-to-date matching kernel
and userland on my -current pmax.  The CPU time used is very wrong -
here's an example of a small program that sits in a "while(1);" loop
for 10 seconds, with reports from tcsh's built-in time command and
/usr/bin/time:

	mona:/var/tmp 32> time /usr/bin/time ./x
	       10.25176 real       261.90 user         0.20 sys
	262.567u 0.425s 4:22.53 100.1%  0+0k 2+1io 0pf+0w

Also, xntpd is not happy at all:

	Aug 11 21:58:05 mona xntpd[214]: synchronized to 172.73.42.42, stratum=3
	Aug 11 21:58:05 mona xntpd[214]: time reset (step) 0.831568 s
	Aug 11 21:58:05 mona xntpd[214]: synchronisation lost
	Aug 11 22:04:23 mona xntpd[214]: synchronized to 172.73.42.199, stratum=2
	Aug 11 22:04:26 mona xntpd[214]: time reset (step) 1.546420 s
	Aug 11 22:04:26 mona xntpd[214]: synchronisation lost
	Aug 11 22:12:55 mona xntpd[214]: synchronized to 172.73.42.199, stratum=2
	Aug 11 22:12:56 mona xntpd[214]: time reset (step) 1.295242 s
	Aug 11 22:12:56 mona xntpd[214]: synchronisation lost
	Aug 11 22:19:20 mona xntpd[214]: synchronized to 172.73.42.199, stratum=2
	Aug 11 22:19:22 mona xntpd[214]: time reset (step) 0.877031 s
	Aug 11 22:19:22 mona xntpd[214]: synchronisation lost

Any pointers?

Simon.