Project

General

Profile

Bug #28377

Update ixl(4) driver

Added by Michael Leone about 1 year ago. Updated about 1 month ago.

Status:
Done
Priority:
Critical
Assignee:
Alexander Motin
Category:
Hardware
Target version:
Seen in:
Severity:
Med High
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

ixl1: Malicious Driver Detection event 2 on TX queue 774, pf number 1
ixl1: MDD TX event is for this function!ixl1: WARNING: queue 6 appears to be hung!
ixl1: WARNING: Resetting

Same issues as the others, but I have the latest release of FreeNAS.

Screenshot 2019-03-11 at 21.33.35.png (219 KB) Screenshot 2019-03-11 at 21.33.35.png Screenshot IPMI Andreas Martin Aanerud, 03/12/2019 01:03 AM
sec_output.txt (9.26 KB) sec_output.txt daily security run output Andreas Martin Aanerud, 03/12/2019 01:05 AM
60510

Related issues

Related to FreeNAS - Feature #80949: Update ixl driverClosed

Associated revisions

Revision 9d65817b (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site.

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

Revision b36d0167 (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site.

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

Revision b36d0167 (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site.

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

Revision dd7f40e0 (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

Revision e63211f5 (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377
(cherry picked from commit dd7f40e0e09c6e02c9a2ea2ca1ff4af4c52ffc92)

Revision 4e1d63bf (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

Revision 4e1d63bf (diff)
Added by Alexander Motin about 1 year ago

Update ixl(4) driver to the latest version from Intel site

Version 1.9.5 for physical, and 1.5.2 for virtual (SR-IOV).

This update seems to be fixing "Malicious Driver Detection".

Ticket: #28377

History

#1 Updated by Michael Leone about 1 year ago

  • File debug-GCSAN1-20180208125816.txz added
  • Private changed from No to Yes

#2 Updated by Dru Lavigne about 1 year ago

  • Assignee changed from Release Council to Alexander Motin
  • Target version set to 11.2-RC2

#3 Updated by Alexander Motin about 1 year ago

We are trying to investigate that issue now, but haven't got far yet. You may try to update NICs firmware, I think there may be one available from Intel, ans in both case it change anything or not -- it would be a useful input. If not, you could ping Intel, since we are using the latest driver version available in FreeBSD. I see some newer driver version of the Intel site, but for some reason it is still not imported to FreeBSD head, while AFAIK they have FreeBSD committers.

#4 Updated by Michael Leone about 1 year ago

Alexander Motin wrote:

We are trying to investigate that issue now, but haven't got far yet. You may try to update NICs firmware, I think there may be one available from Intel, ans in both case it change anything or not -- it would be a useful input. If not, you could ping Intel, since we are using the latest driver version available in FreeBSD. I see some newer driver version of the Intel site, but for some reason it is still not imported to FreeBSD head, while AFAIK they have FreeBSD committers.

I have updated the adapter and created an Intel Community post. As of this writing, there has not been a response. Intel telephone support was a frustrating experience and ultimately a waste of time.

Num Description Ver. DevId S:B Status === ======================================== ===== ===== ====== ===============
01) Intel(R) I350 Gigabit Network Connection 1.99 1521 00:004 Update not
available
02) Intel(R) Ethernet Converged Network 6.01 1572 00:005 Update not
Adapter X710-2 available

#5 Updated by Alexander Motin about 1 year ago

  • Status changed from Not Started to In Progress
  • Priority changed from Nice to have to Critical
  • Target version changed from 11.2-RC2 to 11.1-U2
  • Severity set to Med High

I've created a patch merging latest ixl(4) driver(s) version(s) from the Intel site (1.9.5 for physical, and 1.5.2 for virtual interfaces). More tests are still need to be done, but so far the error was no longer reproduced after the update.

#6 Updated by Dru Lavigne about 1 year ago

  • File deleted (debug-GCSAN1-20180208125816.txz)

#7 Updated by Dru Lavigne about 1 year ago

  • Subject changed from Intel X710 Issue again 11.1-U1 to Update ixl(4) driver
  • Private changed from Yes to No

#8 Updated by Dru Lavigne about 1 year ago

  • Seen in changed from 11.1-U1 to 11.1-U1

#9 Updated by Alexander Motin about 1 year ago

  • Subject changed from Update ixl(4) driver to Update ixl(4) driver
  • Status changed from In Progress to Done
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

I've merged the patch. It should be in next nightly builds and 11.1-U2 release. Please test when you can and report if any problems found.

#10 Updated by Andreas Martin Aanerud about 1 month ago

60510

This bug is still there.

I have a 2x Supermicro 2-Port SFP+ Intel 10GbE LAN card PCI-e LP X710 DA, and the driver loaded is the 1.9.9-k.
I have attached a screenshoot of the server display by IPMI, and the daily security run output.

Whats done is enabling TSO, then all the interfaces are up & down.
Then we start seeing the interrupts, and the LAG is working har to keep the link up,
as it constantly switches between the NIC´s

and you can see its fluctuating , with txcsum up and down,
looks like the NIC resets it self and its settings.

This is reproduced also in FreeBSD Bugs ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221919 )
They got it working on the ixl driver 2.1.0-k .

The latest driver from Intel is 3.3.6 , and is found here ( https://downloadcenter.intel.com/download/14688/Intel-Network-Adapters-Driver-for-PCIe-10-Gigabit-Network-Connections-Under-FreeBSD- )

Is it possible to Update the intel driver in 11.2-U3 ?

#11 Updated by Dru Lavigne about 1 month ago

Andreas: please open a new ticket so we can investigate that driver on the 11.2 series.

#12 Updated by Alexander Motin about 1 month ago

Andreas, FreeNAS 11.2 includes latest version of the driver present in FreeBSD stable/11 branch -- 1.9.9-k. Version 2.1.0 in FreeBSD 12 uses iflib KPI and can not be merged down. I haven't checked intel site myself, but the driver you are pointing to seem to be ixgbe, not ixl.

#13 Updated by Andreas Martin Aanerud about 1 month ago

Ill create a new bug on the newest branch tomorrow morning ( 22.00 here. )

The intel drivers are for both ixgbe and ix, it compiles 3 different drivers and manuals.

I did create a jail, and made the driver there... and I did not however manage to unload the pci/ix with kldunload -i ID , so every time I tried to kldload the if_ixl.ko file that where made from the make processes , it stated that it crashed with the pci/ix

#14 Updated by Andreas Martin Aanerud about 1 month ago

Added Issue #80949

#15 Updated by Dru Lavigne about 1 month ago

Also available in: Atom PDF