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


Groups > linux.debian.kernel > #67888

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

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 2020-08-28 16:40 +0200
Message-ID <AINHQ-8h7-1@gated-at.bofh.it> (permalink)
References (5 earlier) <ACWNP-7Cy-1@gated-at.bofh.it> <Azhe9-3wS-5@gated-at.bofh.it> <AD1kt-1I5-5@gated-at.bofh.it> <Azhe9-3wS-5@gated-at.bofh.it> <AD1kt-1I5-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

hi Dirk,

On Wed, Aug 12, 2020 at 05:53:57PM +0200, Dirk Kostrewa wrote:
> Hi Salvatore,
> 
> I just found out, that if none of the two USB ports is connected, there are
> two kworker processes with permanently high CPU load, if one USB port is
> connected and the other not, there is one such kworker process, and if both
> USB ports are connected, there is no kworker process with high CPU load.
> I think, this supports your suspicion that these kworker processes are
> connected with the overcurrent condition for both USB ports that I also see
> in the dmesg output.
> 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 kernel parameter variant did not work correctly as there are no
dynamic debug output afaics (the double quotes seem to placed in the
wrong place), please just try the setting at runtime instead:

# echo 'file drivers/usb/* +p;' > /sys/kernel/debug/dynamic_debug/control

What I was meaning is (and this is confirmed if you see the issue
issue as well with the more recent kernels), that the specified commit
actually uncovers the issue present possibly with the HW.

Similarly to you someone else, where in known case with faulty HW,
reported the following issue upstream:

https://lore.kernel.org/lkml/20200720083956.GA4074@dhcp22.suse.cz/

I would like to see if we can collect as much information as possible
and possibly crosscheck with upstream.

If build the kernel with the attached patch (that is with the commit
wich is supsected to uncover the issue), does then the issue goes
away?

You can folllow the quide in
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
for the "simple patching and building" and quickly chekcing a patch.

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