From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45061] Power consumption higher after resume, probably vgaswitcheroo/radeon related
Date: Fri, 5 Oct 2012 19:13:52 +0000 (UTC) [thread overview]
Message-ID: <20121005191352.844BB11FB3D@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-45061-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=45061
--- Comment #3 from Peter <lekensteyn@gmail.com> 2012-10-05 19:13:52 ---
You can mark this bug as a duplicate of that bug.
Does your machine have an indicator that shows whether the discrete graphics
card is enabled or not? If you happens to have such an indicator and also have
a Windows installation with drivers installed, can you check what happens
around suspend/resume?
On my Nvidia Optimus laptop, the following holds for a s/r cycle under Windows:
- indicator shows initially that the dGPU is deactivated.
- Before suspend, indicator shows that dGPU is activated.
- On resume, the indicator initially shows the dGPU as deactivated. Then, it
turns shortly to "activated", and then to "deactivated" again.
- indicator finally shows the dGPU as deactivated.
Is this also true for AMD?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-10-05 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 10:15 [Bug 45061] New: Power consumption higher after resume, probably vgaswitcheroo/radeon related bugzilla-daemon
2012-10-05 15:01 ` [Bug 45061] " bugzilla-daemon
2012-10-05 17:56 ` bugzilla-daemon
2012-10-05 19:13 ` bugzilla-daemon [this message]
2012-10-05 19:22 ` bugzilla-daemon
2012-10-05 19:25 ` bugzilla-daemon
2012-10-05 19:36 ` bugzilla-daemon
2012-10-05 20:00 ` 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=20121005191352.844BB11FB3D@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 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).