From nobody Tue Apr 19 07:56:38 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 6491D11D0075 for ; Tue, 19 Apr 2022 07:56:49 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (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 4KjGNJ4Xx5z4SFp for ; Tue, 19 Apr 2022 07:56:48 +0000 (UTC) (envelope-from contact@evilham.com) From: Evilham DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=evilham.com; s=mail; t=1650355000; bh=6dDHTimuiJTcq2bgSHEZlSmjdi1znXX75W9bpQAmiVo=; h=From:To:Cc:Subject:References:In-reply-to:Date; b=awmVoscC6y8yU7gbWeeE6LyfNHeT5DA0oAHwXdlrOBiiWePhe5wwbqaM763yvr513 KRaQ7gLLwFv4VP4hnFQdlNRsTpXQcvmvit5QECzWD8eyluGrLJMykv8XeSh8gMamEU 1JvzuUH/jAxhoHngfpsN46UjtZa9a9aVj1tuudMQ= To: Pete Wright Cc: filis+fbsdcurrent@filis.org, freebsd-current@freebsd.org Subject: Re: -CURRENT hangs since at least 2022-04-04 References: <0c1b4885-dd0f-b48f-2ffe-12ccfd2ec118@filis.org> <3b85072c-eb07-6a74-fae3-258c99756c11@nomadlogic.org> In-reply-to: <3b85072c-eb07-6a74-fae3-258c99756c11@nomadlogic.org> Date: Tue, 19 Apr 2022 09:56:38 +0200 Message-ID: <29e49f2aec9683eb9736326d6596a63730cb@yggdrasil.evilham.com> 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 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4KjGNJ4Xx5z4SFp X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=evilham.com header.s=mail header.b=awmVoscC; dmarc=pass (policy=quarantine) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-2.01 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[evilham.com:s=mail]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TAGGED_RCPT(0.00)[fbsdcurrent]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.99)[0.989]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[evilham.com:+]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,quarantine]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL] X-ThisMailContainsUnwantedMimeParts: N On dl., abr. 18 2022, Pete Wright wrote: > On 4/18/22 12:23, filis+fbsdcurrent@filis.org wrote: >> Hi, >> >> I'm running -CURRENT on this one desktop box which is a "Ryzen=20 >> 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=20 >> started to >> completely freeze under X (I haven't tried letting it run=20 >> without X) after a >> few dozen minutes. >> I went on vacation and came back today and updated it again to=20 >> see if the >> issue went away, but it froze again. I went back to the latest=20 >> BE before >> 2022-04-04, which is from 2022-03-21 and so far it works fine=20 >> again. I use a >> different machine to build and then rsync /usr/src and /usr/obj=20 >> over and run >> make installworld, etc locally and also pkg upgrade (I use=20 >> FreeBSD -latest >> packages) everything, so I can't quite tell if this is related=20 >> to base or >> drm-kmod and I'm not too familiar with changes in the timeframe=20 >> 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=20 >> more light on >> this? >> > > After updating your CURRENT environment did you rebuild the=20 > drm-kmod package? > that's usually required as the LKPI is much more of a moving=20 > target on that > branch compared to STABLE or RELEASE.=C2=A0 i have a pretty much=20 > identical setup and > building/installing drm-devel-kmod has been working flawlessly=20 > for quite a > while. > > after building/installing my latest world i do following (this=20 > is from a local > script i use when rebuilding): > > cd $PORTS/graphics/drm-devel-kmod > sudo pkg unlock -y drm-devel-kmod > sudo make package > sudo pkg upgrade -y work/pkg/*.pkg > sudo pkg lock -y drm-devel-kmod > > -pete I too have recently noticed some freezes after a few hours on=20 -CURRENT that were not happening before. This with a matching drm-devel-kmod package (built with matching=20 source on matching kernel). The hw being: AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx -- Evilham