Kai Krakow

I'm seeing this, too. Steam Beta as of 2021-12-08: ```dmesg [84130.796009] x86/split lock detection: #AC: CHTTPClientThre/3752 took a split_lock trap at address: 0xf20bb273 [84130.944128] x86/split lock detection: #AC: CJobMgr::m_Work/3261 took...

@kisak-valve This affects all distros with a kernel that has split lock detection enabled, and with CPUs that can detect and report this situation to the kernel (although earlier CPUs...

> Can you re-test on the Steam Client Beta? I can still see it but it seems much less noisy: ``` [ 112.572659] x86/split lock detection: #AC: CHTTPClientThre/5662 took a...

Some Assassins Creed games also throw that message but I'm not sure if wine or the Steam client could do something about it. In the light of future kernels killing...

Okay, so I'll retest the games I've seen logging this in the past - and report back here? Or per game?

Here are two other occurrences, one with different address, one with different thread name: ``` [272502.307107] x86/split lock detection: #AC: CIPCServer::Thr/5510 took a split_lock trap at address: 0xf218472d [272502.330099] x86/split...

These seem the only messages left after a reboot, HTH: ``` [ 26.485020] x86/split lock detection: #AC: CHTTPClientThre/3024 took a split_lock trap at address: 0x565fc3e3 [ 49.462890] x86/split lock detection:...

Actually, since the introduction of the new big picture mode into the client (although I don't use it), the spamming has increased again. But this is only one part of...

I'm the maintainer of the Gentoo ebuild. @Zygo if you don't mind I come up with a suggestion, maybe also fixing the other problems mentioned here.

That's to match upstream. Bees itself uses the Git tag which is prefixed by "v".