#kworker — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kworker, aggregated by home.social.
-
Endurance test on a 2009 Atom N450 netbook! 🛠️
This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours.
Goal: Prove our extreme #PREEMPT_RT optimization can permanently eliminate this hardware bug and revive the PC. Superior software rescues vintage hardware. Wish us stability! 🤞
#LinuxRT #KworkerFix #VintageTech #LowLatency -
Endurance test on a 2009 Atom N450 netbook! 🛠️
This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours.
Goal: Prove our extreme #PREEMPT_RT optimization can permanently eliminate this hardware bug and revive the PC. Superior software rescues vintage hardware. Wish us stability! 🤞
#LinuxRT #KworkerFix #VintageTech #LowLatency -
Endurance test on a 2009 Atom N450 netbook! 🛠️
This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours.
Goal: Prove our extreme #PREEMPT_RT optimization can permanently eliminate this hardware bug and revive the PC. Superior software rescues vintage hardware. Wish us stability! 🤞
#LinuxRT #KworkerFix #VintageTech #LowLatency -
Endurance test on a 2009 Atom N450 netbook! 🛠️
This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours.
Goal: Prove our extreme #PREEMPT_RT optimization can permanently eliminate this hardware bug and revive the PC. Superior software rescues vintage hardware. Wish us stability! 🤞
#LinuxRT #KworkerFix #VintageTech #LowLatency -
Endurance test on a 2009 Atom N450 netbook! 🛠️
This Acer Aspire One always failed on standard Linux due to a frustrating #kworker CPU spike, making it unusable. We're challenging that with #BashCoreZ_RT for 48 hours.
Goal: Prove our extreme #PREEMPT_RT optimization can permanently eliminate this hardware bug and revive the PC. Superior software rescues vintage hardware. Wish us stability! 🤞
#LinuxRT #KworkerFix #VintageTech #LowLatency -
[Post-mortem: BashCore Stress Test Investigation]
Test ended on Day 5.
The system didn’t crash, but I noticed the fan was working overtime. The main suspect?
kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management).
So technically… BashCore held up, but ACPI didn’t like the heat. Literally.
This is a known issue on older hardware with imperfect ACPI/BIOS support.Takeaway:
BashCore is stable, it’s the laptop that needs therapy 🤒 -
[Post-mortem: BashCore Stress Test Investigation]
Test ended on Day 5.
The system didn’t crash, but I noticed the fan was working overtime. The main suspect?
kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management).
So technically… BashCore held up, but ACPI didn’t like the heat. Literally.
This is a known issue on older hardware with imperfect ACPI/BIOS support.Takeaway:
BashCore is stable, it’s the laptop that needs therapy 🤒 -
[Post-mortem: BashCore Stress Test Investigation]
Test ended on Day 5.
The system didn’t crash, but I noticed the fan was working overtime. The main suspect?
kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management).
So technically… BashCore held up, but ACPI didn’t like the heat. Literally.
This is a known issue on older hardware with imperfect ACPI/BIOS support.Takeaway:
BashCore is stable, it’s the laptop that needs therapy 🤒 -
[Post-mortem: BashCore Stress Test Investigation]
Test ended on Day 5.
The system didn’t crash, but I noticed the fan was working overtime. The main suspect?
kworker/0:3+kacpid turns out it was busy with ACPI tasks (power management).
So technically… BashCore held up, but ACPI didn’t like the heat. Literally.
This is a known issue on older hardware with imperfect ACPI/BIOS support.Takeaway:
BashCore is stable, it’s the laptop that needs therapy 🤒 -
[Stress Test Interrupted - Day 5]
After almost 5 days of flawless uptime on a 2009 Acer Aspire One, I came back home to find the netbook as warm as a toaster.
The fan was spinning like it was ready for takeoff... main suspect: #kworker.
No crash, but just to be safe, I shut it down. I’ll be away for 3 days.So, the test ends here…
Scientific conclusion:
BashCore survives, but kworker has more stamina than I do 🤣#BashCore #FailWithStyle #kworkerMyNemesis #LinuxOnOldHardware #PentestLiveOS
-
Noticed kworker using high CPU on one of my machines after a while. Seems ACPI-related, so likely hardware-dependent. Nothing to do with #BashCore, just an interesting find.
Anyone else seen this? Let me know!
-
Öfter mal was Neues: Das Kopieren großer Dateien - wie etwa eines 120 GB großen Images einer Speicherkarte - auf ein via CIFS/SMB-Freigabe angebundenes NAS-System löst auf dem kopierenden Rechner irgendwann so lange Meldungen der Art
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kcompactd0:51]watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u16:0:5538]
im Wechsel aus, bis das unter Linux 6.11.4 laufende System steht und nur noch ein Hardware-Reset bleibt.Drollige Nebenerscheinungen des Spuks: Die via USB angebundene Tastatur funktioniert nicht mehr (somit auch kein Magic SysRq), die ebenfalls via USB angebundene Maus hingegen schon. Ein Login übers Netzwerk ist am System möglich, wenn auch sehr zäh. Anweisungen zu einem geordneten Herunterfahren des Systems führen allerdings praktischerweise zu keinerlei Reaktion.
-
Could some full time kernel head tell me: how does a #kworker get towards to the busy end of top in state Idle? If its Idle why does it have >0.1% CPU ? My CPUs are recent enough & desktop power
#linuxkernel
uname == "Linux hiss 5.19.0-43-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC" -
[Stress Test Interrupted - Day 5]
After almost 5 days of flawless uptime on a 2009 Acer Aspire One, I came back home to find the netbook as warm as a toaster.
The fan was spinning like it was ready for takeoff... main suspect: #kworker.
No crash, but just to be safe, I shut it down. I’ll be away for 3 days.So, the test ends here…
Scientific conclusion:
BashCore survives, but kworker has more stamina than I do 🤣#BashCore #FailWithStyle #kworkerMyNemesis #LinuxOnOldHardware #PentestLiveOS
-
[Stress Test Interrupted - Day 5]
After almost 5 days of flawless uptime on a 2009 Acer Aspire One, I came back home to find the netbook as warm as a toaster.
The fan was spinning like it was ready for takeoff... main suspect: #kworker.
No crash, but just to be safe, I shut it down. I’ll be away for 3 days.So, the test ends here…
Scientific conclusion:
BashCore survives, but kworker has more stamina than I do 🤣#BashCore #FailWithStyle #kworkerMyNemesis #LinuxOnOldHardware #PentestLiveOS
-
[Stress Test Interrupted - Day 5]
After almost 5 days of flawless uptime on a 2009 Acer Aspire One, I came back home to find the netbook as warm as a toaster.
The fan was spinning like it was ready for takeoff... main suspect: #kworker.
No crash, but just to be safe, I shut it down. I’ll be away for 3 days.So, the test ends here…
Scientific conclusion:
BashCore survives, but kworker has more stamina than I do 🤣#BashCore #FailWithStyle #kworkerMyNemesis #LinuxOnOldHardware #PentestLiveOS
-
Noticed kworker using high CPU on one of my machines after a while. Seems ACPI-related, so likely hardware-dependent. Nothing to do with #BashCore, just an interesting find.
Anyone else seen this? Let me know!
-
Noticed kworker using high CPU on one of my machines after a while. Seems ACPI-related, so likely hardware-dependent. Nothing to do with #BashCore, just an interesting find.
Anyone else seen this? Let me know!
-
Noticed kworker using high CPU on one of my machines after a while. Seems ACPI-related, so likely hardware-dependent. Nothing to do with #BashCore, just an interesting find.
Anyone else seen this? Let me know!
-
Öfter mal was Neues: Das Kopieren großer Dateien - wie etwa eines 120 GB großen Images einer Speicherkarte - auf ein via CIFS/SMB-Freigabe angebundenes NAS-System löst auf dem kopierenden Rechner irgendwann so lange Meldungen der Art
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kcompactd0:51]watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u16:0:5538]
im Wechsel aus, bis das unter Linux 6.11.4 laufende System steht und nur noch ein Hardware-Reset bleibt.Drollige Nebenerscheinungen des Spuks: Die via USB angebundene Tastatur funktioniert nicht mehr (somit auch kein Magic SysRq), die ebenfalls via USB angebundene Maus hingegen schon. Ein Login übers Netzwerk ist am System möglich, wenn auch sehr zäh. Anweisungen zu einem geordneten Herunterfahren des Systems führen allerdings praktischerweise zu keinerlei Reaktion.
-
Öfter mal was Neues: Das Kopieren großer Dateien - wie etwa eines 120 GB großen Images einer Speicherkarte - auf ein via CIFS/SMB-Freigabe angebundenes NAS-System löst auf dem kopierenden Rechner irgendwann so lange Meldungen der Art
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kcompactd0:51]watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u16:0:5538]
im Wechsel aus, bis das unter Linux 6.11.4 laufende System steht und nur noch ein Hardware-Reset bleibt.Drollige Nebenerscheinungen des Spuks: Die via USB angebundene Tastatur funktioniert nicht mehr (somit auch kein Magic SysRq), die ebenfalls via USB angebundene Maus hingegen schon. Ein Login übers Netzwerk ist am System möglich, wenn auch sehr zäh. Anweisungen zu einem geordneten Herunterfahren des Systems führen allerdings praktischerweise zu keinerlei Reaktion.
-
Öfter mal was Neues: Das Kopieren großer Dateien - wie etwa eines 120 GB großen Images einer Speicherkarte - auf ein via CIFS/SMB-Freigabe angebundenes NAS-System löst auf dem kopierenden Rechner irgendwann so lange Meldungen der Art
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kcompactd0:51]watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u16:0:5538]
im Wechsel aus, bis das unter Linux 6.11.4 laufende System steht und nur noch ein Hardware-Reset bleibt.Drollige Nebenerscheinungen des Spuks: Die via USB angebundene Tastatur funktioniert nicht mehr (somit auch kein Magic SysRq), die ebenfalls via USB angebundene Maus hingegen schon. Ein Login übers Netzwerk ist am System möglich, wenn auch sehr zäh. Anweisungen zu einem geordneten Herunterfahren des Systems führen allerdings praktischerweise zu keinerlei Reaktion.
-
Öfter mal was Neues: Das Kopieren großer Dateien - wie etwa eines 120 GB großen Images einer Speicherkarte - auf ein via CIFS/SMB-Freigabe angebundenes NAS-System löst auf dem kopierenden Rechner irgendwann so lange Meldungen der Art
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kcompactd0:51]watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u16:0:5538]
im Wechsel aus, bis das unter Linux 6.11.4 laufende System steht und nur noch ein Hardware-Reset bleibt.Drollige Nebenerscheinungen des Spuks: Die via USB angebundene Tastatur funktioniert nicht mehr (somit auch kein Magic SysRq), die ebenfalls via USB angebundene Maus hingegen schon. Ein Login übers Netzwerk ist am System möglich, wenn auch sehr zäh. Anweisungen zu einem geordneten Herunterfahren des Systems führen allerdings praktischerweise zu keinerlei Reaktion.
-
Could some full time kernel head tell me: how does a #kworker get towards to the busy end of top in state Idle? If its Idle why does it have >0.1% CPU ? My CPUs are recent enough & desktop power
#linuxkernel
uname == "Linux hiss 5.19.0-43-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC"