------- Comment From [email protected] 2016-11-18 20:02 EDT------- I traced the probolem to __vlan_vid_add(), this code snipit:
/* Try switchdev op first. In case it is not supported, fallback to * 8021q add. */ err = switchdev_port_obj_add(dev, &v.obj); if (err == -EOPNOTSUPP) return vlan_vid_add(dev, br->vlan_proto, vid); return err; switchdev_port_obj_add() returns EOPNOTSUP so it it calls vlan_vid_add() that function is in 8021q module, on my system that was not loaded. If I set the interface to be added to the bridge UP then load 8021q before creating the bridge the problem will not happen. Using the following steps to create the bridge will prevent the problem.. rmmod bridge rmmod 8021q ifconfig enP2p1s0f3 up modprobe 8021q brctl addbr boom brctl stp boom off brctl addif boom enP2p1s0f3 brctl delif boom enP2p1s0f3 I made a few attempts to alter the interfaces script to create a workaround. Not much luck. however we can prevent a panic by not shutting down the interface at system shutdown time. Using the no-auto- down directive in /etc/network/interfaces worked for me. My Bridge definition is: no-auto-down boom iface boom inet static address 192.168.10.1 netmask 255.255.0.0 bridge_ports enP2p1s0f3 bridge_stp off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616107 Title: Kernel oops + system freeze on network-bridge shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1616107/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
