Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp1746526ybt; Thu, 2 Jul 2020 12:47:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxwGVfyO9fxSuLrHK9RaV1sOvRHrpjN0BJKY2ej735eQsF4HmIKHLol8SEcprReTYV7stLJ X-Received: by 2002:a17:906:4356:: with SMTP id z22mr12222185ejm.414.1593719247265; Thu, 02 Jul 2020 12:47:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593719247; cv=none; d=google.com; s=arc-20160816; b=twyQfoP1G8GYAt1tp/ltqu7M8/LvD/a+j80cbLZ2Bgoty8xBa3jlCWd4h7DEVyudPq vihLZ0K2x3uXDtS5l+jieRSLec8X0SGe0kDNM4oHehMf+EshgYLRJ0wa3hgk/GGhpQPm zdkjiT0KLLq69XMvcTGaGxW/DTb9AtNMsom8UdrjVU+i/1ghgBahLIdBSbt2aAPJotyO PPawZMpx2UnmA/Ud5lZ4dSbYE9aanJloe94Dm8sJ01mHCuZtJuSNNRAvxoydoEMbKosM i1zZAYNaVqU9kMyd8CqdPeuUOg+JOprsLI7sFtGHSyL4OsR0ALVD3s5UuKw1oq488sVV KnqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:to:from:date; bh=SD1obtSfpsAeiR0mgk0AAabEIMJmubjdJvQxYaEugJk=; b=ZDuKOS5+ZlgOml1gZyogN7C5jOj2fN9OsR6JmFWXS/YsII6zi3m9AtU7ynlGrUXkQk wOpXpBClDWxD3O63Cz7pC+MaEjIiCcoOU0oSoBjVu8BpsfQL1pI88UkIG+xa8kzumPi4 0upqHnxmQkOo0yja3wzgnMEsPZwx4oulyf6D/9mjy8CM/3Q/QniMALjz3y2qb/QAd6kW M/XF7j7hoTPSR+4MCQKvn5VFqnlvnMj5DDBwjgK0xUvSav7xS+yBW1Dr5ViFJL+Keuc1 rsXburGSj49kmCd4QSAls1OxQILXBsaviifhj3q88pLpXQKx7hMx+fYwNecLsI4qW/vW 6C1w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i3si6474277edr.555.2020.07.02.12.47.03; Thu, 02 Jul 2020 12:47:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726039AbgGBTqG (ORCPT + 99 others); Thu, 2 Jul 2020 15:46:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39972 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725937AbgGBTqG (ORCPT ); Thu, 2 Jul 2020 15:46:06 -0400 Received: from scorn.kernelslacker.org (scorn.kernelslacker.org [IPv6:2600:3c03:e000:2fb::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 50DCEC08C5C1 for ; Thu, 2 Jul 2020 12:46:06 -0700 (PDT) Received: from [2601:196:4600:6634:ae9e:17ff:feb7:72ca] (helo=wopr.kernelslacker.org) by scorn.kernelslacker.org with esmtp (Exim 4.92) (envelope-from ) id 1jr59k-0001eK-Uq; Thu, 02 Jul 2020 15:46:00 -0400 Received: by wopr.kernelslacker.org (Postfix, from userid 1026) id 9F0DE56011F; Thu, 2 Jul 2020 15:46:00 -0400 (EDT) Date: Thu, 2 Jul 2020 15:46:00 -0400 From: Dave Jones To: Linux Kernel , peterz@infradead.org, mgorman@techsingularity.net, mingo@kernel.org, Linus Torvalds Subject: Re: weird loadavg on idle machine post 5.7 Message-ID: <20200702194600.GA28941@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Linux Kernel , peterz@infradead.org, mgorman@techsingularity.net, mingo@kernel.org, Linus Torvalds References: <20200702171548.GA11813@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200702171548.GA11813@codemonkey.org.uk> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Note: SpamAssassin invocation failed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 02, 2020 at 01:15:48PM -0400, Dave Jones wrote: > When I upgraded my firewall to 5.7-rc2 I noticed that on a mostly > idle machine (that usually sees loadavg hover in the 0.xx range) > that it was consistently above 1.00 even when there was nothing running. > All that perf showed was the kernel was spending time in the idle loop > (and running perf). Unfortunate typo there, I meant 5.8-rc2, and just confirmed the bug persists in 5.8-rc3. Dave