https://bugs.freedesktop.org/show_bug.cgi?id=104142
--- Comment #4 from Mike Lothian <m...@fireburn.co.uk> ---
Tried again and it looks a little more promising:
0a214e2fb6b0a56519b6d5efab4b21475c233ee0 is the first bad commit
commit 0a214e2fb6b0a56519b6d5efab4b21475c233ee0
Author: Andrey Grodzovsky <andrey.grodzov...@amd.com>
Date: Thu Jul 13 10:56:48 2017 -0400
drm/amd/display: Release cached atomic state in S3.
Fixes memory leak.
Signed-off-by: Andrey Grodzovsky <andrey.grodzov...@amd.com>
Reviewed-by: Tony Cheng <tony.ch...@amd.com>
Acked-by: Harry Wentland <harry.wentl...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
:040000 040000 494f25ce4ad407678f88d6c85128905762c9fbfb
fb36845ef2ccca7bf823c9fec4d13d0a6e71ea2b M drivers
Which makes sense as that's the commit that adds the WARN_ON, I guess that
takes us back to why is there a cached state
--
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