From owner-freebsd-current@FreeBSD.ORG Mon Feb 14 14:08:24 2005 Return-Path: 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 A0F5F16A4CE for ; Mon, 14 Feb 2005 14:08:24 +0000 (GMT) Received: from arthur.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id E248643D48 for ; Mon, 14 Feb 2005 14:08:23 +0000 (GMT) (envelope-from simon@arthur.nitro.dk) Received: by arthur.nitro.dk (Postfix, from userid 3000) id 1F17511959; Mon, 14 Feb 2005 15:08:22 +0100 (CET) Date: Mon, 14 Feb 2005 15:08:21 +0100 From: "Simon L. Nielsen" To: Jeff Roberson Message-ID: <20050214140821.GC737@arthur.nitro.dk> References: <20050125222311.GB851@zaphod.nitro.dk> <20050126071039.Y18864@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw" Content-Disposition: inline In-Reply-To: <20050126071039.Y18864@mail.chesapeake.net> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: Panic: mutex Giant not owned at sys/nfsclient/nfs_socket.c:461 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Feb 2005 14:08:24 -0000 --jy6Sn24JjFx/iggw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2005.01.26 07:11:26 -0500, Jeff Roberson wrote: > On Tue, 25 Jan 2005, Simon L. Nielsen wrote: >=20 > > Hello > > > > With -CURRENT from today (and also from yesterday for that matter) I > > get the panic "mutex Giant not owned at > > /usr/src/sys/nfsclient/nfs_socket.c:461" sometimes (probably 1/3 of > > the times) when accessing a NFS mount. The mount was /FreeBSD, and it > > panics just by typing "cd /Free" in a shell. My last good kernel > > was from Jan 17. Does this make sense to anyone or is more > > information needed? >=20 > This seems as if it could be caused by my most recent commit, but no one > else is having problems with nfs. Can you cvsup again and see if it's > still happening? After I got back from vacation and updated my system I have not had any panics so it seems it was a temporary problem that has been fixed. --=20 Simon L. Nielsen --jy6Sn24JjFx/iggw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCELDVh9pcDSc1mlERAvaHAKDEhUiA/UBKivUHFbZDyvBFxLkBwACePx+z Mv9z15zU9sro3Gj/E5xhquQ= =Mrxv -----END PGP SIGNATURE----- --jy6Sn24JjFx/iggw--