From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 19:56:46 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1CC2106566B for ; Tue, 23 Sep 2008 19:56:46 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 9B4678FC13 for ; Tue, 23 Sep 2008 19:56:46 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 32100 invoked from network); 23 Sep 2008 19:56:45 -0000 Received: from aldan.algebra.com (HELO [127.0.0.1]) (mi@[216.254.65.224]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Sep 2008 19:56:45 -0000 Message-ID: <48D949F0.10109@aldan.algebra.com> Date: Tue, 23 Sep 2008 15:56:32 -0400 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: josh.carroll@gmail.com References: <48D92589.8000200@aldan.algebra.com> <3a142e750809231125o579445baufb5f2676e4d9a2ca@mail.gmail.com> <48D93914.3020502@aldan.algebra.com> <8cb6106e0809231243q3f874ccap50520dde1e0e63b2@mail.gmail.com> In-Reply-To: <8cb6106e0809231243q3f874ccap50520dde1e0e63b2@mail.gmail.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org, "Paul B. Mahol" Subject: Re: 7.0-stable: a hung process - scheduler bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2008 19:56:46 -0000 Josh Carroll ΞΑΠΙΣΑΧ(ΜΑ): >> However, what I'm seeing on my system today is evidence of the scheduler >> having a bug, rather than merely being suboptimal. If the old scheduler is >> still maintained and supposed to work (however sub-optimally) in 4-CPU >> configurations, I'd expect either inquiries for more debug-information or >> assurances, that the bug is known and worked on. >> > > I'm no expert, but I don't think you can necessarily conclude that it > is the scheduler yet. It very well may be, but I agree that someone > with more expertise hopefully will ask for more detailed debug/trace > information to pin down where the problem lies. > Although the machine seemed fine, it would not launch new processes ever since I tried to start `systat 1 -vm' -- something systat does at start-up must've wedged the system... A process, that was running (cvs over ssh) is currently stuck (according to Ctrl-T) in: load: 0.00 cmd: ssh 59098 [proctree] 0.41u 0.17s 0% 0k I'll reboot it, when I get back home... -mi