Below is the resolution steps for the subjected issue.
how to check :
===============
Validate kernel version
#uname -a
4.18.0-305.el8.x86_64 ß— this is the affected kernel version.
Check if the bug hitting on the dmesg log like below :-
#cd /var/crash
#grep -ir "kernel BUG at lib/list_debug" *
[snipet]
127.0.0.1-2026-01-24-05:58:09/vmcore-dmesg.txt:[565811.965600] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-02-01-14:06:04/vmcore-dmesg.txt:[720457.055917] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-02-04-07:35:08/vmcore-dmesg.txt:[235724.226457] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-02-11-21:31:07/vmcore-dmesg.txt:[654935.054955] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-02-23-10:13:06/vmcore-dmesg.txt:[996098.558096] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-02-26-01:10:08/vmcore-dmesg.txt:[226597.985699] kernel BUG at lib/list_debug.c:50!
127.0.0.1-2026-03-13-11:03:05/vmcore-dmesg.txt:[1331554.858401] kernel BUG at lib/list_debug.c:50!
[/snipet]
Resolution steps:
===================
1. Add the updates repo for RHEL8 with respect to the server location repo/image/pxe server.
2. take general config backup like network details , fstab,mount etc.
3. update the server using #yum update
Note: recommended is to go to the latest available rhel8.10 kernel. kernel-4.18.0-553.51.1.el8_10.x86_64
If requestor insist to be on RHEL8.4 or RHEL8.5 then update to below kernels.
- Red Hat Enterprise Linux 8.4 update the kernel to at least kernel-4.18.0-305.12.1.el8_4 via errata RHSA-2021:3057 or later
- Red Hat Enterprise Linux 8.5 and above update the kernel to at least kernel-4.18.0-348.el8 via Errata RHSA-2021:4356 or greater.
4. Once upgraded then reboot server
5. Verify the config backup all looks good .
6. Ask requestor to observe server and report back in case further issue.