Date: Sun, 08 Dec 2024 15:50:46 +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-B7JBhAgTDt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028 --- Comment #181 from George Mitchell <george@m5p.com> --- After upgrading my system from 13.3-RELEASE-p8 to 13.4-RELEASE-p2 and recompiling drm_510_kmod (getting version drm-510-kmod-5.10.163_10 as reported by pkg info, despite the different version string seen below), I got a crah in single-user mode that at least left intelligible text on the screen, though I did not get a dump. Here, manually transcribed (unfortunately), are the things I saw: (once) Fatal Trap 9 in kernel mode (five times) kernel trap 22 with interrupts disabled Backtrace: kdb_backtrace vpanic panic trap_fatal call_trap linker_load_dependencies link_elf_load_file linker_load_module kern_kldload sys_kldload amd64_syscall fast_syscall_common The string "v5.10.163_7" once. I don't know where it came from, and my system log definitely says: Dec 7 18:04:33 court pkg[1782]: drm-510-kmod-5.10.163_9 deinstalled Dec 7 18:04:41 court pkg[1786]: drm-510-kmod-5.10.163_10 installed That's all I have, regrettably. Probably before the end of the year I will be upgrading to 14-RELEASE. Perhaps this helps. Despite the involvement of the zfs, vboxnetflt, and acpi_wmi kernel modules, none of those modules ever causes any trouble when drm-510-kmod is not present, and my (long) software engineering experience tells me that the simplest explanation is a bug in drm-510-kmod. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267028-227-B7JBhAgTDt>