[Bug 280074] em(4) temporarily hangs and re-enables TX CSUM if a bridge it's a member of is modified

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280074

--- Comment #18 from Joshua Kinard <[email protected]> ---
FWIW, this is the dmesg from the same system, after booting on the out-of-tree
driver built from ports.  Not including the ifconfig output, because nothing
there looks to be different on the ports-built driver.  The three lines at the
~250sec mark are where I stopped the jail there as well, but network
connectivity remains  unaffected while the bridge membership is modified and
epair0 is deleted:

> # dmesg | grep "em0\|epair0\|jail0\|bridge0\|lo0"
> em0: <Intel(R) PRO/1000 Network Connection 7.7.8> mem 0x91b00000-0x91b1ffff at device 31.6 on pci0
> em0: Using an MSI interrupt
> em0: Ethernet address: aa:bb:cc:dd:ee:ff
> [9] bridge0: Ethernet address: aa:bb:cc:dd:ee:ff
> [9] em0: link state changed to UP
> [9] lo0: link state changed to UP
> [10] em0: link state changed to DOWN
> [10] bridge0: WARNING: Adding member interface em0 which has an IP address assigned is deprecated and will be unsupported in a future release.
> [10] bridge0: link state changed to UP
> [10] em0: promiscuous mode enabled
> [13] em0: link state changed to UP
> [14] epair0a: Ethernet address: aa:bb:cc:dd:ee:ff
> [14] epair0b: Ethernet address: aa:bb:cc:dd:ee:ff
> [14] epair0a: link state changed to UP
> [14] epair0b: link state changed to UP
> [14] epair0a: promiscuous mode enabled
> [15] epair0b: changing name to 'jail0'
> [15] lo0: link state changed to UP
> [257] epair0a: promiscuous mode disabled
> [258] epair0a: link state changed to DOWN
> [258] jail0: link state changed to DOWN

The noticeable change is the lack of the lines about the "2 link states
coalesced" on em0, so maybe that's something related?

-- 
You are receiving this mail because:
You are the assignee for the bug.