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

From	Dirk Kostrewa <dirk.kostrewa@mailbox.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	2020-08-13 11:00 +0200
Message-ID	<ADhfz-30n-1@gated-at.bofh.it> (permalink)
References	(5 earlier) <ACWNP-7Cy-1@gated-at.bofh.it> <AD1kt-1I5-5@gated-at.bofh.it> <AD1ua-20T-7@gated-at.bofh.it> <Azhe9-3wS-5@gated-at.bofh.it> <AD1ua-20T-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Hi Salavatore,

I have kernel "linux-image-4.19.0-10-amd64/stable,now 4.19.132-1 amd64" 
installed, so it should already include the mentioned commit, if I 
understand correctly (I'm a bit confused by the two different version 
numbers used by Debian). I have also tried the most recent kernel 
"linux-image-5.6.0-0.bpo.2-amd64/buster-backports 5.6.14-2~bpo10+1 
amd64". For both kernels, I see the two kworker processes with high CPU 
load.

Regards,

Dirk.

Am 12.08.20 um 18:05 schrieb Salvatore Bonaccorso:
> Hi,
>
> Just commenting on the following:
>
> On Wed, Aug 12, 2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
> [...]
>> What puzzles me, is that I've observed these oddly behaving kworker
>> processes also with the 5.6 kernel that I've tried from the Buster Backports
>> repository.
> The mentioned commit, is included in the following upstream versions
> (relevant for Debian): v4.19.119 (so in buster), v5.6.8 (and so the
> buster-backports kernel), v5.7-rc3.
>
> Regards,
> Salvatore

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