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: Sat, 17 Mar 2018 11:13:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1176222117==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4274A6E180 for ; Sat, 17 Mar 2018 11:13:41 +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 --===============1176222117== Content-Type: multipart/alternative; boundary="15212852212.3bbcdC.5194" Content-Transfer-Encoding: 7bit --15212852212.3bbcdC.5194 Date: Sat, 17 Mar 2018 11:13:41 +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 #20 from dwagner --- (In reply to mikita.lipski@amd.com from comment #19) > I have attempted to reproduce an issue, but didn't succeed. > We have used an identical hardware setup with a reference rx460 card and > couldn't reproduce a hang on various kernel versions. Strange. If I didn't keep an older amd-staging-drm-next kernel from October 2017 in use where S3 resumes work every time, I would doubt my hardware - b= ut the way it is the only possible cause is a kernel change sine then. > There is still a possibility that some kernel config options might be > causing an issue.=20 > If its possible, could you please provide kernel configuration so the > testing environment is identical. Sure, will attach my .config (as used with the current drm-next-4.17-wip) a= fter this comment. > Also does the issue reproduce reproduce if you disable DC? (amdgpu.dc=3D0= in > GRUB menu) Tested with today's drm-next-4.17-wip git: With "amdgpu.dc=3D0" on the kern= el command line, resume from S3 works fine for me, both from the console (befo= re starting X11) and when running X11. (But of course, no 4k/60Hz video and no HDMI audio with amdgpu.dc=3D0, so t= hat is not really an option for actual use.) So the resume-from-S3 failures are definitely caused by something in the DC code that changed since early October 2017. --=20 You are receiving this mail because: You are the assignee for the bug.= --15212852212.3bbcdC.5194 Date: Sat, 17 Mar 2018 11:13:41 +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

Comme= nt # 20 on bug 10327= 7 from dwagner 
(In reply to miki=
ta.lipski@amd.com from com=
ment #19)
> I have attempted to reproduce an issue, but didn=
't succeed.
> We have used an identical hardware setup with a reference rx460 card a=
nd
> couldn't reproduce a hang on various kernel versions.

Strange. If I didn't keep an older amd-staging-drm-next kernel from October
2017 in use where S3 resumes work every time, I would doubt my hardware - b=
ut
the way it is the only possible cause is a kernel change sine then.

> There is still a possibility that some kernel co=
nfig options might be
> causing an issue.=20
> If its possible, could you please provide kernel configuration so the
> testing environment is identical.

Sure, will attach my .config (as used with the current drm-next-4.17-wip) a=
fter
this comment.

> Also does the issue reproduce reproduce if you d=
isable DC? (amdgpu.dc=3D0 in
> GRUB menu)

Tested with today's drm-next-4.17-wip git: With "amdgpu.dc=3D0" o=
n the kernel
command line, resume from S3 works fine for me, both from the console (befo=
re
starting X11) and when running X11.
(But of course, no 4k/60Hz video and no HDMI audio with amdgpu.dc=3D0, so t=
hat is
not really an option for actual use.)

So the resume-from-S3 failures are definitely caused by something in the DC
code that changed since early October 2017.

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