From nobody Sun Dec 29 23:43:09 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 4YLwld7059z5j1KC for ; Sun, 29 Dec 2024 23:43:09 +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 4YLwld5BWcz4hXw for ; Sun, 29 Dec 2024 23:43:09 +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=1735515789; 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=joAEq+ycKXQ7KH3m4pKY2TBUs5XnNfyb+14/igTLnh4=; b=D9rP2kF8ich3G0sdU3U8Pil5wHqB3fRUohDGtwi0ToeYGDnmKd37BlXMSM0cLZriOangdo +Lq7mx6R0gzSXeN1jPAe1uZuIQGLbAtbKj3AJbHY3RBBuxp6KWlXMSJlW6/SPfWc7bvxSK W0gPz4UEHLazpwBuINFoPCSy3xdJrv8y2PZOkQd6MHF2xskj8oTBgUJ01vMd2F9S//7UBy DR5E127zu+jdlTdnvsNL/Dz4b2uBdm2rR+jSRqH9Q1z13N8+RH5iDXAhfpILXTm8ke8Dtm rNzIb2Hd2RHaWGXrSLFO0rxgit38wI3x995XLcoBVHJU8ZjQs94YxIgIgi3jQg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1735515789; a=rsa-sha256; cv=none; b=Jml1aV8z6avo1tTo0ycWrelfy08PotC0uKy3MmmlNInv1FJM5TfpIdThEeceuI3IzOWWwK 13WipJZzL1KzoajCPgxXEVzx+Gc47IQ2EH3rv9wwVy76FZo5MzoPIFM5nBEUHAqIrsNN6H OyA8jYWhLDMJmbk6B1WuW0CQFOozWgKg1X+vrcEIzj5vZthd482EjI4ulh63S3dkfGt5BT mMPRr9UKcFcejZ55HpqhMO/OHltbz9qxr6kfxUFry8BcMth2hFuneyj89Ex0wXhK0XPTTp v/kmrM9RtDkJm8QJ1/NVyArvmanf+2A0SZJiC9YzQ+0U1jf0S9rrqo7GnSco5A== 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 4YLwld4gb8zV3V for ; Sun, 29 Dec 2024 23:43:09 +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 4BTNh91I093034 for ; Sun, 29 Dec 2024 23:43:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4BTNh9Y3093033 for fs@FreeBSD.org; Sun, 29 Dec 2024 23:43:09 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: Sun, 29 Dec 2024 23:43:09 +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 #338 from Mark Millard --- (In reply to George Mitchell from comment #337) It again has the "WARNING !drm_modeset_is_locked . . ." lines before there is any trap or panic notice: . . . [drm] Initialized amdgpu 3.40.0 20150101 for drmn0 on minor 0 WARNING !drm_modeset_is_locked(&crtc->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:619 WARNING !drm_modeset_is_locked(&crtc->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:619 WARNING !drm_modeset_is_locked(&crtc->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:619 WARNING !drm_modeset_is_locked(&crtc->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:619 WARNING !drm_modeset_is_locked(&dev->mode_config.connection_mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:669 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/ports/graphics/drm-510-kmod/work/drm-kmod-drm_v5.10.163_7/drivers/gpu/= drm/drm_atomic_helper.c:894 kernel trap 22 with interrupts disabled kernel trap 22 with interrupts disabled panic: modlist_lookup: a prior tqe_next changed! . . . I do not see how to get useful information from the attempted use of the hwatchpoint monitoring for the unexpected tqe_next field value change. The above may be evidence that a detection happened but that the handling does not mix well with the drm/amdgpu operation in some way. --=20 You are receiving this mail because: You are on the CC list for the bug.=