@Andi OK so it still trips but at least the dump is longer now:
[ 48.070785] x86/split lock detection: #AC: CJobMgr::m_Work/4188 took a split_lock trap at address: 0xe768347f
[ 48.151575] x86/split lock detection: #AC: CJobMgr::m_Work/4200 took a split_lock trap at address: 0xe768347f
[ 48.830151] x86/split lock detection: #AC: CJobMgr::m_Work/4274 took a split_lock trap at address: 0xe768347f
[ 50.154695] x86/split lock detection: #AC: CJobMgr::m_Work/4392 took a split_lock trap at address: 0xe768347f
[ 62.952187] x86/split lock detection: #AC: IPC:CSteamEngin/4183 took a split_lock trap at address: 0xe76834ba
[ 80.611973] umip: ChaosGate.exe[5397] ip:6ffff686aa76 sp:6357f9d0: SGDT instruction cannot be used by applications.
[ 80.611981] umip: ChaosGate.exe[5397] ip:6ffff686aa76 sp:6357f9d0: For now, expensive software emulation returns the result.
[ 80.616544] umip: ChaosGate.exe[5397] ip:6fffeb42bb50 sp:6357f9d0: SGDT instruction cannot be used by applications.
[ 80.616548] umip: ChaosGate.exe[5397] ip:6fffeb42bb50 sp:6357f9d0: For now, expensive software emulation returns the result.
[ 81.334429] umip: ChaosGate.exe[5361] ip:6fffe874c11e sp:10f6c8: SGDT instruction cannot be used by applications.
[ 81.357831] x86/split lock detection: #AC: ChaosGate.exe/5361 took a split_lock trap at address: 0x6fffe5f51242
[ 84.552845] x86/split lock detection: #AC: ChaosGate.exe/5554 took a split_lock trap at address: 0x6ffff6801001
[ 89.917136] x86/split lock detection: #AC: Loading.Preload/5471 took a split_lock trap at address: 0x6ffff6a3aee0
[ 673.720113] BTRFS info (device dm-2): qgroup scan completed (inconsistency flag cleared)
[ 907.829729] umip_printk: 51 callbacks suppressed
[ 907.829732] umip: ChaosGate.exe[5361] ip:6ffff4fc53a0 sp:10e0c8: SGDT instruction cannot be used by applications.
[ 907.829737] umip: ChaosGate.exe[5361] ip:6ffff4fc53a0 sp:10e0c8: For now, expensive software emulation returns the result.
[ 7778.421556] umip: ChaosGate.exe[13366] ip:6ffff686aa76 sp:6357f9d0: SGDT instruction cannot be used by applications.
[ 7778.421561] umip: ChaosGate.exe[13366] ip:6ffff686aa76 sp:6357f9d0: For now, expensive software emulation returns the result.
[ 7778.425809] umip: ChaosGate.exe[13366] ip:6fffeb42bb50 sp:6357f9d0: SGDT instruction cannot be used by applications.
[ 7778.425811] umip: ChaosGate.exe[13366] ip:6fffeb42bb50 sp:6357f9d0: For now, expensive software emulation returns the result.
[ 7778.499061] umip: ChaosGate.exe[13330] ip:6fffe874c11e sp:10f6c8: SGDT instruction cannot be used by applications.
[ 7778.516548] x86/split lock detection: #AC: ChaosGate.exe/13330 took a split_lock trap at address: 0x6fffe5f51242
[ 7781.596951] x86/split lock detection: #AC: ChaosGate.exe/13562 took a split_lock trap at address: 0x6ffff6801001
[ 7786.871080] x86/split lock detection: #AC: Loading.Preload/13448 took a split_lock trap at address: 0x6ffff6a3aee0
[ 7911.623629] i915 0000:03:00.0: [drm] GPU HANG: ecode 12:1:84dfd7f7, in ChaosGate.exe [13330]
[ 7911.623637] i915 0000:03:00.0: [drm] ChaosGate.exe[13330] context reset due to GPU hang
[ 7922.254173] umip_printk: 41 callbacks suppressed
[ 7922.254176] umip: ChaosGate.exe[13330] ip:6ffff4fc53a0 sp:10d0c8: SGDT instruction cannot be used by applications.
[ 7922.254182] umip: ChaosGate.exe[13330] ip:6ffff4fc53a0 sp:10d0c8: For now, expensive software emulation returns the result.
Modules loaded:
$ lsmod|grep i915
i915 4284416 115
i2c_algo_bit 24576 2 xe,i915
drm_buddy 20480 2 xe,i915
ttm 110592 3 drm_ttm_helper,xe,i915
drm_display_helper 282624 2 xe,i915
cec 94208 3 drm_display_helper,xe,i915
video 77824 4 asus_wmi,asus_nb_wmi,xe,i915
Some Ideas and thoughts about the new Bitwig 5.2 beta. Compressor+ things, OVER clipper and the new Shift Register in action.
@ptesarik @vbabka the more recent issue was this but i’m still working on the root cause (just haven’t had yet time to spin): https://social.kernel.org/notice/AhAkgNAoOXUOD2ns4u
In this case it could be either or both upstream and downstream issue but I’m not sure. @timojyrinki said that perhaps xe driver is not in use but now that i checked:
$ lsmod|grep i915
i915 4202496 69
i2c_algo_bit 20480 2 xe,i915
drm_buddy 20480 2 xe,i915
ttm 110592 3 drm_ttm_helper,xe,i915
drm_display_helper 245760 2 xe,i915
cec 90112 3 drm_display_helper,xe,i915
video 77824 4 asus_wmi,asus_nb_wmi,xe,i915
I’m not a graphics driver expert but for me it looks based on loaded modules that OpenSUSE does actually select XE driver correctly but I could also understand something incorrectly. On this issue I’ll compile drm-tip as suggested in the thread and hopefully make some further conclusions.
The other issue I need to backtrack that from my mastodon spam :-)
Alastair captures one of the biggest problems with the current RISC-V spec. When I looked into this a while back I was (almost) shocked at the lack of rigor and state of the tooling. I say almost because I expected it, but was still sad. Read his blog.
Incredible research at BlackHat Asia today by Tong Liu and team from the Institute of Information Engineering, Chinese Academy of Sciences (在iie.ac.cn 的电子邮件经过验证)
A dozen+ RCEs on popular LLM framework libraries like LangChain and LlamaIndex - used in lots of chat-assisted apps including GitHub. These guys got a reverse shell in two prompts, and even managed to exploit SetUID for full root on the underlying VM!