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.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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 751E4C433E1 for ; Tue, 21 Jul 2020 16:00:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4E03820720 for ; Tue, 21 Jul 2020 16:00:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1595347231; bh=CqQqYVAMtRWE9ODROSJ5N+xk75ur0i/PkCKJx7AicrI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=LyDbkTdxkm00i9y9Z2FpkBkztgZTAke/5/xIf2ukRDE7NX2a4ikiIuI21O2WPNKqN bGfrY5Ii69y1xPXflIkm2LNJ2LLIUGFGMP3oSYhacnfz8nGfOhh2bloOsEyRI+ruuJ n8Npp0QjE6kshyP3z3yGoTY16whAXnqmhCYBiWJM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729577AbgGUQAa (ORCPT ); Tue, 21 Jul 2020 12:00:30 -0400 Received: from mail-wm1-f44.google.com ([209.85.128.44]:52664 "EHLO mail-wm1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726892AbgGUQA3 (ORCPT ); Tue, 21 Jul 2020 12:00:29 -0400 Received: by mail-wm1-f44.google.com with SMTP id q15so3351135wmj.2; Tue, 21 Jul 2020 09:00:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Kj4rsz080Snn4B9MG3ZbTEom1EbAEYgUHjT0erERj2Q=; b=MsoC2nrwA9QFN2TrodngwqSSW83ssVxsL8z4dTOdESvejPa6Ulro/x0ajMDeryahrQ gzZlUF53fkx4LGyXYyxmX9fLoV2jA4iyVZva5/b0ZeSSWImYImwAPU5v/FgwNCFYBHwZ qjxuEkWvyez+mCrhW3412vMF28PV9cLPtXsQNmOjN+kcjKrjZ1dlCbDHWWwM4Ru10rYI uB1Pjyt9aRNtTZCIxJ02QVQi140T0M6vnHT/8Yw4py41AhHUipL/W4efCSPVeZQ6DY6u DNln2uPv43FCfeWJgBGBM2tDY4stueEJOl8Y3sebVNHDhsSnoIhzLT+UPBOcQF31wwie CNXg== X-Gm-Message-State: AOAM533mNzEoTeGbQsTu+hJmb+dfDxf52ai7n2xaMMKywptbnYnemMNN 1A/GAtmzgB0zy1V6EkTOAK4= X-Google-Smtp-Source: ABdhPJziu+Xxu9YdgzKr7PT4T+W9SMer6L/whdz53Wdb7MYjUO3T40Yx4hEbcMOQz3ZpfMz9J0OH2A== X-Received: by 2002:a1c:65d5:: with SMTP id z204mr4602923wmb.15.1595347227554; Tue, 21 Jul 2020 09:00:27 -0700 (PDT) Received: from localhost (ip-37-188-169-187.eurotel.cz. [37.188.169.187]) by smtp.gmail.com with ESMTPSA id s15sm4234729wmj.41.2020.07.21.09.00.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Jul 2020 09:00:26 -0700 (PDT) Date: Tue, 21 Jul 2020 18:00:25 +0200 From: Michal Hocko To: Alan Stern Cc: LKML , Greg KH , linux-usb@vger.kernel.org, "Rafael J. Wysocki" Subject: Re: kworker/0:3+pm hogging CPU Message-ID: <20200721160025.GP4061@dhcp22.suse.cz> References: <20200720143213.GJ4074@dhcp22.suse.cz> <20200720151255.GE1228057@rowland.harvard.edu> <20200720163355.GA4061@dhcp22.suse.cz> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200721143325.GB1272082@rowland.harvard.edu> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 21-07-20 10:33:25, Alan Stern wrote: [...] Thanks a lot for your analysis. The laptop is slowly dying so this can be related. > So yes, this looks like a hardware design error. Turning off > autosuspend by writing to the sysfs power/control file is probably the > best way to handle the problem. I can use that workaround. But it seems that this also prevents me from suspending the maching into RAM with PM: Some devices failed to suspend, or early wake event detected :/ If there is any workaround for that then I would be really happy but considering the overal state of the machine I suspect this is not the case. Thanks again for your great help! -- Michal Hocko SUSE Labs