From owner-freebsd-current@FreeBSD.ORG Sun Mar 26 17:34:44 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 1B02016A41F for ; Sun, 26 Mar 2006 17:34:44 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2D0D43D45 for ; Sun, 26 Mar 2006 17:34:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BD3711A4D88; Sun, 26 Mar 2006 09:34:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1F66D511D1; Sun, 26 Mar 2006 12:34:43 -0500 (EST) Date: Sun, 26 Mar 2006 12:34:42 -0500 From: Kris Kennaway To: Joao Barros Message-ID: <20060326173442.GA28690@xor.obsecurity.org> References: <70e8236f0603260715u54e4640di18300fa1fd031c4f@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <70e8236f0603260715u54e4640di18300fa1fd031c4f@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: lockmgr: thread 0xc385ebd0 unlocking unheld lock 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: Sun, 26 Mar 2006 17:34:44 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Mar 26, 2006 at 04:15:47PM +0100, Joao Barros wrote: > Last night I was mounting a windows share with mount_smbfs and > browsing it via apache and I got the machine to panic twice. I was > tired and went to bed. > Today I can't replicate the panic but this always happens when I unmount: There is a PR about this - so you should add your traces there if it doesn't include them. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEJtCyWry0BWjoQKURAgZvAJ4hoemum0W4kNtpQL5qTPVp2DjKEQCeILrk Gmj7TkRzQFCy2lb34DxA/Sc= =MCqp -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--