From owner-freebsd-current@FreeBSD.ORG Fri Oct 22 11:30: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 AA98016A4CE for ; Fri, 22 Oct 2004 11:30:31 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCBC243D48 for ; Fri, 22 Oct 2004 11:30:30 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])i9MBU0Vo026400 for ; Fri, 22 Oct 2004 14:30:20 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) i9MBTlh6096325 for ; Fri, 22 Oct 2004 14:29:47 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)i9MBTlMb096324 for freebsd-current@freebsd.org; Fri, 22 Oct 2004 14:29:47 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Fri, 22 Oct 2004 14:29:47 +0300 From: Giorgos Keramidas To: freebsd-current@freebsd.org Message-ID: <20041022112947.GA96234@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: 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 11:30:31 -0000 Recent versions of CURRENT running on a uniprocessor Celeron @ 1800 have started (some time during this week) to behave a bit strangely. I last updated my home workstation yesterday (Thursday 21 Oct) and the bug is still there. 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. I've tried ktrace on the processes that take a long time to exit, but the timestamp of the last call to exit() is not significantly larger than the rest of the trace output. Whatever causes this happens after exit() has been called. Is anyone else seeing something similar? Any ideas why this might be happening? If you need more information about the setup of the machine (for instance, the kernel config file, since it's running a slightly modified version of GENERIC), I'll have to post a followup when I get home in 5-6 hours. In the meantime, if anyone has some idea that might help me track this, it's also welcome. - Giorgos