From owner-freebsd-current  Mon Feb 26  6:25: 4 2001
Delivered-To: freebsd-current@freebsd.org
Received: from cr66388-a.rchrd1.on.wave.home.com (cr66388-a.rchrd1.on.wave.home.com [24.114.165.24])
	by hub.freebsd.org (Postfix) with ESMTP id 3D50137B491
	for <current@FreeBSD.ORG>; Mon, 26 Feb 2001 06:25:02 -0800 (PST)
	(envelope-from jburkholder0829@home.com)
Received: from cr66388-a.rchrd1.on.wave.home.c (localhost [127.0.0.1])
	by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP
	id 7D1A5BACB; Mon, 26 Feb 2001 09:25:01 -0500 (EST)
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: Kris Kennaway <kris@obsecurity.org>
Cc: current@FreeBSD.ORG
Subject: Re: Scheduler panic 
In-Reply-To: Message from Kris Kennaway <kris@obsecurity.org> 
   of "Mon, 26 Feb 2001 04:02:05 PST." <20010226040205.A552@mollari.cthul.hu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 26 Feb 2001 09:25:01 -0500
From: Jake Burkholder <jburkholder0829@home.com>
Message-Id: <20010226142501.7D1A5BACB@cr66388-a.rchrd1.on.wave.home.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Sun, Feb 25, 2001 at 10:29:42PM -0800, Kris Kennaway wrote:
> > This is on a UP system.
> 
> Had another one of these, under the same conditions.  Both times I was
> running more(1) on a stdin stream which was generated by a "find |
> grep | more" operation, and I suspended the process with ^Z,
> triggering the panic.  Perhaps this will help in tracking down the
> root cause.

I'm pretty sure I know what this is; I'll work up a patch tonight.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message