From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 210993] Intel frequency scaling causes electrical noise on 10th gen CPUs
Date: Tue, 05 Jan 2021 08:10:24 +0000 [thread overview]
Message-ID: <bug-210993-137361-TEEYMjodt3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210993-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210993
--- Comment #10 from Karol Herbst (karolherbst@gmail.com) ---
(In reply to Francisco Jerez from comment #7)
> (In reply to Karol Herbst from comment #6)
> >
> > > Does disabling some specific idle state (e.g via
> > > /sys/devices/system/cpu/cpu*/cpuidle/state*/disable) have any effect on
> the
> > > noise?
> >
> > disabling all except state0 stops the noise.
>
> Ah that makes sense, that sounds like the culprit might be a noisy power
> supply coupled to the oscillation of the processor's current draw caused by
> repeated C-state transitions. If that's the case you may be able to tweak
> the latency parameters to make sure the oscillation frequency is outside the
> audible range, though I'm not sure if it would make sense to upstream such a
> change since it will likely come at an energy cost (Though I would expect
> the cost to be minor as long as the processor can still reach the deepest
> sleep state in the steady state while idle, might be a good trade-off in
> your specific case if this is particularly annoying to you).
yeah... might be. Although it felt like this is a more common issue with newer
CPUs, especially 10th gen Intel CPUs and was wondering if there is a way to
mitigate it in software. Limiting the max clock helped to reduce it, so I was
wondering if there could be some nice ideas for people too lazy or not wanting
to bother with replacing the laptop or whatever.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-01-05 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 10:11 [Bug 210993] New: Intel frequency scaling causes electrical noise on 10th gen CPUs bugzilla-daemon
2021-01-01 10:32 ` [Bug 210993] " bugzilla-daemon
2021-01-03 6:45 ` bugzilla-daemon
2021-01-04 19:54 ` bugzilla-daemon
2021-01-04 19:58 ` bugzilla-daemon
2021-01-04 21:01 ` bugzilla-daemon
2021-01-04 22:38 ` bugzilla-daemon
2021-01-04 23:20 ` bugzilla-daemon
2021-01-05 2:19 ` bugzilla-daemon
2021-01-05 8:00 ` bugzilla-daemon
2021-01-05 8:10 ` bugzilla-daemon [this message]
2021-04-22 13:23 ` bugzilla-daemon
2021-06-02 5:45 ` bugzilla-daemon
2021-06-16 7:26 ` bugzilla-daemon
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=bug-210993-137361-TEEYMjodt3@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@vger.kernel.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.