Date: Tue, 25 Apr 2023 22:46:16 +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-UER6EUNPd5@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 #170 from George Mitchell <george@m5p.com> --- Created attachment 241750 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D241750&action= =3Dedit And another plain old boot time crash I had thought I could artificially provoke the crash by booting to single u= ser mode, loading the amdgpu, zfs, vboxnetflt, and acpi_wmi kernel modules in q= uick succession, and then continuing to multiuser mode. But that didn't do it. = So yesterday I went back to the old way of loading zfs with "zfs_enable=3D"YES= "" in rc.conf instead of "zfs_load=3D"YES"" in /boot/loader.conf, and loading amd= gpu by setting kld_list=3D"amdgpu" in rc.conf. And now I get the crashes again. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-3630-UER6EUNPd5>