From: Nils Gillmann <ng0@n0.is>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+)
Date: Tue, 8 May 2018 21:11:08 +0000 [thread overview]
Message-ID: <20180508211108.dhahlvreutqujxtb@abyayala> (raw)
In-Reply-To: <87tvrpqlu8.fsf@gmail.com>
Pierre Neidhardt transcribed 1.0K bytes:
>
> I've re-tested with 4.16.6: still happening, the battery life is about
> 50% down.
>
> If I blacklist the nouveau kernel module, then the module stops crashing
> in loop, which improves battery time a little bit, but the difference
> with 4.15 is still startling.
>
> Note that blacklisting the nouveau kernel module has the side effect of
> preventing the kernel from putting the video card to sleep, which drains
> the battery even more.
>
> --
> Pierre Neidhardt
Out of Guix suppport scope, but I have a mainboard (not with nouveau)
which showed problems with a certain 4.x version of Linux[1]. The debug
sugesstion by Intel is to configure and run the drm-tip branch[0] of
the kernel. I can't advocate how to package or do this here (which is
too bad), but for all things graphics related this will be suggested
by upstream most certainly.
0: branch as in the repository, not linux repository itself. In case you
are unfamilar with linux development branching model.
1: Variants of https://bugs.freedesktop.org/buglist.cgi?quicksearch=i915%20intel_cpu_fifo_underrun_irq_handler&list_id=579081
and this is still going on.
next prev parent reply other threads:[~2018-05-08 21:10 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
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 [this message]
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=20180508211108.dhahlvreutqujxtb@abyayala \
--to=ng0@n0.is \
--cc=ambrevar@gmail.com \
--cc=help-guix@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).