Problem with kernel 5.3.18-150300.59.81

My system began occasionally hang in graphic mode after applying recommended update kernel to the kernel-default- from repository. Error messages in the system journal were:
BUG**: kernel NULL pointer dereference, address: 0000000000000000**
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 0 P4D 0

Rollback to the previous kernel-default-5.3.18-150300.59.76 made the system workable again.

Intel Core i7-6700K (Skylake)
32 Gb RAM

Thanks for reporting this error, Mikhailo. I confirm similar symptoms after installation of kernel version 5.3.18-150300.59.81.

I am currently selecting previous kernel to boot. What does technical community advise?

Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.76.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-150300.59.76-default
OS Type: 64-bit
Processors: 6 × Intel® Core™ i5-8500 CPU @ 3.00GHz
Memory: 7.5 GiB of RAM

I didn’t see any problems with the new kernel. On the other hand, I mostly boot 15.4, so I might have missed any problems.

In the past, I have seen kernels with problems. What I usually do in that case:

(1) report a bug, or add myself to the CC list of an existing bug report.

(2) I edit “/etc/zypp.conf” and change the line:

multiversion.kernels = latest,latest-1,running


multiversion.kernels = oldest,latest,latest-1,running

so that the working kernel won’t be automatically purged. When I am satisfied that the latest kernel is working, I can remove that change.

Thanks for that advice.


I have the same problem after the kernel update to kernel 5.3.18-150300.59.81. My system freezes two times yesterday. I tried to login via ssh from a different computer and after a very long time the login succeeds and I saw messages like"watchdog: BUG: soft lockup - CPU#0 stuck for XXXs!". I was not able to shutdown the computer and had to switch off the power. After booting with the older kernel 5.3.18-150300.59.76 everything was working fine again.


PS: Did you already report this bug?

I had exactly the same crash problem with OpenSUSE Leap 15.3 Kernel 5.3.18-150300.81 , rollback to previous 5.3.18-150300.59.76 version which works fine.

Possible crashes from kernel 5.3.18-150300.81: workqueue lockup, even trying to cancel command ‘journalctl -f’ took a long time, and then complete freeze. I had to force shutdown with Power button…

kernel: 1076.322718] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 366s!
Message from syslogd@opensuse-srv at Jul 19 10:35:59 ...
 kernel: 1076.322718] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 366s!
Message from syslogd@opensuse-srv at Jul 19 10:36:30 ...
 kernel: 1107.130580] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 397s!

Message from syslogd@opensuse-srv at Jul 19 10:37:00 ...
 kernel: 1137.934434] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 428s!
Message from syslogd@opensuse-srv at Jul 19 10:37:31 ...
 kernel: 1168.542299] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 458s!

Message from syslogd@opensuse-srv at Jul 19 10:38:02 ...
 kernel: 1199.202165] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 489s!

Looks like I have something like this. My report:

The question is indeed, did one of you already file a bug report? Because doing it twice is giving extra work to the bugzilla people, but doing it not at all will not help at all.

I would suggest @Mikhailo because he seems to have some logs (I have nothing of the kind).

When you never did it:
for information:
going there: usie same username and password as here on the forums.

Slight correction: /etc/zypp/zypp.conf

Where can I find the changelog of OpenSUSE Leap recent updates, e.g. Kernel 5.3.18-150300.59.81 ? Link or Mailing List ? thx

I think I found it here:

You can see the changelog via YaST Software Management and select kernel-default, or use rpm -q --changelog <package> | less.


Same problem here. I bootet my system with the new kernel and immediately logged in remotely to see this repeatedly:

Message from syslogd@weasel at Jul 18 21:32:38 ...
 kernel:   87.771832] watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [bash:14839]

Message from syslogd@weasel at Jul 18 21:33:06 ...
 kernel:  115.772282] watchdog: BUG: soft lockup - CPU#2 stuck for 52s! [bash:14839]

Message from syslogd@weasel at Jul 18 21:33:38 ...
 kernel:  147.772268] watchdog: BUG: soft lockup - CPU#2 stuck for 82s! [bash:14839]

I had to use the power switch to reboot into “recovery”, i.e. boot the old kernel and set it in “yast2 bootloader” as the kernel to boot. I then did as suggested by nrickert as in (except that the file name is /etc/zypp/zypp.conf).

Now I’m back to the old kernel and everything works as it did before.

# uname -a
Linux weasel 5.3.18-150300.59.76-default #1 SMP Thu Jun 16 04:23:47 UTC 2022 (2cc2ade) x86_64 x86_64 x86_64 GNU/Linux

My computer is an ASUS Q170T board with an Intel i7-7700T CPU and 32 GB RAM.

My question now is: After I did what nrickert has suggested, what do I do with the new kernel? Just “rm” everything “5.3.18-150300.59.81” in /boot, or do I wait for the next kernel and this gets cleaned up automatically, or how is such a thing supposed to be treated?


I would just leave as it is.

When new kernels arrive, it will not fall in any of oldest,latest,latest-1,running, and thus will be purged sometime.
And as @rnickert says, when you have a newer kernel that is OK, remove oldest and all will revert back to normal.

My question is still: is there a bug reported?
When yes, please post the URL in this thread so others can add information.

I have found several similar recent bugreports:

Just for others.
There is no need for “recovery”. From the grub screen you can choose the older kernel. Just Arrow down to the “other …” or how it is called, select it and you will get the possible kernels offered for choice.[/size]

Hi ccvv,

Thanks. I’ll go with that.

I don’t know whether a bug has been filed or not. Since I’m not a pro and only have basic knowledge of such things, I probably am not the right person to provide the necessary information. Also, I can’t get to any logs with the problematic kernel running. So I wouldn’t know what to do anyway.

Thanks again,


I am not affected because I’m running kernel:stabel:backports because of better nouveau Integration.
But kenerl:stable:backports has also often other Problems…

Hi Henk,

Yes, you’re right of course. And in fact, I didn’t do that. My Grub menu shows four entries:

5.3.18-150300.59.81 recovery
5.3.18-150300.59.76 recovery

I chose the third one, i.e. normal 5.3.18-150300.59.76. Sorry for the misunderstanding.


I am not sure if this is the same problem but after upgrading to kernel 5.3.18-150300.59.81 last night mtylaptop will not boot directly. It takes a long tmie running 5 jobs including kernel purging before giving a backtrace and saying SSH could not be started, or NTP canniot start. I do not know how to capture this informarion to be clearer. I eventualy boote using the previous kernel 5.3.18-150300.59.76

Is there a simple way to make this old kernel the default?

Thinkad X270 running Leap 15.3nom
No KDE nor Gnome; Just X with fvwm on top

Remove the latest version and lock kernel (zypper al kernel-default).