On 2015-07-28 18:51, Rose, Gregory V wrote:
>> -----Original Message-----
>> From: Christian Ruppert [mailto:[email protected]]
>> Sent: Tuesday, July 28, 2015 5:43 AM
>> To: Rose, Gregory V
>> Cc: [email protected]
>> Subject: RE: [E1000-devel] X710 / i40e interface resets
>>
>> Greg,
>>
>> On 2015-07-27 18:20, Christian Ruppert wrote:
>> > On 2015-07-27 18:02, Rose, Gregory V wrote:
>> >> So to make sure I've got your report right... Since updating the FW
>> >> the link flap issue occurs much less frequently and VRRP is not
>> >> causing a switch to a different host but your log is getting spammed
>> >> with ATR messages. Is that correct?
>> >
>> > Exactly!
>> >
>> >>
>> >> Have you tried turning off ntuple-filters?
>> >
>> > I'll try that.
>>
>> No more:
>> [341397.489477] i40e 0000:02:00.0: FD filter space full, new ntuple
>> rules
>> will not be added [341398.041918] i40e 0000:02:00.0: FD Filter table
>> flushed and FD-SB replayed.
>> [341398.049403] i40e 0000:02:00.0: FD Sideband/ntuple is being enabled
>> since we have space in the table now [341398.059858] i40e
>> 0000:02:00.0:
>> ATR is being enabled since we have space in the table now
>> [341850.732707]
>> i40e 0000:02:00.0: ATR re-enabled.
>>
>> since I disabled ntuple. So that is gone (not fixed though) for now.
>
> OK - I think the messages you're seeing are part of normal operation
> but they are quite noisy. I know the i40e dev team is trying to
> reduce the amount of message "spam" to the system log so I'll point
> this out to them and perhaps something can be done to reduce the
> message volume.
>
>>
>> The flaps are still persistent:
>> [354195.790717] i40e 0000:02:00.0: TX driver issue detected, PF reset
>> issued [354196.551366] i40e 0000:02:00.0: FCoE capability is disabled
>> [354196.593458] i40e 0000:02:00.0: PHC enabled [354196.653574] i40e
>> 0000:02:00.0: enabling bridge mode: VEPA [354196.672095] i40e
>> 0000:02:00.0
>> eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
>
> I've been told that the Tx driver issue detected message is due to a
> MDD (Malicious Driver Detection) event. We need to find out what is
> causing that so if you could please send me your system log and the
> output of ethtool <intf> and ethtool -i <intf> perhaps I can see what
> might be occurring. If not then we'll have to debug further.
See the initial Mail for ethtool -k and so on. Also:
# ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Advertised link modes: 1000baseT/Full
10000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000000f (15)
drv probe link timer
Link detected: yes
# ethtool -i eth0
driver: i40e
version: 1.2.48
firmware-version: f4.33.31377 a1.2 n4.42 e191b
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
>
> I'll be out the next few days but returning Monday so I'll be able to
> follow up on this issue then.
>
> Thanks,
>
> - Greg
--
Regards,
Christian Ruppert
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
