Date: Mon, 12 Feb 2024 13:44:36 -0500 From: Michael Butler <imb@protected-networks.net> To: John Baldwin <jhb@FreeBSD.org>, Mark Millard <marklmi@yahoo.com>, FreeBSD ARM List <freebsd-arm@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, Bakul Shah <bakul@iitbombay.org> Subject: Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: <pcib1 memory window> request" leads to panic Message-ID: <0b289f85-152b-45b2-a81e-ff34e398c964@protected-networks.net> In-Reply-To: <b060f465-57ef-47cf-9a4f-30f6f39fbf62@FreeBSD.org> References: <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5.ref@yahoo.com> <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5@yahoo.com> <2FE8FA48-180B-4F0D-BCD8-F7F33053B0F7@iitbombay.org> <986D2CD6-6241-4EBE-8BD2-9821AB693BA7@yahoo.com> <b0416b04-68a1-4aa5-9e9c-4d8a82279ac8@protected-networks.net> <b060f465-57ef-47cf-9a4f-30f6f39fbf62@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/12/24 12:36, John Baldwin wrote:
[ .. trimmed .. ]
> Short of a stack trace, you can at least use lldb or gdb to lookup
> the source line associated with the faulting instruction pointer (as
> long as it isn't in a kernel module), e.g. for gdb you would use 'gdb
> /boot/kernel/kernel' and then 'l *<instruction pointer address>',
> e.g. from above: 'l *0xffffffff80acb962'
I still didn't manage to get a core but .. does this make any sense in
htis context?
(kgdb) l *0xffffffff80acb962
0xffffffff80acb962 is in cc_conn_init
(/usr/src/sys/amd64/include/counter.h:92).
87 static inline void
88 counter_u64_add(counter_u64_t c, int64_t inc)
89 {
90
91 KASSERT(IS_BSP() || c != EARLY_COUNTER, ("EARLY_COUNTER
used on AP"));
92 zpcpu_add(c, inc);
93 }
94
95 #endif /* ! __MACHINE_COUNTER_H__ */
96
Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b289f85-152b-45b2-a81e-ff34e398c964>