InnoDB: Semaphore wait has lasted > 600 seconds.

2023-09-02 20:42:42 0 [Note] InnoDB: A semaphore wait:
--Thread 140233390483200 has waited at lock0lock.cc line 3800 for 76.00 seconds the semaphore:
Mutex at 0x55e8cc71c080, Mutex LOCK_SYS created ./storage/innobase/lock/lock0lock.cc:461, lock var 2

InnoDB: Pending reads 0, writes 0
2023-09-02 20:42:42 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
230902 20:42:42 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.5.19-MariaDB-0+deb11u2-log source revision: f8a85af8ca1c937b8d4f847477bd282f80251cde
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=152
max_threads=153
thread_count=154
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467880 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x49000
??:0(my_print_stacktrace)[0x55e8cb61516e]
??:0(handle_fatal_signal)[0x55e8cb10df45]
??:0(__restore_rt)[0x7f8ae3b48140]
??:0(gsignal)[0x7f8ae3680ce1]
??:0(abort)[0x7f8ae366a537]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55e8caded205]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55e8cade3bfe]
??:0(tpool::thread_pool_generic::timer_generic::execute(void*))[0x55e8cb5b6d78]
??:0(tpool::task::execute())[0x55e8cb5b7f32]
??:0(tpool::thread_pool_generic::worker_main(tpool::worker_data*))[0x55e8cb5b5c2f]
??:0(std::error_code::default_error_condition() const)[0x7f8ae3a2eed0]
??:0(start_thread)[0x7f8ae3b3cea7]
??:0(clone)[0x7f8ae3743a2f]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 128073 128073 processes
Max open files 32768 32768 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 128073 128073 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core

Kernel version: Linux version 5.10.0-25-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.191-1 (2023-08-16)

2023-09-02 20:43:11 0 [Note] Starting MariaDB 10.5.19-MariaDB-0+deb11u2-log source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 1183975