From owner-freebsd-current@freebsd.org Thu Nov 7 20:55:59 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 180CA178CE3 for ; Thu, 7 Nov 2019 20:55:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 478Fzy6f0tz4Ksh; Thu, 7 Nov 2019 20:55:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id xA7KtuX2001125 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 7 Nov 2019 12:55:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id xA7Ktu4p001124; Thu, 7 Nov 2019 12:55:56 -0800 (PST) (envelope-from sgk) Date: Thu, 7 Nov 2019 12:55:56 -0800 From: Steve Kargl To: Mark Johnston Cc: freebsd-current@freebsd.org Subject: Re: unkillable process consuming 100% cpu Message-ID: <20191107205556.GA922@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20191107202919.GA4565@troutmask.apl.washington.edu> <20191107203223.GF16978@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191107203223.GF16978@raichu> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 478Fzy6f0tz4Ksh X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2019 20:55:59 -0000 On Thu, Nov 07, 2019 at 03:32:23PM -0500, Mark Johnston wrote: > On Thu, Nov 07, 2019 at 12:29:19PM -0800, Steve Kargl wrote: > > I haven't seen anyone post about an unkillable process > > (even by root), which consumes 100% cpu. > > > > last pid: 4592; load averages: 1.24, 1.08, 0.74 up 13+20:21:20 12:26:29 > > 68 processes: 2 running, 66 sleeping > > CPU: 0.1% user, 0.0% nice, 12.6% system, 0.0% interrupt, 87.2% idle > > Mem: 428M Active, 11G Inact, 138M Laundry, 2497M Wired, 1525M Buf, 2377M Free > > Swap: 16G Total, 24M Used, 16G Free > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 69092 kargl 2 45 0 342M 148M CPU2 2 12:51 100.07% chrome > > > > > > Neither of these have an effect. > > > > kill -1 69092 > > kill -9 69069 > > > > Attempts to attach gdb831 to -p 69092 leads to hung xterm. > > Could you please show us the output of "procstat -kk 69092"? Unfortunately, no. I just rebooted the system to kill 69092. During 'shutdown -r now', a message appeared on the console warning that some processes would not die. Then 'shutdown -r now' hung the console. :( Before rebooting I did try a number of ps and procstat commands, 69092 was chrome: --type=gpu-process --field-trial-handle=long-string-of-number --gpu-preferences=long-string-with-IAs So, it seems that drm-current-kmod may not be happy. For the record, uname gives FreeBSD 13.0-CURRENT r353571 -- Steve