All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106957] GPU runtime suspend broken since 4.17
Date: Tue, 19 Jun 2018 20:09:41 +0000	[thread overview]
Message-ID: <bug-106957-502-FP2aCEaMwq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106957-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Lukas Wunner <lukas@wunner.de> ---
Okay the HDA's runtime ref counter is 0 and it has no active children, so it
should suspend. Chances are it doesn't because rpm_idle() fails for some
reason.

Could you try this debug patch that I had created for #106597 and post the
dmesg output?

https://bugs.freedesktop.org/attachment.cgi?id=139706&action=edit

You can add "log_buf_len=10M ignore_loglevel" to the command line to ensure
that dmesg isn't truncated and contains all debug output.

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

[-- Attachment #1.2: Type: text/html, Size: 1503 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-06-19 20:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 20:49 [Bug 106957] GPU runtime suspend broken since 4.17 bugzilla-daemon
2018-06-18 22:06 ` bugzilla-daemon
2018-06-19 16:08 ` bugzilla-daemon
2018-06-19 17:51 ` bugzilla-daemon
2018-06-19 18:32 ` bugzilla-daemon
2018-06-19 20:09 ` bugzilla-daemon [this message]
2018-06-19 20:25 ` bugzilla-daemon
2018-06-20  4:12 ` bugzilla-daemon
2018-06-20  7:27 ` bugzilla-daemon
2018-06-21 19:43 ` bugzilla-daemon
2018-06-24 16:50 ` bugzilla-daemon
2018-06-29 11:15 ` 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-106957-502-FP2aCEaMwq@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.