Date: Sun, 22 Dec 2024 22:21:09 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko Message-ID: <bug-267028-227-KS3GLCWoCt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-227@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 --- Comment #274 from Mark Millard <marklmi26-fbsd@yahoo.com> --- If you could, I'd like to get a vmcore.* from a successful boot for comparison/contrast with the failures we now have examples of. For reference . . . From: https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ 10.1.3. Testing Kernel Dump Configuration The kernel includes a sysctl(8) node that requests a kernel panic. This can be used to verify that your system is properly configured to save kernel crash dumps. You may wish to remount existing file systems as read-only in single user mode before triggering the crash to avoid data loss. # shutdown now ... Enter full pathname of shell or RETURN for /bin/sh: # mount -a -u -r # sysctl debug.kdb.panic=3D1 debug.kdb.panic:panic: kdb_sysctl_panic ... After rebooting, your system should save a dump in /var/crash along with a matching summary from crashinfo(8). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267028-227-KS3GLCWoCt>