Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp361295ybt; Wed, 8 Jul 2020 01:37:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBchxjKM69yBxHAbU4ONLWO5+Wx/1puSsY7YBQedEPFmNZ0wR8KXByWFKkKAraaXv53J6W X-Received: by 2002:aa7:c887:: with SMTP id p7mr52126873eds.240.1594197431214; Wed, 08 Jul 2020 01:37:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594197431; cv=none; d=google.com; s=arc-20160816; b=O/a84q4hJGgzL3YQq/F2TbprGYgOl3Z2JIY1iwtKmzGIcij+wRtbFjP4lp0WuHSmRK eO+fGOfiJT2eaSdR0u5Cf9K1B0YZ3jup5L9kc4SG5COnyvRFxka69QGgEwlF2VeBrFL8 uSiG+i+YZ8fKpVqLPidpp0SqMq7l0HAhCWy9Xjr2QIgGdglmSAJOX5UlRVWB93l7pczd u2WcNFBwAAi+UZxRsOrKKJrD2sFgfYGn3X8Rs9ylqbwoOkbM1xtC9+o8pOYHHjkjuvCu GolS2wrcO67YtdgvFn+V3O5Vy2buKwPBSaWXEL+JehIxUzqzdkZdcS6YqzAMVgVDEQoe Auzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=h4SPVfRZuCVSbYgatd3ieJt++U37sA6cj7z9VhNAanU=; b=nDViszELAuzB7QabOQD7ZAZzS/zWqNDRo0jBLsR3issPjqhgcT96uDOPARyTOMfgZG 3ZetwMY6RGDpHMQcLJH/68LR8/bWobMy4ggJNYSB9OTDCW/cF5A4zmOu1YiTE0+7teLe RowrTyuIhRelUDMdKsA0Ir6ONl67She/Aa/REgj/5Xo/PdDfENjv/oDsTzUy+TKubOUM cwtixtZNuYs+pCWclvqGRD91g2x9PGeknt+BmSgwdWtUob/SFRxfS1ykstHH4jAx685M dYUpDhonXVDkK/n8FeMC/0mj1XF0zdNxTto97GhFDRcf5+cOeLYFNH/+q13OubjTC530 A+jg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PNWOruLc; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k17si17869255edk.3.2020.07.08.01.36.48; Wed, 08 Jul 2020 01:37:11 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PNWOruLc; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728009AbgGHIfE (ORCPT + 99 others); Wed, 8 Jul 2020 04:35:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726385AbgGHIfD (ORCPT ); Wed, 8 Jul 2020 04:35:03 -0400 Received: from mail-vs1-xe44.google.com (mail-vs1-xe44.google.com [IPv6:2607:f8b0:4864:20::e44]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 71401C08C5DC for ; Wed, 8 Jul 2020 01:35:03 -0700 (PDT) Received: by mail-vs1-xe44.google.com with SMTP id x205so3803242vsc.11 for ; Wed, 08 Jul 2020 01:35:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=h4SPVfRZuCVSbYgatd3ieJt++U37sA6cj7z9VhNAanU=; b=PNWOruLcNlYep0iJV4gN/ef908gpH1uqJoYvaHKCSlQhSZwb7ICfq2r3tSSpVD9tBG 9f0vR4Twkq+KA9v34Kz+1Y8TZ8/tBoeWJMZQBlgE6UGGCj44R4S2Zl7jpduUANo9LjHq PFw/taec8weGxXV0F2lAC3U4/6JVGw/NgwfG4klDtI2YEU+zGe7nP0gy4YPPg8bbLwn4 cD5CX2qnF0cOvHJG1bYweINc6pnL1YCQxZZBYrCTakfTE9aMCsk67i2M1kVB/LFWhxDR vs41OAIPHBwpKvYOZBwJEO9QaBrz7ve8tnxgHGuPzQdJjX4+Qn497RyXrRNpXqPBfBu7 mUlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=h4SPVfRZuCVSbYgatd3ieJt++U37sA6cj7z9VhNAanU=; b=Xu/CzNIeCCr9fnDAJAVE4CiY5J9C/z7h9OKWcEvLP2JY7w97FI8jZmC/2MZUlJO+K3 kbwh72tV1R0SwnJEsbBrZWMyroRN5w3jm2bBl3HyasgRUxAB2QhxeqM+RO11u1qznxc8 TA3PFQCxO0VpighaQxwoTbX3bI1mSv9EtW58oHPIhxtVkPjYmqWxbZxlyY+HeU26dpAd L0cM7Hdh6iLb5xigly6Tsh5fv4HKNMFg1o+cAAqmzeClNBQqcTwgTGRCLWODAvgz6ozm awlgYCsA84muvhC/JQfK8qAfqWj0jDUzDYCYNoH4laGig7rz68f96UNu21IVXcYJ1R1A An0A== X-Gm-Message-State: AOAM533/qn4t/ccvCPoqSQRQRAfZn+EJD1TDbQMhDzD0ZjriNw0QixB9 BN0+PTiRp3l578OFNVnzEMjB0SBp83MRe0COz2skYA== X-Received: by 2002:a05:6102:390:: with SMTP id m16mr25932066vsq.55.1594197302473; Wed, 08 Jul 2020 01:35:02 -0700 (PDT) MIME-Version: 1.0 References: <91805D0F-2D74-4EA3-A2D7-13E4FBBEAB51@gmail.com> <6AD52867-83C1-4C6C-A0AE-4DE0D6C16310@gmail.com> <20200708070912.GA351187@kroah.com> In-Reply-To: <20200708070912.GA351187@kroah.com> From: Martin Zaharinov Date: Wed, 8 Jul 2020 11:34:52 +0300 Message-ID: Subject: Re: Bug Report High CPU Usage events_power_efficient To: Greg KH Cc: "linux-kernel@vger kernel. org" , Florian Westphal , Eric Dumazet Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Yes i search but not find any information. And write hear to help if any have same problem or any of you have idea from where is comme this problem. If need more debug i will only write how to get more information. Martin =D0=9D=D0=B0 =D1=81=D1=80, 8.07.2020 =D0=B3. =D0=B2 10:09 Greg KH =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0: > > On Wed, Jul 08, 2020 at 09:50:49AM +0300, Martin Zaharinov wrote: > > Add Greg , Florian, Eric to this bug > > > > > On 7 Jul 2020, at 22:54, Martin Zaharinov wrote: > > > > > > And this is log from /sys/kernel/debug/tracing/trace > > > > > > > > > # entries-in-buffer/entries-written: 32410/32410 #P:64 > > > # > > > # _-----=3D> irqs-off > > > # / _----=3D> need-resched > > > # | / _---=3D> hardirq/softirq > > > # || / _--=3D> preempt-depth > > > # ||| / delay > > > # TASK-PID CPU# |||| TIMESTAMP FUNCTION > > > # | | | |||| | | > > > <...>-57259 [005] .... 29619.680698: workqueue_execute_star= t: work struct 00000000ef22e4b8: function gc_worker [nf_conntrack] > > > <...>-57259 [005] .... 29623.811407: workqueue_execute_end:= work struct 00000000ef22e4b8: function gc_worker [nf_conntrack] > > > <...>-57259 [005] .... 29623.811410: workqueue_execute_star= t: work struct 0000000000aeec55: function fb_flashcursor > > > <...>-57259 [005] .... 29623.811421: workqueue_execute_end:= work struct 0000000000aeec55: function fb_flashcursor > > > <...>-57259 [005] .... 29623.811422: workqueue_execute_star= t: work struct 00000000a6d382bb: function vmstat_update > > > <...>-57259 [005] .... 29623.811435: workqueue_execute_end:= work struct 00000000a6d382bb: function vmstat_update > > > > > >> On 7 Jul 2020, at 22:44, Martin Zaharinov wrote= : > > >> > > >> the problem is hear with kernel 5.7.7 > > >> > > >> last work kernel without this problem is 5.6.7 > > >> > > >> hear is more info: > > >> > > >> cat /proc/57259/stack > > >> root@megacableamarilis:~# cat /proc/57259/stack > > >> [<0>] gc_worker+0x1be/0x380 [nf_conntrack] > > >> [<0>] process_one_work+0x1bc/0x3b0 > > >> [<0>] worker_thread+0x4d/0x460 > > >> [<0>] kthread+0x10d/0x130 > > >> [<0>] ret_from_fork+0x1f/0x30 > > >> > > >> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ C= OMMAND 57259 root 28 0 0 0 = 0 R 69.8 0.0 82:42.14 kworker/5:2+events_power_efficient > > >> 32 root 21 0 0 0 0 R 31.0 0.0 87:06.33 ks= oftirqd/4 > > >> > > >> > > >> Please help to fix this problem > > >> > > >>> On 22 Apr 2020, at 15:55, Martin Zaharinov wro= te: > > >>> > > >>> Hello Qian and Greg > > >>> With latest 5.6.x kernel have problem with events_power_efficient 2= 8488 root 28 0 0 0 0 R 95.5 0.0 101:38.19 kworker= /2:1+events_power_efficient Process start to load machine after 3-4 hour an= d load not stop only reboot machine remove process . Server runing on AMD E= PIC CPU 2x 7301 32Gb Ram Have 2 x 10G card Intel when machine load over 1G = traffic machine locked and only restart fix problem to next load . After mo= ve traffic and server stop load process still hear and load server ? > > >>> And after reboot process move to other core . > > Have you used 'git bisect' to try to find the offending commit? > > Without that, it's going to be hard to help you out here. > > thanks, > > greg k-h