On Sat, May 02, 2020 at 02:56:27PM +0100, Grzegorz Junka wrote: > > On 02/05/2020 14:15, Grzegorz Junka wrote: > > cpuid = 3 > > > > time = 1588422616 > > > > KDB: stack backtrace: > > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > > 0xfffffe00b27e86b0 > > > > vpanic() at vpanic+0x182/frame 0xfffffe00b27e8700 > > > > panic() at panic+0x43/frame ... > > > > sleepq_add() > > > > ... > > > > I see > > > > db> > > > > in the terminal. I tried "dump" but it says, Cannot dump: no dump > > device specified. > > > > Is there a guide how to deal wit those, i.e. to gather information > > required to investigate issues? > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscr...@freebsd.org" > > > OK, I found this handbook > https://www.freebsd.org/doc/en/books/developers-handbook/book.html#kerneldebug > > Obviously something must have been misconfigured that I can't dump the > core now. Is there anything I can fetch from the system while I am in > db> or I should just forget and restart?
It would be useful to see the output of "bt", "show lockchain" and "alltrace" if possible. The latter command will product a lot of output though. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
