From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Skylake CPU cannot enter package states lower than PC3
Date: Mon, 11 Jan 2021 21:29:54 +0100 [thread overview]
Message-ID: <20210111202954.6uYoQS2WsMiSxuXtik8gUlylErK7i_T86nEMvEWVlrs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27806@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/27806#issuecomment-758204397
Comment:
Fow what it's worth, I have a diff in https://gist.github.com/ericonr/a49d4fa9980aab0a5862a2c50bec6c3a
The only difference that I think could apply is ` SATA_MOBILE_LPM_POLICY 3 -> 0`, which means
```
config SATA_MOBILE_LPM_POLICY
int "Default SATA Link Power Management policy for mobile chipsets"
range 0 4
default 0
depends on SATA_AHCI
help
Select the Default SATA Link Power Management (LPM) policy to use
for mobile / laptop variants of chipsets / "South Bridges".
The value set has the following meanings:
0 => Keep firmware settings
1 => Maximum performance
2 => Medium power
3 => Medium power with Device Initiated PM enabled
4 => Minimum power
Note "Minimum power" is known to cause issues, including disk
corruption, with some disks and should not be used.
```
next prev parent reply other threads:[~2021-01-11 20:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 9:45 [ISSUE] " dkwo
2021-01-11 19:49 ` abenson
2021-01-11 19:52 ` ericonr
2021-01-11 20:29 ` ericonr [this message]
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=20210111202954.6uYoQS2WsMiSxuXtik8gUlylErK7i_T86nEMvEWVlrs@z \
--to=ericonr@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).