[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 21 Dec 2024 18:35:24 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028
--- Comment #263 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to George Mitchell from comment #261)
Looks like the build is somewhat different, possibly more
of a debug build? I think this is the first time that
mod = 0xfffff80000000007 has been reported for inside
modlist_lookup :
core.txt.9 :
#6 <signal handler called>
No locals.
#7 strcmp (s1=<optimized out>, s2=<optimized out>)
at /usr/src/sys/libkern/strcmp.c:44
No locals.
#8 0xffffffff80bc0ab4 in modlist_lookup (name=0xffffffff83255959 "zfsctrl",
ver=1) at /usr/src/sys/kern/kern_linker.c:1488
mod = 0xfffff80000000007
core.txt.0 :
#6 <signal handler called>
No locals.
#7 strcmp (s1=<optimized out>, s2=<optimized out>)
at /usr/src/sys/libkern/strcmp.c:44
No locals.
#8 0xffffffff80bc0ab4 in modlist_lookup (
name=0xffffffff829fd0c4 "vboxnetflt", ver=1)
at /usr/src/sys/kern/kern_linker.c:1488
mod = 0xfffff80000000007
If so, I'll need to synchronize to any updated files
that I'd previously downloaded, not just the vmcore.[90]
files.
(The mod value is not a surprise. It is from the same
linking field that was found to have 0xfffff80000000007
as its value in the earlier vmcore.8 .)
--
You are receiving this mail because:
You are on the CC list for the bug.