protonscr

Dmesg spews errors while Steam client is running - x86/split lock detection

steamclosed
ValveSoftware/steam-for-linux#11755 · opened 2025-02-13 by tykinnison · updated 2025-02-13 · 1 comments · github
Ttykinnison 2025-02-13 github

Your system information

  • Steam client version (build number or date): 1738889325 - Steam Client Build Date: Thu, Feb 6 4:16 PM UTC -08:00
  • Distribution (e.g. Ubuntu): EndeavourOS, updated 02.13.2025
  • Opted into Steam client beta?: [Yes/No] Yes
  • Have you checked for system updates?: [Yes/No] 3 days ago
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: Nvidia 3080

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

Dmesg spews hundreds of error messages per second while Steam client is running. Like so...
[Feb13 14:43] x86/split lock detection: #DB: CHTTPClientThre/3034 took a bus_lock trap at address: 0xe783c304
I expect it not do that.

Steps for reproducing this issue:

  1. sudo dmesg -we
  2. Start Steam client
  3. Observe dmesg output
Kkisak-valve maintainer 2025-02-13 github

Hello @tykinnison, this is effectively the same issue as #8003. Closing as a duplicate.

Nothing extracted yet.