From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 2 06:30:24 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3286016A4A7 for ; Tue, 2 Jan 2007 06:30:24 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D42C713C45D for ; Tue, 2 Jan 2007 06:30:23 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l026UNXK067345 for ; Tue, 2 Jan 2007 06:30:23 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l026UNds067343; Tue, 2 Jan 2007 06:30:23 GMT (envelope-from gnats) Date: Tue, 2 Jan 2007 06:30:23 GMT Message-Id: <200701020630.l026UNds067343@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Andrew Pantyukhin" Cc: Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrew Pantyukhin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2007 06:30:24 -0000 The following reply was made to PR kern/72979; it has been noted by GNATS. From: "Andrew Pantyukhin" To: "David Xu" Cc: bug-followup@freebsd.org, "Mikhail Teterin" Subject: Re: kern/72979: unkillable process(es) stuck in `STOP' state Date: Tue, 2 Jan 2007 09:26:02 +0300 On 1/2/07, David Xu wrote: > On Tuesday 02 January 2007 10:55, Andrew Pantyukhin wrote: > > > It's hard to reproduce it even as it is. Actually, I think > > it's something current-ish. I've been experiencing some > > instabilities for a week or two I think. I'll keep updating > > and tell you if I stumble over it again. > > > > Thanks! > > Do you know the python process is multi-threaded or not ? It is. Actually, before rebooting back then I tried to kill another process (the audacious music player), which ended up in the very same state, so I believe it was a temporary system-wide condition, though all other processes ended successfully.