[Bug 214923] kqueue hangs with busy loop

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Dec 17 02:32:59 UTC 2016


--- Comment #14 from yjh0502 at gmail.com ---
(In reply to Konstantin Belousov from comment #13)

Sorry for the confusion. Here's stacks for two problematic threads.

Tracing pid 764 tid 100622 td 0xfffff80007ccda00
kdb_enter() at kdb_enter+0x3b/frame 0xfffffe004f1757e0
vpanic() at vpanic+0x19f/frame 0xfffffe004f175860
panic() at panic+0x43/frame 0xfffffe004f1758c0
knote_drop() at knote_drop+0x28a/frame 0xfffffe004f175900
knote_fdclose() at knote_fdclose+0xd3/frame 0xfffffe004f175950
closefp() at closefp+0x65/frame 0xfffffe004f1759a0
amd64_syscall() at amd64_syscall+0x2f6/frame 0xfffffe004f175ab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe004f175ab0
--- syscall (6, FreeBSD ELF64, sys_close), rip = 0x80104a7ca, rsp =
0x7fffdf9f9b58, rbp = 0x7fffdf9f9b70 ---

db> trace 1118
Tracing pid 1118 tid 100634 td 0xfffff8000c23b500
cpustop_handler() at cpustop_handler+0x28/frame 0xffffffff81d78d30
ipi_nmi_handler() at ipi_nmi_handler+0x4a/frame 0xffffffff81d78d50
trap() at trap+0x3a/frame 0xffffffff81d78f60
nmi_calltrap() at nmi_calltrap+0x8/frame 0xffffffff81d78f60
--- trap 0x13, rip = 0xffffffff80a90104, rsp = 0xfffffe004f1ac6f0, rbp =
0xfffffe004f1ac710 ---
lock_delay() at lock_delay+0x54/frame 0xfffffe004f1ac710
__mtx_lock_sleep() at __mtx_lock_sleep+0x1b8/frame 0xfffffe004f1ac790
__mtx_lock_flags() at __mtx_lock_flags+0x10d/frame 0xfffffe004f1ac7e0
knote() at knote+0x85/frame 0xfffffe004f1ac840
VOP_READDIR_APV() at VOP_READDIR_APV+0x150/frame 0xfffffe004f1ac870
kern_getdirentries() at kern_getdirentries+0x224/frame 0xfffffe004f1ac970
sys_getdirentries() at sys_getdirentries+0x28/frame 0xfffffe004f1ac9a0
amd64_syscall() at amd64_syscall+0x2f6/frame 0xfffffe004f1acab0
Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe004f1acab0
--- syscall (196, FreeBSD ELF64, sys_getdirentries), rip = 0x80096c69a, rsp =
0x7fffffffe778, rbp = 0x7fffffffe7b0 ---

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

More information about the freebsd-bugs mailing list