Hi!
It seems somewhere lost the message end, so let's try continue down.
On 2016. April 27. 09:47:25 Laszlo Fekete wrote:
> Hello!
>
> So I booted with debian backports 4.5 kernel with its 1.4.8 i40e driver
> 4.5.0-0.bpo.1-amd64 #1 SMP Debian 4.5.1-1~bpo8+1 (2016-04-20)
> x86_64 GNU/Linux
> # ethtool -i enp4s0f0
> driver: i40e
> version: 1.4.8-k
> firmware-version: 4.53 0x80001e5c 17.0.12
> bus-info: 0000:04:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
> Where enp4s0f0 and enp5s0f0 are in bond0 and vlan40 (and vlan5)
on
> that bond interface, did 3 or 4 tcpdump on vlan40 and first interface
> stayed down, switch said it's in suspend because didn't got lacp
> packets.
>
> bond status:
> # cat /proc/net/bonding/bond0
> Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
>
> Bonding Mode: IEEE 802.3ad Dynamic link aggregation
> Transmit Hash Policy: layer3+4 (1)
> MII Status: up
> MII Polling Interval (ms): 100
> Up Delay (ms): 500
> Down Delay (ms): 0
>
> 802.3ad info
> LACP rate: fast
> Min links: 0
> Aggregator selection policy (ad_select): stable
> System priority: 65535
> System MAC address: 3c:fd:fe:05:95:20
> Active Aggregator Info:
> Aggregator ID: 1
> Number of ports: 1
> Actor Key: 13
> Partner Key: 32897
> Partner Mac Address: 00:23:04:ee:be:01
>
> Slave Interface: enp4s0f0
> MII Status: up
> Speed: 10000 Mbps
> Duplex: full
> Link Failure Count: 0
> Permanent HW addr: 3c:fd:fe:05:95:20
> Slave queue ID: 0
> Aggregator ID: 2
> Actor Churn State: monitoring
> Partner Churn State: monitoring
> Actor Churned Count: 0
> Partner Churned Count: 0
> details actor lacp pdu:
> system priority: 65535
> system mac address: 3c:fd:fe:05:95:20
> port key: 0
> port priority: 255
> port number: 1
> port state: 135
> details partner lacp pdu:
> system priority: 16384
> system mac address: 00:23:04:ee:be:01
> oper key: 32897
> port priority: 32768
> port number: 285
> port state: 71
>
> Slave Interface: enp5s0f0
> MII Status: up
> Speed: 10000 Mbps
> Duplex: full
> Link Failure Count: 0
> Permanent HW addr: 3c:fd:fe:05:99:40
> Slave queue ID: 0
> Aggregator ID: 1
> Actor Churn State: none
> Partner Churn State: none
> Actor Churned Count: 0
> Partner Churned Count: 0
> details actor lacp pdu:
> system priority: 65535
> system mac address: 3c:fd:fe:05:95:20
> port key: 13
> port priority: 255
> port number: 2
> port state: 63
> details partner lacp pdu:
> system priority: 16384
> system mac address: 00:23:04:ee:be:01
> oper key: 32897
> port priority: 32768
> port number: 16669
> port state: 191
>
> dmesg last messages (as I said did 3-4 times tcpdump):
> [ 207.025305] device vlan40 entered promiscuous mode
> [ 207.026416] device bond0 entered promiscuous mode
> [ 207.027476] device enp4s0f0 entered promiscuous mode
> [ 207.028544] device enp5s0f0 entered promiscuous mode
> [ 207.933785] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=0
> [ 207.934811] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=5
> [ 207.935779] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=40
> [ 207.957226] bond0: link status up again after 0 ms for interface
> enp4s0f0
> [ 208.225484] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=0
> [ 208.226556] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=5
> [ 208.227549] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=40
> [ 208.245205] bond0: link status up again after 0 ms for interface
> enp5s0f0
> [ 208.933957] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=0
> [ 208.934884] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=5
> [ 208.935728] i40e 0000:04:00.0 enp4s0f0: adding 3c:fd:fe:05:95:20
> vid=40
> [ 208.953156] bond0: link status up again after 0 ms for interface
> enp4s0f0
> [ 209.189776] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=0
> [ 209.190745] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=5
> [ 209.191659] i40e 0000:05:00.0 enp5s0f0: adding 3c:fd:fe:05:95:20
> vid=40
> [ 209.209128] bond0: link status up again after 0 ms for interface
> enp5s0f0
> [ 210.202047] device vlan40 left promiscuous mode
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
