From owner-freebsd-current@FreeBSD.ORG Wed Oct 13 02:53:48 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 930A116A4CE for ; Wed, 13 Oct 2004 02:53:48 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBF7343D48 for ; Wed, 13 Oct 2004 02:53:47 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 2E0A578C55 for ; Tue, 12 Oct 2004 22:56:06 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id E1BAC78C35 for ; Tue, 12 Oct 2004 22:56:01 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 522A3170E2; Tue, 12 Oct 2004 22:53:40 -0400 (EDT) Date: Tue, 12 Oct 2004 22:53:40 -0400 From: Damian Gerow To: current@FreeBSD.org Message-ID: <20041013025340.GA30381@afflictions.org> Mail-Followup-To: current@FreeBSD.org References: <200410121556.51976.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410121556.51976.jhb@FreeBSD.org> X-Operating-System: FreeBSD 5.3-BETA7 on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at afflictions.org Subject: Re: Possible fix for KSE threads that never wake up 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: Wed, 13 Oct 2004 02:53:48 -0000 Thus spake John Baldwin (jhb@FreeBSD.org) [12/10/04 15:59]: : Currently the KSE code arbitrarily sets the SLEEPING inhibitor on any thread : it suspends that is on the sleep queue. Threads that are on the sleep queue : however are not always asleep and it adds needless complication and : opportunity for bugs (if the inhibitor is not otherwise cleared the thread : may never get to run again). Since the suspension code uses its own : inhibitor the hack isn't even needed. This patch just turns it off. Let me : know if this fixes any problems people are seeing: Nope. But it did turn up something strange. I booted into a kernel sup'ed about two hours ago, tested it against firefox, it hung, so I applied the patch, recompiled, installed, and rebooted. When I tested /that/ time around, I successfully ran a few dig's (which I didn't test before), then I ran firefox, then poof! dig stopped working for me. I can also say that once I have one (or more) hung program(s), my system will eventually dissolve into a state of complete unusability -- random processes will just start to hang. There doesn't seem to be a pattern to this -- it once took weeks, it once took days, it once took hours. Earlier tonight (after my first test against firefox alone), it took seconds. I am trying to rebuild firefox, just for kicks. We'll see if that has any effect. Unfortunately, I can't offer any more than this (like debugging output and such).