Bug 105144

Summary: Recent mesa makes GPU temperature too hot with GL/VDPAU/VAAPI
Product: DRI Reporter: K.Ohta <whatisthis.sowhat>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: XOrg git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description K.Ohta 2018-02-17 11:08:36 UTC
With mesa 17.3 (and maybe kernel >= 4.13), using GL,VAAPI or VDPAU, GPU temperature makes to be too hot.

Almost upper than 60℃ with RADEON HD7770 (less than 15℃ at room).
When not using GL etc, temperature upper than 50℃.
With earlier version of GL, VAAPI and VDPAU, temperature is less than 60℃ (at worst, less than 70℃).

Regards,
Ohta.
Comment 1 Luke McKee 2018-02-27 19:30:46 UTC
are you using amdgpu.ko kernel driver?

if so... 
https://forum-en.msi.com/index.php?topic=298468.0

Do you see the same powerplay error messages in the kernel log as described on that thread. There is a workaround to use fancontrol script from lm_sensors

Also try reading your bios file from your card, if you can't it will print an error about PCIE MMIO BAR regions. I have a theory this relates to a buggy motherboard bios efi code - as do others.
Comment 2 K.Ohta 2018-03-07 14:33:15 UTC
Sorry for later.
I don't use AMDGPU, (still) using RADEON kernel driver.
But, this seems to same issue.
I install fancontrol and set parameters of /etc/fancontrol , this issue seems to be fixed.
Thanks for your advice.

Regards,
Ohta.
# I'm using SAPPHIRE's RADEON HD7770 GPU board, and ASROCK 990FX Extreme4 mainboard.
Comment 3 Martin Peres 2019-11-19 09:32:00 UTC
-- 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/840.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.