All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102468] RX470 powerplay issues on hybrid laptop system (dGPU does not power down)
Date: Tue, 29 Aug 2017 16:48:10 +0000	[thread overview]
Message-ID: <bug-102468-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1898 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=102468

            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
  --> https://bugs.freedesktop.org/attachment.cgi?id=133866&action=edit
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3332 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-08-29 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 16:48 bugzilla-daemon [this message]
2017-08-29 16:51 ` [Bug 102468] RX470 powerplay issues on hybrid laptop system (dGPU does not power down) bugzilla-daemon
2017-08-29 18:21 ` bugzilla-daemon
2017-09-04 17:25 ` bugzilla-daemon
2017-09-28 14:06 ` bugzilla-daemon
2017-09-28 17:57 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-102468-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.