[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
https://bugs.freedesktop.org/show_bug.cgi?id=104281 Harry Wentlandchanged: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Harry Wentland --- Marking resolved as reported to work fine on drm-next-4.17-wip. If this is still an issue feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 x86/entry/64: Add missing irqflags tracing to native_load_gs_index() I'm not sure what commit fixed it. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 is still > based on rc4. Thank you Alex. I tried drm-next-4.17-wip and I wasn't able to reproduce again the issue. Do you have by any change a pointer to the bug/fix? thanks! -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 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.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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 bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 104281] black / corrupted screen when resuming from S3 [AMDGPU]
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) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: ca...@caione.org Created attachment 136199 --> https://bugs.freedesktop.org/attachment.cgi?id=136199=edit journal_suspend_resume_corrupted_screen Hardware is AMD Bristol Ridge chipset with AMD A10-9620P RADEON R5 SoC. 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo (rev ca) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 699f (rev ff) Kernel is latest Linus master (4.15.0-rc3) compiled with CONFIG_DRM_AMD_DC_PRE_VEGA=y When resuming from suspend most of the times the screen is black / corrupted. I can still SSH into the system. In attachment the full log, including suspend + resume. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel