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

Groups > linux.debian.kernel > #91489 > unrolled thread

Bug#1121192: kworker: Events_unbound, kworker processes, continually using CPU.

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1121192: kworker: Events_unbound, kworker processes, continually using CPU. ben.75@bmg7.com - 2026-02-28 16:30 +0100
    Bug#1121192: kworker: Events_unbound, kworker processes, continually using CPU. Uwe Kleine-König <ukleinek@debian.org> - 2026-03-02 10:10 +0100
      Bug#1121192: kworker: Events_unbound, kworker processes, continually using CPU. ben.75@bmg7.com - 2026-03-03 03:50 +0100

#91489 — Bug#1121192: kworker: Events_unbound, kworker processes, continually using CPU.

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

Friendly follow up on this bug.

I have been trying several different configurations and they all have 
there own set of problems.

Nvidia  + wayland = Several apps act weird, Spectacle breaks depending 
on which app is open.

Nvidia + X11 = works good except for when waking the screens from sleep. 
I get a black screen with mouse cursor. I can see when move over the 
password box because the cursor changes, I can type in the password and 
usually login. Sometimes it does lock up and I have to do hard reboot. 
This is a Kwin + X11 problem but from what I read its not going to be 
fixed since they are only focusing on Wayland.

Nouveau + Wayland = same as original problem

I did update the firmware from the back-ports and it fixed the missing 
firmware errors listed earlier, but I still get this "kernel: nouveau 
0000:01:00.0: drm: Disabling PCI power management to avoid bug"


Can I get an update on this.

Regards,

Benjamin

[toc] | [next] | [standalone]

#91505

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

Hello Ben,

On Sat, Feb 28, 2026 at 09:20:57AM -0600, ben.75@bmg7.com wrote:
> I have been trying several different configurations and they all have there
> own set of problems.
> 
> Nvidia  + wayland = Several apps act weird, Spectacle breaks depending on
> which app is open.
> 
> Nvidia + X11 = works good except for when waking the screens from sleep. I
> get a black screen with mouse cursor. I can see when move over the password
> box because the cursor changes, I can type in the password and usually
> login. Sometimes it does lock up and I have to do hard reboot. This is a
> Kwin + X11 problem but from what I read its not going to be fixed since they
> are only focusing on Wayland.

The Nvidia parts above only prove that your hardware is probably ok. As
the driver is closed source, there isn't much more we can learn or do
about it.

> Nouveau + Wayland = same as original problem

original problem = kworker threads using CPU? That's nothing I can act
upon---as describe in my earlier mail.
 
> I did update the firmware from the back-ports and it fixed the missing
> firmware errors listed earlier, but I still get this "kernel: nouveau
> 0000:01:00.0: drm: Disabling PCI power management to avoid bug"

The bug mentioned here is described in more detail at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/nouveau/nouveau_drm.c?id=11439c4635edd669ae435eec308f4ab8a0804808#n800

With the nvidia driver that's maybe the issue that you describe above
where on returning from sleep you get black screens. So you have 3
options to go on:

 - Stay on nouveau and live with PCI power management being disabled
 - Stay on nvidia (or patch nouveau to enable PM) and live with the
   black screens on resume
 - Work on the problem and find a better solution

For the 3rd option it's most probably you who would have to do the work.
Maybe upstream is interested and could help you, the Debian kernel team
cannot. Please contact upstream directly then.

Best regards
Uwe

[toc] | [prev] | [next] | [standalone]

#91509

Hi,

Will open a bug report with nouveau to see if they can help me 
troubleshoot this more.

Best regards

Benjamin

On 3/2/26 02:57, Uwe Kleine-König wrote:
> Hello Ben,
>
> On Sat, Feb 28, 2026 at 09:20:57AM -0600, ben.75@bmg7.com wrote:
>> I have been trying several different configurations and they all have there
>> own set of problems.
>>
>> Nvidia  + wayland = Several apps act weird, Spectacle breaks depending on
>> which app is open.
>>
>> Nvidia + X11 = works good except for when waking the screens from sleep. I
>> get a black screen with mouse cursor. I can see when move over the password
>> box because the cursor changes, I can type in the password and usually
>> login. Sometimes it does lock up and I have to do hard reboot. This is a
>> Kwin + X11 problem but from what I read its not going to be fixed since they
>> are only focusing on Wayland.
> The Nvidia parts above only prove that your hardware is probably ok. As
> the driver is closed source, there isn't much more we can learn or do
> about it.
>
>> Nouveau + Wayland = same as original problem
> original problem = kworker threads using CPU? That's nothing I can act
> upon---as describe in my earlier mail.
>   
>> I did update the firmware from the back-ports and it fixed the missing
>> firmware errors listed earlier, but I still get this "kernel: nouveau
>> 0000:01:00.0: drm: Disabling PCI power management to avoid bug"
> The bug mentioned here is described in more detail at
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/nouveau/nouveau_drm.c?id=11439c4635edd669ae435eec308f4ab8a0804808#n800
>
> With the nvidia driver that's maybe the issue that you describe above
> where on returning from sleep you get black screens. So you have 3
> options to go on:
>
>   - Stay on nouveau and live with PCI power management being disabled
>   - Stay on nvidia (or patch nouveau to enable PM) and live with the
>     black screens on resume
>   - Work on the problem and find a better solution
>
> For the 3rd option it's most probably you who would have to do the work.
> Maybe upstream is interested and could help you, the Debian kernel team
> cannot. Please contact upstream directly then.
>
> Best regards
> Uwe

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web