| Bug ID | 94158 |
|---|---|
| Summary | [amdgpu][tonga] GPU randomly gets stuck at 100% load and high clocks |
| Product | DRI |
| Version | DRI git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | csaba.halasz@gmail.com |
I have noticed that my GPU fans start running at high speed after some time. Investigating, I see: # cat /sys/kernel/debug/dri/0/amdgpu_pm_info [ mclk ]: 1425 MHz [ sclk ]: 990 MHz [GPU load]: 100% Of course I am not running any graphics intensive programs and radeontop confirms <1% load. Even shutting down Xorg altogether doesn't help. It may be related to dpms going to "off" state, the last time it happened while the monitors were off, or possibly just as they were switching off. I will try to collect additional data points. Nothing suspicious shows in logs. Powerplay seems to work fine until the issue occurs. Afterwards, I can manually lower clocks, but load stays 100%. Side note: dpms transitions seem to reset the manual power_dpm_force_performance_level back to auto and hence high clock. System: r9 380, amdgpu git agd5f/drm-fixes-4.5 cc1de6e8 merged with agd5f/drm-next-4.6-wip fa9e6991, llvm git ae316aa0, mesa git fe14110f, Xorg 1.18
No, everything still works as usual and no sign of problem in the syslog (no dreaded VM_FAULT or "scheduler is timeout").
Hello, I have the same problem with an rx480. Also think it gets triggered when monitor goes into dpms "off" state. Sometimes I keep vlc run= ning etc so monitor does not go into sleep, than the issue never happens. says gpu load 100% under /sys/kernel/debug/dri/0/amdgpu_pm_info but I only have chrome open with 1 tab and hexchat nothing else. System: mesa-13.0.1, xf86-video-amdgpu-1.2.0, xorg-1.19.0 kernel 4.8.13 (slackware64-current), GPU: xfx 480 gtr
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/63.