Date: Sat, 20 Jun 2009 17:50:55 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Bruce Evans <brde@optusnet.com.au> Cc: Kostik Belousov <kostikbel@gmail.com>, Jilles Tjoelker <jilles@stack.nl>, freebsd-arch@FreeBSD.org Subject: Re: deadlocks with intr NFS mounts and ^Z (or: PCATCH and sleepable locks) Message-ID: <4A3D136F.1090106@FreeBSD.org> In-Reply-To: <20090620121543.F29239@delplex.bde.org> References: <20090619162328.GA79975@stack.nl> <20090619194654.GC2884@deviant.kiev.zoral.com.ua> <20090620121543.F29239@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > These problems seemed to go away, but right now the following problem > like the second set above occurs consistently (I first noticed this > last week): > > Script started on Sat Jun 20 02:32:51 2009 > pts/0:bde@ref8-i386:~/sys7/i386/compile> sh zm > ^Z > [1]+ Stopped sh zm > pts/0:bde@ref8-i386:~/sys7/i386/compile> % > sh zm > *** Stopped -- signal 18 > *** Stopped -- signal 18 > *** Stopped -- signal 18 > *** Signal 1 > *** Signal 1 > *** Signal 1 > `all' not remade because of errors. > linking kernel > ^C > pts/0:bde@ref8-i386:~/sys7/i386/compile> exit > > Script done on Sat Jun 20 02:34:41 2009 > > The shell script zm builds 6 kernels in parallel using make -k -j8 for > each. Signal 18 is SIGTSTP. Receiving this is normal, but the shell > shouldn't print any meesages about it. Signal 1 is SIGHUP. This > shouldn't occur. On another run, ISTR getting messages about i/o > errors or unrestartable processes. Anyway, the messages about signals > are associated with failing jobs in the build. That's a long standing bug that I don't think is limited to NFS. I first started seeing it several years ago after some changes to make(1), but I don't recall if phk disputed that they were to blame. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A3D136F.1090106>