Bug ID | 98004 |
---|---|
Summary | RX470 doesn't reclock memory if a second display has been plugged in at some point |
Product | DRI |
Version | unspecified |
Hardware | x86-64 (AMD64) |
OS | Linux (All) |
Status | NEW |
Severity | minor |
Priority | medium |
Component | DRM/AMDgpu |
Assignee | dri-devel@lists.freedesktop.org |
Reporter | jonathanmoerman@gmail.com |
If a second display has been plugged in the memory clock gets stuck at the highest frequency, even if the display is disabled (using xrandr) or unplugged again. How to reproduce: plug in a second display and either disable it or unplug it again, the memory will continue to be clocked at its maximal frequency (Here: 1750Mhz). Kernels used for testing: Linux 4.4 (amdgpu-pro kernel driver), 4.7, 4.8rc5 The hardware is perfectly capable of clocking back to its lowest frequency if only one display is actually enabled. (It works as expected in Windows) This issue doesn't cause any problems other than using more watts than necessary. I'm not currently using the system with the RX470 GPU, I'll upload a dmesg log in a few minutes. I'm sorry if this isn't the correct place to post this bug, I'm new here.
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