From owner-freebsd-current Sat Jul 25 00:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19751 for freebsd-current-outgoing; Sat, 25 Jul 1998 00:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19746 for ; Sat, 25 Jul 1998 00:17:22 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA08209 for ; Sat, 25 Jul 1998 16:46:55 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA02170; Sat, 25 Jul 1998 16:46:50 +0930 (CST) Message-ID: <19980725164649.P716@freebie.lemis.com> Date: Sat, 25 Jul 1998 16:46:49 +0930 From: Greg Lehey To: FreeBSD current users Subject: Ridiculous CPU time usage in -CURRENT? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just doing a backup on my laptop, and I've noticed the following stuff from top: last pid: 6742; load averages: 0.88, 0.99, 0.93 16:41:59 48 processes: 2 running, 46 sleeping CPU states: 0.8% user, 0.0% nice, 34.7% system, 51.1% interrupt, 13.4% idle Mem: 6660K Active, 4976K Inact, 7204K Wired, 2660K Cache, 2445K Buf, 480K Free Swap: 128M Total, 25M Used, 103M Free, 19% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 6672 root 66 0 588K 336K RUN 195:30 64.93% 64.93% tar last pid: 6742; load averages: 0.94, 0.99, 0.93 16:42:57 (same old blurb) PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 6672 root 56 0 588K 336K RUN 219:09 46.46% 46.46% tar In other words, in the space of 58 seconds the CPU time usage has gone up by 23 minutes. This happens in sudden jumps; the rest of the time things look OK. Any ideas what could be causing it? I'm running a -CURRENT kernel built round 25 June, and probably supped within a day of building. I'm running xntpd, but that doesn't seem to be the reason: the time's been OK for weeks. The machine's been running since 29 June. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message