From nobody Mon Mar 20 23:03:19 2023 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 4PgVdg5Yb5z40Nrb for ; Mon, 20 Mar 2023 23:03:19 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PgVdg4TJlz444y for ; Mon, 20 Mar 2023 23:03:19 +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=1679353399; 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=2khIocQSbNllWf76DpOeVg24TJ6D/qRjMrLSoRhdSqA=; b=QAKWVqFYC330o6rQ2gs+dPYFPRswEBDhrINI6YVjr5IWm6VYUJS2v/m7Vg0ruJuK73BWq3 aoI0lk/3ZCRgqZBYuh4Hl7a0HZTvfuFUCPsNQdkhHSxArHjuAkU3N8XZL4Cjwu72d0hzwL AUo59kAXqZQyxfFFUV0vcLaq/WrQjSQZO5dKFZAhivAxMhXRisDRB7gakPWE24y21nLsaJ n6MXZ+krP/FA3f7XC/AQ/V8IOETfPZ9wOfvRxT8/sDMa8B/RptD/rhmgtDMdXy6xGLMWPi biDzmhxqe8El5hCYU9yjMHfRBsn69sSyjfO0LNV4h1l8RX8q0mHfASpYnhfJ7A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1679353399; a=rsa-sha256; cv=none; b=wj146F5NVUe20WOHYrj7Y4/0PJIOovSNXeYYCZDj7d+KNAaZlcTBHN4be1WuE1pVPtXECc yYyasUs2CnrV5MI2MGBBV56yiKwlZ8kKBLUbm3uvoGr9uaFBbAvJb145jpPvWPmxhdFcrx gPxHDFlOHQmymR7D6aXHbfGnOXhtmZuGZQWnSENHSb37PBavxYzEyq4ecAeHvoMu4UqB1J gu8t1PeNp7EGCnwsIiw54jw8aHtWuWY8X49we9g0oL3h/jsP6i1RaGenSSkMyvOF+YdLXH S8N8fK44phpQZy90WiqPrcUlGqlIo+a6iyhfxlnWeFuVGzoo85rU8Ymuwx7U3A== 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 4PgVdg3b43zpGl for ; Mon, 20 Mar 2023 23:03:19 +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 32KN3Jj4025416 for ; Mon, 20 Mar 2023 23:03:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 32KN3JuA025415 for fs@FreeBSD.org; Mon, 20 Mar 2023 23:03:19 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, 20 Mar 2023 23:03:19 +0000 X-Bugzilla-Reason: CC 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: fs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267028 --- Comment #140 from Mark Millard --- (In reply to George Mitchell from comment #137) All 4 are examples related to dbuf_evict_thread (a.k.a. zfs dbuf related crashes), as I feared. All 4 look like: Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x7 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff82600ba6 Looks to be in: 5 1 0xffffffff82600000 3df128 zfs.ko panic: page fault cpuid =3D 1 time =3D 1679349400 KDB: stack backtrace: #0 0xffffffff80c66ee5 at kdb_backtrace+0x65 #1 0xffffffff80c1bbef at vpanic+0x17f #2 0xffffffff80c1ba63 at panic+0x43 #3 0xffffffff810addf5 at trap_fatal+0x385 #4 0xffffffff810ade4f at trap_pfault+0x4f #5 0xffffffff81084fd8 at calltrap+0x8 #6 0xffffffff827ac768 at zap_evict_sync+0x68 #7 0xffffffff8267d74a at dbuf_destroy+0xba #8 0xffffffff82683129 at dbuf_evict_one+0xf9 #9 0xffffffff8267b43d at dbuf_evict_thread+0x31d #10 0xffffffff80bd8abe at fork_exit+0x7e #11 0xffffffff8108604e at fork_trampoline+0xe #6 0xffffffff810ade4f in trap_pfault (frame=3D0xfffffe00b3bb6d00,=20 usermode=3Dfalse, signo=3D, ucode=3D) at /usr/src/sys/amd64/amd64/trap.c:763 #7 #8 avl_destroy_nodes (tree=3Dtree@entry=3D0xfffff8001a80b5a0,=20 cookie=3Dcookie@entry=3D0xfffffe00b3bb6dd0) at /usr/src/sys/contrib/openzfs/module/avl/avl.c:1023 #9 0xffffffff827ac768 in mze_destroy (zap=3D0xfffff8001a80b480) at /usr/src/sys/contrib/openzfs/module/zfs/zap_micro.c:402 A question would be if this repeats based on amdgpu having been loaded (again last) but no X11 like activity having ever been started: limiting amdgpu use to just the load activity or as close to that limited of use as is possible. (This is separate from your zfs load time adjustment test.) My guess is that the content of some memory area(s) is being trashed in your context. I'm not sure how to track down what is doing the trashing or were all the trashed area(s) are if that is what is going on. At least we now have a clue how to get the specific type of crash. Before I had no clue what an example initial-context might be like. Note: Changing the load order should get a matching kldstat report to indicate the address ranges that end up involved. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=