From: dongli.zhang@oracle.com
To: Artur Piechocki <artur.piechocki@open-e.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [bug report] NVMe hotplug bug in kernel 5.15 with CONFIG_INTEL_IOMMU disabled
Date: Sat, 12 Oct 2024 10:03:37 -0700 [thread overview]
Message-ID: <61fbb21b-c0cb-4267-9275-d4a94ff89179@oracle.com> (raw)
In-Reply-To: <2ea8ff1a-dcd6-4829-a096-63fa30d92b04@open-e.com>
Hi Artur,
On 7/8/24 1:26 AM, Artur Piechocki wrote:
> Hi,
>
> I am experiencing a repeatable (potential deadlock) issue when
> hotplugging NVMe devices on kernel 5.15. The problem occurs on a Ubuntu
> 22.04.4 server environment when Intel IOMMU support is disabled in the
> kernel configuration (CONFIG_INTEL_IOMMU is not set). This issue is also
> reproducible on the native kernel 5.15.161 without any Ubuntu patches.
>
> System Information:
>
> Distribution: Ubuntu 22.04.4 server
> Kernel Version: Ubuntu 5.15.152 (also repeated on native 5.15.161)
> Hardware: NVME Micron SSDPE2KX020T8, Intel(R) Xeon(R) Gold 5222
>
> Description of the Issue:
> When hotplugging an NVMe device, the system experiences a potential
Only for the sake of curiosity, may I have what does NVMe hotplug indicate?
According to the log, the server is a baremetal, not VM (QEMU/KVM).
Jul 5 09:49:11 tarox1 kernel: [ 0.374071] Booting paravirtualized kernel on
bare hardware
Is there any method to hotplug NVMe to a running baremetal server?
Thank you very much!
Dongli Zhang
next prev parent reply other threads:[~2024-10-12 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 8:26 [bug report] NVMe hotplug bug in kernel 5.15 with CONFIG_INTEL_IOMMU disabled Artur Piechocki
2024-07-09 6:46 ` Chaitanya Kulkarni
2024-10-12 17:03 ` dongli.zhang [this message]
2024-10-14 6:55 ` Artur Piechocki
[not found] ` <b5601674-5a26-448f-bb56-a1704e927d2c@open-e.com>
2024-10-14 16:34 ` dongli.zhang
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=61fbb21b-c0cb-4267-9275-d4a94ff89179@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=artur.piechocki@open-e.com \
--cc=linux-nvme@lists.infradead.org \
/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