From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 20:10:04 2004
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 DA23316A4CE
	for <freebsd-current@FreeBSD.org>;
	Thu,  4 Mar 2004 20:10:04 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EAEB743D1D
	for <freebsd-current@FreeBSD.org>;
	Thu,  4 Mar 2004 20:10:03 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i2549p7E005937;
	Thu, 4 Mar 2004 20:09:58 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200403050409.i2549p7E005937@gw.catspoiler.org>
Date: Thu, 4 Mar 2004 20:09:51 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: vladimir@math.uic.edu
In-Reply-To: <20040304201917.GB27377@math.uic.edu>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: debugging lockups
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: Fri, 05 Mar 2004 04:10:05 -0000

On  4 Mar, vladimir@math.uic.edu wrote:
> Following up on my previous post  from a couple of days ago with the
> same subject (unfortunately I don't have my original email, so this
> will probably start  a new thread).   A -CURRENT system (built on Mar 3,
> 2004) frequently locks up when typing "ps" or "w", in addition to when
> killing memory-intensive processes.   The system locks up hard, and I
> cannot break into the debugger from the console, although the necessary
> options are compiled into the kernel.

This is a known problem.  See the thread "sysctl spinning (was: Re: ps
Causes Hard Hang)".