On 2024-10-14, Ian Chilton <i...@ichilton.co.uk> wrote:
>
> Hi,
>
> On Mon, 14 Oct 2024, at 1:15 PM, Janne Johansson wrote:
>> Mostly when boxes crash into ddb{0}> the text above goes "please run
>> these two commands to help debug this issue", so typing those and
>> recording the output could be helpful in order to diagnose what it was
>> doing when it crashed.
>
> Thanks, thought I only have serial console access so upon opening it I only
> see the prompt.
>
> Is there a command to view that info retrospectively?
These would be a good start:
show panic
ps /o (to show which procs are currently running on each cpu)
ps (to show all procs on the system)
trace
then switch to each cpu (mach ddbcpu 0, mach ddbcpu 1, etc) -
ddb should show a trace for each one.
A quick outline of what networking is used on the system might be useful
too (pppoe as you said - any wg? ipsec? trunk/bridge/carp/...?)
--
Please keep replies on the mailing list.
