Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Sep 1999 11:20:30 -0700 (PDT)
From:      John Polstra <jdp@polstra.com>
To:        marcel@scc.nl
Cc:        current@freebsd.org
Subject:   Re: HEADS UP: sigset_t changes committed
Message-ID:  <199909291820.LAA22884@vashon.polstra.com>
In-Reply-To: <37F23064.98EEBC67@scc.nl>
References:  <37F23064.98EEBC67@scc.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <37F23064.98EEBC67@scc.nl>, Marcel Moolenaar  <marcel@scc.nl> wrote:
> 
> Alpha users are invited to test the changes since I've not been able to
> do that myself. I've done all I possibly could do to make this a
> success.

It looks like real bad news for the Alpha. :-(  I built and
installed the kernel as instructed, and then started a make
buildworld.  That died soon with this:

    ===> usr.bin
    "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
    "/a/src/usr.bin/Makefile", line 223: Unclosed conditional/for loop
    "/a/src/usr.bin/Makefile", line 223: 1 open conditional
    "/a/src/usr.bin/Makefile", line 223: 1 open conditional
    make: fatal errors encountered -- cannot continue
    make: fatal errors encountered -- cannot continue
    *** Error code 1
    *** Error code 1

I suspect it's caused by the trailing backslash in the "doscmd" line
near the end:

    .if ${MACHINE_ARCH} == "i386"
    # Things that don't compile on alpha or are aout specific:
    SUBDIR+=ar \ 
	    brandelf \
	    gcore \ 
	    gprof4 \
	    nm \ 
	    ranlib \
	    sasc \
	    size \  
	    strings \
	    strip  
    #       doscmd \
    .endif  

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.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "No matter how cynical I get, I just can't keep up."        -- Nora Ephron


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909291820.LAA22884>