From nobody Mon Dec 30 02:45:40 2024 X-Original-To: fs@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 4YM0pF414Rz5jDcv 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 4YM0pF0Hlbz4wV9 for ; Mon, 30 Dec 2024 02:45:41 +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=1735526741; 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=jJbhyGxBbzEgml9Kh1FL9vVaa8s6XNekOyo8AT5EzDs=; b=Kbhoa+xETToRUEoDrHI22uFoQX2u+xT7Pi1WoVZPprke1sBJZIF1Mi1FyZ8Mu/RnzowqZW MK/hyJ2mPo3NqZCLdKmpHwFKtWwUR8sru6AAxNhBLvhFDW2xrWRW+rIOZhjd55iEPUBUPw a4nlPcd3Dbs3UMkHwYDklIgcrb45tRiW8hffr9up7t0JXqmxBkNolXheP0BexeGembavOB 9J8azRBVA7ETf634g1IFMncB2LoQentRASgvdvXHnKvpO+xKbXG3UDPjAlz4UcYzNBJtnh grVc2L1PY3rOsuvWQu5R7K65riaeNeZC6VEHvlxrXzLnXcI83ksunZ5j5Ws4Dg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735526741; a=rsa-sha256; cv=none; b=AbXjwFEElokRk3qa5p8ZX4ouCA9fbvh+j4hXXF37ajajQMzdduQBwtQOrVz6gBpT7Gv70q H+NSmgK4ZmyQg9OPxyrkjdr1xv8le9a5zCF/xy8xMYJ99FOvD8AtnBIh8QOb0hCsQqBP+j g4S1fLfT1Ji4i0R1vBNamcJT7Azg4h5Xh3WyaiYvSuXV/e+AnjxuMy7xnuYKCxgMe2qZnq +mupvsiGAxYPQgYy6DPaJ5fbtlxeHF8sso5R7wH4GG+/d/pWywGsb5F5cfyZt1knMXS2B3 SUIAnwY31ArVeRtaqmOPSEoblbtfgW+qG3FqHJEKIDf9QsX44Qbv+/V58ztI4g== 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 4YM0pD6hkjzcHp 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 4BU2jeLF011597 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 4BU2jeWv011596 for fs@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: fs@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: CC 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: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@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 on the CC list for the bug.=