Re: panic: Lock so_rcv_sx not exclusively locked

From: Jos Backus <jos_at_catnook.com>
Date: Mon, 28 Jan 2008 17:59:16 -0800
On Mon, Jan 28, 2008 at 08:49:41PM +0000, Robert Watson wrote:
> On Mon, 28 Jan 2008, Jos Backus wrote:
> 
>> Recent -current kernels can reliably be made to panic by killing 
>> npviewer.bin. Right before killing, npviewer.bin shows up like this in 
>> top:
>> 
>> 6288 jos 1 45 5 62844K 36788K so_rcv 0:08 0.00% npviewer.bin
> 
> Is this a multithreaded app?  If so, could you look and see if you can find 
> the other threads in npviewer.bin in the kernel (info thread, etc) and get 
> stack traces for those threads as well?

It's a multithreaded Linux app, installed through ports; see the attached
file. Please let me know if you'd like me to gather more information.

Thanks!

-- 
Jos Backus
jos at catnook.com

Received on Tue Jan 29 2008 - 00:58:55 UTC

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