Date: Sun, 3 May 2020 09:05:52 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Chris <bsd-lists@BSDforge.com> Cc: Grzegorz Junka <list1@gjunka.com>, <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: <20200503090552.36bfe99c@ernst.home> In-Reply-To: <8df5a5cd4ac5bd9e10516c1321ea2de2@udns.ultimatedns.net> References: <cd818dad-3c1c-60aa-ed0b-49da80494228@gjunka.com> <8df5a5cd4ac5bd9e10516c1321ea2de2@udns.ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 02 May 2020 16:28:46 -0700
Chris <bsd-lists@BSDforge.com> wrote:
> On Sun, 3 May 2020 00:15:48 +0100 Grzegorz Junka list1@gjunka.com said
>
> > On 02/05/2020 20:43, Chris wrote:
> > > On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka list1@gjunka.com said
> > >
> > >> On 02/05/2020 14:56, 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?
> > >> >
> > >>
> > >> Another thing is that I don't quite understand why the crash couldn't
> > >> be dumped.
> > >>
> > >> root@crayon2:~ # swapinfo
> > >> Device__________________ 1K-blocks________ Used______ Avail Capacity
> > >> /dev/zvol/tank3/swap__ 33554432______________ 0 33554432________ 0%
> > >>
> > >> There is no entry in /etc/fstab though, should it be there too?
> > >
> > > How about your rc.conf(5) ?
> > >
> > > You need to define a dumpdev within it as:
> > >
> > > # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
> > > dumpdev="YES"
> > >
> > > Which defaults to the location of:
> > >
> > > /var/crash
> > >
> >
> > Yes, of course I have 'dumpdev="AUTO"'. Should it be "YES" instead?
> Yes, it should of course be AUTO. I was distracted at the time of writing.
> Sorry.
> Does /var/crash exist?
>
> That _should_ be enough. Assuming /var/crash is writable.
>
Sorry, but read the man page for rc.conf.
This is the entry for dumpdev:
dumpdev (str) Indicates the device (usually a swap partition) to
which a crash dump should be written in the event of a system
crash. If the value of this variable is "AUTO", the first
suitable swap device listed in /etc/fstab will be used as
dump device. Otherwise, the value of this variable is passed
as the argument to dumpon(8). To disable crash dumps, set
this variable to "NO".
If there are no swap devices in /etc/fstab then "AUTO" will not work. But
a partition can be specified. I have dumpdev="/dev/ada0p5" in my rc.conf.
/var/crash is the target for crash dumps after the system is re-booted.
--
Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200503090552.36bfe99c>