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:00:47 +0000 [thread overview]
Message-ID: <bug-210993-137361-g2w3R7IjlF@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 #9 from Karol Herbst (karolherbst@gmail.com) ---
(In reply to Zhang Rui from comment #8)
> (In reply to Karol Herbst from comment #3)
> > Created attachment 294493 [details]
> > turbostat output
> >
> > first three data sets are "idle", next two are finger on the touchpad, last
> > ones are "idle" again.
> >
> > min clock set to 2.4GHz
>
> "Sadly the scaling_min_freq property is ignored outright and only matters as
> long as the CPU stays idle, but as long as one core gets some load, another
> one drops below scaling_min_freq"
>
> I didn't observe this from the turbostat output attached, because the system
> is idle.
> Can you please attach the turbostat output when the cpu frequency drops
> below scaling_min_freq?
it does in the output, just only one core per entry, and then only in the
entries in the middle.
e.g. line 122
--
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:01 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 [this message]
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-g2w3R7IjlF@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.