Too many crashes last few days, going back to lastweek snapshot (pimd)

louis2

Just for info and hopefully not relevant for you

and perhaps many related to the fact that I try to do / test things with pimd
also switching interfaces on and off

I had so may instability’s and crashes in the past few days, that I had to decide to go back to a snapshot from a week ago.

Louis

louis2

I went back to built on Fri Jul 03 07:02:27 EDT 2020, however ... the same issues.

23/6 I did some test, I can not repeat with the current snapshots, but be aware the situation was never OK

In fact my router is perfectly stable as long as ..

PIMD is not installed
and I am not switching Interfaces on and off especially not if PIMD is installed
Running PIMD and swithing an interface, is in my config "100%" crash garantiee

How the system recovers from such a crash differ from time to time,

sometimes in a one reboot recovery
sometimes a crash during the recovery, however at the end it is recoverd
sometimes it does not recover at all

I noticed that in:

in some cases the system can not find its config, falling back on an earlier version
in some cases even that does not working, but placing an USB containg the config helps
in some cases I had to do a full reinstall

I also noticed following strange error:
starting CRON .... done
ERROR: It was not possible to identify which pfSense kernel is installed
Starting package PIMD .... done

What ever ...... something terrrible wrong .... as soon as you start using PIMD. Can be pimd itself, but my feeling (I can not proof it), is that it something deeper in the kernel.

If some one has ideas how to point more exact to what is causing this ......
That would be helpfull ....

Note that nearly all the crash dumps are ending with the lines copied below

Louis

<118>Bootup complete
ugen0.2: <Kingston DataTraveler SE9> at usbus0 (disconnected)
umass0: at uhub0, port 7, addr 1 (disconnected)
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: <Kingston DataTraveler SE9 PMAP> s/n 000FEAFB7959BC80E7D4000C detached
(da0:umass-sim0:0:0:0): Periph destroyed
umass0: detached
<6>vlan1: changing name to 'lagg0.26'
<6>vlan1: changing name to 'lagg0.26'
<6>vlan1: changing name to 'lagg0.26'

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x0
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff80e934f5
stack pointer = 0x28:0xfffffe00004de7f0
frame pointer = 0x28:0xfffffe00004de7f0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 12 (swi1: netisr 2)
trap number = 12
panic: page fault
cpuid = 0
time = 1594546367
KDB: enter: panic