From nobody Mon Feb 27 17:57:55 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 4PQSs06KHDz3vQKV for ; Mon, 27 Feb 2023 17:57:56 +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 4PQSs05Hbqz3twr for ; Mon, 27 Feb 2023 17:57:56 +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=1677520676; 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=HZKDZDK0ykcIrJA6RKOwPB2SCrKdQ0v8bXmNXSFIsWY=; b=ks8pP7cPbYPUPnJzuHivqO25dSvvIzbgEgRv+l4nhvdM0EmPF0uDVCMcuTDByFWRY/admg 2J+Ae4blQfyCwhzDp0vIOWCCGtmWX+UbsfSVRQv+XUNQn36nQ5+mj9lrV89wTAKfcVmwcJ 4AVbYb3d1XL4/bvWpgQW0ciw41kRdVLLFbk3myC9Lo64qkEKuh1t4WttYDeD3S6Y3Me+bw YkNPCVDs7URPFBFivGe1ZVl8lM2oGJfpSTpA7//qh7NMuW7AFBLcbU97f2sZamxq9VKuN+ A71MtTx7fWnkwgZHmLc4MefYWzxYxZqhbdAqJbgkMupNf7XNNpg+hpoNOEtlTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1677520676; a=rsa-sha256; cv=none; b=mxt8twZIcaoWOsefUyVby2RglSCRHSnsdh/PE6BrklvJO0dmbv60Y71BQa/0bbT9iZNdF6 ouVDRYgA47rR7pdvr/6YheE34EbKgyceu579WCOpREJEggfrHtA4l7Md6ZtA4qzExphEbd TE1Rta2UUSjN04S3QyYboYTCQAiE5NJOLGVbClOS7axXHRkm37+fTCMBYmOvNMPvAQgsii HHkY+Ug+nDougygwdk9kxGqqEeNLloPYgj77Z0zEqY2FVKsuHsthjt3Qon7LjU3MHdNqtV 09L486ql4KRQC4vDgvLW3o2WWq/9S36cw5qIf8KXqiVLAdF5colHL1UQ/N42ag== 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 4PQSs04M5vzbJD for ; Mon, 27 Feb 2023 17:57:56 +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 31RHvuNC010174 for ; Mon, 27 Feb 2023 17:57:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 31RHvuou010173 for fs@FreeBSD.org; Mon, 27 Feb 2023 17:57:56 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, 27 Feb 2023 17:57:55 +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: george@m5p.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 #85 from George Mitchell --- I have a new crash, but I did not get a dump because of an issue I will exp= lain below. For those who came in late, here's a summary of my system. dmesg says I have:CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics (3493.71-MHz K8-c= lass CPU) Origin=3D"AuthenticAMD" Id=3D0x810f10 Family=3D0x17 Model=3D0x11 Step= ping=3D0 =20 Features=3D0x178bfbff =20 Features2=3D0x7ed8320b AMD Features=3D0x2e500800 AMD Features2=3D0x35c233ff Structured Extended Features=3D0x209c01a9 XSAVE Features=3D0xf AMD Extended Feature Extensions ID EBX=3D0x1007 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 TSC: P-state invariant, performance statistics My motherboard is a Gigabyte B450M D53H. BIOS is American Megatrends version F4, dated 1/25/2019. pciconf -lv says: vgapci0@pci0:6:0:0: class=3D0x030000 rev=3D0xc8 hdr=3D0x00 vendor=3D0x1= 002 device=3D0x15dd subvendor=3D0x1458 subdevice=3D0xd000 vendor =3D 'Advanced Micro Devices, Inc. [AMD/ATI]' device =3D 'Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Se= ries]' class =3D display subclass =3D VGA Until recently, when I was running FBSD 12-RELEASE, my box had one hard dri= ve.=20 I added a new drive when I upgraded to FBSD 13-RELEASE so I would still have FBSD 12 as an emergency backup. Part of the upgrade is that on the new dis= k I created a small UFS slice for /, /var, and /tmp, and most of the rest of the disk is a ZFS slice for /usr (so I wouldn't have to wait for fsck on reboot after crashes). That means that it isn't practical to do a test without ZF= S on that new disk (I'll call it my regular disk now). So I installed FBSD 13 (= same version as my regular disk) on the old disk (I'll call it the test disk now= ), which had (and still has) a small UFS slice for /, /var, and /tmp and a big= UFS slice for /usr. To boot from the test disk, I use the BIOS boot menu, since (unsurprisingly= ) I have set the default boot disk to my regular disk. I removed all mentions of ZFS and VBOX from /boot/loader.conf and /etc/rc.c= onf on the test disk. Then I booted up a whole bunch of times. On the thirtee= nth try, I got the crash. Unfortunately, I don't have a crash summary from it because the system rebooted from my regular disk instead of the test disk w= hile I was still staring at the crash message on the screen. Subsequently, I bo= oted 20 more times from the test disk without getting the crash again. What I saw (for a few seconds) on the screen from the one crash sure looked like the same old backtrace, and I have to say, to an ignorant yokel like myself, it seemed to be saying that there's a locking problem in amdgpu. T= here was absolutely no virtual terminal switching, because I had not started an X server and I did not type ALT+Fn. I'll try getting a proper crash dump later (possibly tomorrow). My thanks = to all of you for your patience. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=