From owner-freebsd-current Mon Feb 26 4: 2: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-74.dsl.lsan03.pacbell.net [63.207.60.74]) by hub.freebsd.org (Postfix) with ESMTP id 03F9037B503 for ; Mon, 26 Feb 2001 04:02:06 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8141366B09; Mon, 26 Feb 2001 04:02:05 -0800 (PST) Date: Mon, 26 Feb 2001 04:02:05 -0800 From: Kris Kennaway To: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Scheduler panic Message-ID: <20010226040205.A552@mollari.cthul.hu> References: <20010225222942.A14476@mollari.cthul.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010225222942.A14476@mollari.cthul.hu>; from kris@obsecurity.org on Sun, Feb 25, 2001 at 10:29:42PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. Kris --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6mkW8Wry0BWjoQKURAgCjAKCqTa08sFjJyFf5YH1f2zqoqNx6LwCeLrDM nBALxR+RoOr8vEVE08p71IQ= =+o82 -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message