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, 22 Jan 2018 23:08:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0726187642==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 0B4596E2F0 for ; Mon, 22 Jan 2018 23:08:00 +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 --===============0726187642== Content-Type: multipart/alternative; boundary="15166624792.A3CF4f.18458" Content-Transfer-Encoding: 7bit --15166624792.A3CF4f.18458 Date: Mon, 22 Jan 2018 23:07:59 +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 #13 from dwagner --- (In reply to Harry Wentland from comment #12) > Can you try blacklisting amdgpu and try S3 again? (Assuming you mean adding "module_blacklist=3Damdgpu" on the kernel command line:) Sure, here is what happenes: kernel old =3D amd-staging-drm-next as of early October 2017 kernel new =3D amd-staging-drm-next as of this week amdgpu kernel blacklisted symptom after S3 resume -------------------------------------------------------- old no resumes fine every time old yes no HDMI signal, but system runs otherwise new no no HDMI signal, system crashes every time new yes no HDMI signal, but system runs otherwise > We've seen issues with S3 on 4.15 RCs outside of amdgpu where the system > wouldn't come back from S3. It's fixed in more recent RCs (definitely > 4.15-rc6 and newer) but the issue might still be there in > amd-staging-drm-next. Hmmm. Would "drm-next-4.16" include this fix? --=20 You are receiving this mail because: You are the assignee for the bug.= --15166624792.A3CF4f.18458 Date: Mon, 22 Jan 2018 23:07:59 +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 # 13 on bug 10327= 7 from dwagner 
(In reply to Harry Wentland from comment #12)
> Can you try blacklisting amdgpu and try S3 again=
?

(Assuming you mean adding "module_blacklist=3Damdgpu" on the kern=
el command
line:)

Sure, here is what happenes:

kernel old =3D amd-staging-drm-next as of early October 2017
kernel new =3D amd-staging-drm-next as of this week

          amdgpu
kernel  blacklisted  symptom after S3 resume
--------------------------------------------------------
old         no       resumes fine every time
old        yes       no HDMI signal, but system runs otherwise
new         no       no HDMI signal, system crashes every time
new        yes       no HDMI signal, but system runs otherwise

> We've seen issues with S3 on 4.15 RCs outside of=
 amdgpu where the system
> wouldn't come back from S3. It's fixed in more recent RCs (definitely
> 4.15-rc6 and newer) but the issue might still be there in
> amd-staging-drm-next.

Hmmm. Would "drm-next-4.16" include this fix?

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