https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255386
--- Comment #8 from Guido Falsi <madpi...@freebsd.org> --- To have the kernel save a core dump you need the machine (virtual or physical) to have more swap than ram and configure it to perform the dump with dumpdev="AUTO" in /etc/rc.conf. A machine without any swap (which is a relatively common setup for virtual machines) has no way to save a kernel core dump. But to get actually useful data you should be running a debugging kernel. I think, especially since we're talking about virtual machines, it would be easier for you to install a VM with a snapshot of 14-CURRENT, that comes with debugging kernel by default and see if the problem happens there, you should then be dropped in the debugger an automatically get a backtrace that could help investigating the issue. Use the "bt" debugger command to print it again (the debugger should do that automatically) Having a backtrace is no warranty of a resolution but would at least give an idea to what part of the kernel to start looking at. You should also configure enough swap so you can save a core dump that can be analyzed later. To get that at the debugger prompt use the "save" command, followed by "reboot". You can get head snapshots from https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/14.0/ -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
