Date: Wed, 18 Dec 2024 00:41: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-TijCAUvxbD@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 #249 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #248) A debug build of drm-510-kmod under 13.4-RELEASE would need to match up with vmcore.* examples that used the debug build. A non-debug build of drm-510-kmod under 13.4-RELEASE would need to match up with vmcore.* examples that used the non-debug build. So it is more driven by the vmcore.* content than anything for debug vs. non-debug: which was in use? The only thing that I know of for having the matching *.ko files for a vmcore.* is that "info files" would likely show the (correct) address ranges from the sections in the additional *.ko files that were loaded but are not there to find in what I now have. --=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-TijCAUvxbD>