Re: Random system freezes with Linux 6.12 + Xenomai 3.3.1 on Intel Ultra 5 125H

Yes, I have only installed the kernel with Dovetail and Cobalt patches. No =
user-space programs linked against Cobalt are running.

Liuyang

> From: "Jan Kiszka"<[email protected]>
> Date:=C2=A0 Fri, Jul 31, 2026, 14:10
> Subject:=C2=A0 Re: Random system freezes with Linux 6.12 + Xenomai 3.3.1 =
on Intel Ultra 5 125H
> To: "=E5=88=98=E6=9D=A8"<[email protected]>
> Cc: "xenomai"<[email protected]>, "=E5=AE=8B=E5=81=A5=E7=8E=AE"<son=
[email protected]>, "=E6=9D=8E=E5=B0=8F=E5=AE=81"<lixiaoning@sinsegy=
e.com.cn>, "=E9=A9=AC=E5=90=9B"<[email protected]>
> On 31.07.26 08:01, =E5=88=98=E6=9D=A8 wrote:
> > Hello Jan,
> > =C2=A0=C2=A0=C2=A0 No Xenomai user=E2=80=91space programs are running o=
n the customer=E2=80=99s system.
> >=C2=A0
>=C2=A0
> So, you are getting a stall in the absence of any Xenomai load, but
> while running a Xenomai-enabled kernel?
>=C2=A0
> Another thing you can try is turning on debugging switches of the
> kernel, specifically
>=C2=A0
> https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master=
/cfg/lock-debugging.cfg?ref_type=3Dheads
>=C2=A0
> Jan
>=C2=A0
> >> From: "Jan Kiszka"<[email protected]>
> >> Date:=C2=A0 Fri, Jul 31, 2026, 13:44
> >> Subject:=C2=A0 Re: Random system freezes with Linux 6.12 + Xenomai 3.3=
.1 on Intel Ultra 5 125H
> >> To: "=E5=88=98=E6=9D=A8"<[email protected]>
> >> Cc: "xenomai"<[email protected]>, "=E5=AE=8B=E5=81=A5=E7=8E=AE"<=
[email protected]>, "=E6=9D=8E=E5=B0=8F=E5=AE=81"<lixiaoning@sins=
egye.com.cn>, "=E9=A9=AC=E5=90=9B"<[email protected]>
> >> On 31.07.26 06:25, =E5=88=98=E6=9D=A8 wrote:
> >>> Hello,
> >>> I am using Linux kernel 6.18 with Xenomai 3.3.1. I have set i915.mode=
set=3D0=C2=A0in GRUB to prevent the i915 driver from loading.
> >>> Since trace=E2=80=91cmd logs cannot be dumped when the kernel hangs, =
I configured the following sysctl parameters:
> >>> plaintext
> >>> =C2=A0
> >>> sudo=C2=A0sysctl -w kernel.panic_on_rcu_stall=3D1
> >>> sudo=C2=A0sysctl -w kernel.ftrace_dump_on_oops=3D1
> >>> sudo=C2=A0sysctl -w kernel.panic=3D0
> >>> =C2=A0
> >>> The full serial log is attached. Could you please help analyze whethe=
r the log contains sufficient information for troubleshooting? Thank you.
> >> =C2=A0
> >> I'm missing cobalt events other cores and an annotation inside the tra=
ce
> >> where the error was noticed. That's why I proposed a different recordi=
ng
> >> method.
> >> =C2=A0
> >> Also, as the RCU stall detection may be delayed too much to still see
> >> normal operation in the trace, you might have to tune the timeout
> >> (https://docs.kernel.org/RCU/stallwarn.html#fine-tuning-the-rcu-cpu-st=
all-detector)
> >> until we find an earlier problem indicator.
> >> =C2=A0
> >> Jan
> >> =C2=A0
> >> --=C2=A0
> >> Siemens AG, Foundational Technologies
> >> Linux Expert Center
> >> =C2=A0
>=C2=A0
>=C2=A0
> --=C2=A0
> Siemens AG, Foundational Technologies
> Linux Expert Center
>=C2=A0