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: Mon, 04 Jan 2021 21:01:44 +0000 [thread overview]
Message-ID: <bug-210993-137361-OpwQMZByhM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210993-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210993
Francisco Jerez (currojerez@riseup.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |currojerez@riseup.net
--- Comment #5 from Francisco Jerez (currojerez@riseup.net) ---
O_o, that's really weird. I guess this could also be some sort of
electromagnetic interference (E.g. with your soundcard? Does the problem occur
with the loudspeakers turned off?), or an issue with your PSU.
The apparent frequency dropping below scaling_min_freq might be an artifact of
how the busy frequency of a CPU thread is calculated: It should approximate the
ratio of executed clock cycles to the time it spent in C0 state, which can
deviate from its actual working frequency if the processor enters and exits
some C1+ state repeatedly since the transition may have some significant
latency. According to your turbostat log the CPU cores that report a busy
frequency below scaling_min_freq seem to be handling quite a few interrupts
which is consistent with that explanation. It doesn't necessarily indicate a
power management bug.
Does disabling some specific idle state (e.g via
/sys/devices/system/cpu/cpu*/cpuidle/state*/disable) have any effect on the
noise?
--
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-04 21:02 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 [this message]
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
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-OpwQMZByhM@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.