For about a week now, I've been tracking -CURRENT on two machines, panic and mojave, building world almost daily. On mojave, a number of process timing functions have not been working at all during this time, though panic has no problems. For example: $ cat loop.c main () { while (1); } $ make loop cc loop.c -o loop $ loop& [1] 54987 $ ps up54987 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND grog 54987 0.0 0.2 756 224 p2 R 1:20PM 0:28.98 loop $ ps up54987 In other words, though the process is looping in user state, ps shows no CPU usage, though the process time is being counted relatively correctly. Also, $ time loop Terminated [killed from another xterm] real 0m15.136s user 0m0.000s sys 0m15.040s Here the time has been attributed to the system, though it's all in user space. top shows: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Mem: 47M Active, 8284K Inact, 30M Wired, 6812K Cache, 9530K Buf, 576K Free Swap: 256M Total, 192K Used, 256M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 54999 grog 28 0 756K 224K RUN 0:15 0.00% 0.00% loop The CPU timing information is always 0.0% for everything. vmstat shows: r b w avm fre flt re pi po fr sr wd0 wc0 in sy cs us sy id 1 1 0 9228 7284 112 0 0 0 133 11 0 0 131 230 23 0 0 0 1 1 0 9228 7280 4 0 0 0 0 0 0 0 106 43 24 0 0 0 What makes this all the more puzzling is that it happens only on one machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal Pentium machine of no particular lineage. Does this ring a bell with anybody? Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message