Date: Tue, 31 Oct 2017 15:13:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 221919] ixl: TX queue hang when using TSO and having a high and mixed network load Message-ID: <bug-221919-2472-tEa9tsX2lS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221919-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-221919-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221919 Peter Eriksson <peter@ifm.liu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter@ifm.liu.se --- Comment #2 from Peter Eriksson <peter@ifm.liu.se> --- This is a really annoying bug that we've also seen. I do not think it's rel= ated to iSCSI though (since we aren't using it). Disabling TSO seems to help (but also severly reduces transmission speed - in our case it drops from around 10Gbps to 3Gbps without TSO). I our servers are SMB (and NFS, but not much yet) servers. Dell PowerEdge 730xd. > FreeBSD 11.1 > ixl2: fw 5.40.47690 api 1.5 nvm 5.40 etid 80002d35 oem 18.4608.16 ixl0: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl0: link state changed to UP ixl2: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl2: link state changed to UP ixl0: <Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k> = mem 0xc9000000-0xc9ffffff,0xca008000-0xca00ffff at device 0.0 numa-domain 1 on pci15 ixl0: Using MSIX interrupts with 9 vectors ixl0: fw 5.40.47690 api 1.5 nvm 5.40 etid 80002d35 oem 18.4608.16 ixl0: PF-ID[0]: VFs 64, MSIX 129, VF MSIX 5, QPs 768, I2C ixl0: Allocating 8 queues for PF LAN VSI; 8 queues active ixl0: Ethernet address: 3c:fd:fe:24:e7:e0 ixl0: PCI Express Bus: Speed 8.0GT/s Width x8 ixl0: Failed to initialize SR-IOV (error=3D2) ixl0: netmap queues/slots: TX 8/1024, RX 8/1024 ixl2: <Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k> = mem 0xcc000000-0xccffffff,0xcd008000-0xcd00ffff at device 0.0 numa-domain 1 on pci16 ixl2: Using MSIX interrupts with 9 vectors ixl2: fw 5.40.47690 api 1.5 nvm 5.40 etid 80002d35 oem 18.4608.16 ixl2: PF-ID[0]: VFs 64, MSIX 129, VF MSIX 5, QPs 768, I2C ixl2: Allocating 8 queues for PF LAN VSI; 8 queues active ixl2: Ethernet address: 3c:fd:fe:24:d6:a0 ixl2: PCI Express Bus: Speed 8.0GT/s Width x8 ixl2: Failed to initialize SR-IOV (error=3D2) ixl2: netmap queues/slots: TX 8/1024, RX 8/1024 ixl0: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl0: link state changed to UP ixl2: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl2: link state changed to UP ixl2: link state changed to DOWN ixl0: link state changed to DOWN ixl0: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl0: link state changed to UP ixl2: Link is up, 10 Gbps Full Duplex, FEC: None, Autoneg: False, Flow Cont= rol: Full ixl2: link state changed to UP ixl2: Malicious Driver Detection event 2 on TX queue 0, pf number 0 ixl2: MDD TX event is for this function!ixl2: Interface stopped DISTRIBUTIN= G, possible flapping ixl2: Interface stopped DISTRIBUTING, possible flapping ixl2: Interface stopped DISTRIBUTING, possible flapping ...repeat... ixl2: WARNING: queue 0 appears to be hung! ixl2: WARNING: Resetting! I managed to login to the server after a while and disable TSO and then thi= ngs started working again. Would using the Intel-provided (instead of the 11.1 one) driver and firmware (from their web site) help with this issue? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221919-2472-tEa9tsX2lS>