Hi, I get: ... #0 0xffffffff80224245 in cpu_reboot () #1 0xffffffff807b9723 in db_reboot_cmd () #2 0xffffffff807b9f3b in db_command () #3 0xffffffff807ba2a6 in db_command_loop () #4 0xffffffff807bdc2a in db_trap () #5 0xffffffff80220b15 in kdb_trap () #6 0xffffffff80225c86 in trap () #7 0xffffffff8021ed63 in alltraps () #8 0xffffffff8021f57d in breakpoint () #9 0xffffffff80a33270 in vpanic () #10 0xffffffff80e79e33 in kern_assert () #11 0xffffffff809ae062 in uvm_pageactivate () #12 0xffffffff809947a2 in amap_cow_now () #13 0xffffffff809a8d1e in uvmspace_fork () #14 0xffffffff8099eea9 in uvm_proc_fork () #15 0xffffffff809d9e8b in fork1 () #16 0xffffffff809daa12 in sys_fork () #17 0xffffffff80254d49 in syscall () #18 0xffffffff802096bd in handle_syscall () ....
on uname -a NetBSD marge.lorien.lan 9.99.32 NetBSD 9.99.32 (GENERIC) #13: Wed Jan 1 12:31:34 GMT 2020 sysbuild@ymir:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC amd64 when I try to startxfce4. Normal startx works, as well as xrandr to get me to the right resolution under VirtualBox (with client additions 6.1); gdm also starts OK and subsequently the mate session works. Chavdar -- ----
