# Blocking BUG with the new RockyLinux 9.2 kernel **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [May 18, 2023, 4:16pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937 "2023-05-18T16:16:13Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Fabix](https://avatars.discourse-cdn.com/v4/letter/f/85f322/32.png) [@Fabix](https://forums.rockylinux.org/u/Fabix)\ **Post date:** [May 18, 2023, 4:16pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/1 "2023-05-18T16:16:13Z")
On two servers running Rocky Linux 9.1, I upgraded to 9.2 with new kernel. Since then it has been a disaster. After a random period ranging from a few minutes to a couple of hours, two CPUs completely freeze making the system unusable. The only solution is to restart the server, it works fine again for a while and then same story. This is the message: **kernel:watchdog: BUG: soft lockup - CPU#1 stuck for 3151s kworker/2:2:16322** **kernel:watchdog: BUG: soft lockup - CPU#2 stuck for 3308s kworker/1:0:10255** ![kernelerror](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/4/4370c275ce03e87abcdcc4e4c5a437315f500239.png) Do you have any idea what it is and how to fix it? ---
**Author:** ![timppu](https://avatars.discourse-cdn.com/v4/letter/t/a6a055/32.png) [@timppu](https://forums.rockylinux.org/u/timppu)\ **Post date:** [May 18, 2023, 7:38pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/2 "2023-05-18T19:38:02Z")
I was earlier fighting with a “similar” problem: > [@"watchdog: BUG: soft lockup - CPU stuck" errors with USB devices](https://forums.rockylinux.org/t/watchdog-bug-soft-lockup-cpu-stuck-errors-with-usb-devices/9676): > > Rocky Linux 9.1 (tried both with the default Gnome and XFCE editions) 5.14.0-162.23.1.el9\_1.x86\_64 #1 SMP PREEMPT\_DYNAMIC Tue Apr 11 19:09:37 UTC 2023 I recently installed Rocky Linux 9.1 on my Dell laptop (dual-boot with Windows 11), and if I have any devices connected to the USB-C or USB-A ports, I frequently get e.g. the soft lockup errors. These seem to come either while booting up, or shutting down. On the USB-A port(s) I normally connect my powered USB hub to which I’ve connected the key… I think that CPU stuck error is just a symptom, and the root cause can be various different things. I felt in my case it was related to desktop usage (e.g. connected USB devices or the power management or something), which possibly are not an issue in server use. Are they real server hardware, or e.g. virtual machines, even in the public cloud? In my case (running Rocky Linux in a laptop), things I felt may have at least affected it (this is the timeline too): 1. It seemed at some point some connected USB devices triggered this. Things seemed better if I disconnected all USB devices… but it may be the reason was the next point, as I usually also disconnected AC power along with the USB devices. 2. At some point I noticed that if and when this issue took place, disconnecting my laptop from AC power somehow helped the situation and the laptop would become “unstuck”? This lead me to believe this was somehow related to power management. 3. As i mention in the other thread, I disabled hibernate and sleep mode altogether. I felt it at least helped with the problem. 4. The problem did occur even after that but I got somewhat different error messages (something about some device having to wait for n seconds or something), and googling for it, someone had fixed it by disabling/removing Pipewire and replacing it with PulseAudio, or something like that… I don’t think I ever managed to do that switch. However, now I haven’t seen this issue for awhile, not sure what has changed or what fixed it. From the abovementioned things, I felt disabling (masking) hibernate and sleep mode is most probably the thing that helped it the most, or fixed it. I haven’t checked lately if I get any such errors in logs, but at least I a not experiencing similar unresponsiveness anymore. However, since your issues happen in server use, somehow I feel maybe your root cause is not related to USB devices or power management or audio libraries. ---
**Author:** ![Fabix](https://avatars.discourse-cdn.com/v4/letter/f/85f322/32.png) [@Fabix](https://forums.rockylinux.org/u/Fabix)\ **Post date:** [May 18, 2023, 8:11pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/3 "2023-05-18T20:11:57Z")
In my case I am dealing with a cloud system with dedicated resources. Before upgrading to RockyLinux 9.2 everything worked fine. The one time I was able to log into one of the two machines affected during the problem (usually I can’t even log in via ssh and have to do a hard reset), I got that screen shown above. Looking for some more info, the processes that went to block were of this type: **[kworker/2:1-cifsiod]** giving me the idea that Cifs may have something to do with it. But I have no certainty. ---
**Author:** ![Fabix](https://avatars.discourse-cdn.com/v4/letter/f/85f322/32.png) [@Fabix](https://forums.rockylinux.org/u/Fabix)\ **Post date:** [May 18, 2023, 11:15pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/4 "2023-05-18T23:15:58Z")
This is the screen of top command before kernel crash: ![screenkernelcrash](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/a/a0fc97e55850ad45c01c072550bffdfb6c178c7f.png) Is there any way to disable this cifsiod process? It didn’t exist in the previous kernel. Being a kernel process it won’t let me terminate it. Is there any way to report this bug to the developers? ---
**Author:** ![hspindel](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hspindel](https://forums.rockylinux.org/u/hspindel)\ **Post date:** [May 19, 2023, 1:46am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/5 "2023-05-19T01:46:26Z")
Two days after upgrading to RL 9.2 from 9.1 I saw one of these CPU lockup messages. Only cure was to power down and restart - simple restart didn’t work. USB devicea - an APC UPS, keyboard, mouse. Please devs take a look at this. console message is: Message from syslogd@localhost at May 18 20:24:43 … kernel:watchdog: BUG: soft lockup - CPU#4 stuck for 3397s! [kworker/4:2:519] After rebooting the machine, the issue recurred a couple hours later with a different CPU number. ---
**Author:** ![wolverine](https://avatars.discourse-cdn.com/v4/letter/w/ba9def/32.png) [@wolverine](https://forums.rockylinux.org/u/wolverine)\ **Post date:** [May 19, 2023, 5:15am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/6 "2023-05-19T05:15:51Z")
Hi I can confirm this issue after upgrading yesterday. After ~3 hours, the system (VM on a cloud hoster) becomes unresponsive. > [@](#): > > May 18 17:48:37 docker kernel: rcu: INFO: rcu\_preempt detected expedited stalls on CPUs/tasks: { 0-… } 21406 jiffies s: 8229 root: 0x1/. > May 18 17:48:37 docker kernel: rcu: blocking rcu\_node structures (internal RCU debug): > May 18 17:48:37 docker kernel: Task dump for CPU 0: > May 18 17:48:37 docker kernel: task:kworker/0:1 state:R running task stack: 0 pid:35788 ppid: 2 flags:0x00004008 > May 18 17:48:37 docker kernel: Workqueue: cifsiod smb2\_reconnect\_server [cifs] > May 18 17:48:37 docker kernel: Call Trace: > May 18 17:48:37 docker kernel: > May 18 17:48:37 docker kernel: ? \_\_schedule+0x250/0x620 > May 18 17:48:37 docker kernel: ? smb2\_check\_receive+0xac/0x130 [cifs] > May 18 17:48:37 docker kernel: ? cifs\_mid\_q\_entry\_release+0x43/0x70 [cifs] > May 18 17:48:37 docker kernel: ? compound\_send\_recv+0x5ff/0xa60 [cifs] > May 18 17:48:37 docker kernel: ? mempool\_alloc+0x62/0x190 > May 18 17:48:37 docker kernel: ? SMB2\_tcon+0x296/0x790 [cifs] > May 18 17:48:37 docker kernel: ? sysvec\_apic\_timer\_interrupt+0xb/0x90 > May 18 17:48:37 docker kernel: ? asm\_sysvec\_apic\_timer\_interrupt+0x16/0x20 > May 18 17:48:37 docker kernel: ? native\_queued\_spin\_lock\_slowpath+0x21/0x30 > May 18 17:48:37 docker kernel: ? \_raw\_spin\_lock+0x25/0x30 > May 18 17:48:37 docker kernel: ? smb2\_reconnect.part.0+0x3f/0x5f0 [cifs] > May 18 17:48:37 docker kernel: ? set\_next\_entity+0xda/0x150 > May 18 17:48:37 docker kernel: ? smb2\_reconnect\_server+0x203/0x5f0 [cifs] > May 18 17:48:37 docker kernel: ? process\_one\_work+0x1e8/0x3c0 > May 18 17:48:37 docker kernel: ? rescuer\_thread+0x3a0/0x3a0 > May 18 17:48:37 docker kernel: ? worker\_thread+0x50/0x3b0 > May 18 17:48:37 docker kernel: ? rescuer\_thread+0x3a0/0x3a0 > May 18 17:48:37 docker kernel: ? kthread+0xd9/0x100 > May 18 17:48:37 docker kernel: ? kthread\_complete\_and\_exit+0x20/0x20 > May 18 17:48:37 docker kernel: ? ret\_from\_fork+0x22/0x30 > May 18 17:48:37 docker kernel: ---
**Author:** ![ogis](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/ogis/32/3083_2.png) [@ogis](https://forums.rockylinux.org/u/ogis)\ **Post date:** [May 19, 2023, 11:18am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/7 "2023-05-19T11:18:25Z")
Hello. I have a simple advice. I also had a lot of problems with Rocky Linux 9.2. I spit on everything and switched to Oracle Linux (UEK kernel). All my problems are gone. ---
**Author:** ![james-p](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@james-p](https://forums.rockylinux.org/u/james-p)\ **Post date:** [May 19, 2023, 12:32pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/8 "2023-05-19T12:32:27Z")
Looks like this is known issue: [https://bugzilla.redhat.com/show\_bug.cgi?id=2180423](https://bugzilla.redhat.com/show_bug.cgi?id=2180423) [https://bugzilla.redhat.com/show\_bug.cgi?id=2189320](https://bugzilla.redhat.com/show_bug.cgi?id=2189320) ---
**Author:** ![Fabix](https://avatars.discourse-cdn.com/v4/letter/f/85f322/32.png) [@Fabix](https://forums.rockylinux.org/u/Fabix)\ **Post date:** [May 19, 2023, 1:08pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/9 "2023-05-19T13:08:37Z")
I found a temporary **fix**. I edited the /etc/fstab file removing the cifs network path initializations. I turned the server off and on again and the problem disappeared. Clearly now I no longer have the cifs network paths as directories and have to reach them in another way (e.g. FTP). It’s not optimal but at least the server doesn’t go down anymore. However on Rocky Linux 9.1 this did not happen. Fabio ---
**Author:** ![james-p](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@james-p](https://forums.rockylinux.org/u/james-p)\ **Post date:** [May 19, 2023, 1:56pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/10 "2023-05-19T13:56:14Z")
The BZ reports state this issue is fixed in kernel-5.14.0-301.el9 or later - but these are not available with RHEL/Rocky9 - but they are available with CentOS 9 Stream - so if you can’t wait until RHEL/Rocky have a fix, you could download and update to the latest CentOS 9 Stream kernel RPMS … ---
**Author:** ![hspindel](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hspindel](https://forums.rockylinux.org/u/hspindel)\ **Post date:** [May 19, 2023, 8:45pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/11 "2023-05-19T20:45:45Z")
I used the grub boot choices to boot from the previous kernel (RL 9.1) 5.14.0-162.23.1.el9\_1 So far the server has stayed up. Until this is fixed, this is my workaround. ---
**Author:** ![hspindel](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hspindel](https://forums.rockylinux.org/u/hspindel)\ **Post date:** [May 22, 2023, 5:32am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/12 "2023-05-22T05:32:50Z")
Any ETA on when the fix will get propagated to RL9.2? ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [May 22, 2023, 6:04am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/13 "2023-05-22T06:04:17Z")
It relies on upstream (Red Hat), since the linked posts here suggest it’s fixed in `5.14.0-301.el9` we have to wait until Red Hat release it. As Rocky is 1:1 of RHEL, then Rocky has exactly what RHEL has. ---
**Author:** ![zieba88](https://avatars.discourse-cdn.com/v4/letter/z/35a633/32.png) [@zieba88](https://forums.rockylinux.org/u/zieba88)\ **Post date:** [May 26, 2023, 2:05pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/14 "2023-05-26T14:05:48Z")
FWIW in case anyone else is dealing with this, I have been working to migrate to Rocky Linux 9.1 and at the time I synced the repos locally kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 was available. I ran into the same issues above running kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 and installed the suggested kernel-5.14.0-162.23.1.el9\_1.x86\_64 and it seems to have stabilized the host. Will let it run for longer and report back but it seems like a bug that was introduced in kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 fixed in kernel-5.14.0-162.23.1.el9\_1.x86\_64 and reintroduced in 9.2 ---
**Author:** ![elico](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/elico/32/3142_2.png) [@elico](https://forums.rockylinux.org/u/elico)\ **Post date:** [May 27, 2023, 12:14pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/15 "2023-05-27T12:14:19Z")
> [@zieba88](#): > > I have been working to migrate to Rocky Linux 9.1 and at the time I synced the repos locally kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 was available. … Have you tried using: [ELRepo | HomePage](http://elrepo.org/tiki/HomePage) [Index of /linux/kernel (elrepo.org)](https://elrepo.org/linux/kernel/) just to make sure that a kernel upgrade resolves the issue on one machine? ---
**Author:** ![zieba88](https://avatars.discourse-cdn.com/v4/letter/z/35a633/32.png) [@zieba88](https://forums.rockylinux.org/u/zieba88)\ **Post date:** [May 30, 2023, 1:28pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/16 "2023-05-30T13:28:48Z")
I can confirm kernel-5.14.0-162.23.1.el9\_1.x86\_64 has resolved the issues with the system locking up. The system has been stable for 5 days. kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 seems to have the same issues as reported with the 9.2 kernel. Here is the /var/log/messages output while running on kernel-5.14.0-162.12.1.el9\_1.0.2.x86\_64 [root@hostname123 ~]# grep -iE “soft lockup|Workqueue:” /var/log/messages May 22 09:59:39 hostname123 kernel: [184937.055476] Workqueue: cgroup\_destroy css\_free\_rwork\_fn May 23 12:18:52 hostname123 kernel: [279690.777541] watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [kworker/7:0:2092347] May 23 12:18:52 hostname123 kernel: [279690.782265] Workqueue: deferredclose smb2\_deferred\_work\_close [cifs] May 23 12:18:52 hostname123 kernel: [279690.823543] watchdog: BUG: soft lockup - CPU#11 stuck for 22s! [.NET ThreadPool:2161345] May 23 12:18:52 hostname123 kernel: [279690.866542] watchdog: BUG: soft lockup - CPU#15 stuck for 22s! [migration/15:94] May 23 12:18:52 hostname123 kernel: [279691.085543] watchdog: BUG: soft lockup - CPU#35 stuck for 22s! [zabbix\_agent2:5710] May 23 12:18:52 hostname123 kernel: [279691.095544] watchdog: BUG: soft lockup - CPU#36 stuck for 22s! [zabbix\_agent2:4964] May 23 12:18:53 hostname123 kernel: [279691.206545] watchdog: BUG: soft lockup - CPU#46 stuck for 22s! [.NET ThreadPool:2143310] May 23 12:18:53 hostname123 kernel: [279691.428546] watchdog: BUG: soft lockup - CPU#86 stuck for 26s! [cifsd:5197] May 23 12:18:53 hostname123 kernel: [279691.459548] watchdog: BUG: soft lockup - CPU#94 stuck for 26s! [zabbix\_agent2:85411] May 23 12:18:53 hostname123 kernel: [279691.467547] watchdog: BUG: soft lockup - CPU#96 stuck for 22s! [.NET ThreadPool:2161681] May 23 12:18:53 hostname123 kernel: [279691.471547] watchdog: BUG: soft lockup - CPU#97 stuck for 26s! [FileWriterThrea:2162018] May 23 12:18:53 hostname123 kernel: [279691.503547] watchdog: BUG: soft lockup - CPU#105 stuck for 23s! [.NET ThreadPool:2161682] May 23 12:18:53 hostname123 kernel: [279691.511547] watchdog: BUG: soft lockup - CPU#107 stuck for 23s! [kworker/u226:2:2091130] May 23 12:18:53 hostname123 kernel: [279691.519547] watchdog: BUG: soft lockup - CPU#109 stuck for 27s! [.NET ThreadPool:2161586] May 23 12:18:53 hostname123 kernel: [279691.577019] Workqueue: writeback wb\_workfn May 23 12:18:56 hostname123 kernel: [279694.485572] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [zabbix\_agent2:530182] May 23 12:18:56 hostname123 kernel: [279694.738574] watchdog: BUG: soft lockup - CPU#6 stuck for 27s! [zabbix\_agent2:6984] May 23 12:18:57 hostname123 kernel: [279695.273578] watchdog: BUG: soft lockup - CPU#52 stuck for 22s! [zabbix\_agent2:15933] May 23 12:18:57 hostname123 kernel: [279695.389579] watchdog: BUG: soft lockup - CPU#76 stuck for 22s! [zabbix\_agent2:295377] May 23 12:18:57 hostname123 kernel: [279695.475580] watchdog: BUG: soft lockup - CPU#98 stuck for 22s! [zabbix\_agent2:523551] May 23 12:18:52 hostname123 kernel: [279690.790388] Call Trace: May 23 12:18:52 hostname123 kernel: [279690.790898] \_raw\_spin\_lock+0x25/0x30 May 23 12:18:52 hostname123 kernel: [279690.791372] \_get\_xid+0x13/0xa0 [cifs] May 23 12:18:52 hostname123 kernel: [279690.791921] \_cifsFileInfo\_put+0x2b6/0x430 [cifs] May 23 12:18:52 hostname123 kernel: [279690.792434] ? smb2\_deferred\_work\_close+0x30/0x60 [cifs] May 23 12:18:52 hostname123 kernel: [279690.792954] process\_one\_work+0x1e5/0x3c0 May 23 12:18:52 hostname123 kernel: [279690.793429] worker\_thread+0x50/0x3b0 May 23 12:18:52 hostname123 kernel: [279690.793945] ? rescuer\_thread+0x380/0x380 May 23 12:18:52 hostname123 kernel: [279690.794429] kthread+0x146/0x170 May 23 12:18:52 hostname123 kernel: [279690.794967] ? set\_kthread\_struct+0x50/0x50 May 23 12:18:52 hostname123 kernel: [279690.795507] ret\_from\_fork+0x1f/0x30 May 23 12:18:52 hostname123 kernel: [279690.823543] watchdog: BUG: soft lockup - CPU#11 stuck for 22s! [.NET ThreadPool:2161345] ---
**Author:** ![hspindel](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hspindel](https://forums.rockylinux.org/u/hspindel)\ **Post date:** [June 2, 2023, 12:13am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/17 "2023-06-02T00:13:55Z")
kernel 5.14.0-162.23.1.el9\_1.x64\_64 is fine. Been running with that for months. It’s the upgrade to 5.14.0.284.11.1.el9\_2.x64\_64 that broke things. It installed with RL 9.2 . Currently running on the older kernel waiting for a fix. ---
**Author:** ![mr.durock01](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@mr.durock01](https://forums.rockylinux.org/u/mr.durock01)\ **Post date:** [June 6, 2023, 8:08pm UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/18 "2023-06-06T20:08:04Z")
I get this error in my rock 9(in looping) Kernel Version: Linux rock-kvm-server01 5.14.0-284.11.1.el9\_2.x86\_64 #1 SMP PREEMPT\_DYNAMIC Tue May 9 17:09:15 UTC 2023 x86\_64 x86\_64 x86\_64 GNU/Linux Release: NAME=“Rocky Linux” VERSION=“9.2 (Blue Onyx)” ID=“rocky” Error(in looping and system is very slow…): Message from syslogd@rock-kvm-server01 at Jun 6 17:01:15 … kernel:watchdog: BUG: soft lockup - CPU#14 stuck for 1151s! [kworker/14:1:172] Message from syslogd@rock-kvm-server01 at Jun 6 17:02:03 … kernel:watchdog: BUG: soft lockup - CPU#14 stuck for 1196s! [kworker/14:1:172] Message from syslogd@rock-kvm-server01 at Jun 6 17:03:27 … kernel:watchdog: BUG: soft lockup - CPU#14 stuck for 1274s! [kworker/14:1:172] top: ![image](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/2X/e/e81028080c5749265d697d7648b54fe6986ea73c.png) ---
**Author:** ![Dubbie](https://avatars.discourse-cdn.com/v4/letter/d/958977/32.png) [@Dubbie](https://forums.rockylinux.org/u/Dubbie)\ **Post date:** [June 7, 2023, 12:29am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/19 "2023-06-07T00:29:22Z")
We are also dealing with this bug. All machines that went to 9.2 lock up now. The ones on 9.1 are fine. ---
**Author:** ![hspindel](https://avatars.discourse-cdn.com/v4/letter/h/3bc359/32.png) [@hspindel](https://forums.rockylinux.org/u/hspindel)\ **Post date:** [June 13, 2023, 12:27am UTC](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937/20 "2023-06-13T00:27:49Z")
Posting here in case my fix helps someone else. I got tired of waiting for RHEL to release a fixed kernel. Having to revert to the RL9.1 kernel caused other problems (example: VirtualBox stopped working). I found CentOS kernel-5.14.0-302.el9 here: [https://kojihub.stream.centos.org/koji/buildinfo?buildID=31868](https://kojihub.stream.centos.org/koji/buildinfo?buildID=31868) This is newer than the 284 kernel RL9.2 is supplying. After installing this newer kernel (plus some other dependencies from the same web page) all seems well. Server has been running over 24 hours with no CPU lockups. I see that even newer builds than 302 are available, for example 326 here: [https://kojihub.stream.centos.org/koji/buildinfo?buildID=33654](https://kojihub.stream.centos.org/koji/buildinfo?buildID=33654) [Next page](https://forums.rockylinux.org/t/blocking-bug-with-the-new-rockylinux-9-2-kernel/9937.md?page=2)