[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5164225.DI6hChFYCN@ylum>
Date: Sun, 20 Feb 2022 16:48:43 +0100
From: Dominique Dumont <dod@...ian.org>
To: Salvatore Bonaccorso <carnil@...ian.org>
Cc: Alex Deucher <alexander.deucher@....com>,
Sasha Levin <sashal@...nel.org>,
David Airlie <airlied@...ux.ie>,
Maling list - DRI developers
<dri-devel@...ts.freedesktop.org>,
"Pan, Xinhui" <Xinhui.Pan@....com>,
LKML <linux-kernel@...r.kernel.org>, 1005005@...s.debian.org,
Luben Tuikov <luben.tuikov@....com>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
Evan Quan <evan.quan@....com>,
Christian König <christian.koenig@....com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
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 <powerplay> failed" while suspending
All the best
[1] https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/
hibernate-issues
Powered by blists - more mailing lists