Ubuntu 22.04, "nvme list" will hang for 60 seconds after "nvme subsystem-reset"

[shenlinghai]

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
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-10-27 (306 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
IwConfig:
 lo no wireless extensions.

 enp65s0f0np0 no wireless extensions.

 enp65s0f1np1 no wireless extensions.
MachineType: Tencent Star Lake
Package: linux (not installed)
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=43fd528b-f8c3-4718-a47d-103fa6de50c2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-26-generic N/A
 linux-backports-modules-6.2.0-26-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.14
RfKill:

Tags: jammy
Uname: Linux 6.2.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/09/2021
dmi.bios.release: 5.14
dmi.bios.vendor: Tencent
dmi.bios.version: 1.53.02
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: TC1-SLMB-A
dmi.board.vendor: Inventec
dmi.board.version: MBD3A43200D00001
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 23
dmi.chassis.vendor: Tencent
dmi.modalias: dmi:bvnTencent:bvr1.53.02:bd12/09/2021:br5.14:svnTencent:pnStarLake:pvrC2:rvnInventec:rnTC1-SLMB-A:rvrMBD3A43200D00001:cvnTencent:ct23:cvr:sku01234567890123456789AB:
dmi.product.family: Default string
dmi.product.name: Star Lake
dmi.product.sku: 01234567890123456789AB
dmi.product.version: C2
dmi.sys.vendor: Tencent

[shenlinghai (shenlinghai)]

Here is the dmesg.
nvme subsytem-reset /dev/nvme0 at 11:51:03. And then execute nvme list.
And the nvme0 is normal at 11:52:05.

[11:51:03 2023] pcieport 0000:80:01.1: pciehp: Slot(17): Link Down
[11:52:04 2023] nvme 0000:81:00.0: Unable to change power state from D3cold to D0, device inaccessible
[11:52:04 2023] nvme nvme0: Removing after probe failure status: -19
[11:52:04 2023] nvme0n1: detected capacity change from 27346862080 to 0
[11:52:04 2023] pci 0000:81:00.0: Removing from iommu group 10
[11:52:05 2023] pcieport 0000:80:01.1: pciehp: Slot(17): Card present
[11:52:05 2023] pcieport 0000:80:01.1: pciehp: Slot(17): Link Up
[11:52:05 2023] pci 0000:81:00.0: [1e3b:0600] type 00 class 0x010802
[11:52:05 2023] pci 0000:81:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
[11:52:05 2023] pci 0000:81:00.0: reg 0x20: [mem 0x00000000-0x00001fff 64bit pref]
[11:52:05 2023] pci 0000:81:00.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
[11:52:05 2023] pci 0000:81:00.0: Max Payload Size set to 512 (was 128, max 512)
[11:52:05 2023] pci 0000:81:00.0: Adding to iommu group 10
[11:52:05 2023] pcieport 0000:80:01.1: bridge window [io 0x1000-0x0fff] to [bus 81] add_size 1000
[11:52:05 2023] pcieport 0000:80:01.1: BAR 13: no space for [io size 0x1000]
[11:52:05 2023] pcieport 0000:80:01.1: BAR 13: failed to assign [io size 0x1000]
[11:52:05 2023] pcieport 0000:80:01.1: BAR 13: no space for [io size 0x1000]
[11:52:05 2023] pcieport 0000:80:01.1: BAR 13: failed to assign [io size 0x1000]
[11:52:05 2023] pci 0000:81:00.0: BAR 0: assigned [mem 0xb2400000-0xb240ffff 64bit]
[11:52:05 2023] pci 0000:81:00.0: BAR 6: assigned [mem 0xb2410000-0xb2417fff pref]
[11:52:05 2023] pci 0000:81:00.0: BAR 4: assigned [mem 0x58140f00000-0x58140f01fff 64bit pref]
[11:52:05 2023] pcieport 0000:80:01.1: PCI bridge to [bus 81]
[11:52:05 2023] pcieport 0000:80:01.1: bridge window [mem 0xb2400000-0xb24fffff]
[11:52:05 2023] pcieport 0000:80:01.1: bridge window [mem 0x58140f00000-0x58140ffffff 64bit pref]
[11:52:05 2023] nvme nvme0: pci function 0000:81:00.0
[11:52:05 2023] nvme 0000:81:00.0: enabling device (0000 -> 0002)
[11:52:05 2023] nvme nvme0: 64/0/0 default/read/poll queues
[11:52:05 2023] nvme_log_error: 20 callbacks suppressed

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2031200/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2031200

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[shenlinghai (shenlinghai)]

apport information

[Paul White (paulw2u)]

In comment #3:
> and then change the status of the bug to 'Confirmed'.

Changing on behalf of reporter.