From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106957] GPU runtime suspend broken since 4.17
Date: Mon, 18 Jun 2018 20:49:51 +0000 [thread overview]
Message-ID: <bug-106957-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 933 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106957
Bug ID: 106957
Summary: GPU runtime suspend broken since 4.17
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: prg@cooco.de
CC: lukas@wunner.de
Created attachment 140212
--> https://bugs.freedesktop.org/attachment.cgi?id=140212&action=edit
dmesg from 4.17.2
I got a notebook with some Intel IGP and a Radeon HD5650. Since commit
07f4f97d7b4bf325d9f558c5b58230387e4e57e0 the dGPU is constantly DynPwr'd. This
still happens in 4.17.2, so the patch mentioned in #106597 doesn't help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2413 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
next reply other threads:[~2018-06-18 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 20:49 bugzilla-daemon [this message]
2018-06-18 22:06 ` [Bug 106957] GPU runtime suspend broken since 4.17 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
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@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.