The system was locked up but good--I had to hold down power to turn it off and get it back under control. Upon restart, this line was in logs 20+ times at the time of the problem:
x86/split lock detection: #DB: CHTTPClientThre/4401 took a bus_lock trap at address: 0xf3baac54
Does this provide any useful information for making a permanent resolution?
Did a websearch for you and found this, relating to Steam. Were you running Steam pre-lockup?
Not sure if it is relevant or not, but here is: https://askubuntu.com/questions/1356884/why-is-x86-split-lock-detection-spamming-my-syslog-when-steam-is-running
I was, in fact. Looks like a bug was submitted to Valve about this years ago, but it persists. I'm NOT seeing that this typically hangs the whole system, so it could just be a fluke (after all, I've not had frequent hangs) that it hung with the split lock spam going. Thanks for your link, @zabadabadoo. I need to work out how to kill split lock detection I guess, since Valve doesn't seem inclined to fix this and it spams logs.
I have read, in other related items, that you can turn split lock detection = off as kernel parameter. e.g. Has anyone run into split_lock_detect? - #2 by ricklinux - Kernel, boot, graphics & hardware - EndeavourOS
Maybe worth further investigation, if continued to be problematic.
Yeah, that's what I need to work out, thank you for digging it up. I'm not normally quite this lazy, but during the work day I can't delve into things quite as much as I might like. I appreciate the help!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.