Date: Wed, 03 Oct 2012 11:01:02 +0200 From: Norbert Aschendorff <norbert.aschendorff@yahoo.de> To: freebsd-stable@freebsd.org Subject: Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS" Message-ID: <506BFECE.3020006@yahoo.de> In-Reply-To: <201210021715.19310.jhb@freebsd.org> References: <1990296074.1528480.1349129938870.JavaMail.root@erie.cs.uoguelph.ca> <506B3037.60201@yahoo.de> <201210021715.19310.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Another logs - even with a /var/crash crash report :) Please note: The /var/crash files stem from another crash than the big syslog does! The syslog file inside the tarball is about 4.7 MB; it contains everything since the start of the crash. 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-messages.tgz (Both < 100 KB) The used kernel is called GENERIC-OWN-WITNESS and has all three WITNESS options enabled and nothing else. 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? --norbert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506BFECE.3020006>