Date: Mon, 23 Dec 2024 20:40:14 +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-c6HhAAJyNe@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 #286 from George Mitchell <george@m5p.com> --- The variation on module addresses in recent crashes is because I changed the order of modules in my startup script. For core.txt.9, it was amdgpu, zfs, vboxnetflt, acpi_wmi. For core.txt.0, it was amdgpu, vboxnetflt, acpi_wmi, zfs. For core.txt.1 and the "normal" crash texts, it was amdgpu, acpi_wmi, zfs, vboxnetflt. That was to satisfy myself that it was possible to genera= te crashes where the "other" module involved along with amdgpu could change, a= nd further that it was always the one loaded immediately after amdgpu. I did = not intend to cause additional confusion, and I won't change the order any more= .=20 But I'm pretty sure I can generate more crashes (with no more module loadi= ng order changes) if needed. --=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-c6HhAAJyNe>