Date: Mon, 23 Dec 2024 00:08:40 +0000 From: bugzilla-noreply@freebsd.org To: fs@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-3630-JiS6SZkIJb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-3630@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 #275 from George Mitchell <george@m5p.com> --- Created attachment 256053 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D256053&action= =3Dedit core.txt.1 core.txt.1 starts with my attempt to generate a "normal" vmcore file. (It causes me severe cognitive dissonance to type that phrase.) It wrote a du= mp to my swap partition and rebooted, upon which I got the panic for this very bug, which overwrote the "normal" crash dump, and then that dump got saved = as vmcore.1. I had rearranged my module loading order, which is why this core.txt.1 refers to module acpi_wmi.ko -- it was the first one loaded after amdgpu.ko. I'll put vmcore.1.z in the directory we've been using. Then I = will retry the "normal" crash dump sequence to get you a "normal" crash dump.=20 (cringe) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267028-3630-JiS6SZkIJb>