From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id EF28FA0547;
	Fri, 10 Sep 2021 08:57:23 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id DD6D140041;
	Fri, 10 Sep 2021 08:57:23 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
 by mails.dpdk.org (Postfix) with ESMTP id 96DBE4003E
 for <dev@dpdk.org>; Fri, 10 Sep 2021 08:57:22 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id 7697EA0548; Fri, 10 Sep 2021 08:57:22 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Date: Fri, 10 Sep 2021 06:57:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: core
X-Bugzilla-Version: 20.11
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: li_hong.bi@nokia-sbell.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 target_milestone
Message-ID: <bug-808-3@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-dev] [Bug 808] Unexpected error log 'EAL: Cannot find action:
 mp_malloc_response'
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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

            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 li=
st.

We do a recovery test case as below for our dpdk application in k8s contain=
er:
Test Step:
1. run 'kill -9' to terminate a dpdk primary process
2. restart dpdk primary process=20
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 ou=
t by
dpdk secondary process after the 3th round test. =EF=BC=88The error was NOT=
 found in
the first two rounds test)

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

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