From owner-freebsd-questions@FreeBSD.ORG Mon Mar 23 18:20:14 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 800A4281 for ; Mon, 23 Mar 2015 18:20:14 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 328976B6 for ; Mon, 23 Mar 2015 18:20:14 +0000 (UTC) Received: by qgf74 with SMTP id 74so32009526qgf.2 for ; Mon, 23 Mar 2015 11:20:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=t6qAui3ieva1aZb3yihLl751e/gmzCeQTVK70rvxb6c=; b=EFFdwGZOC1WjNxcCCvDB8xhoLC8eGfX/gY12HH5whMqnAbq9zvM4lPET2FGPavjWgE p3MVQHjY0/LpFITlygbZvtfckjN0OhEcciC+P2lhsgsK7bVC4qpmpkKOI/a+dd4mtT5p ZLCXUis2HOYZaH03tn/xhW1/7+432XoYbEjQVEuCUSL6Tvqn3rK2P8yxZwZ/Szjkq/GU FC/yEoxl7dc0Ad/9fuGQdHrTFk3o2CCEk0CG8J0glSY0ovzISQQsuIZkIhj3lcslJTbI 6vg7jdPAtOrzOzWrcmEsu3MsG4yXuIUjgjzNLz69Wd3f5Z9eTWzlwBhThXf8RohkM1Ky Ag/A== X-Received: by 10.55.55.8 with SMTP id e8mr1002530qka.9.1427134813008; Mon, 23 Mar 2015 11:20:13 -0700 (PDT) Received: from localhost.localdomain ([209.181.150.218]) by mx.google.com with ESMTPSA id f102sm1016713qki.1.2015.03.23.11.20.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2015 11:20:12 -0700 (PDT) Message-ID: <5510594B.6010602@gmail.com> Date: Mon, 23 Mar 2015 12:19:55 -0600 From: jd1008 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Un-kill-able process hang at umtxpi state with 100% cpu References: <1427109169038-5999345.post@n5.nabble.com> <1427134474819-5999426.post@n5.nabble.com> In-Reply-To: <1427134474819-5999426.post@n5.nabble.com> Content-Type: text/plain; charset=windows-1252; format=flowed 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:20:14 -0000 On 03/23/2015 12:14 PM, BBlister wrote: > 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. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Do you know the process name? You might have a malware!!!! Beware!!