Hi, I have "managed" go get a kernel panic in OpenBSD 6.0 -stable (from GENERIC.MP). Unfortunately I cannot provide you with lots of information, but here is what I have:
The panic occured twice on an IBM X3550 server (CPU: Intel(R) Xeon(R) CPU E5-2603 0 @ 1.80GHz, with 4GB RAM and Intel I350 Gigabit Network chips onboard) and once in a VM which was hosted inside Linux KVM with the e1000 as network interface. The IBM server was configured to act as bridged and routed firewall, so we had a hostname.bridge0 (with blocknonip) with em0 and em1 interfaces and vether0 (having the main external ip-address of the firewall and some alias addresses that are routed through into the internal network) and vether1 (having the primary internal ip-adress) - some hosts on the network are not of my responsibility so they stayed with an external ip address (and thus we need bridging). We carefully planned the migration from Linux/iptables to OpenBSD/PF (which is really a joy to use, kudos to you devs for making me happy and enjoying the time spent with PF and the rest of the system), but after we switched, the hardware got a panic at night (and so did I). I could not even type via USB-keyboard in ddb. And since it was already in production I did not have time to fiddle around and get it working, a restart was needed. See picture [1] The second crash occured when I did a "ifconfig vether0 alias EX.TE.RN.IP netmask 255.255.255.240", this time I have switched on ddb.panic=0, but the server did not restart and was hung - no USB keyboard again. See pic [2] The third crash was in a VM, where I was playing around. Here, I did not have a bridge configuration, but a "ifconfig em1 alias XX.XX.XX.XX netmask 255.255.255.0" resulted in picture [3], this time again without being able to type in the VM. We had to switch back to the old Linux based firewall, but in the VM I have not managed to reproduce this. I would appreciate any tipps, comments or info in this matter, I am willing to help if more information is needed or if I can do anything to support a dev to fix this problem. regards, infoomatic [1] https://postimg.org/image/5ogvhmc45/ [2] https://postimg.org/image/mmx6f1nxv/ [3] https://postimg.org/image/687wqsh8j/
