From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 103277] [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit Date: Mon, 11 Dec 2017 21:55:42 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1376500442==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 85E326E1D8 for ; Mon, 11 Dec 2017 21:55:42 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1376500442== Content-Type: multipart/alternative; boundary="15130293421.ce1D1Ff9.2632"; charset="UTF-8" --15130293421.ce1D1Ff9.2632 Date: Mon, 11 Dec 2017 21:55:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D103277 --- Comment #4 from Jerry.Zuo@amd.com --- (In reply to dwagner from comment #3) > (In reply to Jordan L from comment #2) > > Thanks, we can reproduce this too, should have something shortly. >=20 > Any news on this? >=20 > I am asking, because the current head of > https://cgit.freedesktop.org/~agd5f/linux/log/?h=3Damd-staging-drm-next (= as of > commit d66bebab317cc56a2a6d2438fcd89870c3d172ca) still has this very bug - > and that is even though within "git log" I can see in commit > 26c860d5579684528114c3875ef88f7796330eb5 there was > > Revert "drm/amd/display: Match actual state during S3 resume." > so I currently know of no way to make the current amd-staging-drm-next > resume from S3 sleep. S3 starts working since commit 95539e2be57.=20 Test is performed on the following condition: Commit: c6f284d9888 Asic: Baffin 4K display: Acer H277HK S3 passed in 10 runs Please verify at your side as well. Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.= --15130293421.ce1D1Ff9.2632 Date: Mon, 11 Dec 2017 21:55:42 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 4 on bug 10327= 7 from Jerry.Zuo@amd.co= m 
(In reply to dwagner from comment #3)
> (In reply to Jordan L from comment #2)
> > Thanks, we can reproduce this too, should have something shortly.
>=20
> Any news on this?
>=20
> I am asking, because the current head of
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=3Damd-stagin=
g-drm-next (as of
> commit d66bebab317cc56a2a6d2438fcd89870c3d172ca) still has this very b=
ug -
> and that is even though within "git log" I can see in commit
> 26c860d5579684528114c3875ef88f7796330eb5 there was
> > Revert "drm/amd/display: Match actual state during S3 resume=
."
> so I currently know of no way to make the current amd-staging-drm-next
> resume from S3 sleep.

S3 starts working since commit 95539e2be57.=20

Test is performed on the following condition:
Commit: c6f284d9888
Asic: Baffin
4K display: Acer H277HK
S3 passed in 10 runs

Please verify at your side as well. Thanks.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15130293421.ce1D1Ff9.2632-- --===============1376500442== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1376500442==--