From: Pierre Neidhardt <ambrevar@gmail.com>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+)
Date: Fri, 13 Apr 2018 13:03:48 +0530 [thread overview]
Message-ID: <87k1tb8srn.fsf@gmail.com> (raw)
In-Reply-To: <20180413065059.6tvg2xsx722adl7i@doom>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
I ran two powertop reports comparing 4.14.33 and 4.16.1.
The most obvious difference is this on 4.16.1:
--8<---------------cut here---------------start------------->8---
* * * Top 10 Power Consumers * * *
Usage;Events/s;Category;Description
100.0%;;Device;Audio codec hwC0D0: Realtek
0.0%; 47.0;Timer;tick_sched_timer
0.2%; 38.0;Process;[PID 1258] xterm
0.0%; 34.3;Process;[PID 539] dzen2 -p -dock -ta l -fn DejaVu Sans Mono
0.7%; 21.3;Process;[PID 568] /gnu/store/07g1rwvrj7wn4sw6hx10hbvcs1v2adyf-emacs-prerelease-26.1-rc1/bin/emacs-26.1 --daemon -f exwm-enable
0.1%; 22.3;Interrupt;[0] HI_SOFTIRQ
0.3%; 12.9;Process;[PID 538] conky
0.0%; 13.1;Process;[PID 8] [rcu_sched]
0.0%; 8.6;Process;[PID 428] /gnu/store/183jf5g6qsql1i8zrgnziz5psvms68pc-xorg-server-1.19.6/bin/X -xkbdir /gnu/store/fpgz8f64dnz7szskjybrwkz4l9yl1
0.0%; 6.0;Timer;intel_uncore_fw_release_timer
--8<---------------cut here---------------end--------------->8---
That Realtek audio codec looks awfully suspicious.
Sounds a like a think to report on the kernel mailing list?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-04-13 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 6:06 Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+) Pierre Neidhardt
2018-04-13 6:50 ` Tomáš Čech
2018-04-13 7:33 ` Pierre Neidhardt [this message]
2018-04-13 10:14 ` Pierre Neidhardt
2018-04-24 8:37 ` Ludovic Courtès
2018-04-24 13:17 ` Pierre Neidhardt
2018-05-03 6:45 ` Pierre Neidhardt
2018-05-08 21:11 ` Nils Gillmann
2018-05-09 7:20 ` Pierre Neidhardt
2018-05-09 8:19 ` Nils Gillmann
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1tb8srn.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=sleep_walker@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).