Current Kernel version.
6.4.0-150600.23.87-default #1 SMP PREEMPT_DYNAMIC Tue Feb 3 14:58:48 UTC 2026 (0f213a3) x86_64 x86_64 x86_64 GNU/Linux
Which has been re-installed
Also Tried 23.84 and 23.81
I had a problem with OpenSuse 15.6 update tool on MATE Desktop, decided to take to long to update, so I pulled the plug to stop the update. Then tried to do an update on the terminal. The Package manager was still running in the background, that was not closing. So I decided rather to reboot.
After that this BUG showed up
kernel:[ C0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 26925s!
Feb 18 07:02:45 kernel: pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=0s workers=8 idle: 306 376 68723
Feb 18 07:02:45 kernel: pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=0s workers=11 idle: 389 4209 69598
Feb 18 07:02:45 kernel: pool 4: cpus=2 node=0 flags=0x0 nice=0 hung=0s workers=5 idle: 21648 31661
Feb 18 07:02:45 kernel: pool 6: cpus=3 node=0 flags=0x0 nice=0 hung=26955s workers=3 idle: 3430 3452
Feb 18 07:02:45 kernel: pool 136: cpus=0-67 flags=0x4 nice=0 hung=0s workers=5 idle: 5059 16166 47523
Feb 18 07:02:45 kernel: Showing backtraces of running workers in stalled CPU-bound worker pools:
A sudo zypper patch and sudo zypper update updated leap 15.6 on mate desktop successfully to kernel 6.4.0-150600.23.87-default for me. No issues.
Doesn’t help you but looks like update worked fine for others. Perhaps looking at interrupting update as the cause might correct issue. I have had to interrupt updates in the middle in the past with no issues.
Literally disconnected the power cord from the wall or computer, or something less drastic?
Showed up by doing what exactly?
kernel:[ C0] BUG: workqueue lockup - pool cpus=3 node=0 flags=0x0 nice=0 stuck for 26925s!
Feb 18 07:02:45 kernel: pool 0: cpus=0 node=0 flags=0x0 nice=0 hung=0s workers=8 idle: 306 376 68723
Feb 18 07:02:45 kernel: pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=0s workers=11 idle: 389 4209 69598
Feb 18 07:02:45 kernel: pool 4: cpus=2 node=0 flags=0x0 nice=0 hung=0s workers=5 idle: 21648 31661
Feb 18 07:02:45 kernel: pool 6: cpus=3 node=0 flags=0x0 nice=0 hung=26955s workers=3 idle: 3430 3452
Feb 18 07:02:45 kernel: pool 136: cpus=0-67 flags=0x4 nice=0 hung=0s workers=5 idle: 5059 16166 47523
Feb 18 07:02:45 kernel: Showing backtraces of running workers in stalled CPU-bound worker pools:
Exactly what command generated those?
Zypper doesn’t take kindly to getting interrupted. I think I might try rpm --rebuilddb before trying zypper again. Also, journalctl -b -X -p3 where X is the number of the prior boot where you pulled the plug, and repeat for the boot that followed, might offer additional clues.