From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756735AbcGZO1R (ORCPT ); Tue, 26 Jul 2016 10:27:17 -0400 Received: from forward2m.cmail.yandex.net ([5.255.216.20]:52447 "EHLO forward2m.cmail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752703AbcGZO1O (ORCPT ); Tue, 26 Jul 2016 10:27:14 -0400 Authentication-Results: smtp12.mail.yandex.net; dkim=pass header.i=@forstwoof.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0,1 0 Subject: Re: PROBLEM: Intel I210AT NIC resets while using PCI passthrough on ESXi (regression) To: Thomas Gleixner References: <20c1e36b-df93-9b30-31be-8a0a3eeaafc1@forstwoof.ru> Cc: LKML , Matthias Prager , Jason Taylor , Marc Zyngier From: Foster Snowhill Organization: ForstWoof Message-ID: <30a1b076-dc4f-045a-3838-293be9e01c65@forstwoof.ru> Date: Tue, 26 Jul 2016 17:27:10 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:49.0) Gecko/20100101 Thunderbird/49.0a2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 26.07.16 17:06, Thomas Gleixner wrote: > On Tue, 26 Jul 2016, Foster Snowhill wrote: >> On 26.07.16 16:49, Thomas Gleixner wrote: >>> On Mon, 25 Jul 2016, Foster Snowhill wrote: >>>> On 25.07.16 13:56, Thomas Gleixner wrote: >>>>> Could you please give the patch below a try? It might be related, but I'm not >>>>> sure whether it will cure that particular vmware oddity. >>>> >>>> Patch fixed the issue for me. Did 4-5 reboots just to be sure, all working properly, no adapter resets. Just for the sake of experiment built a clean 4.7 kernel without the patch, issue still present there as expected. >>>> >>> >>> Can you please test something else with that patch? >>> >>> After starting the NIC, can you please shutdown the interface, so the >>> interrupt gets shutdown as well. (It should vanish from /proc/interrupts). > > Does reenabling work or does that result in a stall again? Works. root@ubuntutest ~ # ifup ens224 Waiting for DAD... Done root@ubuntutest ~ # ping -s 1000 -n ya.ru PING YA.ru (213.180.204.3) 1000(1028) bytes of data. 1008 bytes from 213.180.204.3: icmp_seq=1 ttl=57 time=2.97 ms 1008 bytes from 213.180.204.3: icmp_seq=2 ttl=57 time=2.85 ms 1008 bytes from 213.180.204.3: icmp_seq=3 ttl=57 time=2.87 ms 1008 bytes from 213.180.204.3: icmp_seq=4 ttl=57 time=2.92 ms ^C --- YA.ru ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 2.851/2.904/2.976/0.072 ms root@ubuntutest ~ # grep ens224 /proc/interrupts 60: 3 PCI-MSI 9961472-edge ens224 61: 1686 PCI-MSI 9961473-edge ens224-rx-0 62: 890 PCI-MSI 9961474-edge ens224-tx-0