From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 75A71C433DB for ; Tue, 5 Jan 2021 08:01:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 224DF2222A for ; Tue, 5 Jan 2021 08:01:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbhAEIB2 convert rfc822-to-8bit (ORCPT ); Tue, 5 Jan 2021 03:01:28 -0500 Received: from mail.kernel.org ([198.145.29.99]:38510 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726599AbhAEIB2 (ORCPT ); Tue, 5 Jan 2021 03:01:28 -0500 Received: by mail.kernel.org (Postfix) with ESMTPS id 2354822582 for ; Tue, 5 Jan 2021 08:00:48 +0000 (UTC) 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Power Management X-Bugzilla-Component: cpufreq X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: karolherbst@gmail.com X-Bugzilla-Status: NEEDINFO X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: linux-pm@vger.kernel.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.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.