Re: Processes stuck in *unp_m after recent uipc changes

From: Robert Watson <rwatson_at_FreeBSD.org>
Date: Tue, 27 Feb 2007 09:05:53 +0000 (GMT)
On Tue, 27 Feb 2007, Robert Watson wrote:

> 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!

Obviously, INVARIANTS also good on general principle. :-)

See the handbook chapter on debugging, and in particular live DDB debugging, 
if you're running into any problems.

Robert N M Watson
Computer Laboratory
University of Cambridge
Received on Tue Feb 27 2007 - 08:05:54 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:06 UTC