* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-02-18 21:18 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2020-02-18 21:18 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 8628 bytes --]
On Wed, Feb 19, 2020, 00:11 Harris, James R <james.r.harris(a)intel.com>
wrote:
> Hi Andrey,
>
> I've never seen that issue on any of the Xeon platforms I've tested with.
> Not sure about Epyc though.
>
> I can't figure out where "set_mempolicy failed" gets printed by DPDK
> though. I see where DPDK prints messages when set_mempolicy fails, but
> it's in a different format.
Hi Jim,
I have also spent some time scratching my head on this until I realized
that DPDK overrides numa_error with its own logging, and that's exactly
where it gets printed.
As to the cause, it appears that the kernel is unhappy with the mode/nodes
combination DPDK tries to give it. The kernel is 3.10, BTW.
Do you by chance have any local edits in your DPDK submodule?
>
No, I'm running stock SPDK/DPDK.
Regards,
Andrey
> -Jim
>
>
> On 2/18/20, 8:28 AM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com> wrote:
>
> Hi guys,
>
> I'm running 20.01 (default configuration) on a CentOS 7 Epyc-based
> system, and getting a lot of subj warnings like in the below example.
> Does that point to a system configuration issue that needs to be
> fixed?
>
> Thanks,
> Andrey
>
> Starting SPDK v20.01 git sha1 5ffffe9 / DPDK 19.11.0 initialization...
> [ DPDK EAL parameters: hotplug --no-shconf -c 0x1
> --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6
> --iova-mode=pa --base-virtaddr=0x200000000000 --match-allocations
> --file-prefix=spdk_pid109760 ]
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: VFIO support initialized
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Initializing NVMe Controllers
> EAL: set_mempolicy failed: Invalid argument
> EAL: using IOMMU type 1 (Type 1)
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:45:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:46:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4b:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4c:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4d:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4e:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:45:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:46:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4b:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4c:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4d:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4e:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Initialization complete. Starting I/O...
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
>
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-04-15 8:56 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2020-04-15 8:56 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Wed, Apr 15, 2020, 03:33 <CHENG.JIN(a)gmail.com> wrote:
> Hi.
>
> I hit the same problem on an AMD EPYC 7301 server. Can you please share
> details how you fix this?
>
You should check how your DDR slots are populated so that each numa node
has at least one of its slots non-empty.
Regards,
Andrey
>
> On-line CPU(s) list: 0-63
> Thread(s) per core: 2
> Core(s) per socket: 16
> Socket(s): 2
> NUMA node(s): 8
>
>
> Thanks,
>
> Jin
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-04-15 0:33 CHENG.JIN
0 siblings, 0 replies; 6+ messages in thread
From: CHENG.JIN @ 2020-04-15 0:33 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
Hi.
I hit the same problem on an AMD EPYC 7301 server. Can you please share details how you fix this?
On-line CPU(s) list: 0-63
Thread(s) per core: 2
Core(s) per socket: 16
Socket(s): 2
NUMA node(s): 8
Thanks,
Jin
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-02-20 7:21 Andrey Kuzmin
0 siblings, 0 replies; 6+ messages in thread
From: Andrey Kuzmin @ 2020-02-20 7:21 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 10603 bytes --]
Just FYI, turned out to be a memory configuration issue where we ended up
with memoryless numa nodes. Not that eal messages were very helpful in
resolving the issue, though.
Regards,
Andrey
On Wed, Feb 19, 2020, 00:27 Harris, James R <james.r.harris(a)intel.com>
wrote:
>
>
> On 2/18/20, 1:19 PM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com> wrote:
>
> On Wed, Feb 19, 2020, 00:11 Harris, James R <james.r.harris(a)intel.com>
> wrote:
>
> > Hi Andrey,
> >
> > I've never seen that issue on any of the Xeon platforms I've tested
> with.
> > Not sure about Epyc though.
> >
> > I can't figure out where "set_mempolicy failed" gets printed by DPDK
> > though. I see where DPDK prints messages when set_mempolicy fails,
> but
> > it's in a different format.
>
>
> Hi Jim,
>
> I have also spent some time scratching my head on this until I realized
> that DPDK overrides numa_error with its own logging, and that's
> exactly
> where it gets printed.
>
> Ah - thanks for teaching me something new today. Now I understand why my
> simple grep failed to find it!
>
> As to the cause, it appears that the kernel is unhappy with the
> mode/nodes
> combination DPDK tries to give it. The kernel is 3.10, BTW.
>
> Do you by chance have any local edits in your DPDK submodule?
> >
>
> No, I'm running stock SPDK/DPDK.
>
> Regards,
> Andrey
>
>
> > -Jim
> >
> >
> > On 2/18/20, 8:28 AM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com>
> wrote:
> >
> > Hi guys,
> >
> > I'm running 20.01 (default configuration) on a CentOS 7
> Epyc-based
> > system, and getting a lot of subj warnings like in the below
> example.
> > Does that point to a system configuration issue that needs to be
> > fixed?
> >
> > Thanks,
> > Andrey
> >
> > Starting SPDK v20.01 git sha1 5ffffe9 / DPDK 19.11.0
> initialization...
> > [ DPDK EAL parameters: hotplug --no-shconf -c 0x1
> > --log-level=lib.eal:6 --log-level=lib.cryptodev:5
> --log-level=user1:6
> > --iova-mode=pa --base-virtaddr=0x200000000000 --match-allocations
> > --file-prefix=spdk_pid109760 ]
> > EAL: No available hugepages reported in hugepages-1048576kB
> > EAL: VFIO support initialized
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Initializing NVMe Controllers
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: using IOMMU type 1 (Type 1)
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:45:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:46:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:4b:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:4c:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:4d:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attaching to 0000:4e:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:45:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:46:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:4b:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:4c:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:4d:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Attached to 0000:4e:00.0
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > EAL: set_mempolicy failed: Invalid argument
> > Initialization complete. Starting I/O...
> > _______________________________________________
> > SPDK mailing list -- spdk(a)lists.01.org
> > To unsubscribe send an email to spdk-leave(a)lists.01.org
> >
> >
> > _______________________________________________
> > SPDK mailing list -- spdk(a)lists.01.org
> > To unsubscribe send an email to spdk-leave(a)lists.01.org
> >
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
>
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-02-18 21:27 Harris, James R
0 siblings, 0 replies; 6+ messages in thread
From: Harris, James R @ 2020-02-18 21:27 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 9775 bytes --]
On 2/18/20, 1:19 PM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com> wrote:
On Wed, Feb 19, 2020, 00:11 Harris, James R <james.r.harris(a)intel.com>
wrote:
> Hi Andrey,
>
> I've never seen that issue on any of the Xeon platforms I've tested with.
> Not sure about Epyc though.
>
> I can't figure out where "set_mempolicy failed" gets printed by DPDK
> though. I see where DPDK prints messages when set_mempolicy fails, but
> it's in a different format.
Hi Jim,
I have also spent some time scratching my head on this until I realized
that DPDK overrides numa_error with its own logging, and that's exactly
where it gets printed.
Ah - thanks for teaching me something new today. Now I understand why my simple grep failed to find it!
As to the cause, it appears that the kernel is unhappy with the mode/nodes
combination DPDK tries to give it. The kernel is 3.10, BTW.
Do you by chance have any local edits in your DPDK submodule?
>
No, I'm running stock SPDK/DPDK.
Regards,
Andrey
> -Jim
>
>
> On 2/18/20, 8:28 AM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com> wrote:
>
> Hi guys,
>
> I'm running 20.01 (default configuration) on a CentOS 7 Epyc-based
> system, and getting a lot of subj warnings like in the below example.
> Does that point to a system configuration issue that needs to be
> fixed?
>
> Thanks,
> Andrey
>
> Starting SPDK v20.01 git sha1 5ffffe9 / DPDK 19.11.0 initialization...
> [ DPDK EAL parameters: hotplug --no-shconf -c 0x1
> --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6
> --iova-mode=pa --base-virtaddr=0x200000000000 --match-allocations
> --file-prefix=spdk_pid109760 ]
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: VFIO support initialized
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Initializing NVMe Controllers
> EAL: set_mempolicy failed: Invalid argument
> EAL: using IOMMU type 1 (Type 1)
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:45:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:46:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4b:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4c:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4d:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attaching to 0000:4e:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:45:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:46:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4b:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4c:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4d:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Attached to 0000:4e:00.0
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> EAL: set_mempolicy failed: Invalid argument
> Initialization complete. Starting I/O...
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
>
> _______________________________________________
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
>
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 6+ messages in thread
* [SPDK] Re: EAL: set_mempolicy failed: Invalid argument
@ 2020-02-18 21:11 Harris, James R
0 siblings, 0 replies; 6+ messages in thread
From: Harris, James R @ 2020-02-18 21:11 UTC (permalink / raw)
To: spdk
[-- Attachment #1: Type: text/plain, Size: 7681 bytes --]
Hi Andrey,
I've never seen that issue on any of the Xeon platforms I've tested with. Not sure about Epyc though.
I can't figure out where "set_mempolicy failed" gets printed by DPDK though. I see where DPDK prints messages when set_mempolicy fails, but it's in a different format. Do you by chance have any local edits in your DPDK submodule?
-Jim
On 2/18/20, 8:28 AM, "Andrey Kuzmin" <andrey.v.kuzmin(a)gmail.com> wrote:
Hi guys,
I'm running 20.01 (default configuration) on a CentOS 7 Epyc-based
system, and getting a lot of subj warnings like in the below example.
Does that point to a system configuration issue that needs to be
fixed?
Thanks,
Andrey
Starting SPDK v20.01 git sha1 5ffffe9 / DPDK 19.11.0 initialization...
[ DPDK EAL parameters: hotplug --no-shconf -c 0x1
--log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6
--iova-mode=pa --base-virtaddr=0x200000000000 --match-allocations
--file-prefix=spdk_pid109760 ]
EAL: No available hugepages reported in hugepages-1048576kB
EAL: VFIO support initialized
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Initializing NVMe Controllers
EAL: set_mempolicy failed: Invalid argument
EAL: using IOMMU type 1 (Type 1)
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:45:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:46:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:4b:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:4c:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:4d:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attaching to 0000:4e:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:45:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:46:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:4b:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:4c:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:4d:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Attached to 0000:4e:00.0
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
EAL: set_mempolicy failed: Invalid argument
Initialization complete. Starting I/O...
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-04-15 8:56 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-18 21:18 [SPDK] Re: EAL: set_mempolicy failed: Invalid argument Andrey Kuzmin
-- strict thread matches above, loose matches on Subject: below --
2020-04-15 8:56 Andrey Kuzmin
2020-04-15 0:33 CHENG.JIN
2020-02-20 7:21 Andrey Kuzmin
2020-02-18 21:27 Harris, James R
2020-02-18 21:11 Harris, James R
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.