Date: Mon, 23 Dec 2024 01:11:33 +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-QEYL6vYtb5@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 #279 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #271) For the 4 example failure vmcore.* that we have so far, it has been that the first *.ko to load after: boot/modules/amdgpu_raven_vcn_bin.ko is the one for which the load activity detects the corruption. Even if it is another module instead of a kernel .ko that ends up having the detection by the code that does the loading. This time it was acpi_wmi that was the first after boot/modules/amdgpu_raven_vcn_bin.ko . This example got: {link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff80003967980= }, container =3D 0xfffff800039fb300, name =3D 0xffffffff82e62026 "amdgpu_raven_mec2_bin_fw", version =3D 1} like vmcore.8 did (but vmcore.8 was with older gpu-* code). --=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-QEYL6vYtb5>