From owner-freebsd-stable@FreeBSD.ORG Tue Aug 15 16:34:56 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9BD016A4FC for ; Tue, 15 Aug 2006 16:34:56 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DFDF43DFD for ; Tue, 15 Aug 2006 16:34:04 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 2DC29114FF for ; Tue, 15 Aug 2006 12:34:22 -0400 (EDT) Message-ID: <44E1F796.5070105@rogers.com> Date: Tue, 15 Aug 2006 12:34:30 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.475, required 3.5, ALL_TRUSTED -1.80, AWL 0.01, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: Subject: TOP shows above 100% WCPU usage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Aug 2006 16:34:57 -0000 last pid: 747; load averages: 2.69, 1.03, 0.58 up 0+01:40:40 10:14:29 35 processes: 7 running, 28 sleeping CPU states: 58.1% user, 0.0% nice, 38.4% system, 1.1% interrupt, 2.4% idle Mem: 642M Active, 416M Inact, 125M Wired, 112M Buf, 825M Free Swap: 4071M Total, 4071M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 465 mysql 18 20 0 905M 641M kserel 0 39:18 160.64% mysqld 631 root 1 96 0 2424K 1668K CPU1 0 0:02 0.00% top How can mysql use 160%? Is this a reporting bug in top because mysql is threaded?