Thanks Michal, Can we also get a full dmesg log from the receiving side during a repro?
Carolyn > -----Original Message----- > From: Michał Mirosław [mailto:michal.miros...@atendesoftware.pl] > Sent: Thursday, April 21, 2016 8:04 AM > To: Ronciak, John <john.ronc...@intel.com> > Cc: e1000-devel@lists.sourceforge.net; mirq-li...@rere.qmqm.pl; intel-wired- > l...@lists.osuosl.org; Pawel Malachowski > <pawel.malachow...@atendesoftware.pl> > Subject: Re: [E1000-devel] i40e: Deadly GRE packet > > Dear John, > > We found the problem using our DPDK application, but later on we reproduced > the same issue using in-kernel drivers (even after fresh reboot). > > Best Regards, > Michał Mirosław > > 2016-04-21 16:54 GMT+02:00 Ronciak, John <john.ronc...@intel.com>: > > > > -----Original Message----- > > > From: Michał Mirosław [mailto:michal.miros...@atendesoftware.pl] > > > Sent: Thursday, April 21, 2016 5:45 AM > > > To: e1000-devel@lists.sourceforge.net; intel-wired-...@lists.osuosl.org > > > Cc: Paweł Małachowski <pawel.malachow...@atendesoftware.pl>; mirq- > > > li...@rere.qmqm.pl > > > Subject: [E1000-devel] i40e: Deadly GRE packet > > > > > > Dear Developers, > > > > > > I have a setup of a pair of SuperMicro-branded XL710s connected with > > > passive crossover cable, one (eth4) is using firmware 5.0, the other > > (eth7) is > > > using fw 4.33. When I send couple of packets with no payload in GRE over > > IP > > > over ETH from eth7 to eth4, the receiving card stops processing further > > > packets. It seems that 4 empty-GRE packets in succession are enough to > > kill > > > the card's receivers (all ports stop working), more if there are other > > packets > > > inbetween. Transmit direction is not affected. After reboot, the card > > comes > > > back, reloading the driver (or unbind/bind) is not enough to fix the > > problem. > > > > > > 14:31:24.299203 00:00:00:00:00:00 > ff:ff:ff:ff:ff:ff, ethertype IPv4 > > (0x0800), > > > length 60: (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto GRE > > (47), length > > > 24) > > > 127.0.0.1 > 127.0.0.1: GREv0, Flags [none], proto unknown (0x0000), > > length > > > 4 > > > gre-proto-0x0 > > > 0x0000: 4500 0018 0001 0000 402f 7cb4 7f00 0001 E.......@ > > /|..... > > > 0x0010: 7f00 0001 0000 0000 0000 0000 0000 0000 > > ................ > > > 0x0020: 0000 0000 0000 0000 0000 0000 0000 .............. > > > > > > scapy 2.2.0 generates this packet from: Ether()/IP()/GRE() > > > > > > Tested on stock Debian kernel, with in-kernel driver and one from > > DPDK-2.2. > > > Linux lab1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) > > x86_64 > > > GNU/Linux > > > > > > Best Regards, > > > Michał Mirosław > > How exactly is DPDK involved? Is it running in all instances where the > > issue is seen? Have you tried the latest i40e driver from our Sourceforge > > site (http://e1000.sf.net)? > > > > Cheers, > > John > > > > > > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
