When I destroy a lagg interface consisting of ix0 and ix1 the system will
command used: ifconfig lagg0 destroy
System: FreeBSD 11.0-RELEASE-p9 (amd64)
Lutz, please post a stack trace. You can find it in /var/crash/core.txt. It will also be printed to the screen when the crash happens.
Created attachment 182244 [details]
the /var/crash/ dir is empty. The system appears to be dead immediately.
I just have IPMI console access and the error message appears for 0.5s
before the BIOS boot screen is shown. I'll attach a screenshot.
Here is the config of the lagg interface:
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet6 fe80::92e2:baff:fe61:c14c%lagg1 prefixlen 64 scopeid 0x11
inet 126.96.36.199 netmask 0xffffff00 broadcast 188.8.131.52
media: Ethernet autoselect
status: no carrier
laggproto lacp lagghash l2,l3,l4
laggport: ix2 flags=0<>
laggport: ix3 flags=0<>
Lutz, unfortunately that screenshot doesn't capture anything useful. It seems like your system is not setup to dump core on panic. Could you please check the output of "dumpon -l"? If it's empty, then you don't have a dump device set. Normally, you can put "dumpdev=AUTO" in /etc/rc.conf, which will use your first swap partition as a dump device.
(In reply to Alan Somers from comment #4)
Yes, dumpdev="NO" was set in rc.conf. I changed it to AUTO and
repeated the crash. There is just a info.0 and vmcore.0:
drwxr-x--- 2 root wheel 8 May 2 16:34 .
drwxr-xr-x 25 root wheel 25 May 2 18:34 ..
-rw-r--r-- 1 root wheel 2 May 2 16:34 bounds
-rw------- 1 root wheel 452 May 2 16:34 info.0
lrwxr-xr-x 1 root wheel 6 May 2 16:34 info.last -> info.0
-rw-r--r-- 1 root wheel 5 Nov 11 2014 minfree
-rw------- 1 root wheel 1013112832 May 2 16:34 vmcore.0
lrwxr-xr-x 1 root wheel 8 May 2 16:34 vmcore.last -> vmcore.0
# cat info.0
Dump header from device: /dev/gpt/swap2
Architecture Version: 2
Dump Length: 1013112832
Dumptime: Tue May 2 16:33:14 2017
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48:40 UTC 2017
Panic String: page fault
Dump Parity: 3897632610
Dump Status: good
Progress! Now try running "crashinfo". Normally that should run automatically, unless you put "crashinfo_enable=NO" in /etc/rc.conf. It could also fail to run if your kernel is stored in a nondefault location.
Created attachment 182246 [details]
It looks like this was fixed in head by svn r312979 by loos, but that change did not make it into 11.0-RELEASE. You could try installing a stable/11 kernel. Alternatively, perhaps loos, CCed could suggest a workaround.