From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
shenlinghai@163.com, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
dwmw2@infradead.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux NVMe <linux-nvme@lists.infradead.org>
Subject: Fwd: Ubuntu 22.04, "nvme list" will hang for 60 seconds after "nvme subsystem-reset"
Date: Wed, 2 Aug 2023 18:41:01 +0700 [thread overview]
Message-ID: <8edde583-2b5f-2332-e59a-f1f4688b9e40@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Issue description:
> root:~# lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 22.04 LTS
> Release: 22.04
> Codename: jammy
>
> root:~# uname -a
> Linux dapu-Star-Lake 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
>
> root:~#nvme subsystem-reset /dev/nvme0
>
> root:~#nvme list //This command will hang about 60 seconds.
>
> Issue analysis:
> Maybe it hangs in function nvme_wait_reset. When we revert the following commit, this issue will disappear.
> if (!nvme_wait_reset(ctrl))
> https://github.com/torvalds/linux/commit/1e866afd4bcdd01a70a5eddb4371158d3035ce03?diff=split
See Bugzilla for the full thread.
Anyway, I'm adding this regression to be tracked by regzbot:
#regzbot introduced: 1e866afd4bcdd0 https://bugzilla.kernel.org/show_bug.cgi?id=217745
#regzbot title: listing nvme devices hangs after subsystem reset
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217745
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-08-02 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 11:41 Bagas Sanjaya [this message]
2023-08-07 10:30 ` Thorsten Leemhuis
2023-09-09 5:36 ` Bagas Sanjaya
2023-09-09 5:37 ` Bagas Sanjaya
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=8edde583-2b5f-2332-e59a-f1f4688b9e40@gmail.com \
--to=bagasdotme@gmail.com \
--cc=axboe@fb.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=regressions@lists.linux.dev \
--cc=sagi@grimberg.me \
--cc=shenlinghai@163.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®