From: Foster Snowhill <forst@forstwoof.ru>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthias Prager <linux@matthiasprager.de>,
Jason Taylor <jason.taylor@simplivity.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: PROBLEM: Intel I210AT NIC resets while using PCI passthrough on ESXi (regression)
Date: Tue, 26 Jul 2016 17:27:10 +0300 [thread overview]
Message-ID: <30a1b076-dc4f-045a-3838-293be9e01c65@forstwoof.ru> (raw)
In-Reply-To: <alpine.DEB.2.11.1607261606160.19896@nanos>
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
prev parent reply other threads:[~2016-07-26 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 15:22 Foster Snowhill
2016-07-25 10:56 ` Thomas Gleixner
2016-07-25 18:06 ` Foster Snowhill
2016-07-26 11:46 ` Thomas Gleixner
2016-07-26 12:48 ` Foster Snowhill
2016-07-26 13:00 ` Thomas Gleixner
2016-07-26 13:49 ` Thomas Gleixner
2016-07-26 14:01 ` Foster Snowhill
2016-07-26 14:06 ` Thomas Gleixner
2016-07-26 14:27 ` Foster Snowhill [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30a1b076-dc4f-045a-3838-293be9e01c65@forstwoof.ru \
--to=forst@forstwoof.ru \
--cc=jason.taylor@simplivity.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@matthiasprager.de \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®