Date: Sun, 08 Dec 2024 21:20:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@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-227-0hmYwUIlZF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267028-227@https.bugs.freebsd.org/bugzilla/> References: <bug-267028-227@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 #183 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to George Mitchell from comment #182) Over the 2+ years of failures, what is just the first failure-indicating message from each failing boot? Well, likely you could only approximate that. The point is to try to ignore later messages from failing boots that could just be consequences of prior failure activity for which there is already evidence. For example, if "WARNING !drm_modeset_is_locked(&crtc->mutex) failed" is never first, it is less likely to be of interest. But if it is always first it could be more likely to be of interest. (This is just for illustration, not special to the specific message.) Going the other way, again just as an example message: does it sometimes occur even when no overall failure happens? Such would also make such a message somewhat less likely to be of interest. Of course, different boots might not get the same kind of first failure-indicating message. But the list and relative frequency of occurrence might be of some use. Another issue could be that you might not have good evidence for first failure-indicating from the failing boot attempts: no way to answer the question then. --=20 You are receiving this mail because: 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-227-0hmYwUIlZF>