kernel: x86/split lock detection: #AC:

[alael]

This error warning message  is filling up my log running Unraid Version: 6.10.0-rc2  

 

I also see this on the boot process:

kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

 

diagnostics-20211204-1011.zip

Edited December 4, 2021 by alael

[Squid]

Post the diagnostics

[alael]

done

 

[SimonF]

4 hours ago, alael said:

This error warning message  is filling up my log running Unraid Version: 6.10.0-rc2  

 

I also see this on the boot process:

kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

 

diagnostics-20211204-1011.zip 139.42 kB · 0 downloads

I see similar messages but only when my Windows 11 VM is running. But dont see crashes.

 

Dec 4 14:02:38 computenode kernel: x86/split lock detection: #AC: CPU 3/KVM/23134 took a split_lock trap at address: 0xfffff8035e0c9808

[chrizzo]

Also same here, but with a WIN10 VM - Unraid 6.10.0.rc2

[SimonF]

Looks like it can be turned off if required.

 

Split-lock detection is enabled by default when it is supported by the hardware. However, system administrators have control over the feature: they can use a new kernel parameter (nosplit_lock_detect) at boot time to disable it. There is also a sysfs interface to disable it at runtime at /sys/devices/system/cpu/split_lock_detect.

[MadMatt337]

I just figured I would post here as well since I just noticed I am getting this same message flooding my syslog running 6.10.0-RC2, appears to be only when my Windows 10 VM is running (hard to tell as it is nearly always running) but I can test this further if I need to. I did have it down for a backup on Feb 24th @ 19:40-20:59 or so and the errors disappear during that timeframe so I am pretty confident in the relation as well. Attached my logs for reference in case it is helpful.

 

This is not causing me any issues as far as I can tell, system has been working well and is stable.

 

Should I be worried about doing anything at this time to get rid of these errors or just ignore them for now?

jarvis-diagnostics-20220302-1019.zip

[chrizzo]

Think you can ignore it.

my system is also absolutely stable, no issues so for.

[je82]

i have this, how do you disable it? no need to have it in the logs if it isnt affecting the system

started when i did windows vm on unraid Version: 6.10.3 

Edited September 20, 2022 by je82

[je82]

Interesting, i read here about what this means, essentially 2 threads doing something s

On 1/29/2022 at 11:26 PM, SimonF said:

Looks like it can be turned off if required.

 

Split-lock detection is enabled by default when it is supported by the hardware. However, system administrators have control over the feature: they can use a new kernel parameter (nosplit_lock_detect) at boot time to disable it. There is also a sysfs interface to disable it at runtime at /sys/devices/system/cpu/split_lock_detect.

Would adding split_lock_detect=off to the syslinux.cfg as such accomplish this?

 

Quote

append initrd=/bzroot split_lock_detect=off

 

Edited September 20, 2022 by je82

[SimonF]

12 minutes ago, je82 said:

Interesting, i read here about what this means, essentially 2 threads doing something s

Would adding split_lock_detect=off to the syslinux.cfg as such accomplish this?

 

 

I think. option is nosplit_lock_detect but not tried. it

Edited September 20, 2022 by SimonF

[je82]

16 minutes ago, SimonF said:

I think. option is nosplit_lock_detect but not tried. it

https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

search split_lock_detect

i guess ill try both when i have a chance at rebooting and see which one works

[je82]

On 9/20/2022 at 8:45 PM, je82 said:

adding split_lock_detect=off to the syslinux.cfg as such accomplish this?

 

just to be clear, this was the command that worked to silence these messages in the syslog.