Hi Dirk,
On Fri, Sep 04, 2020 at 05:51:58PM +0200, Dirk Kostrewa wrote:
> Hi Salvatore,
>
> meanwhile, Dell has replaced the mainboard of my laptop, and after that,
> both the USB over-current kernel messages and the kworker processes with
> high CPU load are gone.
>
> Many thanks for caring
Hi Salvatore,
meanwhile, Dell has replaced the mainboard of my laptop, and after that,
both the USB over-current kernel messages and the kworker processes with
high CPU load are gone.
Many thanks for caring about my bug report!
Best regards,
Dirk.
Am 29.08.20 um 11:26 schrieb Salvatore
Hi Dirk,
Thanks for testing that.
On Sat, Aug 29, 2020 at 11:04:43AM +0200, Dirk Kostrewa wrote:
> Hi Salvatore,
>
> I have enabled the verbose debugging mode on the command line and have
> appended the first 5000 lines of the dmesg output to this e-mail, running
> the current kernel from the
Hi Salvatore,
I have enabled the verbose debugging mode on the command line and have
appended the first 5000 lines of the dmesg output to this e-mail,
running the current kernel from the Buster backports with the two
kworker processes with high CPU load present.
After that, I have applied
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
Hi Salvatore,
I just want to inform you that I've installed the recent kernel from the
Buster backports, 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1
(2020-07-30) x86_64 GNU/Linux, and I'm still seeing the two kworker
processes with high CPU load, probably related to the two USB ports
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
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
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
Hi Salvatore,
yesterday, I installed the kernel 5.6.0 from the Buster Backports and
saw again a kworker process with high CPU load.
Oddly, this morning, my laptop didn't boot, so I decided to do a fresh
install of Debian Buster 10.5.0 (image with non-free firmware because of
my wifi card) and
Hi Dirk,
On Tue, Aug 11, 2020 at 12:58:15PM +0200, Dirk Kostrewa wrote:
> Hi Salavatore,
>
> as an additional control, I have completely uninstalled the nvidia graphics
> driver and repeated the kworker observations using the nouveau graphics
> driver with the kernel 4.19.0-10-amd64. This time,
Hi Salavatore,
as an additional control, I have completely uninstalled the nvidia
graphics driver and repeated the kworker observations using the nouveau
graphics driver with the kernel 4.19.0-10-amd64. This time, there are
even two kworker processes constantly running with high CPU load:
$
Hi Salvatore,
I have removed the xorg.conf with the Nvidia graphics driver and any
nvidia-related *.conf files in /etc/modprobe.d/, and I have rebooted the
laptop. The following output should show, that only the default nouveau
driver is loaded:
# lsmod | grep nvidia
# lsmod | grep nouveau
Hi Salvatore,
thank you for taking care of this!
I first did the tracing for a few seconds, and I have appended the
compressed output "out.txt.gz", cut after line 5000, to this e-mail.
Since some "nvidia"-related processes also appear, I want to inform you
that I have an Optimus laptop where
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,
> >
> >
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
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,
17 matches
Mail list logo
