Date: Sat, 2 May 2020 14:56:27 +0100 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-current@freebsd.org Subject: Re: panic: Assertion lock == sq->sq_lock failed at /usr/src-13/sys/kern/subr_sleepqueue.c:371 Message-ID: <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com> In-Reply-To: <a5cc091b-3694-f822-4573-46cdc1f0736d@gjunka.com> References: <a5cc091b-3694-f822-4573-46cdc1f0736d@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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-unsubscribe@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? GrzegorzJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?93c3b478-3648-a056-f776-8bceafdebc98>