From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radu Nicolau Subject: Re: [PATCH] test: fix hang on FreeBSD Date: Mon, 21 May 2018 14:33:16 +0100 Message-ID: References: <1526902547-12710-1-git-send-email-radu.nicolau@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: thomas@monjalon.net, ferruh.yigit@intel.com, stable@dpdk.org To: "Burakov, Anatoly" , dev@dpdk.org Return-path: In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 5/21/2018 2:28 PM, Burakov, Anatoly wrote: > On 21-May-18 12:35 PM, Radu Nicolau wrote: >> Fixes: af75078fece3 ("first public release") >> Cc: stable@dpdk.org >> >> Signed-off-by: Radu Nicolau >> --- >>   test/test/test_debug.c | 3 ++- >>   1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/test/test/test_debug.c b/test/test/test_debug.c >> index faf2cf5..56fadce 100644 >> --- a/test/test/test_debug.c >> +++ b/test/test/test_debug.c >> @@ -34,7 +34,8 @@ test_panic(void) >>           printf("Fork Failed\n"); >>           return -1; >>       } >> -    wait(&status); >> +    sleep(1); >> +    waitpid(pid, &status, WNOHANG); >>       if(status == 0){ >>           printf("Child process terminated normally!\n"); >>           return -1; >> > > I'd be curious to see which specific problem you are addressing as > well. FreeBSD hanging on abort is a known issue, and a workaround is > already available: > > http://dpdk.org/dev/patchwork/patch/40256/ > > FreeBSD doesn't really "hang" here, it just spends a > looooooooooooooong time doing the core dump because FreeBSD, unlike > Linux, doesn't ignore hugepage and zero-page anonymous memory for core > dumps, resulting in it trying to dump the entire 128 gigabytes of VA > space that we preallocate. > > Setting resource limits will address the immediate issue, a more > complete fix (some memory subsystem refactor) will be coming for 18.08. > So it seems my "fix" only hides the issue and doesn't actually fix anything - so I will remove it from patchwork