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 00:22:58 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1605701251==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 20FCA6E284 for ; Wed, 13 Dec 2017 00:22:58 +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 --===============1605701251== Content-Type: multipart/alternative; boundary="15131245780.9E78cB.7468"; charset="UTF-8" --15131245780.9E78cB.7468 Date: Wed, 13 Dec 2017 00:22:58 +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 #9 from dwagner --- 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 above, but the result is still the same as in the origin= al description of this bug report. 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 computer does not react on input. 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? --=20 You are receiving this mail because: You are the assignee for the bug.= --15131245780.9E78cB.7468 Date: Wed, 13 Dec 2017 00:22:58 +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 # 9 on bug 10327= 7 from dwagner 
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=3Dc2a8=
99da6d8c0658c6f8493cb6b5ca4e890a15b7
referenced by Alex above, but the result is still the same as in the origin=
al
description of this bug report.

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 computer
does not react on input.

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?

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