Date: Sun, 05 Mar 2023 06:57:25 +0000 From: bugzilla-noreply@freebsd.org To: fs@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-3630-oNVfuPVxH9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-3630@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 #92 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #91) So, apparently, this was not one of the UFS-only experiments. The gdb backtrace is messy: . . . #7 <signal handler called> . . . #27 <signal handler called> #28 0x00000000002881da in ?? () Backtrace stopped: Cannot access memory at address 0x7fffffffd688 This indicates that we are not seeing evidence from the earlier problem that got #27. That, in turn, may or may not have been the original problem. The context looks to be a very different context than prior reports. But not seeing what lead to #27 makes forming solid judgments problematical. I see from this that a modern gdb (kgdb) was in use for this failure for the crashinfo generation after the savecore operation, having no problems with DWARF 4 vs. 2. But it would seem to be the boot media normally used with ZFS instead of the boot media intended for UFS-only testing. The two might be different for what is around for gdb (kgdb) for crashinfo to use. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-3630-oNVfuPVxH9>