From nobody Fri Dec 27 12:44:11 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 4YKQDD0Ykdz5jhdl for ; Fri, 27 Dec 2024 12:44:12 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YKQDC5s4Sz4KTT for ; Fri, 27 Dec 2024 12:44:11 +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=1735303451; 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=cBrxuXGalD4z8cScEIS97aZWSeYAswkKOdax9eI5YsY=; b=qL2uDAtSTsp0A8ZLTtcf6L+z4eWVIpFe+PRkL22lfaIvAgQ0cdUvF1eR2kZKxeDTZvxv6P Hre7utImLTxWii6N+1nLcWOFy4LGOCvriE3EvLENroluHS3vA9+OUZKru1pzYYhOsI0ZoM r4Lac92dIqlpdUkkyifjwdW0qec1Rn3Tz8mJJDXlv3RbXLrY+16ZPXV5/Ej+T8ZcgqybF6 bhVJrUGHHn2F835VPC15yn704cBLkzoahZs/1eL/AAOqvtY9iZyayZA2Wxbo6qjuReFi8k W3/6G0Ty2vA/GsMW4ZWlR4MEaNV4hnpHPhySSRjxfB357E/7FJtrkkZKSu4a+Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735303451; a=rsa-sha256; cv=none; b=uMxXmb9XDcViNMWFULOKuR4rd6KWPVV6EKNxibu6/MevlLM7NeFXuFj4iyDXkh3SiW4264 pb9+E0pElas95Lj6krkK/t1w2GYc5/Jdi9a8a6kt9mc5x1z/2bUIcNZfB0EBAyWYbhv7by CT1+TS5sV7qA7Eor3G4NR0MCI7OoZo1/g0K5UaK9eC94nE3n1kDfPpkElB1zQendmaZH8F BqCbvlggyW3YeGeD3+VuRr+S0UaCf2/BL92WMdgWAJ8UtN+wlkAMdSe0zOvVFd9C08OM1e UtfzaIVf8aH5LAgBgb1/12fwD3hNn7ySUlJk8aEfTgv4KlAgz8S+Qj45cfbZNw== 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 4YKQDC5TPMzfZ6 for ; Fri, 27 Dec 2024 12:44:11 +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 4BRCiBF9032060 for ; Fri, 27 Dec 2024 12:44:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BRCiBsv032059 for bugs@FreeBSD.org; Fri, 27 Dec 2024 12:44:11 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: Fri, 27 Dec 2024 12:44:11 +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 #309 from Mark Millard --- (In reply to Andriy Gapon from comment #308) How many hardware watchpoints can be active at once? Which node gets the corruption varies . . . Failures based on the same kernel and kernel.debug: *(modlist_t) 0xfffff800045fd2c0 showed (vmcore.9): {link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800035b6f00= }, container =3D 0xfffff8000359f300, name =3D 0xffffffff82e1e010 "amdgpu_raven_mec_bin_fw", version =3D 1} *(modlist_t) 0xfffff800036f6300 showed (vmcore.0): {link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800047571c0= }, container =3D 0xfffff80004bfad80, name =3D 0xffffffff829ef000 "amdgpu_raven_me_bin_fw", version =3D 1} *(modlist_t) 0xfffff800035a0200 showed (vmcore.1): {link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff80003967980= }, container =3D 0xfffff800039fb300, name =3D 0xffffffff82e62026 "amdgpu_raven_mec2_bin_fw", version =3D 1} But even when it is the same node by name (and same number of nodes down the list) the address varies: *(modlist_t) 0xfffff800047c1180 shows (vmcore.4): {link =3D {tqe_next =3D 0xfffff80000000007, tqe_prev =3D 0xfffff800047c11c0= }, container =3D 0xfffff80004861a80, name =3D 0xffffffff82e62026 "amdgpu_raven_mec2_bin_fw", version =3D 1} Overall those suggest some sort of racy context at the time for the system, rather than a single, sequential-processing handling. For reference: vmcore.[23] were for capturing a successful boot. vmcore.2 involved a "shutdown now" which unloaded things of interest, making it of no use. vmcore.3 was a good capture of a successful boot. --=20 You are receiving this mail because: You are the assignee for the bug.=