From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU] Date: Tue, 02 Jan 2018 13:47:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1993815541==" 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 7467D89CF8 for ; Tue, 2 Jan 2018 13:47:04 +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 --===============1993815541== Content-Type: multipart/alternative; boundary="15149008240.a24071F.25947"; charset="UTF-8" --15149008240.a24071F.25947 Date: Tue, 2 Jan 2018 13:47:04 +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=3D104281 --- Comment #5 from Carlo Caione --- Created attachment 136493 --> https://bugs.freedesktop.org/attachment.cgi?id=3D136493&action=3Dedit journal corrupted screen amd-staging-drm-next Unfortunately I just verified that this is still reproducible on the development branch (agd5f/amd-staging-drm-next), it's just a bit more difficult. In attachment the log captured when the system is resumed and the screen is corrupted. --=20 You are receiving this mail because: You are the assignee for the bug.= --15149008240.a24071F.25947 Date: Tue, 2 Jan 2018 13:47:04 +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 # 5 on bug 10428= 1 from = Carlo Caione
Created attachment 136493 [details]=

journal corrupted screen amd-staging-drm-next

Unfortunately I just verified that this is still reproducible on the
development branch (agd5f/amd-staging-drm-next), it's just a bit more
difficult.

In attachment the log captured when the system is resumed and the screen is
corrupted.


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