From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 20 02:15:14 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 85B492F6 for ; Wed, 20 Aug 2014 02:15:14 +0000 (UTC) Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 582253A6C for ; Wed, 20 Aug 2014 02:15:14 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id y10so10909449pdj.14 for ; Tue, 19 Aug 2014 19:15:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=iai3TdlRO0hRSxdawKb1bj3VqsnjwuzKWk3fyssSGjI=; b=BtaRzve2osA5wKqUBF0eQe62rnQU2VIWMrG1kVUZpqt6pGGQLxfBfLNo+unPa2dWhc fPoYA7R2BlHnYt/DT0fd9BXeqtBOFqmDWU6lk/ba4I63XIcOfj4NR1qdq0AFUTuER1zt J1DeSO/4J5SNz1ePgBD5oEJjZVboKmQ+dV3q81lREWnzzRJUFiOBE322C7FX8VnReD5q etfSfW5rA3c42+0NLQRLBGGAJi3oxBaIwzYrbpZyGlAG3xAcT5vwTEFUmzjx2nM874FM +YY0VA1YVZ2NjWBc9RNejPRxnUdrY8Q1I2EUC/bdW+iJwX+ul3BN5AsQu21F/SJHTZ7C QDUA== X-Gm-Message-State: ALoCoQn1ophYKpWJx+Z08glMOkfLvszPeXgZOT3w6MA+/m8v7JOZGF0tXq9uQcDmVraFOdEnhViK X-Received: by 10.70.93.8 with SMTP id cq8mr13940837pdb.160.1408499123547; Tue, 19 Aug 2014 18:45:23 -0700 (PDT) Received: from [192.168.1.100] (c-24-6-220-224.hsd1.ca.comcast.net. [24.6.220.224]) by mx.google.com with ESMTPSA id gi8sm20626279pbc.16.2014.08.19.18.45.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 18:45:23 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: stopped processes using cpu? From: Tim Kientzle In-Reply-To: <53F3A564.8070202@freebsd.org> Date: Tue, 19 Aug 2014 18:45:21 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <10AEB4BC-B1B3-4312-A36C-ECE33EC56805@kientzle.com> References: <53F3A564.8070202@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2014 02:15:14 -0000 On Aug 19, 2014, at 12:28 PM, Allan Jude wrote: > On 2014-08-19 15:21, Dieter BSD wrote: >> 8.2 on amd64 >> Top(1) with no arguments reports that some firefox processes are = using cpu >> dispite being stopped (via kill -stop pid) for at least several = hours. >> Adding -C doesn't change the numbers. Ps(1) reports the same. >> Interestingly, a firefox that isn't stopped is (correctly?) reported = as >> using 0 cpu. The 100% idle should be correct, but who knows. >>=20 >> last pid: 51932; load averages: 0.07, 0.99, 1.42 up 14+19:02:56 = 08:48:28 >> 267 processes: 1 running, 138 sleeping, 128 stopped >> CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% = idle >> Mem: 1665M Active, 653M Inact, 240M Wired, 95M Cache, 372M Buf, 815M = Free >> Swap: 8965M Total, 560K Used, 8965M Free >>=20 >> PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU = COMMAND >> 44188 a 9 44 0 303M 187M STOP 113:19 13.43% = firefox-bin >> 92986 b 11 44 0 164M 62848K STOP 0:18 5.03% = firefox-bin >> 16507 c 11 44 0 189M 88976K STOP 0:13 0.24% = firefox-bin >> 2265 root 1 44 0 248M 193M select 625:38 0.00% Xorg >> 51271 d 10 44 0 233M 128M ucond 12:12 0.00% = firefox-bin >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>=20 >=20 > I wonder if jhb@'s new top code solves this. He adjusted the way CPU > usage is tracked to be more responsive, and not based on averages I wonder if jhb@=92s new top code fixes the whacky WCPU values we=92ve = been seeing on FreeBSD/ARM. (1713% CPU is a little hard to believe on a = single-core board ;-). Tim