Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #67659

Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Salvatore Bonaccorso <carnil@debian.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load
Date Sun, 02 Aug 2020 18:30:01 +0200
Message-ID <Azp21-8cM-1@gated-at.bofh.it> (permalink)
References <Azhe9-3wS-5@gated-at.bofh.it> <Azmxb-6Cd-7@gated-at.bofh.it> <Azhe9-3wS-5@gated-at.bofh.it> <Azmxb-6Cd-7@gated-at.bofh.it>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Sun Aug 2 16:27:08 2020
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score -0.5
Reply-To Salvatore Bonaccorso <carnil@debian.org>, 966703@bugs.debian.org
Original-Sender Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc Debian Kernel Team <debian-kernel@lists.debian.org>
X-Debian-Pr-Message followup 966703
X-Debian-Pr-Package src:linux
X-Debian-Pr-Keywords moreinfo
X-Debian-Pr-Source linux
X-Spam-Bayes score:0.0000 Tokens: new, 8; hammy, 150; neutral, 173; spammy, 0. spammytokens: hammytokens:0.000-+--H*F:U*carnil, 0.000-+--H*r:TLS1_3, 0.000-+--Hx-spam-relays-external:eldamar, 0.000-+--UD:kernel.org, 0.000-+--Hx-spam-relays-external:sk:80-218-
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=CxCA1wiSNMgEnQUgvFtabS43yHU2D78wdoIqOIm1I6E=; b=OxlD7TEUYPlb9uUM6jzo1igCm/DKuqgEXgJ9QRz8nZJvD7uGeOBQp22a1X1WWZ+Fml L1F52+zjkKgFfbKH/J28ZmMOpWf8IEcEkWbDVnYFbUmn1aDq8144O8Y70d5DegUgmnQZ sLiP2AYRa/w0Ap39Dy7yJKqte08EY64Cb3i3d6cW5PXjPs3ahpj7eBo4dHNHp+ZvVLR5 tj4YABl1M3REGNfFyFPwDeJKsCth7vAJre3R8fHKRltuoRQBtJulwVTEBphU4sRwDnwI UkwjZB7ofBL0E/3iuuQi/CM+yRT6jutc+Zw+hwFO8o9nVXmKQr3t+8Zl6OiTruzzROUJ YDVA==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=CxCA1wiSNMgEnQUgvFtabS43yHU2D78wdoIqOIm1I6E=; b=qkAk3rsXZKLDIwL1fIYISZqWVYt3Vc1YVPQHNhfedGFFaI9ZbLOcxQydUIMEyK3M1N dMHpxw9S8lPTonii4wr9Lu6HXzcVHwAVz/z6F7dRmfjsoOnRkoeEYKz6BnsYtMkSxLK+ McuhOVKVJPxdHfw7GEd0u8HLVkZTut3yyaa88yvke7C2F12nceqKfb41nyKw/VcYRUjv XSmX5FXwVNN6V4eTM1PoESIrc2IneYjZ5hVgmIpyZS8omBIqNRd7mTcxzWfBqT3Kajqu USNIcm0U/F5jJkTkJJxp6w+HKLWclS6k+AwywL5rcYqa+HUMrtoA8djuu8aYe/Oll/ox DvfQ==
X-Gm-Message-State AOAM532n4j177mq/EGTJtqxmmurU/f6XnvTGyQEWnhQTVqlN5M1yt90M 0faW0/328BnucLqFq+Xqoazmh6fOoUs=
X-Google-SMTP-Source ABdhPJw1kup1bYTGNF5Vx4dIj80dQ9Zc167G4C3rbocrbLLV7DWiToXaz2AKA60UIKM1mbD6JzzRlA==
X-Received by 2002:a7b:c7d5:: with SMTP id z21mr12767946wmk.145.1596385364212; Sun, 02 Aug 2020 09:22:44 -0700 (PDT)
Sender robomod@news.nic.it
MIME-Version 1.0
Content-Type text/plain; charset=iso-8859-1
Content-Disposition inline
Content-Transfer-Encoding 8bit
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1616636
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 67
Organization linux.* mail to news gateway
X-Original-Date Sun, 2 Aug 2020 18:22:42 +0200
X-Original-Message-ID <20200802162242.GA876319@eldamar.local>
X-Original-References <7e21da22-83a7-665b-817d-bdf99867de70@mailbox.org> <20200802134406.GA863200@eldamar.local> <7e21da22-83a7-665b-817d-bdf99867de70@mailbox.org> <20200802134406.GA863200@eldamar.local>
X-Original-Sender Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Xref csiph.com linux.debian.bugs.dist:1020167 linux.debian.kernel:67659

Cross-posted to 2 groups.

Show key headers only | View raw


Hi Dirk,

On Sun, Aug 02, 2020 at 03:44:09PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi Dirk
> 
> On Sun, Aug 02, 2020 at 10:00:27AM +0200, Dirk Kostrewa wrote:
> > Package: src:linux
> > Version: 4.19.132-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > after booting the kernel 4.19.0-10-amd64, there is a kworker process running
> > with a permanent high CPU load of almost 90% as reported by the "top"
> > command:
> > 
> > $ top
> > top - 09:48:19 up 0 min,  4 users,  load average: 1.91, 0.58, 0.20
> > Tasks: 218 total,   2 running, 216 sleeping,   0 stopped,   0 zombie
> > %Cpu(s):  0.8 us, 12.4 sy,  0.0 ni, 84.5 id,  0.0 wa,  0.0 hi,  2.3 si,  0.0
> > st
> > MiB Mem :  15889.4 total,  14173.1 free,    889.3 used,    827.0 buff/cache
> > MiB Swap:      0.0 total,      0.0 free,      0.0 used.  14677.7 avail Mem
> > 
> >   PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM TIME+ COMMAND
> >    64 root      20   0       0      0      0 R  86.7   0.0 0:47.41
> > kworker/0:2+pm
> >     9 root      20   0       0      0      0 S  20.0   0.0 0:08.84
> > ksoftirqd/0
> >   364 root     -51   0       0      0      0 S   6.7   0.0 0:00.50
> > irq/126-nvidia
> >  1177 dirk      20   0 2921696 122848  94268 S   6.7   0.8 0:02.23 kwin_x11
> >     1 root      20   0  169652  10280   7740 S   0.0   0.1 0:01.56 systemd
> >     2 root      20   0       0      0      0 S   0.0   0.0 0:00.00 kthreadd
> > ...
> > 
> > The expected result after booting the kernel 4.19.0-10-amd64 is a kworker
> > process with a CPU load close to 0%.
> > 
> > As a control, booting the previous kernel 4.19.0-9-amd64 does not show a
> > high CPU load for the kworker process. Instead, the kworker CPU load
> > reported by the "top" command is 0.0%.
> > 
> > Therefore, I suspect a bug in the kernel 4.19.0-10-amd64.
> > 
> > Neither "dmesg" nor "journalctl -b" show any messages containing "kworker".
> > 
> > I am using Debian/GNU Linux 10.5 with kernel 4.19.0-10-amd64 and libc6:amd64
> > 2.28-10.
> > 
> > If you need more information, I would be happy to provide it.
> 
> To find out what could be the cause, could you have a look at
> https://www.kernel.org/doc/html/latest/core-api/workqueue.html#debugging
> this could help determining isolating why the kworker goes crazy.

Please as well to the above one additional thing: Can you reproduce
the issue when the kernel does not get tained? So without loading the
propriertary, out-of-tree modules.

This is particularly important if the issue can be tracked down, found
in upstream and needs to be reported upstream.

Regards,
Salvatore

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-02 15:50 +0200
  Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-02 18:30 +0200
    Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-11 21:30 +0200
      Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Dirk Kostrewa <dirk.kostrewa@mailbox.org> - 2020-08-12 13:10 +0200
        Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Dirk Kostrewa <dirk.kostrewa@mailbox.org> - 2020-08-12 18:00 +0200
          Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-12 18:10 +0200
            Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Dirk Kostrewa <dirk.kostrewa@mailbox.org> - 2020-08-13 11:00 +0200
            Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Dirk Kostrewa <dirk.kostrewa@mailbox.org> - 2020-08-21 11:40 +0200
          Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-28 16:40 +0200
            Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-08-29 11:40 +0200
              Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Dirk Kostrewa <dirk.kostrewa@mailbox.org> - 2020-09-04 18:00 +0200
                Bug#966703: linux-image-4.19.0-10-amd64: kworker process with permanent high CPU load Salvatore Bonaccorso <carnil@debian.org> - 2020-09-04 19:20 +0200

csiph-web