All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dexuan Cui <decui@microsoft.com>
To: Solio Sarabia <solio.sarabia@intel.com>,
	"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
	KY Srinivasan <kys@microsoft.com>,
	Michael Kelley <mikelley@microsoft.com>,
	Shiny Sebastian <shiny.sebastian@intel.com>
Subject: RE: linux-5.1-rc3: nvme hv_pci: request for interrupt failed
Date: Thu, 4 Apr 2019 02:42:56 +0000	[thread overview]
Message-ID: <PU1P153MB01691F731370D45D13C3615CBF500@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <FCE231C24CDC4243982F7030CC75E92F644C034C@FMSMSX102.amr.corp.intel.com>

> From: Solio Sarabia <solio.sarabia@intel.com>
> Sent: Wednesday, April 3, 2019 5:38 PM
> To: linux-hyperv@vger.kernel.org; linux-nvme@lists.infradead.org
> 
> When two nvme devices are discrete-assigned [1] to a linuxvm on
> hyper-v rs5 host, it fails to initialize both.  It worked a couple of
> times and after some reboots it failed. `dmesg` shows:
> 
> [   14.099310] hv_pci 96a07283-8dac-417a-82c6-111eb8b9a4c0: Request for
> interrupt failed: 0xc000009a
> 
> Thanks,
> -Solio

0xc000009a is STATUS_INSUFFICIENT_RESOURCES.

This is a known host resource leakage bug of the RS5 host. After the issue
happens, rebooting the VM can not help, and rebooting the host may hang
and we may have to power cycle the host by force.

The bug has been fixed in 19H1, which is in the Insider Preview phase, though:
https://docs.microsoft.com/en-us/windows-insider/at-home/whats-new-wip-at-home-19h1
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

The fix is being backported to RS5, but I don't have an ETA yet. 
I'll try to get more info today and keep you updated.

Thanks,
-- Dexuan

WARNING: multiple messages have this Message-ID (diff)
From: decui@microsoft.com (Dexuan Cui)
Subject: linux-5.1-rc3: nvme hv_pci: request for interrupt failed
Date: Thu, 4 Apr 2019 02:42:56 +0000	[thread overview]
Message-ID: <PU1P153MB01691F731370D45D13C3615CBF500@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <FCE231C24CDC4243982F7030CC75E92F644C034C@FMSMSX102.amr.corp.intel.com>

> From: Solio Sarabia <solio.sarabia at intel.com>
> Sent: Wednesday, April 3, 2019 5:38 PM
> To: linux-hyperv at vger.kernel.org; linux-nvme at lists.infradead.org
> 
> When two nvme devices are discrete-assigned [1] to a linuxvm on
> hyper-v rs5 host, it fails to initialize both.  It worked a couple of
> times and after some reboots it failed. `dmesg` shows:
> 
> [   14.099310] hv_pci 96a07283-8dac-417a-82c6-111eb8b9a4c0: Request for
> interrupt failed: 0xc000009a
> 
> Thanks,
> -Solio

0xc000009a is STATUS_INSUFFICIENT_RESOURCES.

This is a known host resource leakage bug of the RS5 host. After the issue
happens, rebooting the VM can not help, and rebooting the host may hang
and we may have to power cycle the host by force.

The bug has been fixed in 19H1, which is in the Insider Preview phase, though:
https://docs.microsoft.com/en-us/windows-insider/at-home/whats-new-wip-at-home-19h1
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced

The fix is being backported to RS5, but I don't have an ETA yet. 
I'll try to get more info today and keep you updated.

Thanks,
-- Dexuan

  reply	other threads:[~2019-04-04  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  0:38 linux-5.1-rc3: nvme hv_pci: request for interrupt failed Solio Sarabia
2019-04-04  0:38 ` Solio Sarabia
2019-04-04  2:42 ` Dexuan Cui [this message]
2019-04-04  2:42   ` Dexuan Cui
2019-04-04  4:37   ` Solio Sarabia
2019-04-04  4:37     ` Solio Sarabia

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=PU1P153MB01691F731370D45D13C3615CBF500@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM \
    --to=decui@microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mikelley@microsoft.com \
    --cc=shiny.sebastian@intel.com \
    --cc=solio.sarabia@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.