From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 18:44:48 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 A138F1065671 for ; Tue, 23 Sep 2008 18:44:48 +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 7A97D8FC13 for ; Tue, 23 Sep 2008 18:44:48 +0000 (UTC) (envelope-from mi+mill@aldan.algebra.com) Received: (qmail 8497 invoked from network); 23 Sep 2008 18:44:48 -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 18:44:47 -0000 Message-ID: <48D93914.3020502@aldan.algebra.com> Date: Tue, 23 Sep 2008 14:44:36 -0400 From: Mikhail Teterin User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: "Paul B. Mahol" References: <48D92589.8000200@aldan.algebra.com> <3a142e750809231125o579445baufb5f2676e4d9a2ca@mail.gmail.com> In-Reply-To: <3a142e750809231125o579445baufb5f2676e4d9a2ca@mail.gmail.com> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org 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 18:44:48 -0000 Paul B. Mahol ΞΑΠΙΣΑΧ(ΜΑ): >> Let me know, what else I can do to help fix this bug -- I'm going to >> reboot the machine tonight... Should I switch to SCHED_ULE as a >> work-around? >> > > SCHED_BSD4 is suboptimal for 4 CPUs, and it is replaced with SCHED_ULE > on 7 STABLE. > Thanks, Paul for the explanation. I've heard of some problems still lingering in the ULE and figured, I'll stay with the BSD-scheduler for a while. I guess, it is time to switch. 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. In the July 26th sys/conf/NOTES file the SCHED_BSD4 is still on the default option.... Yours, -mi