From nobody Mon Apr 18 19:23:11 2022 X-Original-To: freebsd-current@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 4E61D11DB291 for ; Mon, 18 Apr 2022 19:23:22 +0000 (UTC) (envelope-from filis+fbsdcurrent@filis.org) Received: from smtp1.nkhosting.net (smtp1.nkhosting.net [84.200.40.83]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4Khxfx3lW7z4Yb7 for ; Mon, 18 Apr 2022 19:23:21 +0000 (UTC) (envelope-from filis+fbsdcurrent@filis.org) Received: from [IPV6:2a01:170:1170:54:aaa1:59ff:fe9a:3960] (unknown [IPv6:2a01:170:1170:54:aaa1:59ff:fe9a:3960]) by smtp1.nkhosting.net (Postfix) with ESMTPSA id 9F9D3269F4 for ; Mon, 18 Apr 2022 21:23:12 +0200 (CEST) Message-ID: <0c1b4885-dd0f-b48f-2ffe-12ccfd2ec118@filis.org> Date: Mon, 18 Apr 2022 21:23:11 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 To: freebsd-current@FreeBSD.org Content-Language: en-US From: filis+fbsdcurrent@filis.org Subject: -CURRENT hangs since at least 2022-04-04 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Khxfx3lW7z4Yb7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=fail (mx1.freebsd.org: domain of filis@filis.org does not designate 84.200.40.83 as permitted sender) smtp.mailfrom=filis@filis.org X-Spamd-Result: default: False [-2.10 / 15.00]; ARC_NA(0.00)[]; R_SPF_FAIL(1.00)[-all:c]; FREEFALL_USER(0.00)[filis]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_NO_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; MLMMJ_DEST(0.00)[freebsd-current]; DMARC_NA(0.00)[filis.org]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:44066, ipnet:84.200.0.0/16, country:DE]; TAGGED_FROM(0.00)[fbsdcurrent]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N Hi, I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U with Radeon Graphics", since it didn't work on 13R. I use Boot environments and on 2022-04-04 I updated it and it started to completely freeze under X (I haven't tried letting it run without X) after a few dozen minutes. I went on vacation and came back today and updated it again to see if the issue went away, but it froze again. I went back to the latest BE before 2022-04-04, which is from 2022-03-21 and so far it works fine again. I use a different machine to build and then rsync /usr/src and /usr/obj over and run make installworld, etc locally and also pkg upgrade (I use FreeBSD -latest packages) everything, so I can't quite tell if this is related to base or drm-kmod and I'm not too familiar with changes in the timeframe between 2022-03-21 and 2022-04-04 that would affect my setup. Is there anything I can try and/or find or collect info to shed more light on this? Cheers, filis