Comment # 68
on bug 110674
from Tom B
Apologies for the multiple replies/emails. I think I must just have got lucky. It worked several boots (in a row) and now only works very occasionally. I think it was just coincidence that it worked a few times after I installed that kernel, sorry guys. During my tests with 5.2.7 I have noticed some interesting findings with the wattage though. It will indeed get stuck on a specific wattage, I've had 33, 24, 45, 133, 134 and on several wattages there is some fluctuation. e.g. 33-34. Higher wattages are significantly more stable, 133w lasts quite a while before it crashes, 33w crashes instantly. I'm assuming this is because the card just doesn't have enough power to do what's required. When the wattage gets stuck, if you force the performance mode: # echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level it confuses the driver and sensors then shows ERROR: Can't get value of subfeature power1_average: I/O error Despite working until manually setting the power state. There doesn't seem to be a way to get it back to a state where sensors shows the wattage after it reaches this state, other than rebooting. The inconsistent nature of this bug and the fact that it sometimes doesn't appear suggests a race condition. I'd assume something else on the system happens before or after amdgpu is expecting. Is there any way to delay loading the amdgpu driver and manually loading it after everything else?
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
