https://bugs.freedesktop.org/show_bug.cgi?id=104281
Harry Wentland changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #9 from Alex Deucher ---
The commit that broke it was:
commit ca37e57bbe0cf1455ea3e84eb89ed04a132d59e1 (refs/bisect/bad)
Author: Andy Lutomirski
Date: Wed Nov 22 20:39:16 2017 -0800
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #8 from Carlo Caione ---
(In reply to Alex Deucher from comment #7)
> 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
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- 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 based
on rc4.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #6 from Carlo Caione ---
Hey Harry,
any idea about this? This is still reproducible today on the
agd5f/amd-staging-drm-next branch.
Thanks,
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #5 from Carlo Caione ---
Created attachment 136493
--> https://bugs.freedesktop.org/attachment.cgi?id=136493=edit
journal corrupted screen amd-staging-drm-next
Unfortunately I just verified that this is still
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #4 from Harry Wentland ---
Thanks, Daniel. The fix should land for 4.16 then.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #3 from Daniel Drake ---
Need to do more testing to be sure, but it appears that this is not
reproducible on the development branch
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #2 from Daniel Drake ---
Suspend/resume is working OK on these machines with DC disabled, so it seems to
be a DC regression.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104281
--- Comment #1 from Carlo Caione ---
The issue is not limited to this laptop model. We have at least 3 other ACER
models affected by this.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104281
Bug ID: 104281
Summary: black / corrupted screen when resuming from S3
[AMDGPU]
Product: DRI
Version: XOrg git
Hardware: Other
OS: Linux (All)
11 matches
Mail list logo