[Bug 210641] panic: witness warn during sys/kqueue/kqueue_test:main

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jun 27 20:54:28 UTC 2016


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

            Bug ID: 210641
           Summary: panic: witness warn during sys/kqueue/kqueue_test:main
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: i386
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: asomers at FreeBSD.org
                CC: freebsd-i386 at FreeBSD.org
                CC: freebsd-i386 at FreeBSD.org

Created attachment 171885
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=171885&action=edit
Textdump

Running sys/kqueue/kqueue_test:main on i386 with FreeBSD 11.0-ALPHA5 r302180M
resulted in the following panic:

userret: returning with the following locks held:
exclusive sleep mutex process lock (process lock) r = 0 (0xc827aab0) locked @
/usr/home/alans/freebsd/head/sys/kern/kern_event.c:2125
panic: witness_warn
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper(c15b2c1c,c1840520,0,c15850b4,f1174af8,...) at
db_trace_self_wrapper+0x2a/frame 0xf1174ac8
kdb_backtrace(c17a4cd1,1,c12208af,f1174b94,1,...) at kdb_backtrace+0x2d/frame
0xf1174b30
vpanic(c12208af,f1174b94,c12208af,f1174b94,f1174b94,...) at vpanic+0x115/frame
0xf1174b64
kassert_panic(c12208af,c15b7038,c827aab0,c15a4df0,84d,...) at
kassert_panic+0xd9/frame 0xf1174b88
witness_warn(2,0,c15b570f,f1174ca8,c0bfef10,...) at witness_warn+0x32a/frame
0xf1174bdc
userret(c8abd340,f1174ce8,c15a543f,4,0,...) at userret+0x92/frame 0xf1174c20
syscall(f1174ce8) at syscall+0x50b/frame 0xf1174cdc
Xint0x80_syscall() at Xint0x80_syscall+0x2f/frame 0xf1174cdc
--- syscall (1, FreeBSD ELF32, sys_sys_exit), eip = 0x281a044b, esp =
0xbfbfe8c8, ebp = 0xbfbfe8f0 ---
KDB: enter: panic

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


More information about the freebsd-bugs mailing list