From owner-freebsd-current@FreeBSD.ORG Tue Sep 7 16:39:53 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 1F7A116A4CE for ; Tue, 7 Sep 2004 16:39:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C36A443D2F for ; Tue, 7 Sep 2004 16:39:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i87GeCGQ004731; Tue, 7 Sep 2004 10:40:13 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <413DE3AB.9080707@samsco.org> Date: Tue, 07 Sep 2004 10:36:59 -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: rnejdl@ringofsaturn.com References: <33307.12.148.147.242.1094574244.squirrel@mail.ringofsaturn.com> In-Reply-To: <33307.12.148.147.242.1094574244.squirrel@mail.ringofsaturn.com> 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: current@freebsd.org Subject: Re: Beta 3 Crash with machdep.hlt_logical_cpus 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, 07 Sep 2004 16:39:53 -0000 Rusty Nejdl wrote: > I am running on a Dual 1.8 Ghz Xeon box and I have hyperthreading turned > on in the BIOS such that it appears that I have 4 processors. I am not > physically at the machine right now but wanted to report a problem I had > today. I changed machdep.hlt_logical_cpus from 0 to 1 while running and > the system completely froze up. I don't know what error occurred as I > wasn't at the machine and have rebooted since then. I do know that using > 5.2 I was able to do this and the sytstem would move all the processes to > the correct CPU's. Not sure if anyone else has seen this. > > Rusty Nejdl > This is a known problem with the SCHED_ULE scheduler. Fixing it doesn't appear to be trivial, so we are considering other alternatives for RELENG_5 and 5.3, including switching back to the 4BSD scheduler. The 4BSD scheduler also appears to be much more stable than ULE, especially with kernel preemption enabled. Scott