DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 808] Unexpected error log 'EAL: Cannot find action: mp_malloc_response'
Date: Fri, 10 Sep 2021 06:57:22 +0000	[thread overview]
Message-ID: <bug-808-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=808

            Bug ID: 808
           Summary: Unexpected error log 'EAL: Cannot find action:
                    mp_malloc_response'
           Product: DPDK
           Version: 20.11
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: li_hong.bi@nokia-sbell.com
  Target Milestone: ---

Our test env has two CPU sockets (2 NUMA nodes), and we hope that dpdk can
automatically identify CPU sockets and allocate hugepage memory according to
runtime requirement of application without manual designation, therefore we set
"--socket-mem 0,0 --socket-limit 0,0" into dpdk initialization parameter list.

We do a recovery test case as below for our dpdk application in k8s container:
Test Step:
1. run 'kill -9' to terminate a dpdk primary process
2. restart dpdk primary process 
3. run a dpdk secondary process after dpdk primary process restarted
successfully.
Repeat the upper 1-3 test steps for 3 rounds

Expected result:
- no error log was found.
Test result:
- An error log "EAL: Cannot find action: mp_malloc_response" was printed out by
dpdk secondary process after the 3th round test. (The error was NOT found in
the first two rounds test)

Could you help to check this issue ?
Note:
We don't know whether "- socket MEM 0,0 -- socket limit 0,0" is correct.
If not, could you give some suggestions?

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-09-10  6:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-808-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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;
as well as URLs for NNTP newsgroup(s).