From owner-freebsd-current@FreeBSD.ORG Tue Feb 27 08:44:07 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CBB116A402 for ; Tue, 27 Feb 2007 08:44:07 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 318FD13C47E for ; Tue, 27 Feb 2007 08:44:07 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E42D04979C; Tue, 27 Feb 2007 03:44:06 -0500 (EST) Date: Tue, 27 Feb 2007 08:44:06 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jiawei Ye In-Reply-To: Message-ID: <20070227084214.Y56223@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current Subject: Re: Processes stuck in *unp_m after recent uipc changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 27 Feb 2007 08:44:07 -0000 On Tue, 27 Feb 2007, Jiawei Ye wrote: > With the latest uipc locking changes, I experienced a hard lockup on my > -current machine. Many processes got stuck in *unp_m state and > ctrl-alt-delete at the console cannot properly restart the machine and I had > to hard-reset (no coredump available). Is there anyway to diagnose this? Please configure WITNESS, DDB, and BREAK_TO_DEBUGGER on a box with a serial console. Then attach the output of "ps", "show alllocks", and "alltrace" to an e-mail. With any luck, this is a leaked lock in some missed error case and we can just add a missing unlock. Thanks! Robert N M Watson Computer Laboratory University of Cambridge