<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - RX470 powerplay issues on hybrid laptop system (dGPU does not power down)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102468">102468</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>RX470 powerplay issues on hybrid laptop system (dGPU does not power down)
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>taijian@posteo.de
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=133866" name="attach_133866" title="relevant dmesg output">attachment 133866</a> <a href="attachment.cgi?id=133866&action=edit" title="relevant dmesg output">[details]</a></span>
relevant dmesg output
I have an Alienware 15R3 laptop with hybrid Intel (HD 630) / AMD (RX470)
graphics. I run Arch Linux, up to date as of 2017-08-29.
My issue is that when booting the laptop with a 'normal' kernel command line,
the dGPU *never* turns off, even when it is not normally needed in desktop
operations. This is confirmed by running powertop, which reports a power drain
of ~36 W even under basically zero load. This is accompanied by various
[powerplay] error messages in dmesg. As a side effect, the CPU is blocked from
going to power states below pc2.
If I blacklist amdgpu in the kcl and then force the dGPU to off with acpi_call,
the reported power consumption in powertop drops to ~12 W, with a corresponding
increase in battery time. The CPU is now able to reach pc3.
Booting into Windows 10 also gives me the same battery time as blacklisting
amdgpu in Linux, but also the expected 'on-demand-switching' of the dGPU that I
expect from such a setup. This is just to confirm that this is not a hardware
issue - it is definitely possible to dynamically switch the dGPU on or off from
the OS level, the implementation is just botched in amdgpu.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>