Steam causes dmesg log message spam
So on my Flow Z13 2025 with bazzite I see lots of the following in the dmesg logs whenever Steam is running:
[ 5417.450523] x86/split lock detection: #DB: CHTTPClientThre/7114 took a bus_lock trap at address: 0xf3fcd304
[ 5417.450683] x86/split lock detection: #DB: CHTTPClientThre/7114 took a bus_lock trap at address: 0xf3fcd304
Apparently the root cause is sloppy lock management in the Steam app. There is a long ignored github issue for it and this stack overflow article. https://askubuntu.com/questions/1356884/why-is-x86-split-lock-detection-spamming-my-syslog-when-steam-is-running
As mentioned in that article I 'fixed' this problem by turning the messages off with a kernel flag.
sudo rpm-ostree kargs --append=split_lock_detect=offWorks great. Any interest in having this be the default bazzite behavior? If so I can dig around and find the right place to do this more cleanly and send in a PR.
Ask Ubuntu
Why is "x86/split lock detection" spamming my syslog when Steam is ...
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 m...
3 Replies
its a bug in the kernel causing that
it will be fixed upstream from what i was told in the vfio grapevine
nvm that patchset is not related, if the dmesg log annoys you, use the karg, not something we will turn off by default though unless it actually causes issues
it does making reading dmesg for other reasons almost impossible if Steam is running 😉
sudo dmesg | grep -v "split lock"
not everyone is affected though
its a bit different than the msrs reporting we turn off when you enable virtualization
because you need to ignore msrs calls from the vm to not have some versions of windows not bluescreen
but since youre ignoring the msrs call the kernel will now scream from the rooftops that it is ignoring the call 🤣
so there we also turn off the reporting of ignored msrs calls