From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============0555867243751703970==" MIME-Version: 1.0 From: Oza Oza Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3 Date: Mon, 07 Aug 2017 11:13:21 +0530 Message-ID: In-Reply-To: 8310670A-ADFF-40A4-9A3E-4FA734BE46A1@intel.com List-ID: To: spdk@lists.01.org --===============0555867243751703970== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Harris, I have gone through the http://www.spdk.io/development/ but, is there any easy way to send out patches ? it is like you commit on my behalf ? PS: this is basic armv8 port for SPDK Regards, Oza. -----Original Message----- From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, James R Sent: Tuesday, April 04, 2017 9:09 PM To: Storage Performance Development Kit Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization timed out in state 3 > On Apr 4, 2017, at 7:18 AM, Oza Oza wrote: > > And I am using following command. > > fio --randrepeat=3D1 > --ioengine=3D/home/oza/SPDK/spdk/examples/nvme/fio_plugin/fio_plugin > --direct=3D1 --numjobs=3D1 --gtod_reduce=3D1 --name=3Dreadtest > --filename=3D0000.01.00.00/1 --bs=3D4096 --iodepth=3D128 --size=3D4G > --readwrite=3Dread Hi Oza, Please add =E2=80=94thread=3D1. I will push a patch shortly that documents= this option for the SPDK plugin and checks for it at runtime. Regarding your patches, you can submit them as a pull request to the SPDK GitHub project. See http://www.spdk.io/development/ for more details. Thanks, -Jim > > Regards, > Oza. > -----Original Message----- > From: Oza Oza [mailto:oza.oza(a)broadcom.com] > Sent: Tuesday, April 04, 2017 2:55 PM > To: 'Storage Performance Development Kit' > Subject: RE: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: > ***ERROR*** Initialization timed out in state 3 > > Hi Harris, > > Thanks for the response. > > for time-being, I am stuck with one after the other problem. Although > problems are being resolved. > > Whatever I posted on 1st of April is resolved, and that exposed bug in > our RC driver where I was not checking competition status. > That is now solved. > > The controller timeout also is resolved by adding some delay after > SPDK nvme_ctrlr.c > > And I think all the errors have nothing to do with ARMv8 porting, > because mostly it compiled straightly, there are some minor patches. > Which I will let you know, also at the same time let me know how do I > contribute/discuss any change ? > > Now I am stuck here: let me know if you have clue. > > odepth=3D128 --size=3D4G --readwrite=3Dread --filename=3D0000.01.00.00/1 > --bs=3D4096 --i /home/oza/fio /home/oza/SPDK/spdk > EAL: pci driver is being registered 0x1nreadtest: (g=3D0): rw=3Dread, > bs=3D4096B-4096B,4096B-4096B,4096B-4096B, ioengine=3Dspdk_fio, iodepth=3D= 128 > fio-2.17-29-gf0ac1 > Starting 1 process > Starting Intel(R) DPDK initialization ... > [ DPDK EAL parameters: fio -c 1 --file-prefix=3Dspdk_pid6177 > --base-virtaddr=3D0x1000000000 --proc-type=3Dauto ] > EAL: Detected 8 lcore(s) > EAL: Auto-detected process type: PRIMARY > EAL: Probing VFIO support... > EAL: VFIO support initialized > EAL: cannot open /proc/self/numa_maps, consider that all memory is in > socket_id 0 > EAL: PCI device 0000:01:00.0 on NUMA socket 0 > EAL: probe driver: 8086:953 spdk_nvme > EAL: using IOMMU type 1 (Type 1) > EAL: vfio_group_fd=3D11 iommu_group_no=3D3 *vfio_dev_fd=3D13 > EAL: reg=3D0x2000 fd=3D13 cap_offset=3D0x50 > EAL: Hotplug doesn't support vfio yet > EAL: probe driver: 8086:953 spdk_nvme > EAL: vfio_group_fd=3D11 iommu_group_no=3D3 *vfio_dev_fd=3D16 > EAL: reg=3D0x2000 fd=3D16 cap_offset=3D0x50 > nvme_pcie.c: 994:nvme_pcie_qpair_complete_pending_admin_request:[ > 1041.919073] pgd =3D ffff800975800000 > ***ERROR*** the active process (pid 6184) is not found for this[ > 1041.928312] [00000008] *pgd=3D00000009f5815003 controller. > fio: pid=3D6184, got signal=3D11 > > readtest: (groupid=3D0, jobs=3D1): err=3D 0: pid=3D6184: Tue Apr 4 09:12= :28 2017 > read: IOPS=3D442k, BW=3D1727MiB/s (1811MB/s)(4096MiB/2372msec) > cpu : usr=3D99.87%, sys=3D0.00%, ctx=3D238, majf=3D0, minf=3D16 > IO depths : 1=3D0.1%, 2=3D0.1%, 4=3D0.1%, 8=3D0.1%, 16=3D0.1%, 32=3D0= .1%, >> =3D64=3D100.0% > submit : 0=3D0.0%, 4=3D100.0%, 8=3D0.0%, 16=3D0.0%, 32=3D0.0%, 64= =3D0.0%, >> =3D64=3D0.0% > complete : 0=3D0.0%, 4=3D100.0%, 8=3D0.0%, 16=3D0.0%, 32=3D0.0%, 64= =3D0.0%, >> =3D64=3D0.1% > issued rwt: total=3D1048576,0,0, short=3D0,0,0, dropped=3D0,0,0 > latency : target=3D0, window=3D0, percentile=3D100.00%, depth=3D128 > > Run status group 0 (all jobs): > READ: bw=3D1727MiB/s (1811MB/s), 1727MiB/s-1727MiB/s > (1811MB/s-1811MB/s), io=3D4096MiB (4295MB), run=3D2372-2372msec > > Regards, > Oza. > -----Original Message----- > From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Harris, > James R > Sent: Monday, April 03, 2017 9:12 PM > To: Storage Performance Development Kit > Subject: Re: [SPDK] nvme_ctrlr.c:1224:nvme_ctrlr_process_init: > ***ERROR*** Initialization timed out in state 3 > > Hi Oza, > >> On Apr 3, 2017, at 2:01 AM, Oza Oza wrote: >> >> I have ported SPDK for ARMv8. > > Great! Do you have patches that you can share? > >> And DPDK is compiled with version: 16.11.1 >> >> init controller is failing. > > Does this mean that the previous issue you reported on April 1 has > been resolved? If so, can you share details? > >> >> root(a)ubuntu:/home/oza/SPDK/spdk# >> odepth=3D128 --size=3D4G --readwrite=3Dread --filename=3D0000.01.00.00/1 >> --bs=3D4096 --i /home/oza/fio /home/oza/SPDK/spdk >> EAL: pci driver is being registered 0x1nreadtest: (g=3D0): rw=3Dread, >> bs=3D4096B-4096B,4096B-4096B,4096B-4096B, ioengine=3Dspdk_fio, >> iodepth=3D128 >> fio-2.17-29-gf0ac1 >> Starting 1 process >> Starting Intel(R) DPDK initialization ... >> [ DPDK EAL parameters: fio -c 1 --file-prefix=3Dspdk_pid6448 >> --base-virtaddr=3D0x1000000000 --proc-type=3Dauto ] >> EAL: Detected 8 lcore(s) >> EAL: Auto-detected process type: PRIMARY >> EAL: Probing VFIO support... >> EAL: VFIO support initialized >> EAL: cannot open /proc/self/numa_maps, consider that all memory is in >> socket_id 0 >> EAL: PCI device 0000:01:00.0 on NUMA socket 0 >> EAL: probe driver: 8086:953 spdk_nvme >> EAL: using IOMMU type 1 (Type 1) >> EAL: vfio_group_fd=3D11 iommu_group_no=3D3 *vfio_dev_fd=3D13 >> EAL: reg=3D0x2000 fd=3D13 cap_offset=3D0x50 >> EAL: the msi-x bar number is 0 0x2000 0x200 >> EAL: Hotplug doesn't support vfio yet >> spdk_fio_setup() is being called >> EAL: PCI device 0000:01:00.0 on NUMA socket 0 >> EAL: probe driver: 8086:953 spdk_nvme >> EAL: vfio_group_fd=3D11 iommu_group_no=3D3 *vfio_dev_fd=3D16 >> EAL: reg=3D0x2000 fd=3D16 cap_offset=3D0x50 >> EAL: the msi-x bar number is 0 0x2000 0x200 >> EAL: inside pci_vfio_write_config offset=3D4 >> nvme_ctrlr.c:1224:nvme_ctrlr_process_init: ***ERROR*** Initialization >> timed out in state 3 >> nvme_ctrlr.c: 403:nvme_ctrlr_shutdown: ***ERROR*** did not shutdown >> within >> 5 seconds > > I think this is where seeing your ARMv8 patches would help. Then we > could collaborate on if/how the ARMv8 changes you have made may be > causing the initialization error. > >> EAL: Hotplug doesn't support vfio yet >> EAL: PCI device 0000:01:00.0 on NUMA socket 0 >> EAL: probe driver: 8086:953 spdk_nvme >> EAL: vfio_group_fd=3D11 iommu_group_no=3D3 *vfio_dev_fd=3D18 >> EAL: reg=3D0x2000 fd=3D18 cap_offset=3D0x50 >> EAL: the msi-x bar number is 0 0x2000 0x200 >> EAL: Hotplug doesn't support vfio yet >> EAL: Requested device 0000:01:00.0 cannot be used >> spdk_nvme_probe() failed > > Thanks, > > -Jim > > _______________________________________________ > SPDK mailing list > SPDK(a)lists.01.org > https://lists.01.org/mailman/listinfo/spdk > _______________________________________________ > SPDK mailing list > SPDK(a)lists.01.org > https://lists.01.org/mailman/listinfo/spdk _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk --===============0555867243751703970==--