Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Skylake CPU cannot enter package states lower than PC3
Date: Sun, 10 Jan 2021 10:45:31 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27806@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

New issue by dkwo on void-packages repository

https://github.com/void-linux/void-packages/issues/27806

Description:
On my Thinkpad T460s (i5-6300U), even after running `powertop --auto-tune`, the package cannot go below pc3 state. This seems specific to Void, as on Arch Linux it can go below that.
```
$ xuname
Void 5.10.5_1 x86_64-musl GenuineIntel uptodate hold rrnDDFFF
```
```
$ sudo powertop --auto-tune
Password:
modprobe cpufreq_stats failedLoaded 147 prior measurements
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
Devfreq not enabled
glob returned GLOB_NOMATCH
To show power estimates do 192 measurement(s) connected to battery only
Leaving PowerTOP
```
Incidentally, I've been trying to use Arch Linux kernel in Void, with the final goal of pinning this powertop issue down to some kernel config difference between Arch and Void, but while I can successfully build it (after changing some part about signing modules, vary GCC version and add `zstd` as `hostmakedepends`), when I try to boot it fails at decrypting the partition, with
```
encrypted_key: failed to alloc_cypher (-2)
modprobe: ERROR: could not insert 'dm_crypt': Unknown symbol in module, or unknown parameter (see dmesg)
device-mapper: reload ioctl on  failed: Invalid argument
```

Does anyone know what I'm missing?
Thanks.

             reply	other threads:[~2021-01-10  9:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-10  9:45 dkwo [this message]
2021-01-11 19:49 ` abenson
2021-01-11 19:52 ` ericonr
2021-01-11 20:29 ` ericonr
2021-01-11 22:41 ` abenson
2021-01-11 23:32 ` abenson
2021-01-12  8:56 ` dkwo
2021-01-13 12:16 ` dkwo
2021-01-13 12:18 ` dkwo
2021-01-13 13:07 ` dkwo
2021-01-13 22:28 ` abenson
2021-01-13 22:29 ` abenson
2021-01-14 10:57 ` dkwo
2021-01-16 15:44 ` dkwo
2021-01-16 15:44 ` [ISSUE] [CLOSED] " dkwo
2021-01-17  2:32 ` travankor
2021-01-17  9:09 ` dkwo
2021-01-21 22:05 ` dkwo

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27806@inbox.vuxu.org \
    --to=dkwo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).