Comment # 13
on bug 109246
from Nicholas Kazlauskas
(In reply to Michel Dänzer from comment #12) > (In reply to tme from comment #9) > > Setting amdgpu.dc=1 on 4.15.18 and 4.16.18 does not reproduce the problem. > > It does, however, reproduce on 4.17.19. > > Can you bisect between 4.16.18 and 4.17.19? > > (I see some HPD filtering related changes between them, Nicholas / Harry > maybe you can take a look if anything jumps out?) I haven't had a chance to look into the HPD changes yet, but we haven't seen this bug occur with our DPMS tests so I'm guessing that it's monitor specific. A system environment with Ubuntu/Plasma/xf86-video-amdgpu seems pretty standard at least. A bisection point on amd-staging-drm-next would certainly help narrow this down.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
