From owner-freebsd-current@FreeBSD.ORG  Mon Apr 21 11:12:14 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 949B137B405
	for <freebsd-current@freebsd.org>;
	Mon, 21 Apr 2003 11:12:14 -0700 (PDT)
Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F33C443FDD
	for <freebsd-current@freebsd.org>;
	Mon, 21 Apr 2003 11:12:13 -0700 (PDT)
	(envelope-from mhunter@ack.Berkeley.EDU)
Received: (from mhunter@localhost)
	by ack.Berkeley.EDU (8.11.3/8.11.3) id h3LICCZ00705;
	Mon, 21 Apr 2003 11:12:12 -0700 (PDT)
Date: Mon, 21 Apr 2003 11:12:12 -0700
From: Mike Hunter <mhunter@ack.Berkeley.EDU>
To: Craig Reyenga <creyenga@connectmail.carleton.ca>
Message-ID: <20030421181212.GB28257@ack.Berkeley.EDU>
References: <000501c307ad$86897d80$0200000a@fireball>
	<20030421162242.GB23473@ack.Berkeley.EDU>
	<000d01c3082f$0ef83ae0$0200000a@fireball>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000d01c3082f$0ef83ae0$0200000a@fireball>
User-Agent: Mutt/1.4i
cc: freebsd-current@freebsd.org
Subject: Re: Hang after running out of memory
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2003 18:12:14 -0000

On Apr 21, "Craig Reyenga" wrote:

> From: "Mike Hunter" <mhunter@ack.berkeley.edu>
> > I've experienced similar things after running out of memory.  It seemed
> > like the scheduler went crazy:  The only way I could get my ssh session to
> > keep talking was to start other ssh sessions, which would buy me about 20
> > keystrokes.  shutdown -r got half done and failed into a weird state.  I
> > think the kernel was from around April 8.
> >
> 
> Was it SCHED_ULE? That's the one I've been using.

No, it's SCHED_4BSD.  I think my scheduler remark was unfounded.  What I
should have said is that doing weird stuff like banging on the keys and
making new ssh connections into the box seemed to help the terminal I was
actually trying to use get cycles.  There are probably more things than
just a wacked out scheduler that could produce that.

Mike