From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 12:19:18 2004 Return-Path: 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 D785116A4CE for ; Thu, 4 Mar 2004 12:19:18 -0800 (PST) Received: from math.uic.edu (shell.math.uic.edu [131.193.178.53]) by mx1.FreeBSD.org (Postfix) with SMTP id 8F7E743D1F for ; Thu, 4 Mar 2004 12:19:18 -0800 (PST) (envelope-from vladimir@math.uic.edu) Received: (qmail 27582 invoked by uid 31415); 4 Mar 2004 20:19:17 -0000 From: vladimir@math.uic.edu Date: Thu, 4 Mar 2004 14:19:17 -0600 To: freebsd-current@freebsd.org Message-ID: <20040304201917.GB27377@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 20:19:18 -0000 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. -- Vladimir