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


Groups > linux.debian.kernel > #67658

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

Path csiph.com!news.neodome.net!weretis.net!feeder7.news.weretis.net!usenet.goja.nl.eu.org!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 15:50:02 +0200
Message-ID <Azmxb-6Cd-7@gated-at.bofh.it> (permalink)
References <Azhe9-3wS-5@gated-at.bofh.it> <Azhe9-3wS-5@gated-at.bofh.it>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Sun Aug 2 13:48: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-Source linux
X-Spam-Bayes score:0.0000 Tokens: new, 21; hammy, 150; neutral, 132; 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=TvoBBhlTBOX/KQ0Kdzw8oy2zc5ZhlBAZvU0/rrkDYjA=; b=vVuECziMpMouCurs0F2vcHUZK5+cjJXuer5Oo0oJB26Zi+2t5xhbp4HG0BTgQYmf5U 8rGCiiDcMrNLuCfFq41fdhK/WbeuWpRUMLoQt8He9qrfGGKoXPSkMDDRNEpQlMhpUFeO krCKDY71SfAJa1m7d+RnLPu0foZcQTxAra/lMoKi3fUD4HZ92Ao/TQ6Xyu1u8nBU00LZ m3jCXodORA2LtOxYpE3KzEg7dIrZW6jUOoSanuMpT22dQ/k3Kv3oa/fWESJoPXOrTOoA TiPORlw8WQSnW1dZcKHfGqHpp25hzHUSVjrz7JKYGYtbHy7rUoynb6Jiyybn87fEIzDJ rFxg==
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=TvoBBhlTBOX/KQ0Kdzw8oy2zc5ZhlBAZvU0/rrkDYjA=; b=NY0a8p/rO6rxO20jrHIjDOcCctp5D0YBTEhSdv6zI6zF7YcYlnv2/md65EGo9TnBv2 qjjJwJJ0BK/KHO9mnRe76zjJVHxymWnO1LVdGq5yOBFsk29rZee84RUVi1Pcf1qbLb0b uULcf1sqopgDvlfSe9aNR4nywgppyXV2qx2wf3r5mxOa5xdgX2u4C9PBnv0Mu0hH9471 jG8u/Me1Pi+3S1ScEKyvDltUchuhdiOq2CrYNJ0FF3bO3/hfYusUWmjed/VZpxqIi8a7 aaqMAX/RPYAb6OYruq0NH+2WKh6Pos2cNewdcKt0kS13Ty0PSKRTBekX73Tk70esdZcU E1hA==
X-Gm-Message-State AOAM531X5I4on068qajcRwbK5omIE86habNA/GR6g2ThpESNCreSFJs0 JOxbMQR+eGmhQ3XOwectgBnsYRYBnK4=
X-Google-SMTP-Source ABdhPJzSw9E0Cp7m142uE5IB9HQ9ZQa5we7M8e23e0Gggy7JJT9NLsrcdUtKjr4fuVwLH1D0QbYwFg==
X-Received by 2002:a05:600c:2146:: with SMTP id v6mr11754606wml.87.1596375849269; Sun, 02 Aug 2020 06:44:09 -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/1616612
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 57
Organization linux.* mail to news gateway
X-Original-Date Sun, 2 Aug 2020 15:44:06 +0200
X-Original-Message-ID <20200802134406.GA863200@eldamar.local>
X-Original-References <7e21da22-83a7-665b-817d-bdf99867de70@mailbox.org> <7e21da22-83a7-665b-817d-bdf99867de70@mailbox.org>
X-Original-Sender Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com>
Xref csiph.com linux.debian.bugs.dist:1020146 linux.debian.kernel:67658

Cross-posted to 2 groups.

Show key headers only | View raw


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.

Regards,
Salvatore

Back to linux.debian.kernel | Previous | NextNext 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