On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka li...@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
--
GrzegorzJ
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
