Date: Mon, 09 Dec 2024 17:21:14 +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-98KYneAE7l@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 #191 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to John F. Carr from comment #190) Note the attachment named "Crash without any use of ZFS, with acpi_wmi" ( see also comment #107 and "Relevant part of /var/log/messages" ). There is not even the likes of: ZFS filesystem version: 5 ZFS storage pool version: features support (5000) in the log, much less a backtrace with zfs content. Also, "Latest crash dump" is one that makes no mention of ZFS in its backtraces, as I remember. Each exposes-failure context had a similar "does not need to be in the backtrace for a failure to occur" status, at least given other example failure-reporting code was involved. My memory of the history was that failure never happened without drm-510-kmod being in use but the initial exposure of the problem was never via a backtrace involving drm-510-kmod . --=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-98KYneAE7l>