Project

General

Profile

Bug #9358

network problem with intel x710 FreeNAS-9.3-STABLE-201504152200

Added by Germán Iturbide over 3 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Alexander Motin
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Problem: the device loses packages or disconnects

Messages error
Apr 22 08:15:10 thundercracker ixl0: Malicious Driver Detection event 0x02 on TX queue 1 pf number 0x00
Apr 22 08:15:14 thundercracker ixl0: MDD TX event is for this function 0x00000001ixl0: Warning queue 1 appears to be hung!
Apr 22 08:15:59 thundercracker ixl1: Malicious Driver Detection event 0x02 on TX queue 0 pf number 0x01
Apr 22 08:16:04 thundercracker ixl1: Warning queue 0 appears to be hung!
Apr 22 08:17:19 thundercracker ixl1: Malicious Driver Detection event 0x02 on TX queue 1 pf number 0x01
Apr 22 08:17:23 thundercracker ixl1: MDD TX event is for this function 0x00000001ixl1: Warning queue 1 appears to be hung!
Apr 22 08:18:18 thundercracker ixl1: Malicious Driver Detection event 0x02 on TX queue 4 pf number 0x01
Apr 22 08:18:22 thundercracker ixl1: Warning queue 4 appears to be hung!
Apr 22 08:18:36 thundercracker ixl1: Malicious Driver Detection event 0x02 on TX queue 3 pf number 0x01
Apr 22 08:18:41 thundercracker ixl1: MDD TX event is for this function 0x00000001ixl1: Warning queue 3 appears to be hung!

Driver version
<Intel(R) Ethernet Connection XL710 Driver, Version - 1.2.8>


Related issues

Related to FreeNAS - Bug #9117: 10GbE SFP+ network card giving error ixl0: ixl_set_flowcntl: Error retrieving link info from aq, -56Resolved2015-04-08
Related to FreeNAS - Bug #24820: Update ixl(4) driverResolved2017-06-26

History

#1 Updated by Xin Li over 3 years ago

  • Related to Bug #9117: 10GbE SFP+ network card giving error ixl0: ixl_set_flowcntl: Error retrieving link info from aq, -56 added

#2 Updated by Xin Li over 3 years ago

  • Status changed from Unscreened to Screened
  • Target version set to Unspecified

#3 Updated by Jordan Hubbard about 3 years ago

  • Assignee changed from Xin Li to Alexander Motin

#4 Updated by Alexander Motin almost 3 years ago

  • Status changed from Screened to 19
  • Seen in changed from to 9.3-STABLE-201505040117

I've updated all Intel NIC drivers to the most recent ones from present FreeBSD stable/10. They should be included into the next nightly build. Please try it if you are still here.

#5 Updated by Alexander Motin almost 3 years ago

  • Status changed from 19 to Ready For Release
  • Target version changed from Unspecified to 261

#6 Updated by Germán Iturbide almost 3 years ago

Works for months without problems just adding these parameters -lro -tso on the interface, lost some performance but work.
Sadly i dont't have de hardware available to make tests again

#7 Updated by Jordan Hubbard almost 3 years ago

  • Target version changed from 261 to 9.10-RELEASE

#8 Updated by Jordan Hubbard almost 3 years ago

  • Status changed from Ready For Release to Resolved

#9 Updated by Richard Zowalla over 2 years ago

Latest FreeNAS release with the Intel X710-da2 and latest Intel firmware (5.0.4) brings up the same error as described above under high load circumstances.
Using the options -lro -tso as described by Germán Iturbide for the link aggregation group and the related VLANs solved the issue even under high load.

#10 Updated by David Y over 2 years ago

Hello, can we open this bug again? I don't know that it's "resolved" we simply have a workaround.

My X710-DA2 is still getting the error with 9.10-latest

Thanks

#11 Updated by Germán Iturbide over 2 years ago

  • Seen in changed from 9.3-STABLE-201505040117 to 9.10-STABLE-201604261518

FreeNAS-9.10-STABLE-201604261518
I agree, i checked with this version and still persist the problem, only works stable with the parameters modified

#12 Updated by Ozgur Akkaymak about 2 years ago

I agree too. I encounter with the same problem " Malicious Driver Detection event".

#13 Updated by Dru Lavigne about 2 years ago

Please create a new bug report that includes a debug from System -> Advanced -> Save Debug.

#14 Updated by Alexander Motin over 1 year ago

  • Related to Bug #24820: Update ixl(4) driver added

Also available in: Atom PDF