From owner-freebsd-current Wed Sep 29 11:51:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id BBE8C15145 for ; Wed, 29 Sep 1999 11:51:00 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11WOq3-000AUQ-00; Wed, 29 Sep 1999 18:52:27 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA17514; Wed, 29 Sep 1999 20:50:53 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37F25F8D.5687E677@scc.nl> Date: Wed, 29 Sep 1999 20:50:53 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: HEADS UP: sigset_t changes committed References: <37F23064.98EEBC67@scc.nl> <199909291820.LAA22884@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > I suspect it's caused by the trailing backslash in the "doscmd" line > near the end: > > strip > # doscmd \ > .endif It doesn't give me any problems... > Anyway, when the make buildworld failed, I tried to do a "cvs > status" or some such thing, which caused amd to attempt to mount the > repository from a different machine. Wham, instant panic, and it > trashed out one of my filesystems _thoroughly_ -- 1000 files and 10 > MB in lost+found. :-( > Once I got things patched up again with a little chewing gum, I was > able to get a core dump. It overflowed the kernel stack with > zillions of recursive calls to nfs_sigintr: > > #37 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #38 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #39 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #40 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #41 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #42 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #43 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > #44 0xfffffc0000409404 in nfs_sigintr (nmp=0x0, rep=0x0, p=0x0) > at ../../nfs/nfs_socket.c:1504 > > I haven't found the bottom of the stack yet (11000 frames and > counting ...). Let me know if you'd like some additional info. Yes please. Looking at the code, it seems to me that nmp shouldn't be 0. What I like to know is, if sendsig/sigreturn is somehow involved. A bad stack can do all sorts of nasty things. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message