Date: Sat, 2 May 2020 07:40:18 -0700 From: Conrad Meyer <cem@freebsd.org> To: Grzegorz Junka <list1@gjunka.com> Cc: freebsd-current <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: <CAG6CVpUbcuNePnQzWXLtsmPkuKQeDxEkk%2B4RwNXm=PO-Yd7OBg@mail.gmail.com> In-Reply-To: <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com> References: <a5cc091b-3694-f822-4573-46cdc1f0736d@gjunka.com> <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Grzegorz, If you have another machine connected by network that you can install and start netdumpd on, and; ipv4 configured on a supported network device before the machine paniced; and a recent CURRENT; you should be able to initiate a kernel dump over the network with 'netdump -s server-ip' in DDB. In more complicated situations you might also need to specify '-g gateway-ip -c client-ip -i interface', but for servers on the LAN or available via the default gateway route, the former ought to work. Best, Conrad On Sat, May 2, 2020 at 6:56 AM Grzegorz Junka <list1@gjunka.com> 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-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 > > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUbcuNePnQzWXLtsmPkuKQeDxEkk%2B4RwNXm=PO-Yd7OBg>