From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id B4EC08E47; Sat, 23 May 2026 08:25:57 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 5FA4F8E3D; Sat, 23 May 2026 08:25:56 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fout-b4-smtp.messagingengine.com (fout-b4-smtp.messagingengine.com [202.12.124.147]) by atuin.qyliss.net (Postfix) with ESMTPS id 497078E3B for ; Sat, 23 May 2026 08:25:54 +0000 (UTC) Received: from phl-compute-03.internal (phl-compute-03.internal [10.202.2.43]) by mailfout.stl.internal (Postfix) with ESMTP id 539C41D00016; Sat, 23 May 2026 04:25:51 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-03.internal (MEProxy); Sat, 23 May 2026 04:25:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1779524751; x=1779611151; bh=ZhDyK9oDL8 2icIpzlqblRBvELcL5fZVtHLM9sVA9CP4=; b=spx/ddyE8gXFOIvq4Yp+51QaTa zNZ14Q4Xe+Dr8twJ7re3uOeRTQ/LzJ0cSXp8mZ44Yf+WTk3pmf8ZCZ7xAv6/0lOD AGbRCc/hd7ZHjNozS+jzt8Qr01RncZy7BYIrkgM76jOdUtmoXKAe0Xd/djPEEl/8 Ewn4pJlF+HE30w9+mV/WENW5CA75gkgM2tG85w/8PkriARjblAs2iNz7RqOZuuaz 8y0w4aNrlOidirlx1SuEb7bPDaNrVcWslIbpFzapw/1NfHB/TUe14IVy5MCToLYI NUAdEn9QX//naMaoI7YVGPo5G/Iy1+o4PUsqiesg0ke65wOxp+So0/2H8mAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1779524751; x=1779611151; bh=ZhDyK9oDL82icIpzlqblRBvELcL5fZVtHLM 9sVA9CP4=; b=B6FDzDXj6bfx6fWc1bAKWoh9olcI92onDNBqlSPgB4shTpnVH0e DxocEYspwUfYRRwXkEODa+yiWfMTrYkwbWrJZA4luws+/RtCeTcQo/sOL23W7e6b GmiytUPdVDcddU7r1U62QtKwInicYSSU7S2OGkWHNm27hyiaYFVvbdlqHFgi273V Zu09UC9KTfgdLVVJi1qehoQdWyA/zPDyAbzY24oaXN6NsIyxPYkUOuJwG+lP5SXp kzwFXyAUJilS9CJWLdAFEN5/4veoCBYcQXyvse52IvdllRwHwFnEQTG/MnHZyqx1 Tv41ewowr4hWQBo2sxTA0CJG1vMcFg+ESvw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdduhedvheeiucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhephffvvefujghffffkgggtsehgtderredttddtnecuhfhrohhmpeetlhihshhsrgcu tfhoshhsuceohhhisegrlhihshhsrgdrihhsqeenucggtffrrghtthgvrhhnpeeijeduhe fhteeigfegleekhfdthfelvdehledvtdejtdehtdeukeffgeffffeggfenucffohhmrghi nhepkhguvgdrohhrghdpfhhrvggvuggvshhkthhophdrohhrghdpkhgvrhhnvghlrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephhhi segrlhihshhsrgdrihhspdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuth dprhgtphhtthhopeguvghmihhosggvnhhouhhrsehgmhgrihhlrdgtohhmpdhrtghpthht ohepuggvvhgvlhesshhpvggtthhruhhmqdhoshdrohhrgh X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 23 May 2026 04:25:50 -0400 (EDT) Received: by fw12.qyliss.net (Postfix, from userid 1000) id 019B6B223BCB; Sat, 23 May 2026 10:25:48 +0200 (CEST) From: Alyssa Ross To: Demi Marie Obenour Subject: Re: [PATCH v2] Disable panel self-refresh on AMD GPUs In-Reply-To: <88bed6c7-8c7c-4708-8fc1-a3fba4ef7c21@gmail.com> References: <20260520-disable-panel-self-refresh-v1-1-dbc6ff6617c8@gmail.com> <20260520-disable-panel-self-refresh-v2-1-959c8ac37078@gmail.com> <87jyswdiwa.fsf@alyssa.is> <87h5o0vk14.fsf@alyssa.is> <88bed6c7-8c7c-4708-8fc1-a3fba4ef7c21@gmail.com> Date: Sat, 23 May 2026 10:25:46 +0200 Message-ID: <87bje6r0qd.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: QSBSCTVV55BEU4EZLEQJJM4OR36TSPHF X-Message-ID-Hash: QSBSCTVV55BEU4EZLEQJJM4OR36TSPHF X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Spectrum OS Development X-Mailman-Version: 3.3.9 Precedence: list List-Id: Patches and low-level development discussion Archived-At: <> List-Archive: <> List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Demi Marie Obenour writes: > On 5/21/26 11:50, Alyssa Ross wrote: >> Demi Marie Obenour writes: >>=20 >>> On 5/21/26 08:52, Alyssa Ross wrote: >>>> Demi Marie Obenour writes: >>>> >>>>> KDE Linux has already done this. It works around a long-running bug = in >>>>> the AMD GPU driver, which I believe also affects my test laptop. >>>>> Without the workaround, the system freezes and does not recover until= a >>>>> hard reboot. >>>> >>>> You tested this on your test laptop and it solved the problem? >>> >>> I didn't test it on my own hardware. After having spent so long on >>> Cloud Hypervisor, I'm having to set myself up for Spectrum development >>> again, and that is taking a little bit of time. >>> >>> However, the symptoms are identical to what many others have seen: >>> a freeze that needs a hard reboot to recover from. >>> >>>> Did you manually work around the card0/card1 bug? >>> >>> That bug would cause Weston to fail to start, but not to freeze >>> once started. >>=20 >> Right, but you'd have to get past it to even observe this problem, >> wouldn't you? So I'm not sure anybody would actually be affected by >> this currently. > > This patch could still be useful once Spectrum uses COSMIC, or for > anyone who has worked around the card0/card1 bug in their trees. > I'll see if it fixes the problem on my system. > > If this does fix the problem on my system (with the workaround), > I recommend applying it. Once KDE Linux stops including > amdgpu.dcdebugmask=3D0x10, it then makes sense for Spectrum to do > the same. > > This problem is very severe and has lasted quite a while [1]. > > There is also a report [2] of corruption on certain systems that > needs amdgpu.dcdebugmask=3D0x410 to resolve. There is a patch [3] > but it is not upstreamed to Linus's tree. It might be fixed by > AMD moving the relevant functionality into the power module in the > display controller. Presumably, this is firmware shared with Windows, > which means it should be better tested. > > Given the long list of problems with the display controller driver [4], > I suspect it is better to use the workaround for now.=20 > > [1]: https://invent.kde.org/kde-linux/kde-linux/-/merge_requests/431 > [2]: https://gitlab.freedesktop.org/drm/amd/-/work_items/5087 > [3]: https://lore.kernel.org/amd-gfx/20260329035830.21953-1-voroninan95to= n@gmail.com/ > [4]: https://gitlab.freedesktop.org/drm/amd/-/work_items?state=3Dopened&l= abel_name%5B%5D=3DDC I don't see any point in working around an issue that will likely be fixed before we make things work enough for anybody to encounter it. If it's still unfixed upstream once the card0/card1 issue is sorted, or if we discover there are systems that would have card0 and be affected by this bug, I'll consider applying it then. Otherwise it's just churn that benefits nobody. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQGoGac7QfI+H5ZtFCZddwkt31pFQUCahFkigAKCRCZddwkt31p FShbAQD2QJYlpzEqJ8pF6KcKoLPzk8gZrCgyPexKHueOzNQf+wEA40p1hUkJSGps lXCi/uIfawLn8CpEAzXSfwRsTguKbAI= =WmvK -----END PGP SIGNATURE----- --=-=-=--