[Bug 206634] "panic: ncllock1" from FreeBSD client after NFSv4 server was taken offline and brought back to life; lots of spam about "protocol prob err=10006"

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206634

Lev A. Serebryakov <lev at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lev at FreeBSD.org

--- Comment #3 from Lev A. Serebryakov <lev at FreeBSD.org> ---
I've got same panic on FreeBSD build from r295696, in VirtualBox. My NFS server
was on-line, and panic occured when sources were updated from my local SVN
mirror via NFS (file:// protocol).

I have core. bt is:

#0  doadump (textdump=0) at pcpu.h:221
#1  0xffffffff802f230b in db_dump (dummy=<value optimized out>, dummy2=false,
dummy3=0, dummy4=0x0) at /data/src/sys/ddb/db_command.c:533
#2  0xffffffff802f20fe in db_command (cmd_table=0x0) at
/data/src/sys/ddb/db_command.c:440
#3  0xffffffff802f1e94 in db_command_loop () at
/data/src/sys/ddb/db_command.c:493
#4  0xffffffff802f492b in db_trap (type=<value optimized out>, code=0) at
/data/src/sys/ddb/db_main.c:251
#5  0xffffffff804a7c43 in kdb_trap (type=3, code=0, tf=<value optimized out>)
at /data/src/sys/kern/subr_kdb.c:654
#6  0xffffffff806e0510 in trap (frame=0xfffffe023b618210) at
/data/src/sys/amd64/amd64/trap.c:556
#7  0xffffffff806c21a7 in calltrap () at
/data/src/sys/amd64/amd64/exception.S:234
#8  0xffffffff804a732b in kdb_enter (why=0xffffffff80795899 "panic", msg=0x400
<Address 0x400 out of bounds>) at cpufunc.h:63
#9  0xffffffff8046c06f in vpanic (fmt=<value optimized out>, ap=<value
optimized out>) at /data/src/sys/kern/kern_shutdown.c:750
#10 0xffffffff8046c0d3 in panic (fmt=0xffffffff80b29c40 "\004") at
/data/src/sys/kern/kern_shutdown.c:688
#11 0xffffffff803aeb37 in nfs_lock1 (ap=<value optimized out>) at
/data/src/sys/fs/nfsclient/nfs_clvnops.c:3372
#12 0xffffffff8073e020 in VOP_LOCK1_APV (vop=<value optimized out>, a=<value
optimized out>) at vnode_if.c:2083
#13 0xffffffff8052887a in _vn_lock (vp=0xfffff800ba28bb10, flags=<value
optimized out>, file=0xffffffff807a7901 "/data/src/sys/kern/vfs_subr.c",
line=2476)
    at vnode_if.h:859
#14 0xffffffff80519953 in vget (vp=0xfffff800ba28bb10, flags=279040, td=0x0) at
/data/src/sys/kern/vfs_subr.c:2476
#15 0xffffffff8050c51c in vfs_hash_get (mp=0xfffff800077e6990, hash=790540428,
flags=<value optimized out>, td=0x0, vpp=0xfffffe023b618568,
    fn=0xffffffff803b66e0 <newnfs_vncmpf>) at /data/src/sys/kern/vfs_hash.c:89
#16 0xffffffff803b6f81 in nfscl_ngetreopen (mntp=0xfffff800077e6990, fhp=<value
optimized out>, fhsize=<value optimized out>, td=0x0, npp=0xfffffe023b618670)
    at /data/src/sys/fs/nfsclient/nfs_clport.c:347
#17 0xffffffff80392bcd in nfscl_hasexpired (clp=0xfffffe00039d2000,
clidrev=<value optimized out>, p=0x0) at
/data/src/sys/fs/nfsclient/nfs_clstate.c:4052
#18 0xffffffff803a0d0a in nfsrpc_read (vp=0xfffff800937fd760,
uiop=0xfffffe023b6189d0, cred=0xfffff800b3286600, p=0x0,
nap=0xfffffe023b618890,
    attrflagp=0xfffffe023b61895c) at
/data/src/sys/fs/nfsclient/nfs_clrpcops.c:1381
#19 0xffffffff803af9fa in ncl_readrpc (vp=0xfffff800937fd760,
uiop=0xfffffe023b6189d0, cred=0xfffff800b3195d00)
    at /data/src/sys/fs/nfsclient/nfs_clvnops.c:1381
#20 0xffffffff803ba638 in ncl_doio (vp=0xfffff800937fd760,
bp=0xfffffe01f168aeb0, cr=0xfffffe023b617e40, td=<value optimized out>,
called_from_strategy=-510)
    at /data/src/sys/fs/nfsclient/nfs_clbio.c:1610
#21 0xffffffff803bc694 in nfssvc_iod (instance=<value optimized out>) at
/data/src/sys/fs/nfsclient/nfs_clnfsiod.c:302
#22 0xffffffff80436544 in fork_exit (callout=0xffffffff803bc420 <nfssvc_iod>,
arg=0xffffffff80b28ec0, frame=0xfffffe023b618ac0)
    at /data/src/sys/kern/kern_fork.c:1034
#23 0xffffffff806c266e in fork_trampoline () at
/data/src/sys/amd64/amd64/exception.S:609

-- 
You are receiving this mail because:
You are the assignee for the bug.