[Bug 267028] kernel panics when booting with both (zfs,ko or vboxnetflt,ko or acpi_wmi.ko) and amdgpu.ko

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028

--- Comment #90 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to George Mitchell from comment #89)

What vintage/version of *gdb was in use? (If it was
gdb that complained.) Was it /usr/local/bin/*gdb ?
/usr/libexec/*gdb ? Actually, for the backtrace
activity, it is kgdb that is used, not gdb. Thus my
use of "*gdb" notation.

But a core.txt.* file in my context shows:

GNU gdb (GDB) 12.1 [GDB v12.1 for FreeBSD]

which would be for /usr/local/bin/*gdb ( not
/usr/libexec/*gdb ). This is because I have:

# pkg info gdb
gdb-12.1_3
Name           : gdb
Version        : 12.1_3
. . .

installed. (I had to a livecore.* to have something
to reference/illustrate with, having no example
vmcore.* files around for a long time.)

A significantly older gdb might indicate use of
an old /usr/libexec/*gdb that had not been cleaned
out.

I'll note that I got no DWARF complaints from
kgdb and:

# llvm-dwarfdump -r 1 /usr/lib/debug/boot/kernel/kernel.debug | grep DWARF |
head -1
0x00000000: Compile Unit: length = 0x000001d3, format = DWARF32, version =
0x0004, abbr_offset = 0x0000, addr_size = 0x08 (next unit at 0x000001d7)

indicates  version = 0x0004 .

This leads me to expect that you have an old
gdb (kgdb) around that is in use.


It sounds like you got a savecore into /var/crash/ .
It should be possible to try investigating that without
having to cause another crash, presuming the system
is not updated (so that it matches the crash contents).
For example, the same sort of command that crashinfo
uses on the saved system-core file could be manually
tried, possibly with a more modern kgdb vintage being
used that would handle the more recent dwarf version.

Attaching your core.txt.* file content might prove
useful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.