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
