Date: Mon, 30 Dec 2024 02:45:40 +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-6X4aK8w9vl@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 #339 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Andriy Gapon from comment #314) Thanks for clearing my muddled thinking about having a sufficiently known context for hwatchpoint specification. Unfortunately, my attempt at using db_hwatchpoint_cmd to automatically set up the monitoring seems to have lead to "WARNING !drm_modeset_is_locked . . ." as what visibly happens on detection --and is not providing for access to backtraces or such for the code doing the unexpected modification. If I did not mess up the db_hwatchpoint_cmd calls, I doubt that I have enough background knowledge to figure out what is going on or how to get it to allow providing the backtrace for the value change. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267028-3630-6X4aK8w9vl>