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.
Works 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.
[ 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=off
Works 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
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...
Googling CJobMgr led m...
