From owner-freebsd-stable@FreeBSD.ORG Wed Apr 22 06:51:09 2009 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B4001065673 for ; Wed, 22 Apr 2009 06:51:09 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 376F68FC0C for ; Wed, 22 Apr 2009 06:51:07 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA04404 for ; Wed, 22 Apr 2009 09:51:06 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1] helo=edge.pp.kiev.ua) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1LwWIU-000EnJ-1w for freebsd-stable@FreeBSD.org; Wed, 22 Apr 2009 09:51:06 +0300 Message-ID: <49EEBE58.2090809@icyb.net.ua> Date: Wed, 22 Apr 2009 09:51:04 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: <49EC48C2.20402@icyb.net.ua> In-Reply-To: <49EC48C2.20402@icyb.net.ua> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: panic: nfs sndunlock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2009 06:51:09 -0000 Any ideas, interest? I still have the core file. on 20/04/2009 13:04 Andriy Gapon said the following: > System is stable/7: 7.2-PRERELEASE r191214 i386 uni-processor. > > NFS mount options: ro,noauto,nfsv3,tcp,intr,rdirplus,-r=32768,-w=32768 > > The panic occurred on client after losing and then restoring > connectivity with NFS server. There may have been parallel access to > NFS-mounted tree at the time of the accident. > > Kernel messages just before the panic: > kernel: nfs server odyssey:/usr/ports: not responding > kernel: nfs send error 57 for server odyssey:/usr/ports > > kgdb information: > #0 doadump () at pcpu.h:196 > #1 0xc0555a33 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 > #2 0xc0555c7f in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:574 > #3 0xc064be63 in nfs_connect_unlock (rep=0x0) at > /usr/src/sys/nfsclient/nfs_socket.c:1819 > #4 0xc064da24 in nfs_reconnect (rep=0xc40a0c80) at > /usr/src/sys/nfsclient/nfs_socket.c:581 > #5 0xc064ff50 in nfs_request (vp=0xc4464450, mrest=0xc435a000, > procnum=3, td=0xc398cd20, cred=0xc420b800, mrp=0xdac06a04, > mdp=0xdac06a00, dposp=0xdac06a08) > at /usr/src/sys/nfsclient/nfs_socket.c:737 > #6 0xc065d3f2 in nfs_lookup (ap=0xdac06a84) at > /usr/src/sys/nfsclient/nfs_vnops.c:922 > #7 0xc0729cd6 in VOP_LOOKUP_APV (vop=0xc07a0fe0, a=0xdac06a84) at > vnode_if.c:99 > #8 0xc05cad71 in lookup (ndp=0xdac06ba8) at vnode_if.h:57 > #9 0xc05cbab8 in namei (ndp=0xdac06ba8) at > /usr/src/sys/kern/vfs_lookup.c:220 > #10 0xc05db02d in kern_stat (td=0xc398cd20, path=0x2814d040
0x2814d040 out of bounds>, pathseg=UIO_USERSPACE, sbp=0xdac06c18) > at /usr/src/sys/kern/vfs_syscalls.c:2123 > #11 0xc05db21f in stat (td=0xc398cd20, uap=0xdac06cfc) at > /usr/src/sys/kern/vfs_syscalls.c:2107 > #12 0xc0712055 in syscall (frame=0xdac06d38) at > /usr/src/sys/i386/i386/trap.c:1090 > #13 0xc06ff290 in Xint0x80_syscall () at > /usr/src/sys/i386/i386/exception.s:255 > > I am not sure why rep parameter shows up as NULL in nfs_connect_unlock > call. In frame 4: > (kgdb) p/x rep->r_nmp->nm_state > $2 = 0x10100000 > > I am keeping the core file. > -- Andriy Gapon