From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 20 13:17:15 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 91B7D8DD; Wed, 20 Aug 2014 13:17:15 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 618703DB0; Wed, 20 Aug 2014 13:17:14 +0000 (UTC) Received: from [73.34.117.227] (helo=ilsoft.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1XK5lE-000I98-Dn; Wed, 20 Aug 2014 13:17:08 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id s7KDH7h4053503; Wed, 20 Aug 2014 07:17:07 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19g1IZOVMaGxv5RGbStKm0W X-Authentication-Warning: paranoia.hippie.lan: Host revolution.hippie.lan [172.22.42.240] claimed to be [172.22.42.240] Subject: Re: stopped processes using cpu? From: Ian Lepore To: Tim Kientzle In-Reply-To: <10AEB4BC-B1B3-4312-A36C-ECE33EC56805@kientzle.com> References: <53F3A564.8070202@freebsd.org> <10AEB4BC-B1B3-4312-A36C-ECE33EC56805@kientzle.com> Content-Type: text/plain; charset="iso-8859-7" Date: Wed, 20 Aug 2014 07:17:06 -0600 Message-ID: <1408540626.1150.1.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ilsoft.org id s7KDH7h4053503 Cc: freebsd-hackers@freebsd.org, Allan Jude 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 13:17:15 -0000 On Tue, 2014-08-19 at 18:45 -0700, Tim Kientzle wrote: > On Aug 19, 2014, at 12:28 PM, Allan Jude wrote: >=20 > > On 2014-08-19 15:21, Dieter BSD wrote: > >> 8.2 on amd64 > >> Top(1) with no arguments reports that some firefox processes are usi= ng cpu > >> dispite being stopped (via kill -stop pid) for at least several hour= s. > >> 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 0= 8:48:28 > >> 267 processes: 1 running, 138 sleeping, 128 stopped > >> CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% id= le > >> 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 COMMA= ND > >> 44188 a 9 44 0 303M 187M STOP 113:19 13.43% fire= fox-bin > >> 92986 b 11 44 0 164M 62848K STOP 0:18 5.03% fire= fox-bin > >> 16507 c 11 44 0 189M 88976K STOP 0:13 0.24% fire= fox-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% fire= fox-bin > >> _______________________________________________ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebs= d.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 >=20 > I wonder if jhb@=A2s new top code fixes the whacky WCPU values we=A2ve = been seeing on FreeBSD/ARM. (1713% CPU is a little hard to believe on a = single-core board ;-). >=20 > Tim >=20 *Fixes* it? I've been under the impression those changes caused it. I certainly never saw 1000%+ numbers in top until very recently. -- Ian