All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205291] Cannot switch off Radeon HD 4330/4350/4550 with vgaswitcheroo
Date: Wed, 22 Apr 2020 05:58:50 +0000	[thread overview]
Message-ID: <bug-205291-2300-6fbjHxmgkA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205291-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205291

Lukas Wunner (lukas@wunner.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lukas@wunner.de

--- Comment #8 from Lukas Wunner (lukas@wunner.de) ---
Starting with v4.17, the power management of HDA controllers on discrete GPUs
was changed such that the HDA keeps the GPU awake as long as it's in use:
https://lists.freedesktop.org/archives/nouveau/2018-February/029851.html

This exposed an issue with some ATI cards which was fixed in June 2018:
https://git.kernel.org/linus/57cb54e53bdd

So if you still experience GPU insomnia with v5.3 (which contains that fix),
then it's a different problem.

In one case, a user reported GPU insomnia with an Nvidia card and it turned out
that it was caused by a user space tool called "tlp" which disabled runtime
power management of the HDA via sysfs. Naturally, this caused the GPU to stay
awake. The solution in this case was to change the configuration of "tlp". But
it was also possible to manually override disablement of runtime PM on the HDA
by echoing "on" to the "power/control" file in the HDA PCI device's sysfs
directory:
https://bugs.freedesktop.org/show_bug.cgi?id=75985#c116

So you first may want to check whether runtime PM is disabled in sysfs, try to
manually enable it and see if the GPU runtime suspends, and if that works, find
out which user space tool disabled runtime PM on the HDA.

It's also possible that you've got a user space tool running which has opened
the HDA and thereby keeps the GPU awake. Some audio mixers do that.

If none of that fixes the problem, then we may indeed be dealing with a kernel
bug. The other bugs related to runtime PM of the HDA contain all the steps and
several debug patches to understand what's keeping the HDA awake, so we need
you to follow those instructions and report the results back. Here are the
relevant bugzillas:
https://bugs.freedesktop.org/show_bug.cgi?id=106597#c4
https://bugs.freedesktop.org/show_bug.cgi?id=106957#c1

One oddity I notice in your dmesg output is that there's only a single HDA
controller detected in your machine and that's the one on the discrete GPU.
Normally there are two HDAs, one is part of the Intel chipset and is
responsible for headphones, loudspeakers, mic and so on, and the other one is
on the discrete GPU and is only responsible for HDMI audio. On your machine,
there's no Intel chipset HDA and the one on the discrete GPU has a Line Out for
loudspeakers, headphone out, digital out and two microphone inputs. So that's a
little odd and may contribute to this issue.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-04-22  5:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-205291-2300@https.bugzilla.kernel.org/>
2020-04-20  2:46 ` [Bug 205291] Cannot switch off Radeon HD 4330/4350/4550 with vgaswitcheroo bugzilla-daemon
2020-04-20 13:50 ` bugzilla-daemon
2020-04-20 13:52 ` bugzilla-daemon
2020-04-20 21:03 ` bugzilla-daemon
2020-04-20 21:04 ` bugzilla-daemon
2020-04-20 21:05 ` bugzilla-daemon
2020-04-20 21:08 ` bugzilla-daemon
2020-04-20 21:16 ` bugzilla-daemon
2020-04-20 21:27 ` bugzilla-daemon
2020-04-22  5:58 ` bugzilla-daemon [this message]
2020-04-22 11:46 ` bugzilla-daemon
2020-04-22 11:49 ` bugzilla-daemon
2020-04-23  9:57 ` bugzilla-daemon
2020-05-07 10:39 ` 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-205291-2300-6fbjHxmgkA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.