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: Fri, 26 Jan 2018 23:08:18 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1954065020=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 084936E6B1
for ; Fri, 26 Jan 2018 23:08:18 +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
--===============1954065020==
Content-Type: multipart/alternative; boundary="15170080973.caB7c1e4f.6079"
Content-Transfer-Encoding: 7bit
--15170080973.caB7c1e4f.6079
Date: Fri, 26 Jan 2018 23:08:17 +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 #7 from Alex Deucher ---
Does it work with drm-next-4.17-wip? There was a non-drm bug that broke S3=
in
the kernel what was not fixed until rc6. amd-staging-drm-next is still bas=
ed
on rc4.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15170080973.caB7c1e4f.6079
Date: Fri, 26 Jan 2018 23:08:17 +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
Does it work with drm-next-4.17-wip? There was a non-drm bug =
that broke S3 in
the kernel what was not fixed until rc6. amd-staging-drm-next is still bas=
ed
on rc4.