From nobody Mon Dec 30 02:45:40 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 4YM0pF0cVdz5jDk2 for ; Mon, 30 Dec 2024 02:45:41 +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 4YM0pD6hT4z4w6w for ; Mon, 30 Dec 2024 02:45:40 +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=1735526740; 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=nwM99nbn0w84gJ+DJgLTUTPSB0uqC+woUmRUDS5WfRk=; b=TY0oSC2rm9N9EHJVmHrOZg4GHodfu7dod05vKAOklvnp5thchIjKlRR2Gu+gZ+RNhNLHyS 2cwGZOnTEkpO+aIBDFwT/JjZmU9Nmyq5woXfPOHGt7AIjVP1+D0CxK6iIQOyL4p4gEW0qI 25+dkAVyN+M03xN5gnkneJhbuX74aswOQFFSjROqCK/1vUQaT9TRwSf1EzVWZcmTgL3yxS htrRoqFXWbhyNCfiXwrqkdLZskpFa6dFD/0mieE//Eb49ms+5FmjeLNJv1qgdq534QZDo1 yZar1uXwEmgt7zyMAvtlvQP55TkUkhuJlb+jpV8xyJy3sBMvq9aqxrB7w9QoLA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735526740; a=rsa-sha256; cv=none; b=y0UkfuzUtL8d2SespL9A51HewSbqaqUbSzXFFHUzEp+W31zwIFmdRcgZYgAuHz089qW87Y UaXPkvCy0VWoa9ZRfKshXaA+rBO8NBSHL/TYKlGP2D+OxnW2rUJxWU1kDny4mwQp2x6xaW GPI/hQ0NILM6X0B2rMLNm8H2tA1q7U/gijf9lLETJzetm2/rHPty6JmowYNFG+FVnGoLii PwKlxhnW37hhbCD4divaxaAD34Vh9RUkWNLUnmOM1OhuLzFVA++oxKMfZmdJt6/B3olMrf LFpaSMKBnyFd8SFuiwNvmgAgNqsdhcOBGZHCjMStUoOB/z/vGAO6mCwsawfAuQ== 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 4YM0pD6G4Szc8n for ; Mon, 30 Dec 2024 02:45:40 +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 4BU2jeOY011593 for ; Mon, 30 Dec 2024 02:45:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BU2je8w011592 for bugs@FreeBSD.org; Mon, 30 Dec 2024 02:45:40 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: Mon, 30 Dec 2024 02:45:40 +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 #339 from Mark Millard --- (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 the assignee for the bug.=