From owner-freebsd-current Fri Feb 28 11:24:12 2003 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 D7F7037B405 for ; Fri, 28 Feb 2003 11:24:11 -0800 (PST) Received: from smak.uberduper.com (12-213-188-143.client.attbi.com [12.213.188.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B55043FBD for ; Fri, 28 Feb 2003 11:24:11 -0800 (PST) (envelope-from james@uberduper.com) Received: from uberduper.com (unknown [208.33.24.5]) by smak.uberduper.com (Postfix) with ESMTP id DC16C9C90E for ; Fri, 28 Feb 2003 11:24:15 -0800 (PST) Message-ID: <3E5FB785.6000704@uberduper.com> Date: Fri, 28 Feb 2003 11:24:53 -0800 From: James Satterfield User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030227 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Subject: SCHED_ULE oddities Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG First off, I found SCHED_ULE to be very slow. More importantly, the two times that I rebooted while running it, shutdown failed to sync the disks. On the second reboot, I had just installed a new kernel. The results of this were ugly. /boot/kernel and /boot/kernel.old disappeared. I've since gotten the box back up and running using a SCHED_4BSD kernel and I no longer have these sync problems. James. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message