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: Wed, 13 Dec 2017 16:11:12 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0243465967==" 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 208236E52D for ; Wed, 13 Dec 2017 16:11:12 +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 --===============0243465967== Content-Type: multipart/alternative; boundary="15131814721.fc0717bEe.21630"; charset="UTF-8" --15131814721.fc0717bEe.21630 Date: Wed, 13 Dec 2017 16:11:12 +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 #10 from Jerry Zuo --- (In reply to dwagner from comment #9) > Bad news: Tried amd-staging-drm-next as of commit > 367a3d2bdc27fd1d23be9ea75cec34b52297184d, which does include the commit > https://cgit.freedesktop.org/~agd5f/linux/commit/?h=3Damd-staging-drm- > next&id=3Dc2a899da6d8c0658c6f8493cb6b5ca4e890a15b7 referenced by Alex abo= ve, > but the result is still the same as in the original description of this b= ug > report. >=20 > I tested "echo "mem" >/sys/power/state" both without starting X and from = an > Xterm, in both cases no picture comes up at resume from S3, and the compu= ter > does not react on input. >=20 > The test scenario Jerry Zuo described above does not mention whether the > display was connected via DP or HDMI - could this be of relevance for > reproduction? I tested on HDMI in 4K display. I'll check the commit on drm-next. --=20 You are receiving this mail because: You are the assignee for the bug.= --15131814721.fc0717bEe.21630 Date: Wed, 13 Dec 2017 16:11:12 +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 # 10 on bug 10327= 7 from <= span class=3D"fn">Jerry Zuo 
(In reply to dwagner from comment #9)
> Bad news: Tried amd-staging-drm-next as of commit
> 367a3d2bdc27fd1d23be9ea75cec34b52297184d, which does include the commit
> https://cgit.freedesktop.org/~agd5f/linux/commit/?h=3Damd-stagi=
ng-drm-
> next&id=3Dc2a899da6d8c0658c6f8493cb6b5ca4e890a15b7 referenced by A=
lex above,
> but the result is still the same as in the original description of thi=
s bug
> report.
>=20
> I tested "echo "mem" >/sys/power/state" both wi=
thout starting X and from an
> Xterm, in both cases no picture comes up at resume from S3, and the co=
mputer
> does not react on input.
>=20
> The test scenario Jerry Zuo described above does not mention whether t=
he
> display was connected via DP or HDMI - could this be of relevance for
> reproduction?

I tested on HDMI in 4K display. I'll check the commit on drm-next.

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