Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
ghx-label-1
Description
I've seen this a few times now, the kernel_stack_watchdog is used in a few places in the KRPC code and it prints out the kernel + user stack whenever a thread is stuck in some method call for too long. The issue is that the user stack does not get printed:
W0908 17:15:00.365721 6605 kernel_stack_watchdog.cc:198] Thread 6612 stuck at outbound_call.cc:273 for 120ms: Kernel stack: [<ffffffff810f5126>] futex_wait_queue_me+0xc6/0x130 [<ffffffff810f5deb>] futex_wait+0x17b/0x280 [<ffffffff810f7b26>] do_futex+0x106/0x5a0 [<ffffffff810f8040>] SyS_futex+0x80/0x180 [<ffffffff816b4fc9>] system_call_fastpath+0x16/0x1b [<ffffffffffffffff>] 0xffffffffffffffff User stack: <Not implemented: unable to take thread stack: signal handler unavailable>
It says that the signal handler of taking the thread stack is unavailable.