Created attachment 159299 [details]
Photo of the kernel trace after kernel panic
FreeBSD versions: multiple 10.1-RELEASE versions up to p14 have been tested.
How to reproduce:
(You need latest net/syncthing installed.)
The panic appeared after some syncthing update.
The system does not write coredump, but I can reproduce it every time and it is very annoying, because I cannot shut down the server properly (I need syncthing). I attached a photo of the trace, I hope it's enough.
Panic also occurs with 10.2-RELEASE and syncthing-0.11.18.
I forgot to tell that the kernel is not GENERIC.
> options DDB
> options GDB
> options ALTQ
> options ALTQ_CBQ # Class Bases Queueing
> options ALTQ_RED # Random Early Detection
> options ALTQ_RIO # RED In/Out
> options ALTQ_HFSC # Hierarchical Packet Scheduler
> options ALTQ_CDNR # Traffic conditioner
> options ALTQ_PRIQ # Priority Queueing
> options MROUTING
FWIW; duplicate of bug #202978
There is a workaround there; the problem is 'local announce' is triggering an ipv6 multicast kernel bug.
I want to confirm that the workaround works. Thank you Peter.
Fixed as noted in PR 202978.
Re-open. Will add more context/information shortly.
Underlying userland causing kernel panic is being tracked in the duplicated (original) bug 200846
*** This bug has been marked as a duplicate of bug 200846 ***