From owner-freebsd-net@FreeBSD.ORG Fri Mar 13 11:35:14 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4479910656E4 for ; Fri, 13 Mar 2009 11:35:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1EEAB8FC1B for ; Fri, 13 Mar 2009 11:35:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id B426D46B2E; Fri, 13 Mar 2009 07:35:13 -0400 (EDT) Date: Fri, 13 Mar 2009 11:35:13 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Richard Tector In-Reply-To: <49B92090.40406@thekeelecentre.com> Message-ID: References: <200903101530.n2AFU3ud007640@freefall.freebsd.org> <49B92090.40406@thekeelecentre.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@FreeBSD.org, Richard Tector Subject: Re: kern/129846: [panic] /usr/sbin/ppp causes panic "Sleeping thread owns a non-sleepable lock X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Mar 2009 11:35:14 -0000 On Thu, 12 Mar 2009, Richard Tector wrote: > Robert Watson wrote: >> On Tue, 10 Mar 2009, Richard Tector wrote: >> >>> Just a me too on 7.1-STABLE amd64 (as of 2009-03-05 at least). Note this >>> does not happen with a 7.1-RELEASE kernel, so I'm assuming it's not >>> userland. >> >> This problem is believed fixed as of r189531, committed 8 March -- could >> you try updating and see if that helps? A more complete description of the >> problem can be found here: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=132222 > > Been running for just over 14 hours now with the new kernel and no problems > observed. I think can you close this PR now, thanks. Thanks for the feedback -- let me know if you see the problem recur. Robert N M Watson Computer Laboratory University of Cambridge