Re: -current diskless panic on boot

From: Jeff Roberson <jroberson_at_chesapeake.net>
Date: Thu, 14 Apr 2005 02:46:48 -0400 (EDT)
Please try this:

Index: nfs_vnops.c
===================================================================
RCS file: /home/ncvs/src/sys/nfsclient/nfs_vnops.c,v
retrieving revision 1.257
diff -u -r1.257 nfs_vnops.c
--- nfs_vnops.c 13 Apr 2005 10:59:09 -0000      1.257
+++ nfs_vnops.c 14 Apr 2005 06:44:40 -0000
_at__at_ -809,8 +809,6 _at__at_
                        vput(newvp);
                else
                        vrele(newvp);
-               if (flags & ISDOTDOT)
-                       vn_lock(dvp, LK_EXCLUSIVE|LK_RETRY, td);
                *vpp = NULLVP;
        }
        error = 0;

On Thu, 14 Apr 2005, Poul-Henning Kamp wrote:

>
> Oops
>
> forgot the backtrace:
>
> db> trace
> Tracing pid 110 tid 100059 td 0xc1b5d7d0
> kdb_enter(c082857d) at 0xc063df0f = kdb_enter+0x2b
> panic(c082693a,c1b5d7d0,0,c08922e0,d997c9b0) at 0xc0626117 = panic+0x127
> lockmgr(c1e4e5bc,3002,c1e4e5e0,c1b5d7d0,d997c990) at 0xc061b782 = lockmgr+0x3d6
> vop_stdlock(d997c9b0,1002,c1e4e564,d997c9cc,c06840bd) at 0xc067171e = vop_stdlock+0x1e
> VOP_LOCK_APV(c0898780,d997c9b0) at 0xc07d1e17 = VOP_LOCK_APV+0x87
> vn_lock(c1e4e564,1002,c1b5d7d0) at 0xc06840bd = vn_lock+0x101
> nfs_lookup(d997cb14,c1e4e564,c1d58408,d997cb30,c0673452) at 0xc06daadb = nfs_lookup+0x1f7
> VOP_LOOKUP_APV(c0898780,d997cb14) at 0xc07d0027 = VOP_LOOKUP_APV+0x87
> lookup(d997cc00,0,1,c1b5d7d0,c0637228) at 0xc0673452 = lookup+0x3da
> namei(d997cc00,c093b0a4,d997cbc4,c064833a,c093b0a0) at 0xc0672dfa = namei+0x372
> kern_stat(c1b5d7d0,bfbfe8a0,0,d997cc74) at 0xc067ea45 = kern_stat+0x35
> stat(c1b5d7d0,d997cd04,2,4,206) at 0xc067e9f3 = stat+0x1b
> syscall(3b,3b,3b,0,bfbfe6c0) at 0xc07bd077 = syscall+0x243
> Xint0x80_syscall() at 0xc07aa59f = Xint0x80_syscall+0x1f
> --- syscall (188, FreeBSD ELF32, stat), eip = 0x280b73bb, esp = 0xbfbfe63c, ebp = 0xbfbfecb8 ---
> db>
>
> In message <25700.1113460936_at_critter.freebsd.dk>, Poul-Henning Kamp writes:
> >
> >sis3: link state changed to UP
> >sysctl: unknown oid 'kern.bootp_cookie'
> >Interface fxp0 IP-Address 192.168.68.29 Broadcast 192.168.68.255
> >Loading configuration files.
> >Entropy harvesting: interrupts ethernet point_to_point kickstart.
> >Starting file system checks:
> >lock order reversal
> > 1st 0xc0944ac0 vm page queue mutex (vm page queue mutex) _at_ kern/vfs_bio.c:1485
> > 2nd 0xc1e4e808 vnode interlock (vnode interlock) _at_ kern/vfs_subr.c:1993
> >KDB: stack backtrace:
> >kdb_backtrace(0,ffffffff,c08fe468,c08fce10,c088a5a8) at 0xc063de8d = kdb_backtrace+0x29
> >witness_checkorder(c1e4e808,9,c08314aa,7c9) at 0xc0647e48 = witness_checkorder+0x550
> >_mtx_lock_flags(c1e4e808,0,c08314a1,7c9,c1d9cdec) at 0xc061e363 = _mtx_lock_flags+0x5b
> >vdrop(c1e4e78c) at 0xc06794f1 = vdrop+0x1d
> >vm_page_remove(c1756f90,c1756f90) at 0xc07624e0 = vm_page_remove+0xd4
> >vm_page_free_toq(c1756f90,c1756f90,40,c1756f90,d9982a30) at 0xc0762b7c = vm_page_free_toq+0x90
> >vm_page_free(c1756f90,c1756f90) at 0xc07620ed = vm_page_free+0x15
> >vfs_vmio_release(cbf0b080) at 0xc066b113 = vfs_vmio_release+0x9b
> >brelse(cbf0b080,cbf0b080) at 0xc066a9a9 = brelse+0x485
> >flushbuflist(c1e4e854,1,c1e4e850,0,0) at 0xc0677ca2 = flushbuflist+0x1c6
> >bufobj_invalbuf(c1e4e850,1,c1b5daf0,0,0) at 0xc06778cd = bufobj_invalbuf+0x10d
> >vinvalbuf(c1e4e78c,1,c1b5daf0,0,0) at 0xc0677ad6 = vinvalbuf+0x2a
> >nfs_vinvalbuf(c1e4e78c,1,c1b5daf0,1,a) at 0xc06d33a0 = nfs_vinvalbuf+0xd0
> >nfs_close(d9982b74,a,c1e4e78c,d9982ba0,c0683413) at 0xc06da24a = nfs_close+0xca
> >VOP_CLOSE_APV(c0898780,d9982b74) at 0xc07d067f = VOP_CLOSE_APV+0x9b
> >vn_close(c1e4e78c,a,c1984d80,c1b5daf0,d9982bd8) at 0xc0683413 = vn_close+0x8b
> >vn_closefile(c1d670d8,c1b5daf0) at 0xc06841c6 = vn_closefile+0xca
> >fdrop_locked(c1d670d8,c1b5daf0,c196ba54,0,c0825433) at 0xc060b620 = fdrop_locked+0x88
> >fdrop(c1d670d8,c1b5daf0,6ab,c08f4a40,0) at 0xc060b590 = fdrop+0x24
> >closef(c1d670d8,c1b5daf0,0,0,4) at 0xc060a0d3 = closef+0x35f
> >close(c1b5daf0,d9982d04,1,7,216) at 0xc0607b5b = close+0x1a3
> >syscall(3b,3b,3b,0,2814c060) at 0xc07bd077 = syscall+0x243
> >Xint0x80_syscall() at 0xc07aa59f = Xint0x80_syscall+0x1f
> >--- syscall (6, FreeBSD ELF32, close), eip = 0x280b903b, esp = 0xbfbfe8cc, ebp = 0xbfbfe8e8 ---
> >Expensive timeout(9) function: 0xc078dafc(0xc094f7e0) 2.508722197 s
> >panic: lockmgr: locking against myself
> >cpuid = 0
> >KDB: enter: panic
> >[thread pid 110 tid 100059 ]
> >Stopped at      0xc063df0f = kdb_enter+0x2b:    nop
> >db>
> >--
> >Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> >phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
> >FreeBSD committer       | BSD since 4.3-tahoe
> >Never attribute to malice what can adequately be explained by incompetence.
> >_______________________________________________
> >freebsd-current_at_freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> >
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
Received on Thu Apr 14 2005 - 04:46:51 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:32 UTC