From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 29 05:26:16 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 C6D4D106566B for ; Wed, 29 Jun 2011 05:26:16 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 989D68FC08 for ; Wed, 29 Jun 2011 05:26:16 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p5T5Q6gl009567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Jun 2011 22:26:07 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p5T5Q6b1009566; Tue, 28 Jun 2011 22:26:06 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA21126; Tue, 28 Jun 11 22:02:29 PDT Date: Tue, 28 Jun 2011 22:09:40 -0700 From: perryh@pluto.rain.com To: yuri@rawbw.com Message-Id: <4e0ab394.THjNIl1+j9sXmZ4f%perryh@pluto.rain.com> References: <194213048.2218776.1309307083380.JavaMail.root@vznit170078> <3C3128F5.7030303@rawbw.com> In-Reply-To: <3C3128F5.7030303@rawbw.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, babkin@verizon.net, jhell@DataIX.net Subject: 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 05:26:16 -0000 Yuri wrote: > On 06/28/2011 17:24, Sergey Babkin wrote: > > Most probably the process is running in an endless loop in the > > kernel mode ... While it's in the kernel mode, you can't do > > anything to it other than use the kernel debugger. > > How is this normally possible to make program to loop in kernel > mode on -STABLE kernel? Doesn't this mean bug in kernel? In kernel code, but not necessarily in the -STABLE kernel itself -- there could be a problem in a kernel module. I haven't checked, but would not be surprised if VirtualBox included one.