Bug 474761 - kworker very often starts with new PID
Summary: kworker very often starts with new PID
Status: RESOLVED UPSTREAM
Alias: None
Product: unknown
Classification: Bugzilla Internals
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-21 09:29 UTC by d033845
Modified: 2023-09-21 10:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description d033845 2023-09-21 09:29:25 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
I have the situation at my HP Z620 32 core system, that within around 2-3 days the system fails with PID max. The situation seams to be related to kworker process starting very often subprocesses. 

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nicolas Fella 2023-09-21 10:50:17 UTC 
Despite the name kworker doesn't have anything to do with KDE. It's a component of the Linux kernel (that's where the 'k' is coming from).

With that in mind it's very unlikely that your issue is related to any KDE software