Date: Wed, 3 Oct 2012 18:54:52 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Norbert Aschendorff <norbert.aschendorff@yahoo.de>, freebsd-stable@freebsd.org Subject: Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS" Message-ID: <20121003155452.GY35915@deviant.kiev.zoral.com.ua> In-Reply-To: <37099006.1631279.1349270651574.JavaMail.root@erie.cs.uoguelph.ca> References: <506BFECE.3020006@yahoo.de> <37099006.1631279.1349270651574.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--oYrjhH26xX5Rz9aF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 03, 2012 at 09:24:11AM -0400, Rick Macklem wrote: > Norbert Aschendorff wrote: > > Another logs - even with a /var/crash crash report :) > >=20 > > Please note: The /var/crash files stem from another crash than the big > > syslog does! > >=20 > > The syslog file inside the tarball is about 4.7 MB; it contains > > everything since the start of the crash. > >=20 > > New /var/crash files: > > http://lbo.spheniscida.de/Files/nfs-rsync-crash-witnessII.tgz > > New syslog file: > > http://lbo.spheniscida.de/Files/nfs-rsync-crash-witnessIII-only-message= s.tgz > >=20 > > (Both < 100 KB) > >=20 > > The used kernel is called GENERIC-OWN-WITNESS and has all three > > WITNESS > > options enabled and nothing else. > >=20 > I'll take a look at these later to-day. >=20 > > But I just get an idea: Should I try it without Rick's NFSv4 > > numeric-uid-gid patch? Or is that completely unrelated? > > @Rick: Can you assure that it is impossible that the patch added this > > bug? > Doesn't seem likely, but I'd never guarantee that a patch isn't broken > and/or can never have weird side effects. So, it might be worth trying > backing the patch out and seeing if it still crashes. >=20 > Thanks for doing this testing, rick So do you use nullfs exported mounts ? And stable ? Can you try to remove nullfs from the set up ? I wonder if there are any calls to VFS_FHTOVP() with LK_INTERLOCK set. Specifically, nullfs probably does not handle LK_INTERLOCK properly both for nullfs_vget and nullfs_fhtovp() at all. --oYrjhH26xX5Rz9aF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlBsX8wACgkQC3+MBN1Mb4jVUgCdGLTaqb5MUC28ZAAFgkejgltV MsgAnj4I7ucVhtjvuscj+PBZUIel/XiS =Zqwx -----END PGP SIGNATURE----- --oYrjhH26xX5Rz9aF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121003155452.GY35915>