From owner-freebsd-current@FreeBSD.ORG Tue Oct 26 02:28:27 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 80C0D16A4CE; Tue, 26 Oct 2004 02:28:27 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C8E543D54; Tue, 26 Oct 2004 02:28:27 +0000 (GMT) (envelope-from scottl@freebsd.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 i9Q2TODM078882; Mon, 25 Oct 2004 20:29:24 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <417DB5E1.7000308@freebsd.org> Date: Mon, 25 Oct 2004 20:26:41 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current , developers@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime 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 Subject: HEADS UP: ULE off in 5.3 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: Tue, 26 Oct 2004 02:28:27 -0000 All, A lot of poeple have noted recently that a lot of bug reports are coming in with strange symptoms, and only after a lot of detective work does it turn out that the submitter is using the ULE scheduler. We turned off the ULE scheduler months ago and tried to make it clear that it has problems and is not considered stable. Since there are likely many people out there that might not be aware of what scheduler they are using, I've set the ULE source code to error out and not compile at all for RELENG_5 and RELENG_5_3. The time spent debugging ULE-induced problems is causing way too much lost time, and we need to focus on debugging the supported configurations, not the unsupported ones. Scott