#StackBounty: #networking #drivers #21.04 #iwlwifi Kernel: 5.11, Wi-Fi UNCLAIMED, "dmesg |grep iwlwifi" is empty. Wifi [8086:…

Bounty: 50

What I have different from all other cases is that I have nothing on dmesg.

# dmesg |grep iwlwifi | wc -l
0
  • I have dual boot with Windows 10.
  • Windows "Fast Startup" is disabled.
  • Secure boot is disabled (I have it enabled when install the linux, but disable to fix nvidia).
  • Ubuntu 21 "Ubuntu 21.04.
  • The classic "Ubuntu Drivers" only offer drivers for NVidia
# inxi -Fxxxrz
System:    Kernel: 5.11.0-34-generic x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.4 tk: GTK 3.24.25 
           wm: gnome-shell dm: GDM3 3.38.2.1 Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Laptop System: Alienware product: Alienware x17 R1 v: 1.2.1 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: Alienware model: Alienware x17 R1 v: A00 serial: <filter> UEFI: Alienware v: 1.2.1 date: 07/12/2021 
...
Network:   Device-1: Realtek Killer E3000 2.5GbE vendor: Dell driver: r8169 v: kernel port: 3000 bus ID: 0000:3b:00.0 
           chip ID: 10ec:3000 class ID: 0200 
           IF: enp59s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz vendor: Rivet Networks driver: N/A port: 3000 bus ID: 0000:3c:00.0 
           chip ID: 8086:2725 class ID: 0280 
           IF-ID-1: docker0 state: down mac: <filter> 
...
# lspci -nnk | grep -iA3 net 
0000:3b:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. Killer E3000 2.5GbE Controller [10ec:3000] (rev 06)
    Subsystem: Dell Device [1028:0a8f]
    Kernel driver in use: r8169
    Kernel modules: r8169
0000:3c:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
    Subsystem: Rivet Networks Device [1a56:1673]
# mokutil --sb-state
SecureBoot disabled
# rfkill list
0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
# sudo lshw -c network
  *-network UNCLAIMED
       description: Network controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:3c:00.0
       version: 1a
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
       resources: memory:87200000-87203fff
# apt info linux-firmware | grep Version
Version: 1.197.3

In launchpad it say that device [8086:2725] Subsystem [8086:4020] was added to linux-firmware 1.187.7. But lspic say mine is [1a56:1673], that I can not find anything in internet.

Edit:

This is what windows see, it come installed on from factory.

enter image description here

Trying to enable iwlwifi, still no logs:

# lsmod | grep iwlwifi
<emtpy>

# modinfo iwlwifi | grep -i version
srcversion:     C4766991DE91166408C39CE
vermagic:       5.11.0-34-generic SMP mod_unload modversions

# modprobe iwlwifi
<empty>

# dmesg | grep -i iwl
<empty>

Edit 3

I enable panic mode and clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git and copy into my /lib/firmware. Everything is the same with exception of

# lsmod | grep iwlwifi
iwlwifi               380928  0
cfg80211              892928  1 iwlwifi


Get this bounty!!!

#StackBounty: #20.04 #display #21.04 Squiggly/wavy/interlaced display

Bounty: 50

I’m on a MSI PE70 2QE Laptop with an NVIDIA Geforce GTX960M.

I was running Ubuntu 21.04 and since I’ve installed all the latest software updates my display is acting up.

It doesn’t flicker but it’s kind of squiggly looking interlacing or something (best description I could come up with :p).

I’m running a dual boot setup, and on Windows there’s no problem, so I guess I can rule out the display being broken.

I’ve tried installing proprietary drivers (several of them), tried rolling back the updates and even uninstalled Ubuntu and installed Ubuntu 20.04 but the problem persists now.

Hope someone can help me out!


Some pictures of the problem (pictures are all taken during startup but the problem persists when in UI/OS as well):
Image 1
Close
enter image description here


Get this bounty!!!

#StackBounty: #suspend #21.04 #acpi #msi Can't suspend: system resumes for unknown reason after ~40 minutes of sleep

Bounty: 100

I’ve bought new MSI Summit B15 which was supplied without OS and happily installed on it fresh Ubuntu 21.04. So far everything works pretty well (except couple of troubles with touchpad & no drivers for FP scanner but that’s a different story) except one pretty annoying issue: when I try to suspend the machine it suddenly wakes up in about ~40-60 minutes and start running fans full-speed. Not only it sometimes wakes up me if I happened to sleep nearby, it drains the battery over night, making suspend essentially useless.

I’ve tried to disable everything (see here how) but power button in /proc/acpi/wakeup, so it looks like this currently:

➜  ~ cat /proc/acpi/wakeup | grep enabled
PWRB      S4    *enabled   platform:PNP0C0C:00

It doesn’t help.

Here is part of syslog (here I’ve put system to suspend at 7:48 and it started fanning at 8:35 but I logged in later, only at 10:56):

Sep  5 07:48:00 rb-base tracker-store[6784]: OK
Sep  5 07:48:00 rb-base systemd[3246]: tracker-store.service: Succeeded.
Sep  5 07:48:01 rb-base kernel: [  146.937861] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base kernel: [  150.972633] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base kernel: [  150.977982] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base ModemManager[2119]: <info>  [sleep-monitor] system is about to suspend
Sep  5 07:48:05 rb-base kernel: [  150.997219] wlo1: deauthenticating from b0:4e:26:31:82:b8 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep  5 07:48:05 rb-base wpa_supplicant[1978]: wlo1: CTRL-EVENT-DISCONNECTED bssid=b0:4e:26:31:82:b8 reason=3 locally_generated=1
Sep  5 07:48:05 rb-base NetworkManager[1931]: <info>  [1630817285.6861] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-ifac
e-state: 'managed')
Sep  5 07:48:05 rb-base wpa_supplicant[1978]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Sep  5 07:48:07 rb-base systemd[1]: Reached target Sleep.
Sep  5 07:48:07 rb-base systemd[1]: Starting Suspend...
Sep  5 07:48:07 rb-base kernel: [  152.341436] PM: suspend entry (s2idle)
Sep  5 07:48:07 rb-base systemd-sleep[7072]: Suspending system...
Sep  5 07:48:07 rb-base systemd[1]: zsysd.service: Succeeded.
Sep  5 07:48:07 rb-base kernel: [  152.424613] Filesystems sync: 0.083 seconds
Sep  5 10:56:42 rb-base kernel: [  152.426323] Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep  5 10:56:42 rb-base kernel: [  152.428515] OOM killer disabled.
Sep  5 10:56:42 rb-base kernel: [  152.428516] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep  5 10:56:42 rb-base kernel: [  152.429676] printk: Suspending console(s) (use no_console_suspend to debug)
Sep  5 10:56:42 rb-base kernel: [  153.214718] ACPI: EC: interrupt blocked
Sep  5 10:56:42 rb-base kernel: [11468.660690] ACPI: EC: interrupt unblocked
Sep  5 10:56:42 rb-base kernel: [11469.338032] nvme nvme0: 8/0/0 default/read/poll queues
Sep  5 10:56:42 rb-base kernel: [11469.574414] OOM killer enabled.
Sep  5 10:56:42 rb-base kernel: [11469.574416] Restarting tasks ... done.
Sep  5 10:56:42 rb-base kernel: [11469.584884] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Sep  5 10:56:42 rb-base kernel: [11469.586402] thermal thermal_zone6: failed to read out thermal zone (-61)
Sep  5 10:56:42 rb-base systemd[1]: Condition check resulted in Run anacron jobs being skipped.
Sep  5 10:56:43 rb-base systemd-sleep[7072]: System resumed.
Sep  5 10:56:43 rb-base kernel: [11469.846714] PM: suspend exit
Sep  5 10:56:43 rb-base systemd[1]: systemd-suspend.service: Succeeded.
Sep  5 10:56:43 rb-base systemd[1]: Finished Suspend.
Sep  5 10:56:43 rb-base systemd[1]: Stopped target Sleep.
Sep  5 10:56:43 rb-base systemd[1]: Reached target Suspend.
Sep  5 10:56:43 rb-base systemd[1]: Stopped target Suspend.
Sep  5 10:56:43 rb-base NetworkManager[1931]: <info>  [1630828603.2303] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Sep  5 10:56:43 rb-base ModemManager[2119]: <info>  [sleep-monitor] system is resuming
Sep  5 10:56:43 rb-base NetworkManager[1931]: <warn>  [1630828603.5154] sup-iface[499bce01c63427b3,1,wlo1]: call-p2p-cancel: failed with P2P cancel failed
Sep  5 10:56:45 rb-base ModemManager[2119]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Sep  5 10:56:46 rb-base dbus-daemon[1927]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.90' (uid=1000 pid=3490 comm="/usr/bin/gnome-shell " label="unconfined")
Sep  5 10:56:46 rb-base systemd[1]: Starting Fingerprint Authentication Daemon...
Sep  5 10:56:46 rb-base dbus-daemon[1927]: [system] Successfully activated service 'net.reactivated.Fprint'
Sep  5 10:56:46 rb-base systemd[1]: Started Fingerprint Authentication Daemon.

(Here is the full log, in case I’ve removed something relevant)

As you can see, there’s no record at the moment the machine is actually woke up. So my next assumption is that something outside the OS causes wake-up. But system looks not suspended: e.g. monitor is lite up and login screen is shown when immediately when I open the lid, it usually takes some time to start login screen, when I open lid on sleeping system.

UPD1: Thanks to @David comment, although WOL itself is not relevant to my system (MSI Summit doesn’t even have an Ethernet card), I’ve figured out, that I have to search for some configuration in BIOS setup. And I found there "Wake on Thunderbolt™ device" entry which was enabled. I have 0 Thunderbolt™ devices but disabled the entry, just in case. This didn’t help though.

UPD2: It seams that /proc/acpi/wakeup just doesn’t work: as I mentioned earlier, I’ve disabled everything but power button in it, however, when I open the lid, computer still wakes up.


Get this bounty!!!

#StackBounty: #suspend #21.04 #acpi #msi Can't suspend: system resumes for unknown reason after ~40 minutes of sleep

Bounty: 100

I’ve bought new MSI Summit B15 which was supplied without OS and happily installed on it fresh Ubuntu 21.04. So far everything works pretty well (except couple of troubles with touchpad & no drivers for FP scanner but that’s a different story) except one pretty annoying issue: when I try to suspend the machine it suddenly wakes up in about ~40-60 minutes and start running fans full-speed. Not only it sometimes wakes up me if I happened to sleep nearby, it drains the battery over night, making suspend essentially useless.

I’ve tried to disable everything (see here how) but power button in /proc/acpi/wakeup, so it looks like this currently:

➜  ~ cat /proc/acpi/wakeup | grep enabled
PWRB      S4    *enabled   platform:PNP0C0C:00

It doesn’t help.

Here is part of syslog (here I’ve put system to suspend at 7:48 and it started fanning at 8:35 but I logged in later, only at 10:56):

Sep  5 07:48:00 rb-base tracker-store[6784]: OK
Sep  5 07:48:00 rb-base systemd[3246]: tracker-store.service: Succeeded.
Sep  5 07:48:01 rb-base kernel: [  146.937861] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base kernel: [  150.972633] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base kernel: [  150.977982] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep  5 07:48:05 rb-base ModemManager[2119]: <info>  [sleep-monitor] system is about to suspend
Sep  5 07:48:05 rb-base kernel: [  150.997219] wlo1: deauthenticating from b0:4e:26:31:82:b8 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep  5 07:48:05 rb-base wpa_supplicant[1978]: wlo1: CTRL-EVENT-DISCONNECTED bssid=b0:4e:26:31:82:b8 reason=3 locally_generated=1
Sep  5 07:48:05 rb-base NetworkManager[1931]: <info>  [1630817285.6861] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-ifac
e-state: 'managed')
Sep  5 07:48:05 rb-base wpa_supplicant[1978]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Sep  5 07:48:07 rb-base systemd[1]: Reached target Sleep.
Sep  5 07:48:07 rb-base systemd[1]: Starting Suspend...
Sep  5 07:48:07 rb-base kernel: [  152.341436] PM: suspend entry (s2idle)
Sep  5 07:48:07 rb-base systemd-sleep[7072]: Suspending system...
Sep  5 07:48:07 rb-base systemd[1]: zsysd.service: Succeeded.
Sep  5 07:48:07 rb-base kernel: [  152.424613] Filesystems sync: 0.083 seconds
Sep  5 10:56:42 rb-base kernel: [  152.426323] Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep  5 10:56:42 rb-base kernel: [  152.428515] OOM killer disabled.
Sep  5 10:56:42 rb-base kernel: [  152.428516] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep  5 10:56:42 rb-base kernel: [  152.429676] printk: Suspending console(s) (use no_console_suspend to debug)
Sep  5 10:56:42 rb-base kernel: [  153.214718] ACPI: EC: interrupt blocked
Sep  5 10:56:42 rb-base kernel: [11468.660690] ACPI: EC: interrupt unblocked
Sep  5 10:56:42 rb-base kernel: [11469.338032] nvme nvme0: 8/0/0 default/read/poll queues
Sep  5 10:56:42 rb-base kernel: [11469.574414] OOM killer enabled.
Sep  5 10:56:42 rb-base kernel: [11469.574416] Restarting tasks ... done.
Sep  5 10:56:42 rb-base kernel: [11469.584884] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Sep  5 10:56:42 rb-base kernel: [11469.586402] thermal thermal_zone6: failed to read out thermal zone (-61)
Sep  5 10:56:42 rb-base systemd[1]: Condition check resulted in Run anacron jobs being skipped.
Sep  5 10:56:43 rb-base systemd-sleep[7072]: System resumed.
Sep  5 10:56:43 rb-base kernel: [11469.846714] PM: suspend exit
Sep  5 10:56:43 rb-base systemd[1]: systemd-suspend.service: Succeeded.
Sep  5 10:56:43 rb-base systemd[1]: Finished Suspend.
Sep  5 10:56:43 rb-base systemd[1]: Stopped target Sleep.
Sep  5 10:56:43 rb-base systemd[1]: Reached target Suspend.
Sep  5 10:56:43 rb-base systemd[1]: Stopped target Suspend.
Sep  5 10:56:43 rb-base NetworkManager[1931]: <info>  [1630828603.2303] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Sep  5 10:56:43 rb-base ModemManager[2119]: <info>  [sleep-monitor] system is resuming
Sep  5 10:56:43 rb-base NetworkManager[1931]: <warn>  [1630828603.5154] sup-iface[499bce01c63427b3,1,wlo1]: call-p2p-cancel: failed with P2P cancel failed
Sep  5 10:56:45 rb-base ModemManager[2119]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Sep  5 10:56:46 rb-base dbus-daemon[1927]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.90' (uid=1000 pid=3490 comm="/usr/bin/gnome-shell " label="unconfined")
Sep  5 10:56:46 rb-base systemd[1]: Starting Fingerprint Authentication Daemon...
Sep  5 10:56:46 rb-base dbus-daemon[1927]: [system] Successfully activated service 'net.reactivated.Fprint'
Sep  5 10:56:46 rb-base systemd[1]: Started Fingerprint Authentication Daemon.

(Here is the full log, in case I’ve removed something relevant)

As you can see, there’s no record at the moment the machine is actually woke up. So my next assumption is that something outside the OS causes wake-up. But system looks not suspended: e.g. monitor is lite up and login screen is shown when immediately when I open the lid, it usually takes some time to start login screen, when I open lid on sleeping system.

UPD1: Thanks to @David comment, although WOL itself is not relevant to my system (MSI Summit doesn’t even have an Ethernet card), I’ve figured out, that I have to search for some configuration in BIOS setup. And I found there "Wake on Thunderbolt™ device" entry which was enabled. I have 0 Thunderbolt™ devices but disabled the entry, just in case. This didn’t help though.

UPD2: It seams that /proc/acpi/wakeup just doesn’t work: as I mentioned earlier, I’ve disabled everything but power button in it, however, when I open the lid, computer still wakes up.


Get this bounty!!!

#StackBounty: #kubuntu #steam #21.04 Why is "x86/split lock detection" spamming my syslog when Steam is running?

Bounty: 50

I have a ThinkPad X1C9 laptop connected to 3 displays via thunderbolt and an nVidia 1050Ti in an external GPU enclosure. My syslog is getting spammed with the following, why?

Googling CJobMgr led me to Steam. Closed Steam and it stopped. If I open Steam again it starts happening immediately.

[Tue Aug 10 10:17:42 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:44 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:45 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
alan@ac:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 21.04
Release:        21.04
Codename:       hirsute
alan@ac:~$ uname -a
Linux ac 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I have found the following resources during my search but they haven’t helped:

I have filed an issue upstream with the Steam client, as it’s the only thing that triggers this issue:


Get this bounty!!!

#StackBounty: #boot #drivers #intel-graphics #21.04 No driver Intel iRIS xe under Ubuntu 21.04

Bounty: 50

Since I have make the new Ubuntu update, I have a black screen when I start my HP laptop (11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz × 8 ) with a Intel iRIS xe GPU.

The only solution that I have find until now to work with my laptop is to put the "nomodeset" command in the grub but with this option, linux don’t used the Intel vendor driver and the driver that I can see in my config is a "llvmpipe (LLVM 12.0.0, 256 bits)"

I have reinstall my laptop one time with Secure Boot and one time without but I have always the same issue. I have try other solution like the "oibaf" drivers but always the same issue.

Here are info :

uname -r 
5.11.0-22-generic

lspci -nnk | grep -iA2 VGA
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
    DeviceName:  Onboard IGD
    Subsystem: Hewlett-Packard Company Iris Xe Graphics [103c:87fe]

inxi -G
Graphics:
  Device-1: Intel TigerLake GT2 [Iris Xe Graphics] driver: N/A 
  Device-2: IMC Networks HP TrueVision HD Camera type: USB driver: uvcvideo 
  Display: x11 server: X.Org 1.20.11 driver: loaded: fbdev 
  unloaded: modesetting,vesa resolution: 1920x1080~77Hz 
  OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) 
  v: 4.5 Mesa 21.2.0-devel (git-25ad699 2021-07-02 hirsute-oibaf-ppa) 

lshw -c video
*-display NON-RÉCLAMÉ     
       description: VGA compatible controller
       produit: TigerLake GT2 [Iris Xe Graphics]
       fabricant: Intel Corporation
       identifiant matériel: 2
       information bus: pci@0000:00:02.0
       version: 01
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: pciexpress msi pm vga_controller bus_master cap_list
       configuration : latency=0
       ressources : mémoireE/S:600-5ff mémoireE/S:400-3ff mémoire:6002000000-6002ffffff mémoire:4000000000-400fffffff portE/S:4000(taille=64) mémoire:c0000-dffff mémoire:4010000000-4016ffffff mémoire:4020000000-40ffffffff

Without this drivers, I can’t change the brighthess of my screen and everybody is a little bit to dark for me 🙂

Can somebody help me ?

Thanks you

Jean-Marc


Get this bounty!!!

#StackBounty: #kubuntu #21.04 Why is "x86/split lock detection" spamming my syslog

Bounty: 50

I have a ThinkPad X1C9 laptop connected to 3 displays via thunderbolt and an nVidia 1050Ti in an external GPU enclosure. My syslog is getting spammed with the following, why?

[Tue Aug 10 10:17:42 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:43 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:44 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28520 took a split_lock trap at address: 0xf21b3263
[Tue Aug 10 10:17:45 2021] x86/split lock detection: #AC: CJobMgr::m_Work/28558 took a split_lock trap at address: 0xf21b3263
alan@ac:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 21.04
Release:        21.04
Codename:       hirsute
alan@ac:~$ uname -a
Linux ac 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux


Get this bounty!!!