Summary: | discrete radeon HD 6400M/7400M intense heating even though it's "off" | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Tomas Pospisek <tpo_deb> | ||||
Component: | DRM/Radeon | Assignee: | 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: | ||||||
Attachments: |
|
Description
Tomas Pospisek
2013-07-22 15:04:33 UTC
Created attachment 82828 [details]
dmesg
dmesg with wlan stuff edited out
So if I boot with "radeon.dpm=1" then, as allready described, the laptop uses "relatively little" power, and is faning off some heat continuously, even when I set: # echo "battery" > /sys/class/drm/card1/device/power_dpm_state Whether I do the following does *not* seem to matter: # echo IGD > /sys/kernel/debug/vgaswitcheroo/switch # echo OFF > /sys/kernel/debug/vgaswitcheroo/switch But if I boot *without* "radeon.dpm=1" then the laptop will stay cool without fans running out of the box using around 14W. The various settings will show this then: # cat /sys/class/drm/card1/device/power_method dpm # cat /sys/class/drm/card1/device/power_profile default # cat /sys/class/drm/card1/device/power_dpm_state balanced Weird that power_method would show "dpm" even though I have booted *without* "radeon.dpm=1" ?! When I then set: # echo "battery" > /sys/class/drm/card1/device/power_dpm_state Power consumption will drop even further to ~11W. The overal logic of all of this is evidently completely escaping me... 8-o -- 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/358. |
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.