From owner-freebsd-current@freebsd.org Fri Nov 8 22:09:45 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 B31AA162669; Fri, 8 Nov 2019 22:09:45 +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 478vZb6YL2z40V1; Fri, 8 Nov 2019 22:09:43 +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 xA8M9ZKU000863 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 8 Nov 2019 14:09:35 -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 xA8M9ZDr000862; Fri, 8 Nov 2019 14:09:35 -0800 (PST) (envelope-from sgk) Date: Fri, 8 Nov 2019 14:09:35 -0800 From: Steve Kargl To: Mark Johnston Cc: freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: unkillable process consuming 100% cpu Message-ID: <20191108220935.GA856@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: 478vZb6YL2z40V1 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of sgk@troutmask.apl.washington.edu has no SPF policy when checking 128.95.76.21) smtp.mailfrom=sgk@troutmask.apl.washington.edu X-Spamd-Result: default: False [-1.25 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; NEURAL_HAM_MEDIUM(-0.92)[-0.924,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[washington.edu]; REPLYTO_ADDR_EQ_FROM(0.00)[]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; IP_SCORE(-0.23)[ip: (0.06), ipnet: 128.95.0.0/16(-0.29), asn: 73(-0.84), country: US(-0.05)]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Fri, 08 Nov 2019 22:09:45 -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"? Just had another lock-up. A force 'shutdown -r now' from a remote terminal led to a console message about an unkillable process. Here's 'procstat -kk' for the stuck process with the long line wrapped. PID TID COMM TDNAME KSTACK 877 100161 Xorg - radeon_gem_busy_ioctl+0x30 drm_ioctl_kernel+0xf1 drm_ioctl+0x279 linux_file_ioctl+0x298 kern_ioctl+0x284 sys_ioctl+0x157 amd64_syscall+0x273 fast_syscall_common+0x101 877 100344 Xorg X:rcs0 mi_switch+0xcb sleepq_catch_signals+0x35d sleepq_wait_sig+0xc _sleep+0x1bd umtxq_sleep+0x132 do_wait+0x3d6 __umtx_op_wait_uint_private+0x7e amd64_syscall+0x273 fast_syscall_common+0x101 It looks like radeonkms+drm is getting stuck. -- Steve