Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
Our infrastructure migration is complete. Please remember to update your SSH remote to point to ssh.gitlab.freedesktop.org; SSH to the old hostname will time out. You should not see any problems apart from that. Please let us know if you do have any other issues.
GPU RX580 Nitro+ over DisplayPort to a single AOC 75hz monitor. Issue is on last kernels 4.18 4.19 but not in 4.14.
Screen starts flickering until reboot if I sleep/wake or if I manually switch the monitor off/on.
Tried to turn amdgpu.dc=0, screen then flickers everywhere anytime unless I manually change frequency from 75hz to 60hz. That only solves it inside KDE though.
Checking gpu related logs shows this error, but couldn't find anything else:
"Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff"
Compiled last AMD-drm-next kernel from git and problem's still here, even worse, it's now flickering everywhere at 75hz.
Discovered from another bug report that forcing clocks to high "fixed" the flickering, and it does indeed.
It also doesn't flicker if I force 60hz everywhere. It's worth mentioning its a 1080p Freesync 75hz DP1.2 monitor.
Will keep it like this for now and test it in games, but in kde plasma/chromium 73hz is smooth as silk it seems. Another thing I noticed is gtf generates higher pixel clocks than the ones from my monitor (edid?). You can compare above result with the attached xorg log.
This would be unrelated - those patches are still in review and not part of any tree yet.
Luminance flickering is also a bit different from typical flickering. It is a more subtle effect and doesn't have any sort of visual corruption associated with it - lines, the screen displaying black, etc.
This issue hasn't had any activity since 2019-11-19. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.