Date: Thu, 02 Jul 2026 08:29:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 296441] linuxolator: opencode deadlocks at startup (lost FUTEX_WAKE? all threads stuck in umtxq_sleep) Message-ID: <bug-296441-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296441 Bug ID: 296441 Summary: linuxolator: opencode deadlocks at startup (lost FUTEX_WAKE? all threads stuck in umtxq_sleep) Product: Base System Version: 15.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: ale@FreeBSD.org Starting the current linux version of opencode (1.17.13) under linuxulator immediately deadlocks (blank UI, kill -9 is the only solution). The only way to reliably start it seems to set BUN_JSC_useJIT=0 Running procstat on the hung process shows that every thread (main "opencode", HeapHelper, JITWorker, Bun Pool workers, timer helper, Worker) has the IDENTICAL kernel stack: mi_switch+0xbc sleepq_catch_signals+0x27d sleepq_wait_sig+0x9 _sleep+0x197 umtxq_sleep+0x2cd linux_sys_futex+0x282 amd64_syscall+0x126 fast_syscall_common+0xf8 i.e. all threads are blocked in linux_sys_futex -> umtxq_sleep, none runnable, so no thread is left to issue the FUTEX_WAKE the others are waiting on. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-296441-227>