| Bug ID | 102468 |
|---|---|
| Summary | RX470 powerplay issues on hybrid laptop system (dGPU does not= power down) |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | taijian@posteo.de |
Created attachment 133866<=
/a> [details]
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 lin=
e,
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 dr=
ain
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 f=
rom
going to power states below pc2.
If I blacklist amdgpu in the kcl and then force the dGPU to off with acpi_c=
all,
the reported power consumption in powertop drops to ~12 W, with a correspon=
ding
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 th=
at I
expect from such a setup. This is just to confirm that this is not a hardwa=
re
issue - it is definitely possible to dynamically switch the dGPU on or off =
from
the OS level, the implementation is just botched in amdgpu.
(In reply to taijian from comment #0) > 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 p= c3. What acpi call did you use?
I followed the recommendations of this page: https://wi= ki.archlinux.org/index.php/Hybrid_graphics The call working on my system is: echo "\\_SB.PCI0.PEG0.PEGP._OFF"= ; > /proc/acpi/call If I use this command on a system that does not have amdgpu blacklisted, however, this will lead to unstable system behaviour and a certain crash wi= thin ~5 min.
Also, this might be related: https:= //bugzilla.kernel.org/show_bug.cgi?id=3D156341#c65
| What | Removed | Added |
|---|---|---|
| Attachment #133866 is obsolete | 1 |
Created attachme=
nt 134540 [details]
dmesg output with kernel 4.13.3
| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTOURBUG |
| Status | NEW | RESOLVED |
OK, so I finally summoned to courage to decompile my laptop's = DSDT and look at that to debug my ACPI problems - turns out that "Linux" just gets= plain shafted by the firmware. I rebootet with 'acpi_osi=3D!* acpi_osi=3D"Windows 20= 15"' and the problem disappeared.=20 So, I'm sorry if I wasted anybody's time. I'll direct the rest of the power= play bugs to a different topic.