From: Marc MERLIN <marc_powertop at merlins.org>
To: powertop@lists.01.org
Subject: [Powertop] Has anyone seen power bugs from kill -STOP process before and after S3 sleep?
Date: Sat, 23 Nov 2013 16:53:06 -0800 [thread overview]
Message-ID: <20131124005306.GC11389@merlins.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
I'm still trying to figure out why my laptop can idle at 12-13W or 20W
with no differences in processes, and why powertop (even latest, 1.25)
can provide very incorrect power values.
One thing I do that likely few people do:
killall -STOP chrome chromium firefox-bin xmms mplayer pidgin procmeter3 plugin-container
That seems to work with power of course, but I think it later causes
problem when I go to sleep (shut the lid) and come back later.
Have others seen issues with this?
It's happened for me for over a year, all the way to kernel 3.11
Could it also be generating the weird powertop behaviour I get and no
one else does?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
reply other threads:[~2013-11-24 0:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131124005306.GC11389@merlins.org \
--to=powertop@lists.01.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.