From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CB05AC4332F for ; Mon, 21 Feb 2022 08:30:50 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id CF4BF112408; Mon, 21 Feb 2022 08:30:48 +0000 (UTC) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by gabe.freedesktop.org (Postfix) with ESMTPS id 510C610E380; Sun, 20 Feb 2022 15:48:58 +0000 (UTC) Received: from ylum.localnet (unknown [IPv6:2a01:e0a:3d9:ddd0:37f3:7f74:639b:b0a3]) (Authenticated sender: domi.dumont@free.fr) by smtp1-g21.free.fr (Postfix) with ESMTPSA id 4BF65B004EE; Sun, 20 Feb 2022 16:48:43 +0100 (CET) From: Dominique Dumont To: Salvatore Bonaccorso Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? Date: Sun, 20 Feb 2022 16:48:43 +0100 Message-ID: <5164225.DI6hChFYCN@ylum> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Mailman-Approved-At: Mon, 21 Feb 2022 08:30:47 +0000 X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: dod@debian.org Cc: Sasha Levin , amd-gfx list , David Airlie , "Pan, Xinhui" , LKML , Maling list - DRI developers , Luben Tuikov , 1005005@bugs.debian.org, Alex Deucher , Evan Quan , Christian =?ISO-8859-1?Q?K=F6nig?= Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote: > Does the system actually suspend? Not really. The screens looks like it's going to suspend, but it does come back after 10s or so. The light mounted in the middle of the power button does not switch off. > Is this system S0i3 or regular S3? I'm not sure how to check that. After a bit of reading on the Internet [1], I hope that the following information answers that question. Please get back to me if that's not the case. Looks like my system supports both Soi3 and S3 $ cat /sys/power/state freeze mem disk I get the same result running these 2 commands as root: # echo freeze > /sys/power/state # echo mem > /sys/power/state > Does this patch help by any chance? > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i > d=e55a3aea418269266d84f426b3bd70794d3389c8 yes, with this patch: - the suspend issue is solved - kernel logs no longer show messages like "failed to send message" or "*ERROR* suspend of IP block failed" while suspending All the best [1] https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/ hibernate-issues