geeksville
UBUniversal Blue
•Created by geeksville on 3/12/2025 in #🛟bazzite-help
Amdgpu 6.13.6, kernel fault while playing Satisfactory
okay. With the PSR stuff disabled can play much longer, but after a couple more hours of play a different fault. Details posted in comment below.
OS:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:testing
Digest: sha256:1c3f9cfb10d64c5516badd4e03df81b68df292e391756f18c1b4446784c80e72
Version: testing-41.20250311 (2025-03-11T05:58:11Z)
kernel:
Linux version 6.13.6-101.bazzite.fc41.x86_64 (builder@c17c044c8371) (gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-7), GNU ld version 2.43.1-5.fc41) #1 SMP PREEMPT_DYNAMIC Sun Mar 9 11:06:13 UTC 2025 [ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt8)/ostree/default-9555151c1eb5e72f6ee3d51a275ce61145fa3426ade07b90beac4b014577e8f6/vmlinuz-6.13.6-101.bazzite.fc41.x86_64 rhgb root=UUID=bee0ab4d-eb88-4bf8-af87-ae420b2ffac8 rootflags=subvol=00 rw bluetooth.disable_ertm=1 preempt=full amdgpu.ppfeaturemask=0xfff7ffff iomem=relaxed module_blacklist=wl module_blacklist=wl split_lock_detect=off no_console_suspend amdgpu.dcdebugmask=0x10 ostree=/ostree/boot.0/default/9555151c1eb5e72f6ee3d51a275ce61145fa3426ade07b90beac4b014577e8f6/0>
15 replies
UBUniversal Blue
•Created by geeksville on 3/11/2025 in #🛟bazzite-help
Misc Z13/395+ CPU problems.
So I'm finally getting around to playing a game on this thing (woot! Satisfactory factory goodness).
Alas, after about 30 minutes of play (steam + proton), the wayland user session suddenly locked up. But fortunately the keycombo to enter a virtual console worked (and alas - I don't have another machine here with me where I could have sshed).
Here's the dmseg logs I could snarf. Nasty amdgpu errors:
134 replies
UBUniversal Blue
•Created by geeksville on 3/11/2025 in #🛟bazzite-help
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.
10 replies
UBUniversal Blue
•Created by geeksville on 3/10/2025 in #🛟bazzite-help
Z13 Flow 2025: Back camera doesn't work/appear in UI
Not an issue for me, but in case it matters to others.
This laptop has three cameras, one user facing camera, one user facing IR camera, one back/lid based camera.
The back camera doesn't appear anywhere in the UI (i.e. if you use the Cheeze app only the other two cameras are listed). Also, less important but the camera order is wrong - the IR camera is first, which makes apps default to use that camera (which is almost certainly the wrong choice).
Someday I'll look into using/adding the Howdy camera based user auth/login...
2 replies
UBUniversal Blue
•Created by geeksville on 3/10/2025 in #🛟bazzite-help
Z13 Flow 2025: Bluetooth kernel exceptions on wake
This isn't urgent for me (because I think the 6.14 kernel might fix this for 'free'). But FYI for anyone searching:
Bluetooth on the Z13 Flow 2025 (Halo 395+ CPU + mt7925e wifi/bt chip) 'mostly' works. The only problem I've seen is that if BT wake due to keyboard/bt-mouse packets will often cause a nasty kernel exception in dmesg. Only sometimes does that exception result in user-space badness/lockup.
I'll add the exception log to this the next time it happens (but really - I think not worth investigating until after 6.14 kernel is in use)
6 replies