From owner-freebsd-hackers@FreeBSD.ORG  Wed Jun 29 01:48:51 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 018C9106566B
	for <freebsd-hackers@freebsd.org>; Wed, 29 Jun 2011 01:48:51 +0000 (UTC)
	(envelope-from yuri@rawbw.com)
Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45])
	by mx1.freebsd.org (Postfix) with ESMTP id E0CF38FC12
	for <freebsd-hackers@freebsd.org>; Wed, 29 Jun 2011 01:48:50 +0000 (UTC)
Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1])
	(authenticated bits=0)
	by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id p5T1gEMj089805;
	Tue, 28 Jun 2011 18:42:14 -0700 (PDT) (envelope-from yuri@rawbw.com)
Message-ID: <3C3128F5.7030303@rawbw.com>
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.1.16) Gecko/20101211 Thunderbird/3.0.11
MIME-Version: 1.0
To: Sergey Babkin <babkin@verizon.net>
References: <194213048.2218776.1309307083380.JavaMail.root@vznit170078>
In-Reply-To: <194213048.2218776.1309307083380.JavaMail.root@vznit170078>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: jhell@DataIX.net, freebsd-hackers@freebsd.org
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
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
Date: Wed, 29 Jun 2011 01:48:51 -0000
X-Original-Date: Mon, 31 Dec 2001 19:11:49 -0800
X-List-Received-Date: Wed, 29 Jun 2011 01:48:51 -0000

On 06/28/2011 17:24, Sergey Babkin wrote:
>
> (Sorry about quoting, it doesn't always work well from the web client).
> Most probably the process is running in an endless loop in the kernel 
> mode.
> Where it got after entering the STOP state. Remember, the signals are 
> processed
> only after the process exits from the 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.

How is this normally possible to make program to loop in kernel mode on 
-STABLE kernel? Doesn't this mean bug in kernel?

Yuri