From owner-freebsd-current@FreeBSD.ORG Sat Sep 18 22:50:29 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 7BBDD16A4D4 for ; Sat, 18 Sep 2004 22:50:29 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CC2643D1F for ; Sat, 18 Sep 2004 22:50:29 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8IMo71q018578; Sat, 18 Sep 2004 16:50:07 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <414CBB68.9070800@samsco.org> Date: Sat, 18 Sep 2004 16:49:12 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <1095534403.1151.4.camel@server.mcneil.com> <20040918222412.GA10696@xor.obsecurity.org> In-Reply-To: <20040918222412.GA10696@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: ULE scheduler not quite there yet 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: Sat, 18 Sep 2004 22:50:29 -0000 Kris Kennaway wrote: > On Sat, Sep 18, 2004 at 12:06:43PM -0700, Sean McNeil wrote: > >>I've had good luck with the 4BSD scheduler and PREEMPTION on so I >>thought I would try the ULE scheduler. Was up for just a short time >>before I got the following on my amd64 machine: > > > This is a known problem, BTW. > > Kris There is likely a message at the top of the dmesg output that says, "WARNING: Kernel PREEMPTION is unstable under SCHED_ULE." This has been discussed quite a bit recently and we decided that focusing on the 4BSD scheduler gave us a better chance at having a stable system for 5.3. I still welcome anyone to step in and investigate the problems with ULE. Scott