dispmsg_issue(2) resolution change panics kernel
It was reported that changing the resolution with installer or with chvidemode panics the kernel.
Assertion failure: thread.cpp:135: Sortix::Thread::* Sortix::CreateKernelThread(Sortix::Process*, Sortix::thread_registers*): !process->firstthread || process == CurrentProcess()
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.