From owner-freebsd-hackers@freebsd.org Thu Nov 28 19:50:23 2019 Return-Path: Delivered-To: freebsd-hackers@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 091E61B53CC for ; Thu, 28 Nov 2019 19:50:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47P7XY58VTz40tp for ; Thu, 28 Nov 2019 19:50:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id xASJoDHP004779 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 28 Nov 2019 21:50:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua xASJoDHP004779 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id xASJoDlY004776; Thu, 28 Nov 2019 21:50:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 28 Nov 2019 21:50:13 +0200 From: Konstantin Belousov To: Willem Jan Withagen Cc: FreeBSD Hackers , Eugene Grosbein Subject: Re: Process in T state does not want to die..... Message-ID: <20191128195013.GU10580@kib.kiev.ua> References: <966f830c-bf09-3683-90da-e70aa343cc16@digiware.nl> <3c57e51d-fa36-39a3-9691-49698e8d2124@grosbein.net> <91490c30-45e9-3c38-c55b-12534fd09e28@digiware.nl> <20191128115122.GN10580@kib.kiev.ua> <296874db-40f0-c7c9-a573-410e4c86049a@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <296874db-40f0-c7c9-a573-410e4c86049a@digiware.nl> User-Agent: Mutt/1.12.2 (2019-09-21) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 47P7XY58VTz40tp X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; IP_SCORE(0.00)[ip: (-2.75), ipnet: 2001:470::/32(-4.64), asn: 6939(-3.52), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 19:50:23 -0000 On Thu, Nov 28, 2019 at 08:24:43PM +0100, Willem Jan Withagen wrote: > On 28-11-2019 12:51, Konstantin Belousov wrote: > > On Thu, Nov 28, 2019 at 11:37:50AM +0100, Willem Jan Withagen wrote: > >> On 27-11-2019 16:36, Eugene Grosbein wrote: > >>> 27.11.2019 22:11, Willem Jan Withagen wrote: > >>> > >>> [skip] > >>> > >>> Process in state T is STOPPED and prohibited for execution. > >>> It cannot even process signal like SIGTERM or SIGKILL because they are queied waiting for continuation. > >>> You need to resume it with kill -CONT first. > >> Tried that several times, but does not really have any effect. > >> I could check and see if the signals (TERM, KILL) were waiting somewhere? > >> With procstat?? > >> > >> But the original question was more for a way on preventing this state of > >> affairs. > >> Because uptill now the only resolution was to reboot the server, which > >> is not a nice > >> thing for a storage sollution. > >> > >> Hence the: how to debug? question. > > Start with the output from > > $ procstat -kk -L > > Also useful is the output from > > $ ps -o pid,lwp,flags,flags2,state,tracer,command -p > > After that is shown, it could be determined where to look next. > > What is your system version ? > > > This is 12.1 RELEASE... > But I get this: > # procstat -L 3448 > procstat: sysctl method is not supported > > And > > # procstat -kk -L > > Gives me the help info Remove -L.