x86 split locks with cpu

[boxieee]

asus z790
13600k i5
32gbram

CPU(s) 20 x 13th Gen Intel(R) Core(TM) i5-13600K (1 Socket)

Kernel Version Linux 6.2.16-11-bpo11-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-11~bpo11+2 (2023-09-04T14:49Z)

PVE Manager Version pve-manager/7.4-17/513c62be

Oct 26 13:43:07 Prox1 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Oct 26 13:43:12 Prox1 kernel: x86/split lock detection: #AC: CPU 3/KVM/1350 took a split_lock trap at address: 0x7eefe050
Oct 26 13:43:12 Prox1 kernel: x86/split lock detection: #AC: CPU 1/KVM/1348 took a split_lock trap at address: 0x7eefe050
Oct 26 13:43:12 Prox1 kernel: x86/split lock detection: #AC: CPU 2/KVM/1349 took a split_lock trap at address: 0x7eefe050
Oct 26 13:43:12 Prox1 kernel: x86/split lock detection: #AC: CPU 5/KVM/1352 took a split_lock trap at address: 0x7eefe050
Oct 26 13:43:12 Prox1 kernel: x86/split lock detection: #AC: CPU 4/KVM/1351 took a split_lock trap at address: 0x7eefe050
Oct 26 13:43:21 Prox1 kernel: x86/split lock detection: #AC: CPU 1/KVM/1740 took a split_lock trap at address: 0x7ef3e050
Oct 26 13:43:25 Prox1 kernel: x86/split lock detection: #AC: CPU 1/KVM/1985 took a split_lock trap at address: 0x7ef3e050
Oct 26 13:43:27 Prox1 kernel: x86/split lock detection: #AC: CPU 0/KVM/1347 took a split_lock trap at address: 0x749edb26
Oct 26 13:43:39 Prox1 kernel: x86/split lock detection: #AC: CPU 1/KVM/2195 took a split_lock trap at address: 0x7ef1e050
Oct 26 13:43:39 Prox1 kernel: x86/split lock detection: #AC: CPU 3/KVM/2197 took a split_lock trap at address: 0x7ef1e050
Oct 26 13:43:50 Prox1 kernel: x86/split lock detection: #AC: CPU 0/KVM/1738 took a split_lock trap at address: 0x119c757
Oct 26 13:44:05 Prox1 kernel: x86/split lock detection: #AC: CPU 0/KVM/2194 took a split_lock trap at address: 0x713baa8d

is this normal??

 

[Neobin]

See here (especially the answers/explanations from @sterzy):
https://forum.proxmox.com/threads/x86-split-lock-detection.111544

 

[boxieee]

## Oct 27 13:28:00 Prox1 kernel: x86/split lock detection: #AC: CPU 3/KVM/2149 took a split_lock trap at address: 0x7ef1e050

## systemd,1
└─kvm,2110 -id 108 -name NrvAgentDvrWin10,debug-threads=on -no-shutdown -chardevsocket,id=qmp,path=/var/run/qemu-server/108.qmp,server=on,wai
└─{kvm},2149

so where do i exactly take the lens to the vm? i mean how do i find out what in vm 108
is causing this?

 

[sterzy]

so where do i exactly take the lens to the vm? i mean how do i find out what in vm 108

There isn't really a straight forward way to do that. From what I can tell this is a Windows 10 VM? I tried to look around what is currently the best way to find misaligned memory access from a user's perspective (not a developer's!). However, I haven't found much, especially not in cases where you analyze a VM, which adds at least one layer of indirection. Your best bet may be to turn off one task at a time and see if that stops the messages from appearing.

However, even then there isn't much you can do other than contact the vendor of said software and tell them to fix it.

 

[boxieee]

well my ui slows down too if i leave the system for some time.
open ip and "Linux PAM standard authentication" comes after some time and login.
open shell then again it takes sometime.
open hardware of any vm takes some time, after login leave it for 2 minutes speed in ui is fine.
same with all browsers or any machine.
cpu is at 9% i5 3700k
ram is used 74% 32gb ddr5
hdd sppeds 7000m read 5800write nvme. 980 pro
all disks test okay.
changed the lancard too.

i have a few windows vms , access them from rdp they are fine
iperf is goo approx 800-900

is it the 6.2 kernel