From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 21:21:31 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 2151616A4CE; Thu, 21 Oct 2004 21:21:31 +0000 (GMT) Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B31043D39; Thu, 21 Oct 2004 21:21:29 +0000 (GMT) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (oleg@localhost [127.0.0.1]) by core.zp.ua (8.13.1/8.13.1) with ESMTP id i9LLL5Hl001271; Fri, 22 Oct 2004 00:21:05 +0300 (EEST) (envelope-from oleg@core.zp.ua) Received: (from oleg@localhost) by core.zp.ua (8.13.1/8.13.1/Submit) id i9LLL56I001270; Fri, 22 Oct 2004 00:21:05 +0300 (EEST) (envelope-from oleg) Date: Fri, 22 Oct 2004 00:21:05 +0300 From: "Oleg V. Nauman" To: Michael Nottebrock Message-ID: <20041021212105.GX12192@core.zp.ua> Mail-Followup-To: Michael Nottebrock , kde-freebsd@freebsd.kde.org, threads@freebsd.org, Mikhail Teterin , kde@freebsd.org, current@freebsd.org References: <200410211523.52663@misha-mx.virtual-estates.net> <200410212227.02663.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200410212227.02663.michaelnottebrock@gmx.net> User-Agent: Mutt/1.5.6i cc: threads@freebsd.org cc: Mikhail Teterin cc: kde@freebsd.org cc: current@freebsd.org cc: kde-freebsd@freebsd.kde.org Subject: Re: [kde-freebsd] 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 21:21:31 -0000 On Thu, Oct 21, 2004 at 10:26:50PM +0200, Michael Nottebrock wrote: > On Thursday, 21. October 2004 21:23, Mikhail Teterin wrote: > > 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. > > [...] > > > 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? > > There have been no similar reports (to my knowledge) and I haven't seen > anything similar on either 4.x or 5.x (I don't run 6-CURRENT). This problem looks like not specific to KDE, but for OpenOffice and clamav-milter at least. Unkillable by -9 OpenOffice (5.3-BETA7,information from local mailing list): ps -O flags,lim,lockname,mwchan,nwchan,sigcatch,sigignore,sigmask,state,wchan,xstat 2194 PID F LIM LOCK MWCHAN NWCHAN CAUGHT IGNORED BLOCKED STAT WCHAN XSTAT TT STAT TIME COMMAND 2194 8c081 - - - - 1b80eeb7 781000 fffefeff TL - 0 ?? TL 0:05,47 /usr/local/OpenO clamav-milter (doesn't respond to SIGCONT), but killable by -9 only, without any library mappings (5.3-STABLE): #ps -O flags,lim,lockname,mwchan,nwchan,sig,sigcatch,sigignore,sigmask,state,wchan,xstat 418 PID F LIM LOCK MWCHAN NWCHAN PENDING CAUGHT IGNORED BLOCKED STAT WCHAN XSTAT TT STAT TIME COMMAND 418 88180 - - - - 0 10040000 87a9001 fffefeff TLs - 0 ?? TLs 0:02.78 /usr/local/sbin/ # kill -CONT 418 #ps -O flags,lim,lockname,mwchan,nwchan,sig,sigcatch,sigignore,sigmask,state,wchan,xstat 418 PID F LIM LOCK MWCHAN NWCHAN PENDING CAUGHT IGNORED BLOCKED STAT WCHAN XSTAT TT STAT TIME COMMAND 418 288180 - - - - 40000 10040000 87a9001 fffefeff TLs - 0 ?? TLs 0:02.78 /usr/local/sbin/ > > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -- NO37-RIPE