From owner-freebsd-current@freebsd.org Sat May 2 19:43:58 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C752D2C06F5 for ; Sat, 2 May 2020 19:43:58 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49F01B2mhbz4Ydt for ; Sat, 2 May 2020 19:43:58 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 042Jhom6006512 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 2 May 2020 12:43:57 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Grzegorz Junka Subject: Re: panic: Assertion lock == sq->sq_lock failed at /usr/src-13/sys/kern/subr_sleepqueue.c:371 Date: Sat, 02 May 2020 12:43:56 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49F01B2mhbz4Ydt X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.87 / 15.00]; NEURAL_HAM_MEDIUM(-0.91)[-0.909,0]; NEURAL_HAM_LONG(-0.97)[-0.965,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2020 19:43:58 -0000 On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka list1@gjunka=2Ecom said > On 02/05/2020 14:56, Grzegorz Junka wrote: > > > > On 02/05/2020 14:15, Grzegorz Junka wrote: > >> cpuid =3D 3 > >> > >> time =3D 1588422616 > >> > >> KDB: stack backtrace: > >> > >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame=20 > >> 0xfffffe00b27e86b0 > >> > >> vpanic() at vpanic+0x182/frame 0xfffffe00b27e8700 > >> > >> panic() at panic+0x43/frame =2E=2E=2E > >> > >> sleepq_add() > >> > >> =2E=2E=2E > >> > >> I see > >> > >> db> > >> > >> in the terminal=2E I tried "dump" but it says, Cannot dump: no dump=20 > >> device specified=2E > >> > >> Is there a guide how to deal wit those, i=2Ee=2E to gather information=20 > >> required to investigate issues? > > >=20 > Another thing is that I don't quite understand why the crash couldn't be= =20 > dumped=2E >=20 > root@crayon2:~ # swapinfo > Device=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1K-blocks= =C2=A0=C2=A0=C2=A0=C2=A0 Used=C2=A0=C2=A0=C2=A0 Avail Capacity > /dev/zvol/tank3/swap=C2=A0 33554432=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 0 33554432=C2=A0=C2=A0=C2=A0=C2=A0 0% >=20 > There is no entry in /etc/fstab though, should it be there too? How about your rc=2Econf(5) ? You need to define a dumpdev within it as: # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev=3D"YES" Which defaults to the location of: /var/crash >=20 > -- >=20 > GrzegorzJ >=20 >=20 > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= "