dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3
Date: Wed, 23 May 2018 06:54:51 +0000	[thread overview]
Message-ID: <bug-106597-502-iSDFRT2tWH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106597-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from Lukas Wunner <lukas@wunner.de> ---
Created attachment 139688
  --> https://bugs.freedesktop.org/attachment.cgi?id=139688&action=edit
drm-next-4.18-wip debug patch 1

So, the HDA device's usage counter is 0, it has no active children and runtime
PM is allowed. Still, it's runtime active. Why is it not suspending? Here's a
little patch which litters relevant code with debug printks, hopefully this
will get us closer to the answer. Could you apply this on top of
drm-next-4.18-wip and attach the resulting dmesg output?

Oh and could you also try:
cat /sys/bus/pci/devices/0000:01:00.1/power/runtime_status
... to double check that runtime PM is enabled?

Thanks!

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

[-- Attachment #1.2: Type: text/html, Size: 1943 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

  parent reply	other threads:[~2018-05-23  6:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 20:36 [Bug 106597] [vga_switcheroo] commit 07f4f97d7b4bf325d9f558c5b58230387e4e57e0 breaks dpm on Alienware 15R3 bugzilla-daemon
2018-05-21 20:59 ` bugzilla-daemon
2018-05-21 21:17 ` bugzilla-daemon
2018-05-21 21:26 ` bugzilla-daemon
2018-05-21 21:34 ` bugzilla-daemon
2018-05-21 21:47 ` bugzilla-daemon
2018-05-21 22:03 ` bugzilla-daemon
2018-05-21 22:43 ` bugzilla-daemon
2018-05-22  8:16 ` bugzilla-daemon
2018-05-22  8:18 ` bugzilla-daemon
2018-05-22  8:19 ` bugzilla-daemon
2018-05-22  8:22 ` bugzilla-daemon
2018-05-22  9:03 ` bugzilla-daemon
2018-05-22 20:40 ` bugzilla-daemon
2018-05-22 21:18 ` bugzilla-daemon
2018-05-22 21:49 ` bugzilla-daemon
2018-05-23  6:54 ` bugzilla-daemon [this message]
2018-05-23  9:59 ` bugzilla-daemon
2018-05-23 10:21 ` bugzilla-daemon
2018-05-23 12:19 ` bugzilla-daemon
2018-05-23 23:12 ` bugzilla-daemon
2018-05-24  8:56 ` bugzilla-daemon
2018-05-24 10:01 ` bugzilla-daemon
2018-05-24 10:04 ` bugzilla-daemon
2018-05-24 10:13 ` bugzilla-daemon
2018-05-24 10:28 ` bugzilla-daemon
2018-05-24 13:07 ` bugzilla-daemon
2018-05-24 15:34 ` bugzilla-daemon
2018-05-24 15:43 ` bugzilla-daemon
2018-05-24 16:15 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 16:40 ` bugzilla-daemon
2018-05-24 17:18 ` bugzilla-daemon
2018-05-24 17:42 ` bugzilla-daemon
2018-05-24 21:08 ` 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-106597-502-iSDFRT2tWH@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).