From nobody Sun Dec 8 21:20:06 2024 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Y5yZH63fFz5fD4P for ; Sun, 08 Dec 2024 21:20:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y5yZG4T9Jz4ZDk for ; Sun, 8 Dec 2024 21:20:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1733692806; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6x3n3vO19qVEGx2fyONNET8YGQ4HzLKZEA4aOT/oybM=; b=RWairORDh6fnueo9UK2ODyW+74DBVY/6QXGNnOZclOJ9rsv+u+xxxTPdhqdpVuBNkYPjBT J/E7nwxtiOZS80N/24H99+85I462y94e9ek+IKyzOkFfnn7RasKvOt7+GJOlndvSLcIH81 QbhKFlsegVERABVYDBfsmErAjUvLNsHAeS3LPruwu2y/9QfFXubX/bCEI/cgT6kKaQ47aG CCjFDYldMO72g5FsOYKxRCKt1dL/V5U/TBdOQ0ybzH4eXeh8m2tGPhIVgupP4A6x8Eh/YL V+xhNVoA/AMJ6SGQGkuliIMFJMtTbG30O+DaJHyUF4H9zb20U1gLzUARuDnNAg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1733692806; a=rsa-sha256; cv=none; b=XruFISC4uvAnjAgVcntCnGKzOFZNxE+Z/ldfY6CP9KoFYFyomqk/5JKYfLyEU2A1TWJrYw biiJsUZZxJprNFTQMkDPJihSrHkDHsO8Lc8dETsccN7zZeEPSeZ5pes+3PkE0lxFl87Hl5 tF63crlHvzFcPI7IkKC2pbUSbtdAWOQGa32mHvn0wihkV8b5lf/UPPzurwPNxlwJUeym78 Sb1uDnHwq7Za9OtyQuAIrRvtVWnsR9it1D8WlkwHQsAMGZ4KEBQIp//r1QoH7llFSps72K a8kbUeKjVSeHNlHuU5XXXjNrhLYhfY0mRmkX9eZPARaslWYgbKkE+UTiuqoamQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Y5yZG45XGz181S for ; Sun, 8 Dec 2024 21:20:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4B8LK6wW091933 for ; Sun, 8 Dec 2024 21:20:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4B8LK6sw091932 for bugs@FreeBSD.org; Sun, 8 Dec 2024 21:20:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Sun, 08 Dec 2024 21:20:06 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 --- Comment #183 from Mark Millard --- (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.=