Bug#892105: linux-image-4.9.0-6-amd64: i40e driver still unstable

2019-01-09 Thread Paul Szabo 
I use kernel 4.9.130 (my own build from current "stretch" sources,
package linux-source-4.9 version 4.9.130-2), and on my new machines
with i40e devices, I observe similar, occasional issues:

Jan  9 07:30:06 viale kernel: [428469.260531] i40e :19:00.1: cleared 
PE_CRITERR
Jan  9 07:30:06 viale kernel: [428469.260639] i40e :19:00.1: TX driver 
issue detected, PF reset issued

Jan  9 08:47:06 siv kernel: [422993.009196] i40e :19:00.1: cleared 
PE_CRITERR
Jan  9 08:47:06 siv kernel: [422993.013535] i40e :19:00.1 eth1: NIC Link is 
Down
Jan  9 08:47:16 siv kernel: [423002.131389] i40e :19:00.1 eth1: NIC Link is 
Up 10 Gbps Full Duplex, Flow Control: None

Curiously each of those machines only ever show the one type of error
(never show an error like the other machine), and both only complain
about eth1, never about eth0 (though eth0 is also connected with similar
traffic volumes).

Following the hints in this bug report, I will try the Intel i40e
driver, from (either)
   https://downloadcenter.intel.com/download/24411/
   https://sourceforge.net/projects/e1000/files/i40e%20stable/

Cheers, Paul
-- 
Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#892105: linux-image-4.9.0-6-amd64: i40e driver still unstable

2018-03-05 Thread Raymond Burkholder 
> Our usual solution is to install a i40e driver from Intel (version
> 1.6.42 works nice for us). Please note that this is the only driver
taining our
> kernel - as a workaround.

I am in a similar circumstance.  After a few days of moderate operation, it
appears packets can be transmitted, but tcpdump does not see the ingress
packet.  The IRQs may have issues?

I did some troubleshooting with a network appliance vendor in whose devices
these cards are installed.

Their comments are to use a more current kernel, and to use Intel's drivers
from their e1000 sourceforge site.  The i40e driver in a more current kernel
may operate better.  Debian Stretch has 4.14 in stretch-backports.  

I see many many commits to the i40e module between the 4.9 and 4.14 kernel
versions.  Maybe the issue has been solved in a more recent kernel/module
incarnation.  And/Or use the intel (tainted) module/driver.  I am persuing
both:  install the stretch-backports kernel (which provides additional
iproute2 functions as a bonus), plus install the separate intel i40e driver.
I am testing my auto-build scripts to suit the new requirements.

What the real problem is with the driver, I do not know.  The above is my
version of a workaround.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Bug#892105: linux-image-4.9.0-6-amd64: i40e driver still unstable

2018-03-05 Thread Harald Wilhelmi 
Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

After rebooting the system with a new Kernel we see various problems
with i40e driver. Usually the problems start to occure within one day
or so under load. The last time we got the error messages shown below,
while the NIC seemed to stop processing some(?) packages. tcpdump
suggested that the machine received packages but either failed to
forward them or to send out the responses. With older Kernels we have
seen also Panics.

Our usual solution is to install a i40e driver from Intel (version
1.6.42 works nice for us). Please note that this is the only driver
taining our kernel - as a workaround.

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.9.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u2 (2018-02-21)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-6-amd64 root=/dev/mapper/vg--data-root ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
2018-02-28T18:10:23.090521+01:00 fire13a1 kernel: [2.951283] i40e: Intel(R) 
Ethernet Connection XL710 Network Driver - version 1.6.16-k
2018-02-28T18:10:23.090522+01:00 fire13a1 kernel: [2.951283] i40e: 
Copyright (c) 2013 - 2014 Intel Corporation.
2018-02-28T18:10:23.090544+01:00 fire13a1 kernel: [2.967616] i40e 
:01:00.0: fw 4.40.35115 api 1.4 nvm 4.53 0x8000206e 0.0.0
2018-02-28T18:10:23.090635+01:00 fire13a1 kernel: [3.227930] i40e 
:01:00.0: MAC address: 3c:fd:fe:9e:51:80
2018-02-28T18:10:23.090635+01:00 fire13a1 kernel: [3.231934] i40e 
:01:00.0: SAN MAC: 3c:fd:fe:9e:51:82
2018-02-28T18:10:23.090646+01:00 fire13a1 kernel: [3.402043] i40e 
:01:00.0: Added LAN device PF0 bus=0x00 func=0x00
2018-02-28T18:10:23.090647+01:00 fire13a1 kernel: [3.402053] i40e 
:01:00.0: PCI-Express: Speed 8.0GT/s Width x8
2018-02-28T18:10:23.090652+01:00 fire13a1 kernel: [3.431852] i40e 
:01:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 4 RSS FD_ATR FD_SB NTUPLE 
DCB VxLAN Geneve PTP VEPA
2018-02-28T18:10:23.090654+01:00 fire13a1 kernel: [3.443530] i40e 
:01:00.1: fw 4.40.35115 api 1.4 nvm 4.53 0x8000206e 0.0.0
2018-02-28T18:10:23.090669+01:00 fire13a1 kernel: [3.720312] i40e 
:01:00.1: MAC address: 3c:fd:fe:9e:51:81
2018-02-28T18:10:23.090669+01:00 fire13a1 kernel: [3.724518] i40e 
:01:00.1: SAN MAC: 3c:fd:fe:9e:51:83
2018-02-28T18:10:23.090693+01:00 fire13a1 kernel: [3.887825] i40e 
:01:00.1: Added LAN device PF1 bus=0x00 func=0x01
2018-02-28T18:10:23.090693+01:00 fire13a1 kernel: [3.887833] i40e 
:01:00.1: PCI-Express: Speed 8.0GT/s Width x8
2018-02-28T18:10:23.090696+01:00 fire13a1 kernel: [3.917891] i40e 
:01:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 4 RSS FD_ATR FD_SB NTUPLE 
DCB VxLAN Geneve PTP VEPA
2018-02-28T18:10:23.090697+01:00 fire13a1 kernel: [3.918420] i40e 
:01:00.1 eth3: renamed from eth2
2018-02-28T18:10:23.090698+01:00 fire13a1 kernel: [3.940100] i40e 
:01:00.0 eth2: renamed from eth1
2018-02-28T18:10:23.411181+01:00 fire13a1 kernel: [   10.794451] i40e 
:01:00.0 eth2: already using mac address 3c:fd:fe:9e:51:80
2018-02-28T18:10:23.415575+01:00 fire13a1 kernel: [   10.797168] i40e 
:01:00.0 eth2: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None
2018-02-28T18:10:23.415583+01:00 fire13a1 kernel: [   10.799073] i40e 
:01:00.1 eth3: set new mac address 3c:fd:fe:9e:51:80
2018-02-28T18:10:23.421269+01:00 fire13a1 kernel: [   10.803806] i40e 
:01:00.1 eth3: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None
...
2018-03-01T11:23:49.484086+01:00 fire13a1 kernel: [62013.858296] i40e 
:01:00.0: TX driver issue detected, PF reset issued
2018-03-01T11:23:50.100101+01:00 fire13a1 kernel: [62014.475520] i40e 
:01:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode 
forced on
2018-03-01T11:23:52.020101+01:00 fire13a1 kernel: [62016.393751] i40e 
:01:00.0: TX driver issue detected, PF reset issued
2018-03-01T11:23:53.088122+01:00 fire13a1 kernel: [62017.461657] i40e 
:01:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode 
forced on
2018-03-01T11:23:54.624095+01:00 fire13a1 kernel: [62018.999104] i40e 
:01:00.0: TX driver issue detected, PF reset issued
2018-03-01T11:23:55.100100+01:00 fire13a1 kernel: [62019.473449] i40e 
:01:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode 
forced on


** Model information
sys_vendor: Thomas-Krenn.AG
product_name: X10SLH-F/X10SLM+-F
product_version: 0123456789
chassis_vendor: Supermicro
chassis_version: 0123456789
bios_vendor: American Megatrends Inc.
bios_version: 3.0
board_vendor: Supermicro
board_name: X10SLH-F/X10SLM+-F
board_version: 1.01 

** Loaded modules:
fuse
btrfs
ufs
qnx4