From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 116251] New: radeon 5a427809cd9143bef89ee3110f45e84f37484218 "drm/radeon: disable runtime pm on PX laptop" makes dGPU never stop
Date: Thu, 14 Apr 2016 02:35:55 +0000 [thread overview]
Message-ID: <bug-116251-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=116251
Bug ID: 116251
Summary: radeon 5a427809cd9143bef89ee3110f45e84f37484218
"drm/radeon: disable runtime pm on PX laptop" makes
dGPU never stop
Product: Drivers
Version: 2.5
Kernel Version: 4.5.1
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: eugene.shalygin@gmail.com
Regression: No
Clevo P177SM, these two GPUs:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor
Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Neptune XT [Radeon HD 8970M] (rev ff)
With kernel 4.5.1 the Radeon card is always on. Reverting
5a427809cd9143bef89ee3110f45e84f37484218 fixes the problem.
--
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
next reply other threads:[~2016-04-14 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 2:35 bugzilla-daemon [this message]
2016-04-14 2:37 ` [Bug 116251] radeon 5a427809cd9143bef89ee3110f45e84f37484218 "drm/radeon: disable runtime pm on PX laptop" makes dGPU never stop bugzilla-daemon
2016-04-14 2:43 ` bugzilla-daemon
2016-04-14 3:24 ` bugzilla-daemon
2016-04-14 12:12 ` bugzilla-daemon
2016-04-14 16:55 ` bugzilla-daemon
2016-04-15 10:26 ` bugzilla-daemon
2016-04-26 14:49 ` bugzilla-daemon
2016-04-26 14:52 ` bugzilla-daemon
2016-06-02 21:21 ` 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-116251-2300@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.