From nobody Mon Dec 23 17:47:36 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 4YH58926kLz5X1qB for ; Mon, 23 Dec 2024 17:47:37 +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 4YH5885ykWz54mb for ; Mon, 23 Dec 2024 17:47:36 +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=1734976056; 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=TDPmrgLUfi0Vz/Q7jzl1iIUgY9w35zqlkAoanxiOaEs=; b=scyEKlI3j2Gk66w5EfcZj6cMoEon0rRHooLEOTLN1bAi1KR+sA5Lqsf1/OM1wE+N5B+o8+ doKDT9P4fF3l3RchtFF2S9JGD1c+aXKam9HrHgXzhUjQ9yBP4ifYsRMJNdyl5kKL0Lax71 iCqn84v7vYNEOBa9rFlM79gZ6IWb0mIXFt4nXypY37pHtZ9i3WmvBXVasCpm83FVKD7bX8 qvvClS6QgTD3FQxKHb9eyPLN3GzF/1LeowspWA3EVbj4SYKW8rhCID28ZGQHKEbFhe0hxF +r2wAn/RD4HVPo0mXZ6AQA8LZQuDBHyO7eJmbUARb2FrtxsXZxDH7o6qPa/Irg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1734976056; a=rsa-sha256; cv=none; b=mguYE16ldWY+ixxSb+9pL8EQ60NKuUq5iDELFNuNwnL8xZ+ASJFuEGWDr2v2NKr17VBcbx W7VzBJMLvnvoEeXl/CgCNhdYB5X16f07+bLdku2cV2qvsrFR86d29dTx7j/kXnSoCAcCA6 OF9wgOQAG4P4RcKTN9v2HxZqkvRZgA2O0H1gDGI4MpRLHtZrP3QiY+q8to42o0g6fv0eCR RUDxA3RiLCe6J/x5LWXTLQZjDYkaC3b9yUeRPtzTO5o//6w7/hPB/ZCOMsGbDBJQFnx9um mOmW8xb96TzFCUujvdA2OcpZXnl285X+x1nxRliaH3ue2i3PY7/Eqi1SI2agpQ== 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 4YH5885Y92z13l7 for ; Mon, 23 Dec 2024 17:47:36 +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 4BNHlaUa052507 for ; Mon, 23 Dec 2024 17:47:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BNHlapl052506 for bugs@FreeBSD.org; Mon, 23 Dec 2024 17:47:36 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, 23 Dec 2024 17:47:36 +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 #285 from Mark Millard --- (In reply to George Mitchell from comment #282) As for what I was trying to do . . . Turns out that the addresses of the entries in the found_modules list are not stable in detail from boot to boot. So I can not use the successful-boot case to figure out where to expect to find the last entries might be at in the failing case (nodes after the corrupted pointer is involved). --=20 You are receiving this mail because: You are the assignee for the bug.=