Date: Mon, 30 Dec 2024 03:06:45 +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-RLC3niSWPQ@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 #340 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #337) For the vmcore.* file, I'm still seeing: Not Found In a week or so there will be a couple of weeks or so when I'll have no access to FreeBSD systems and I'll be otherwise fully occupied. Also, I'm likely in a greatly restricted FreeBSD-time context until then. [I'll remind that kernels with my investigative patches should not be used beyond boot testing. Normal operation should use a normal kernel.] But I've also not managed to generate any more potentially working ideas for identifying what is doing the unexpected modification. I've no clue what is going on for the db_hwatchpoint_cmd usage leading to "WARNING !drm_modeset_is_locked . . ." while giving no access to a backtrace or the like for when the unexpected modification happens. I'm not sure that I'm ever going to be all that much more help in isolating the problem if hwatchpoint use proves insufficient. --=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-RLC3niSWPQ>