Date: Sun, 3 May 2020 00:19:58 +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: <868e136f-7a4a-dd64-c6de-35a30332fcd2@gjunka.com> In-Reply-To: <20200502201840.GA48096@raichu> References: <a5cc091b-3694-f822-4573-46cdc1f0736d@gjunka.com> <93c3b478-3648-a056-f776-8bceafdebc98@gjunka.com> <20200502201840.GA48096@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/05/2020 21:18, Mark Johnston wrote: >> 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. Sorry, had to restart. I tried "netdump -s someIP -g someGateway which forced netdump into a loop (of requesting ARP for someIP and failing) and couldn't stop it. I only have the photo of the crash itself which ends at and sleepq_add before going to panic. I can hardtranscribe if it might be of any use. --GrzegorzJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?868e136f-7a4a-dd64-c6de-35a30332fcd2>