[Bug 230510] iflib/vlan panic: sleeping thread

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Aug 20 17:44:37 UTC 2018


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

--- Comment #3 from Harald Schmalzbauer <bugzilla.freebsd at omnilan.de> ---
Kudos!

No more LORs and the described problem is solved with D16808 against r338093.
But vlan(4) doesn't work as expected.
I have to reduce MTU to 1468 on the vlan(4) device to get frames passed out.
I haven't really checked much, since there were some offloading changes
recently and I'm not sure if if_valn(4) is known to be under rework/broken.

I have if_em(4) (I217-V) as parent device.
For the moment I haven't disabled any offloading feature, so the interfaces
involved read like this:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=81249b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LRO,WOL_MAGIC,VLAN_HWFILTER>
        ether 56:be:f7:0b:d7:4e
        hwaddr 
        inet 192.0.2.1 netmask 0xffffff00 broadcast 192.0.2.255 
        inet6 2001:db8:1::3:1 prefixlen 64 
        inet6 fe80::54be:f7ff:fe0b:d74e%em0 prefixlen 64 scopeid 0x1 
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

vlegn: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1468
        options=403<RXCSUM,TXCSUM,LRO>
        ether 56:be:f7:0b:d7:4e
        inet 169.254.0.1 netmask 0xffffff00 broadcast 169.254.0.255 
        inet6 2001:db8:2::3:2 prefixlen 64 
        inet6 fe80::54be:f7ff:fe0b:d74e%vlegn prefixlen 64 scopeid 0x3 
        groups: vlan 
        vlan: 1234 vlanpcp: 0 parent interface: em0
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Usually vlegn (if_vlan(4) child of em0) should work with the inherited MTU of
9000

Shall I file a different PR?
And test with different offloading scenarios before doing so?

Thanks,

-harry

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


More information about the freebsd-net mailing list