Bug 233198

Summary: ixl: vlan handling causes connectivity issues and kernel panic -> reboot
Product: Base System Reporter: pmisch <jochen>
Component: kernAssignee: freebsd-net (Nobody) <net>
Status: Open ---    
Severity: Affects Some People CC: erj, sbruno
Priority: --- Keywords: IntelNetworking
Version: 11.2-RELEASE   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
screenshot of when it happens none

Description pmisch 2018-11-13 13:21:04 UTC
Created attachment 199203 [details]
screenshot of when it happens

Hardware:
IntelĀ® Server Board S1200SPL
Xeon E3 1230 v6 3,5 GHz
8 GB RAM ECC
2 x 120 GB SSD RAID 1 (ZFS)
Intel 10 Gigabit Ethernet SFP Fiber X710
Intel I210 onboard for dedicated HA

OS:
FreeBSD 11.2 / pfSense 2.4.4

The error occurred in pfSense 2.4.4 which is using FreeBSD 11.2. I've also installed an additional FreeBSD 11.2 with the same NIC (ixl) and see similar behaviour.

Under pfSense network connectivity first gets lost and then system reboots. Under FreeBSD 11.2 I just receive the error without the reboot issue.

This is the thread in the netgate forum for reference:
https://forum.netgate.com/topic/136656/kernel-panic-when-applying-setting
Comment 1 Eric Joyner freebsd_committer 2018-12-19 00:32:31 UTC
It's bizarre that it would lead to a kernel panic on one system, but not the other. I don't think that error, specifically, should cause one, either.

Is the attached history the sequence of commands from just before the error message gets printed out?
Comment 2 pmisch 2018-12-20 15:34:25 UTC
The pfSense community suggested that I needed to reproduce the problem with stock FreeBSD since it might be a driver error that cannot get fixed by pfSense community but FreeBSD.

I tried several attempts to provoke the error. The error message did not occur every single time.
I reconfigured the NIC several times with either command line or rc.conf.

I don't know which commands pfSense invokes when I change VLAN settings via GUI.
So that might be the reason why it actually crashes while FreeBSD only gives an error message.

Tell me if you need any more input. I might also be able to give you access to my test machine with the NIC inside but not before second week in January.