From owner-freebsd-current@FreeBSD.ORG Mon Apr 17 11:56:31 2006 Return-Path: X-Original-To: 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 8D70916A403 for ; Mon, 17 Apr 2006 11:56:31 +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 2730D43D45 for ; Mon, 17 Apr 2006 11:56:31 +0000 (GMT) (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 C6B4846B10; Mon, 17 Apr 2006 07:56:30 -0400 (EDT) Date: Mon, 17 Apr 2006 12:56:30 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Peter Kostouros In-Reply-To: <444349E9.2090800@melbpc.org.au> Message-ID: <20060417125443.G36452@fledge.watson.org> References: <444349E9.2090800@melbpc.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@FreeBSD.ORG Subject: Re: [panic] lock ... is not initialized 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: Mon, 17 Apr 2006 11:56:31 -0000 On Mon, 17 Apr 2006, Peter Kostouros wrote: > I have attached a debug session that I hope someone finds useful in tracking > the panic. My sources are from 07APR2006. > > My system panicked each time I tried to portupgrade net-im/amsn. > > Please let me know if I can provide further information. Could you file this as a PR, forward me the PR reciept, and keep the debugging information around for a couple of weeks? I'm currently on travel, but have received one other report of similar symptoms. I'll be back in the UK around the 21st, and can investigate in detail then. It looks like, under some circumstances, we enter the socket free code a second time for the same socket, which is not a good thing, but it will take some fairly intensive debugging and code reading to track that down, which I can't do currently. Thanks, Robert N M Watson > > -- > > Regards > > Peter > > As always the organisation disavows knowledge of this email > >