New PC, ME errors

[macdr...@gmail.com]

Hi, 

I built a new PC with Debian and ME.

I'm trouble shooting an issue where the machine just hangs.

The hang appears random, but always after hour of up time. (Typically, 12 or more, sometimes a couple days.)

The system log shows this, is it a clue?

Dec 17 07:03:00 Motioneye3 kernel: microcode: microcode updated early to revision 0x24000026, date = 2023-09-26
Dec 17 07:03:00 Motioneye3 kernel: Linux version 6.1.0-28-amd64 (xxx) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22)
Dec 17 07:03:00 Motioneye3 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-28-amd64 root=UUID=fa28c875-7a8c-4122-aec5-369e16487c2d ro resume=UUID=975f9104-e799-4b4c-be06-680c969eba3c
Dec 17 07:03:00 Motioneye3 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

[StarbaseSSD]

What else are you running on it? Maybe UnRAID?

https://forums.unraid.net/topic/116791-kernel-x86split-lock-detection-ac/

Everything I see searching for the error goes back to UnRAID...

[macdr...@gmail.com]

Hmm...vanilla Debian 12. Never heard of Unraid.

[StarbaseSSD]

X64 or ARM?

In a VM?

In a docker container?

When you go into settings in mE, which version do you have for motion, motionEye, and OS showing?

I can try to reproduce the issue with the above info...

I have all 4 options available to me to test.

[macdr...@gmail.com]

X86_64

motionEye 0.43.1b2

Motion 4.7.0

OS 6.1.0-28-amd64

II don't think it is in any kind of container, unless the basic install instructions did that and it went over my head.

[StarbaseSSD]

I would open a new issue with motionEye Devs here:

https://github.com/motioneye-project/motioneye/issues

I am not seeing it with my Deb12/motion 4.5.1/motionEye0.43.1b2 or Deb10/motion 4.3.2/motionEye 0.42.1 as straight installs.