I can confirm. It appears to be the dispmsg_issue system call that spawns a thread in the kernel process, but a recent change (62bd9bf9014d770b90b6c887698624059960d9e9 Fix pid 1 deadlocking when exiting with children.) forbids that. However, that should be allowed for the kernel process.