Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1875121pxk; Tue, 1 Sep 2020 09:46:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJza9laefJhKjTa9a/IgnjBuaFCPe3SIWMnaKKvMsy2IqYb7eLogLUY/Mm+nyOGqDv/flw90 X-Received: by 2002:aa7:cb05:: with SMTP id s5mr2495567edt.212.1598978796113; Tue, 01 Sep 2020 09:46:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598978796; cv=none; d=google.com; s=arc-20160816; b=JrVr2kCxkVFL17odqyf+AA1axyxd7VEDcc20W+8U85sQK1hGKUDBsQ4Ry23HD+ut4C gHLquirukzL30RxvDNj9tlKrSnIfBhlNbVhEAaJjr6b+5eH25hW3ANNxdGphtdvUzzw0 GB8tAt/8tmDFcQ0G1b1iBaTqYcwn58H9wVlyZ3YMEBrHl3jmviFdL4JtfNGMiG9zPriy 9NrxhdjYq1IORTLkw/1vqKFsuHykyzgwSKOhO+y0fmSu5cR6CEh7XxsVRyn46m3pwgAT jpNV58A2VeoKC/tbjMs8ah1CxnPLU0yn2noULVS7f4QheYiWmiS2TJl/M0QFPn+ajqWk /M7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=/F+dpzMxtIfO3mX0xer3k+pT4UzY/eNV+trQ3j3qBwo=; b=FBRQt96Y2Cxypca7JnnvbTJOKMxzRLXasxFIOSym/KTy9o5KhQkAo44pFvj31FuDp8 lbhXwxRAtX1PDyI2M+hn5Y0Ol91OL5rnk8DRc741qFzR1L0JcApFXBJQ4ECIGvnt2dfp 7JHwYqYFZ1oXgChhMKDA+9HJZvFXM15VvsyIUo/7YuTHz5fEfcA/NZTiaTIk5eLRQhrG nxrCpH/5L0Ixnf5FNXv70kvNFkCxwQWbUHR9FoyBiitNNXZSsw51bUUtQJqHZW4GmMf+ 2bje/tf5hRB9XG211GL4/uRIp4NUJWgsKnfNOy2De62U9oT9GO5ryr5zMmX/fap/Jmbc BQZA== 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 jw7si813468ejb.53.2020.09.01.09.46.13; Tue, 01 Sep 2020 09:46:36 -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 S1730763AbgIAQpY (ORCPT + 99 others); Tue, 1 Sep 2020 12:45:24 -0400 Received: from mx2.suse.de ([195.135.220.15]:37340 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730014AbgIAP1a (ORCPT ); Tue, 1 Sep 2020 11:27:30 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 5AA32ACC3; Tue, 1 Sep 2020 15:27:29 +0000 (UTC) Date: Tue, 1 Sep 2020 17:27:28 +0200 From: Michal Hocko To: Mathias Nyman Cc: Alan Stern , Salvatore Bonaccorso , LKML , Greg KH , linux-usb@vger.kernel.org, "Rafael J. Wysocki" , Dirk Kostrewa Subject: Re: kworker/0:3+pm hogging CPU Message-ID: <20200901152728.GI16650@dhcp22.suse.cz> References: <20200720173807.GJ1228057@rowland.harvard.edu> <20200720174530.GB4061@dhcp22.suse.cz> <20200720174812.GK1228057@rowland.harvard.edu> <20200720181605.GC4061@dhcp22.suse.cz> <20200720200243.GA1244989@rowland.harvard.edu> <20200721055917.GD4061@dhcp22.suse.cz> <20200721143325.GB1272082@rowland.harvard.edu> <20200829095003.GA2446485@eldamar.local> <20200829155949.GA499295@rowland.harvard.edu> <38dfdef4-f9ab-1755-8418-2285d843af86@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <38dfdef4-f9ab-1755-8418-2285d843af86@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 31-08-20 14:37:10, Mathias Nyman wrote: [...] > I can't come up with any good solution to this right now. > Only bad ideas such as > a. Add a sleep to the over-current case, > doesn't solve anything else than the ~100% cpu hogging part of the problem This sounds like a better thing from the user space point of view. I do not have any insight on what kind of other side effects this might have so I didn't dare to try that on my piece of (broken) HW. I do not see the problem all the time and I plan to replace it soon anyway. Considering that tweaking the power management helps maybe that could be done automagically after many consecutive failures. Just my 2c -- Michal Hocko SUSE Labs