Date: Thu, 12 Dec 2024 18:44:36 +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-bWgsmERM7l@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 #217 from Mark Millard <marklmi26-fbsd@yahoo.com> --- comment #5 and comment #82 both identify strcmp for the failure context and both identify it is a strcmp during modlist_lookup that got the failures in those examples. This is part of the linker_load_module activity, something the back trace in your recent example also indicates as going on. comment #5 was for a context attempting to find "zfs". comment #82 was for a cotnext attempting to find "acpi_wmi". (That aspect varies across the failures.) The comment #82 notes are likely the closest to being failure details as far as I can tell. Only the kgdb backtrace seems to be all that useful and is what comment #5 and comment #82 were based on, apparently with correct contexts for matching the live system kernel of the times in question. --=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-bWgsmERM7l>