-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
rhel-9.0.0
-
None
-
Critical
-
sst_storage_io
-
ssg_platform_storage
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem: NVMe connect command hung and Call traces
Version-Release number of selected component (if applicable):
5.14.0-70.13.1.el9_0.x86_64
How reproducible:
Easily
Steps to Reproduce:
1) Configure the system for HPE Millbury testing.
2) RHEL 9 BFS system on SN1700Q adapter.
3) Present NVMe namespace
4) Reboot the server or Initiator Port toggle
5) Expected: NVMe namespace are discovered without any call trace
6) Actual: NVMe namespace not discovered and connect command got hung and resulted in Call trace.
Actual results:
Connect command hangs
Expected results:
Connect should not hang
--------------
[root@MillburyRegRH9 ~]# nvme list-subsys
nvme-subsys0 - NQN=nqn.2020-07.com.hpe:5553f61e-48a2-449b-a28c-759d4d938820
\
+- nvme0 fc traddr=nn-0x2ff70102ac0282dd:pn-0x22340102adf282dd host_traddr=nn-0x51402ec012c9cdef:pn-0x51402ec012c9cdee live
+- nvme1 fc traddr=nn-0x2ff70102ac0282dd:pn-0x22340102adf282dd host_traddr=nn-0x51402ec012c9ab5b:pn-0x51402ec012c9ab5a live
+- nvme2 fc traddr=nn-0x2ff70102ac0282dd:pn-0x23320102adf282dd host_traddr=nn-0x51402ec012c9ab5b:pn-0x51402ec012c9ab5a live
+- nvme3 fc traddr=nn-0x2ff70102ac0282dd:pn-0x23320102adf282dd host_traddr=nn-0x51402ec012c9cdef:pn-0*x51402ec012c9cdee connecting*
-----------------
Additional info:
- external trackers
