From owner-freebsd-questions@FreeBSD.ORG Mon Mar 23 18:14:49 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89C33FC for ; Mon, 23 Mar 2015 18:14:49 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1.freebsd.org (Postfix) with ESMTP id 728F4667 for ; Mon, 23 Mar 2015 18:14:48 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mwork.nabble.com (Postfix) with ESMTP id 861C31861B42 for ; Mon, 23 Mar 2015 11:14:50 -0700 (PDT) Date: Mon, 23 Mar 2015 11:14:34 -0700 (MST) From: BBlister To: freebsd-questions@freebsd.org Message-ID: <1427134474819-5999426.post@n5.nabble.com> In-Reply-To: <1427109169038-5999345.post@n5.nabble.com> References: <1427109169038-5999345.post@n5.nabble.com> Subject: Re: Un-kill-able process hang at umtxpi state with 100% cpu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 18:14:49 -0000 Following an advice from a user of this list, I did a kill -STOP 35662 in order to minimize the CPU consumption and as soon as I hit enter the process disappeared (died). I had already killed its parent, but it was not possible to kill this process. By sending the STOP signal it was killed. Thanks again. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Un-kill-able-process-hang-at-umtxpi-state-with-100-cpu-tp5999345p5999426.html Sent from the freebsd-questions mailing list archive at Nabble.com.