From owner-freebsd-current Sat Mar 1 0:53:10 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 0B24237B401 for ; Sat, 1 Mar 2003 00:53:09 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4B2943F3F for ; Sat, 1 Mar 2003 00:53:07 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA31131; Sat, 1 Mar 2003 19:51:49 +1100 Date: Sat, 1 Mar 2003 19:53:26 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Kris Kennaway Cc: James Satterfield , Subject: Re: SCHED_ULE oddities In-Reply-To: <20030228194701.GB86820@rot13.obsecurity.org> Message-ID: <20030301194725.C25711-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Fri, 28 Feb 2003, Kris Kennaway wrote: > On Fri, Feb 28, 2003 at 11:24:53AM -0800, James Satterfield wrote: > > 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. > > It's still inoperable for me as well..I guess Jeff is busy at the > moment. Jeff agreed with that when I sent him a bug report about #!/bin/sh while :; do :; done hanging the system (this gives an unkillable shell, and no other user processes can run). He said that he was going to announce this, but I haven't seen anything. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message