===== DF-2212 FIXED run Tue Oct 20 22:12:05 UTC 2026 =====
DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #2: Tue Oct 20 22:05:26 UTC 2026     root@dfbsd:/usr/obj/usr/src/sys/DFV2212  x86_64
4faabe2f6a7f28231bcee79db239110a4b909985a67a4f12d93ab62f715187b9
--- control: boot check ---
df_ttm2212: BOOT CHECK: verbatim ttm_init() ran via SYSINIT (module.h:58-59): register_calls=1 device_released=0 (register>0 + value 0 => SUCCESS path => a later ttm_exit() can never pass its wait)
hw.df_ttm2212.status: register_calls=1 unregister_calls=0 device_released=0 exit_done=1 exit_ms=-1 wdog_samples=0 exit_thread=0 tsleepq=0 wmesg=- wchan=0 kill9_mark=0

--- trigger: the sysctl command itself must COMPLETE now ---
hw.df_ttm2212.trigger: 0 -> 0
        0.07 real         0.00 user         0.07 sys
trigger rc=0
hw.df_ttm2212.status: register_calls=1 unregister_calls=1 device_released=0 exit_done=1 exit_ms=0 wdog_samples=0 exit_thread=0 tsleepq=0 wmesg=- wchan=0 kill9_mark=0

--- cycle test: 500 x (ttm_init;ttm_exit) ---
hw.df_ttm2212.cycle: 0 -> 0
--- second trigger ---
hw.df_ttm2212.trigger: 0 -> 0
rc=0
--- stuck sysctl procs: ---
(none)
--- kernel log ---
df_ttm2212: stack snapshot at entry to the wait path:
df_ttm2212: ttm_exit() RETURNED after 0 ms (device_released=0) - fixed kernel behaviour
df_ttm2212: CYCLE: 500 x (ttm_init(); ttm_exit()) completed, every call returned
df_ttm2212: TRIGGER pid=880 (sysctl): calling the REAL ttm_exit() (verbatim ttm_module.c:89-99) in THIS thread - exactly what linker_file_sysuninit() (kern_linker.c:535) does to the kldunload(2) thread of drm.ko
df_ttm2212: stack snapshot at entry to the wait path:
df_ttm2212: ttm_exit() RETURNED after 0 ms (device_released=0) - fixed kernel behaviour