From owner-freebsd-current@FreeBSD.ORG Fri Oct 22 14:34:13 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 4D68916A4CE for ; Fri, 22 Oct 2004 14:34:13 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DE5343D55 for ; Fri, 22 Oct 2004 14:34:12 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])i9MEWqxn009437; Fri, 22 Oct 2004 17:33:32 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) i9MEQ4Gf045101; Fri, 22 Oct 2004 17:26:04 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)i9MEQ4va045100; Fri, 22 Oct 2004 17:26:04 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Fri, 22 Oct 2004 17:26:04 +0300 From: Giorgos Keramidas To: cpghost@cordula.ws Message-ID: <20041022142603.GA43820@orion.daedalusnetworks.priv> References: <20041022112947.GA96234@orion.daedalusnetworks.priv> <20041022133333.GA561@bsdbox.farid-hajji.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041022133333.GA561@bsdbox.farid-hajji.net> cc: freebsd-current@freebsd.org Subject: Re: delayed process exit 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: Fri, 22 Oct 2004 14:34:13 -0000 On 2004-10-22 15:33, cpghost@cordula.ws wrote: > On Fri, Oct 22, 2004 at 02:29:47PM +0300, Giorgos Keramidas wrote: > > Some times, in a seemingly unpredictable manner, exiting processes take > > a lot of time to finish. I'm seeing this almost every time I exit > > Emacs, because bash takes a long time to show me a shell prompt. > > This is a known issue, that has AFAICS not yet been solved (at least > not MFC-ed in RELENG_5 as of Oct. 21st). > > The problem is not with the exiting process, but with the wakeup > of its parent. There seems to be some bug in the scheduler that > results in LONG (1 to 5 seconds) delays to wakeup processes that > have been swapped out. Nearly every swapped out process can be > affected by this bug. Ah, I see... Thanks for the detailed explanation! At least, now I'm not worried that something I did locally has caused the problem. Do you perchance know if this affects both SCHED_ULE and SCHED_BSD? - Giorgos