From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 29 01:24:54 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE930106564A for ; Wed, 29 Jun 2011 01:24:54 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173009pub.verizon.net (vms173009pub.verizon.net [206.46.173.9]) by mx1.freebsd.org (Postfix) with ESMTP id A0B338FC08 for ; Wed, 29 Jun 2011 01:24:54 +0000 (UTC) Received: from vznit170078 ([unknown] [172.18.12.134]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LNI00G2BZT7XR31@vms173009.mailsrvcs.net> for freebsd-hackers@freebsd.org; Tue, 28 Jun 2011 19:24:43 -0500 (CDT) Received: from 173.54.27.21 ([173.54.27.21]) by vznit170078 (Verizon Webmail) with HTTP; Tue, 28 Jun 2011 19:24:43 -0500 (CDT) Date: Tue, 28 Jun 2011 19:24:43 -0500 (CDT) From: Sergey Babkin To: jhell@DataIX.net Message-id: <194213048.2218776.1309307083380.JavaMail.root@vznit170078> Content-transfer-encoding: quoted-printable X-Originating-IP: [173.54.27.21] X-Mailman-Approved-At: Wed, 29 Jun 2011 03:55:05 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: yuri@rawbw.com, freebsd-hackers@freebsd.org Subject: Re: Re: How can process in STOP state consume 200% CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2011 01:24:54 -0000 Jun 28, 2011 04:29:35 PM, jhell@DataIX.net wrote: >> I got Vir= tualBox process in a strange state. It has the status STOP but >>= shows by top as consuming 200% CPU for a very long time. >> How i= s this possible and what does this mean? Process time stays at 0:00 >= ;> TIME. kill -9 doesn't kill it. > > >I would suppose= that because you stopped the clients frontend that the >backend has = not been notified and is doing its best to draw to the >screen causin= g a high CPU usage. (Sorry about quoting, it doesn't always work wel= l from the web client). Most probably the process is running in an endle= ss loop in the kernel mode. Where it got after entering the STOP state. = Remember, the signals are processed only after the process exits from th= e kernel mode to the user mode, and so are the scheduling states. While = it's in the kernel mode, you can't do anything to it other than use the = kernel debugger. -SB