mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Foster Snowhill <forst@forstwoof.ru>
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 16:06:53 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1607261606160.19896@nanos> (raw)
In-Reply-To: <20c1e36b-df93-9b30-31be-8a0a3eeaafc1@forstwoof.ru>

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?

Thanks,

	tglx

  reply	other threads:[~2016-07-26 14:09 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 [this message]
2016-07-26 14:27           ` Foster Snowhill

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=alpine.DEB.2.11.1607261606160.19896@nanos \
    --to=tglx@linutronix.de \
    --cc=forst@forstwoof.ru \
    --cc=jason.taylor@simplivity.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@matthiasprager.de \
    --cc=marc.zyngier@arm.com \
    /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®