Bug 296441 - linuxolator: opencode deadlocks at startup (lost FUTEX_WAKE? all threads stuck in umtxq_sleep)
Summary: linuxolator: opencode deadlocks at startup (lost FUTEX_WAKE? all threads stuc...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 15.1-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-emulation (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-02 08:29 UTC by Alex Dupre
Modified: 2026-07-02 10:02 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Dupre freebsd_committer freebsd_triage 2026-07-02 08:29:55 UTC 
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.