Dear reader, I will try to run more up to date, but sometimes it takes time to get those kinds of bugs, so following current is not really an option .
I do not know if something can be done with that since i do not have the core file fatal protection fault in supervisor mode trap type 4 code 0 rip ffffffff81a9f346 cs 8 rflags 10246 cr2 ffff80003340c830 cpl 0 rsp ffff80003358a510 gsbase 0xffff800022410ff0 kgsbase 0x0 panic: trap type 4, code=0, pc=ffffffff81a9f346 Starting stack trace... panic(ffffffff81de3229) at panic+0x11d kerntrap(ffff80003358a460) at kerntrap+0x114 alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b fill_file(ffff800000173800,fffffd813bdfd1f8,fffffd800bef31b8,4,0,ffff800033665648) at fill_file+0x756 sysctl_file(ffff80003358aa88,4,4ff3ab05c00,ffff80003358aab8,ffff80003393a830) at sysctl_file+0x9b2 kern_sysctl(ffff80003358aa84,5,4ff3ab05c00,ffff80003358aab8,0,0) at kern_sysctl+0x1d1 sys_sysctl(ffff80003393a830,ffff80003358ab20,ffff80003358ab80) at sys_sysctl+0x184 syscall(ffff80003358abf0) at syscall+0x389 Xsyscall() at Xsyscall+0x128 end of kernel end trace frame: 0x7f7ffffe8560, count: 248 End of stack trace. syncing disks...panic: kernel diagnostic assertion "!_kernel_lock_held()" failed: file "/usr/src/sys/uvm/uvm_map.c", line 2709 Starting stack trace... panic(ffffffff81dee41d) at panic+0x11d __assert(ffffffff81e54e23,ffffffff81e69319,a95,ffffffff81e1902a) at __assert+0x2b uvm_map_teardown(fffffd8133b4e010) at uvm_map_teardown+0x23e uvmspace_free(fffffd8133b4e010) at uvmspace_free+0x5d uvm_exit(ffff800033665648) at uvm_exit+0x24 reaper(ffff800022965158) at reaper+0x14c end trace frame: 0x0, count: 251 End of stack trace. best. -- -- --------------------------------------------------------------------------------------------------------------------- Knowing is not enough; we must apply. Willing is not enough; we must do
