From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65811] New: AMD 7970M (PowerXpress) power management not functioning properly when using Xrandr to offload rendering
Date: Mon, 25 Nov 2013 20:36:05 +0000 [thread overview]
Message-ID: <bug-65811-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=65811
Bug ID: 65811
Summary: AMD 7970M (PowerXpress) power management not
functioning properly when using Xrandr to offload
rendering
Product: Drivers
Version: 2.5
Kernel Version: 3.13-rc1
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: jack@cyphernaut.org
Regression: No
rc1 appears to have solved my issues of X not starting or crashing when
starting, which I ran into when using the DRM patches on 3.12. However I've run
into another issue:
When I start my laptop, if I do not immediately offload rendering to the
discrete Radeon card (xrandr --setprovideroffloadsink radeon Intel) the state
in vgaswitcheroo will change to 'DynOff', and xrandr --listproviders will no
longer report the radeon as a potentially offload source
Conversely, if I *do* --setprovideroffloadsink to the radeon within a few
seconds after X starts, the state in vgaswitcheroo changes to DynPwr and never
actually turns off (laptop behaves as if runpm was not enabled at all).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-11-25 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 20:36 bugzilla-daemon [this message]
2013-11-25 20:38 ` [Bug 65811] AMD 7970M (PowerXpress) power management not functioning properly when using Xrandr to offload rendering bugzilla-daemon
2013-11-25 20:46 ` bugzilla-daemon
2013-11-26 13:43 ` bugzilla-daemon
2013-11-26 13:44 ` bugzilla-daemon
2013-11-26 19:56 ` bugzilla-daemon
2013-11-26 20:46 ` bugzilla-daemon
2013-11-26 21: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-65811-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.