From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 19:24:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55ECB16A4CF; Thu, 21 Oct 2004 19:24:01 +0000 (GMT) Received: from corbulon.video-collage.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2D4343D46; Thu, 21 Oct 2004 19:24:00 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i9LJNwEq029214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Oct 2004 15:23:59 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) Received: from localhost (mteterin@localhost [127.0.0.1]) i9LJNrgw057511; Thu, 21 Oct 2004 15:23:53 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: current@FreeBSD.org Date: Thu, 21 Oct 2004 15:23:52 -0400 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410211523.52663@misha-mx.virtual-estates.net> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Mailman-Approved-At: Fri, 22 Oct 2004 11:56:47 +0000 cc: threads@FreeBSD.org cc: kde@FreeBSD.org Subject: unkillable multithreaded processes stuck in `STOP' state X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 19:24:01 -0000 Hello! This happened twice already -- first with KMail and now with Kontact. A process crashes as usual (KDE's 3.3.0 release was of unusually low quality), and seems to go away, except it does not. It stays in the `STOP' (according to top(1)) or in the `T' (as per ps(1)) state and can not be killed -- neither with -CONT, nor with -KILL. There is also a zombie-child of it: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1042 1096 1 57 8 0 68044 50524 - T ?? 0:27,88 kontact 1042 4903 1096 0 -84 0 0 0 - Z ?? 0:03,07 This is all, probably, due to something in KDE's attempts to capture crashes and collect backtraces for better bug reports. But whatever bugs they may have there, having an unkillable process -- of any kind -- worries me greatly. Is this a known issue, or is a PR warranted? I'm running a fresh -current with libpthread.so by default, using a P4 with HTT enabled -- two "logical processes", one of which is occupied by setiathome -- my way of testing out a new motherboard. Thanks! -mi