Kernel panic (12.0-p3 RPI3B+ aarch64)

Ronald Klop ronald-lists at klop.ws
Wed Mar 27 19:40:01 UTC 2019


Hi,

I had a kernel panic last evening. My RPI3B+ had run out of mbuf clusters  
a couple of hours before. I logged in by serial cable and increased the  
sysctl kern.ipc.nmbclusters -> 30000 (the default is 19262) after which it  
looked like running ok.

Any thoughts about this? Can I provide more information?

Regards,
Ronald.


------- Forwarded message -------
From: "FreeBSD Panic Reporting" <xxx>
To: root
Cc:
Subject: Kernel panic
Date: Wed, 27 Mar 2019 20:27:41 +0100

A kernel panic has occurred on this system.  You can assist in
debugging this by allowing some information to be reported
about this panic.

The following information is contained in the encrypted panic
report at the end of this email:

> Dump header from device: /dev/gpt/ssddumpdev
>   Architecture: aarch64
>   Architecture Version: 1
>   Dump Length: 252329984
>   Blocksize: 512
>   Compression: none
>   Dumptime: Tue Mar 26 22:35:00 2019
>   Hostname: rpi3
>   Magic: FreeBSD Kernel Dump
>   Version String: FreeBSD 12.0-RELEASE-p3 #10 r343874M: Thu Feb  7  
> 20:19:54 CET 2019
>     builder at rpi3:/data/src/obj-12/data/src/12/arm64.aarch64/sys/GENERIC-MMCCAM
>   Panic String: vm_fault failed: ffff00000067fab8
>   Dump Parity: 1033498431
>   Bounds: 6
>   Dump Status: good
>
> Backtrace:
> Reading symbols from /boot/kernel/kernel...(no debugging symbols  
> found)...done.
> 0xffff0000003b6868 in sched_switch ()
> (kgdb) #0  0xffff0000003b6868 in sched_switch ()
> #1  0xffff000000393094 in mi_switch ()
> #2  0xffff0000003df134 in sleepq_wait ()
> #3  0xffff000000392cb4 in msleep_spin_sbt ()
> #4  0xffff0000003cfad0 in gtaskqueue_thread_loop ()
> #5  0xffff00000034a4f8 in fork_exit ()
> #6  <signal handler called>
> (kgdb)



More information about the freebsd-arm mailing list