Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-05 Thread Norbert Aschendorff
On 10/05/2012 05:40 AM, Konstantin Belousov wrote: > This is the whole difference between stable and HEAD nullfs. > Retest the HEAD then. Can't reproduce it with HEAD (FreeBSD freebsd-tower.goebo.site 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r241218: Fri Oct 5 08:26:17 CEST 2012 l...@freebsd-tower.go

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Konstantin Belousov
On Thu, Oct 04, 2012 at 03:29:31PM +0200, Norbert Aschendorff wrote: > Nop, the patch doesn't seem to work - the machine crashes again. :| > This is the whole difference between stable and HEAD nullfs. Retest the HEAD then. pgpCMOX0jlgk4.pgp Description: PGP signature

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
Nop, the patch doesn't seem to work - the machine crashes again. :| Norbert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
On 10/04/2012 01:53 PM, Rick Macklem wrote: > Looks like you missed the change to fs/nfs/nfs_var.h, which changes > the prototypes for nfsv4_strtouid() and nfsv4_strtogid(). I see the problem, but I don't really understand why it failed. I applied the whole patch... However, 9.1-PRERELEASE is com

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Rick Macklem
Norbert Aschendorff wrote: > Does not compile: http://nopaste.info/2bc2c189eb.html (I also > #define-d > a constant, but that works) > Looks like you missed the change to fs/nfs/nfs_var.h, which changes the prototypes for nfsv4_strtouid() and nfsv4_strtogid(). Btw, the numeric uid/gid patch is no

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
On 10/04/2012 12:45 PM, Konstantin Belousov wrote: > But the errors has nothing to do with my nullfs backport. You're right; they stem from Rick's patch (from line 207 in numeric-uidgid.patch on): -nd->nd_repstat = nfsv4_strtogid(cp,j,&gid,p); +nd->nd_repstat = nfsv4_strtogid(nd, cp, j, &gid, +

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Konstantin Belousov
On Thu, Oct 04, 2012 at 12:29:51PM +0200, Norbert Aschendorff wrote: > Does not compile: http://nopaste.info/2bc2c189eb.html (I also #define-d > a constant, but that works) > You completely strip off the quotes and attributions, as well as your To: address is bogus, so I do not know whom did you a

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Konstantin Belousov
On Thu, Oct 04, 2012 at 09:08:08AM +0200, Norbert Aschendorff wrote: > On 10/04/2012 08:41 AM, Norbert Aschendorff wrote: > > I just applied the numeric-uidgid patch to CURRENT (worked so far) and > > compile the kernel with the patch and try it another time, just to > > eliminate the possibility o

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
Does not compile: http://nopaste.info/2bc2c189eb.html (I also #define-d a constant, but that works) --Norbert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-s

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
Hehe, sure, if you assist me :) I'm not very experienced with SVN, I'm actually a git user and I think it's also better if I do /not/ express my opinion on SVN here ;) The only actions I'm currently able to do in SVN are checkout, update, commit and view log and status -- so any help is appreciated

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Konstantin Belousov
On Thu, Oct 04, 2012 at 10:22:37AM +0200, Norbert Aschendorff wrote: > Hehe, sure, if you assist me :) > I'm not very experienced with SVN, I'm actually a git user and I think > it's also better if I do /not/ express my opinion on SVN here ;) > The only actions I'm currently able to do in SVN are c

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-04 Thread Norbert Aschendorff
On 10/04/2012 08:41 AM, Norbert Aschendorff wrote: > I just applied the numeric-uidgid patch to CURRENT (worked so far) and > compile the kernel with the patch and try it another time, just to > eliminate the possibility of a bug in this patch (the machine never > crashed before using this patch, b

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
I exported the NFSv4 shares via nullfs, booted the 10.0-CURRENT kernel and the machine does not crash. Running 9.1-PRERELEASE, it still crashes (as it should ;). I just applied the numeric-uidgid patch to CURRENT (worked so far) and compile the kernel with the patch and try it another time, just t

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
On 10/03/2012 07:39 PM, Konstantin Belousov wrote: > Can you try HEAD kernel ? Theoretically, yes. But it's a network machine, so... if something goes wrong, it'd be rather bad :| And I'm afraid of HEAD ;) I'll try it nevertheless... Fortunately, I even have Screen&Keyboard at the machine (if som

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Rick Macklem
Konstantin Belousov wrote: > On Wed, Oct 03, 2012 at 07:26:47PM +0200, Norbert Aschendorff wrote: > > On 10/03/2012 05:54 PM, Konstantin Belousov wrote: > > > So do you use nullfs exported mounts ? And stable ? > > > Can you try to remove nullfs from the set up ? > > > > Yes, I am using nullfs for

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Konstantin Belousov
On Wed, Oct 03, 2012 at 07:26:47PM +0200, Norbert Aschendorff wrote: > On 10/03/2012 05:54 PM, Konstantin Belousov wrote: > > So do you use nullfs exported mounts ? And stable ? > > Can you try to remove nullfs from the set up ? > > Yes, I am using nullfs for the exports (mounting the exported > d

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
On 10/03/2012 05:54 PM, Konstantin Belousov wrote: > So do you use nullfs exported mounts ? And stable ? > Can you try to remove nullfs from the set up ? Yes, I am using nullfs for the exports (mounting the exported directories to subdirectories of /srv). In the FreeBSD man pages and the documenta

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Konstantin Belousov
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 :) > > > > Please note: The /var/crash files stem from another crash than the big > > syslog does! > > > > The syslog file inside the tarball is about

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Rick Macklem
Norbert Aschendorff wrote: > 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

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
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

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
On 10/03/2012 09:21 AM, Norbert Aschendorff wrote: > So I just have to compile a kernel including "option WITNESS_WARN" and Well, obviously doesn't work, so only WITNESS_SKIPSPIN... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mai

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-03 Thread Norbert Aschendorff
On 10/02/2012 11:15 PM, John Baldwin wrote: > You could try adding a different WITNESS check (using WITNESS_WARN) to see > which NFS proc returns with a lock held so you can catch this when it first > occurs rather than much later after the fact. Do you have the start of the > log messages? Yep

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-02 Thread Rick Macklem
John Baldwin wrote: > On Tuesday, October 02, 2012 2:19:35 pm Norbert Aschendorff wrote: > > Well... > > > > Here the results for a kernel without WITNESS_SKIPSPIN (I'll compile > > one > > including that tomorrow, but until then...) > > > > Good news is: The kernel crashed with activated WITNESS.

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-02 Thread John Baldwin
On Tuesday, October 02, 2012 2:19:35 pm Norbert Aschendorff wrote: > Well... > > Here the results for a kernel without WITNESS_SKIPSPIN (I'll compile one > including that tomorrow, but until then...) > > Good news is: The kernel crashed with activated WITNESS. > Bad news is: I have to turn power

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-02 Thread Norbert Aschendorff
Well... Here the results for a kernel without WITNESS_SKIPSPIN (I'll compile one including that tomorrow, but until then...) Good news is: The kernel crashed with activated WITNESS. Bad news is: I have to turn power off after the crash with WITNESS. The crash dump is _not_ written to disk :( Goo

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-02 Thread John Baldwin
On Tuesday, October 02, 2012 11:21:06 am Norbert Aschendorff wrote: > I'll compile a kernel with > > options WITNESS > options WITNESS_KDB > > ok? Or should I include WITNESS_SKIPSPIN too? Yes, you should include WITNESS_SKIPSPIN. We should probably make that the default. -- John Baldwin ___

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-02 Thread Norbert Aschendorff
I'll compile a kernel with options WITNESS options WITNESS_KDB ok? Or should I include WITNESS_SKIPSPIN too? Regards, Norbert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Rick Macklem
John Baldwin wrote: > On Monday, October 01, 2012 8:07:44 am Rick Macklem wrote: > > Norbert Aschendorff wrote: > > > Hi, > > > > > > my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site > > > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 > > > 12:52:01 > > > CEST 2012 > >

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Norbert Aschendorff
On 10/01/2012 02:07 PM, Rick Macklem wrote: > Is the NFS client using Kerberos or AUTH_SYS for the mount? (And if you > are using Kerberos, have you tried the rsync with an AUTH_SYS mount?) No, it's not using Kerberos. Only network-based access control or however it's called (restricted via client

Re: panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread John Baldwin
On Monday, October 01, 2012 8:07:44 am Rick Macklem wrote: > Norbert Aschendorff wrote: > > Hi, > > > > my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site > > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 > > CEST 2012 l...@freebsd-tower.goebo.site:/usr/obj/usr/

panic "Sleeping thread owns a non-sleepable lock" via cv_timedwait_signal, was "rsync over NFS"

2012-10-01 Thread Rick Macklem
Norbert Aschendorff wrote: > Hi, > > my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 > CEST 2012 l...@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC > i386) crashes reproducibly when rsync-ing files to an