Re: Kernel crash before login prompt

The SoC has 4 CPU’s, but we have restricted it to only one by disabling other 3.

So the cpu value should be 0, I can confirm, with a print, because we are not getting the function frame for the functions calling __mtx_lock_spin_flags

Regards
Faisal



Juniper Business Use Only

From: andrew@fubar.geek.nz <andrew@fubar.geek.nz>
Date: Thursday, 29 June 2023 at 20:49
To: Sha Faisal <sfaisal@juniper.net>
Cc: freebsd-arm@FreeBSD.org <freebsd-arm@freebsd.org>, Steve Kiernan <stevek@juniper.net>, Mahesh Vardhamanaiah <maheshmv@juniper.net>, Amit Verma <amitv@juniper.net>
Subject: Re: Kernel crash before login prompt
[External Email. Be cautious of content]


On 2023-06-29 16:03, Sha Faisal wrote:
> Hello Andrew,
>
> The addr2line for the address points to,
>
> [sfaisal@svl-bsdx-02 /b/sfaisal/stable_main/src]$ addr2line -e
> ../obj/arm64/juniper/kernels/JNPR-ARM64-WIT/kernel/kernel.full -f
> 0xffff0000002244dc
>
> sched_add
>
> /b/sfaisal/stable_main/src/sys/kern/sched_ule.c:1309
>
> Sched_setcpu is the exact function which calls
> TDQ_LOCK(__mtx_lock_spin_flags) , and sched_setcpu is an inline called
> from sched_add()

What cpu is being passed in to sched_setcpu?

Andrew