Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Nov 2019 07:13:00 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 242184] r354398 causes panic in nfs_unmount during shutdown
Message-ID:  <bug-242184-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242184

            Bug ID: 242184
           Summary: r354398 causes panic in nfs_unmount during shutdown
           Product: Base System
           Version: 12.0-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: rk@ronald.org

Created attachment 209375
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D209375&action=
=3Dedit
core.txt.3

Recent 12.1-STABLE kernels panic on every reboot/shutdown in nfs_unmount (w=
hen
NFS file systems are mounted). I tracked it down to the change in r354398:

  MFC r353891:
  Fix interface between nfsclient and vnode pager.=20

Starting with r354398 the system panics on every reboot/shutdown while
mounted NFS file systems are present:

Fatal trap 12: page fault while in kernel mode
cpuid =3D 0; apic id =3D 10
fault virtual address   =3D 0x18
fault code              =3D supervisor write data, page not present
instruction pointer     =3D 0x20:0xffffffff80acc688
stack pointer           =3D 0x28:0xfffffe0075d55350
frame pointer           =3D 0x28:0xfffffe0075d553a0
code segment            =3D base 0x0, limit 0xfffff, type 0x1b
                        =3D DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        =3D interrupt enabled, resume, IOPL =3D 0
current process         =3D 1 (init)
trap number             =3D 12
panic: page fault
cpuid =3D 0
time =3D 1574577411
KDB: stack backtrace:
#0 0xffffffff80c1d917 at kdb_backtrace+0x67
#1 0xffffffff80bd0dad at vpanic+0x19d
#2 0xffffffff80bd0c03 at panic+0x43
#3 0xffffffff810aa82c at trap_fatal+0x39c
#4 0xffffffff810aa87f at trap_pfault+0x4f
#5 0xffffffff810a9eb1 at trap+0x2a1
#6 0xffffffff8108364c at calltrap+0x8
#7 0xffffffff8122ea0c at VOP_LOCK1_APV+0x7c
#8 0xffffffff80cb26f4 at _vn_lock+0x44
#9 0xffffffff80ca1a88 at vputx+0x138
#10 0xffffffff80ba903d at lf_free_lock+0x25d
#11 0xffffffff80ba940f at lf_purgelocks+0x2df
#12 0xffffffff80c8ffa4 at vop_stdadvlockpurge+0x14
#13 0xffffffff8122f4bc at VOP_ADVLOCKPURGE_APV+0x7c
#14 0xffffffff80ca2a38 at vgonel+0x248
#15 0xffffffff80ca2112 at vflush+0x312
#16 0xffffffff80ad3865 at nfs_unmount+0xd5
#17 0xffffffff80c99e09 at dounmount+0x579

Revision r354394 is stable.
Core information core.txt.3 is attached. I can make vmcore available when
needed.

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



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