From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0B73FA034C; Wed, 21 Dec 2022 21:59:12 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A842340A7F; Wed, 21 Dec 2022 21:59:11 +0100 (CET) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id 6A03040698 for ; Wed, 21 Dec 2022 21:59:09 +0100 (CET) Received: by linux.microsoft.com (Postfix, from userid 1086) id ADC5E20C3386; Wed, 21 Dec 2022 12:59:08 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com ADC5E20C3386 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1671656348; bh=Ev9ngY+KPtHnjhXXrzIp+z+jJaxt0T6QuB/AJ1O/HCE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cYEK9/h6R9cz35hIB16OrTabs9bPuk/tEdZdlggdvu618gIclJrLjsZDgCgrlwr55 IHCnVAxf4XuRCDVQfZUkodOeGCtD/T+i9xBtZuCo3Bq8Gbqde9RSOS0S+Q+12FlduR 1FpfcyZutAJYCCDalRgXumVbvTP+iK1IMUwEUyGU= Date: Wed, 21 Dec 2022 12:59:08 -0800 From: Tyler Retzlaff To: Stephen Hemminger Cc: dev@dpdk.org Subject: Re: DPDK:fast-tests suite linux/vm Message-ID: <20221221205908.GD20526@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20221221181349.GB20526@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <20221221110333.6a10cf48@hermes.local> <20221221193336.GC20526@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <20221221114941.63e3bd24@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221221114941.63e3bd24@hermes.local> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, Dec 21, 2022 at 11:49:41AM -0800, Stephen Hemminger wrote: > On Wed, 21 Dec 2022 11:33:36 -0800 > Tyler Retzlaff wrote: > > > On Wed, Dec 21, 2022 at 11:03:33AM -0800, Stephen Hemminger wrote: > > > On Wed, 21 Dec 2022 10:13:49 -0800 > > > Tyler Retzlaff wrote: > > > > > > > hi folks, > > > > > > > > are there any additional requirements that may not be documented for > > > > running the DPDK:fast-tests suite in a vm on linux? > > > > > > > > if i run the suite as follows i end up getting intermittent failures. > > > > are there known issues running in a vm? > > > > > > > > meson test -C u --test-args='--no-huge' --suite fast-tests > > > > > > > > RTE>>fbarray_autotest > > > > + ------------------------------------------------------- + > > > > + Test Suite : fbarray autotest > > > > > > > > Thread 1 "dpdk-test" received signal SIGBUS, Bus error. > > > > __memset_evex_unaligned_erms () at > > > > ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:250 > > > > 250 ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S: No such > > > > file or directory. > > > > (gdb) bt > > > > #0 __memset_evex_unaligned_erms () at > > > > ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:250 > > > > #1 0x0000555556022d5b in rte_fbarray_init (arr=0x55555e3566c0 , > > > > name=0x55555bebdb28 "fbarray_autotest", len=256, elt_sz=4) at ../lib/eal/common/eal_common_fbarray.c:802 > > > > #2 0x00005555557b24af in autotest_setup () at ../app/test/test_fbarray.c:31 > > > > #3 0x0000555555636f03 in unit_test_suite_runner (suite=0x55555c846140 ) > > > > at ../app/test/test.c:306 > > > > #4 0x00005555557b5ffc in test_fbarray () at ../app/test/test_fbarray.c:733 > > > > #5 0x00005555556292c4 in cmd_autotest_parsed (parsed_result=0x7fffffff8140, cl=0x55556a8b2fa0, data=0x0) > > > > at ../app/test/commands.c:68 > > > > #6 0x0000555555fb3294 in __cmdline_parse (cl=0x55556a8b2fa0, buf=0x55556a8b2fe8 "fbarray_autotest\n", > > > > call_fn=true) at ../lib/cmdline/cmdline_parse.c:294 > > > > #7 0x0000555555fb32dc in cmdline_parse (cl=0x55556a8b2fa0, buf=0x55556a8b2fe8 "fbarray_autotest\n") > > > > at ../lib/cmdline/cmdline_parse.c:302 > > > > #8 0x0000555555fb1577 in cmdline_valid_buffer (rdl=0x55556a8b2fb0, buf=0x55556a8b2fe8 "fbarray_autotest\n", > > > > size=18) at ../lib/cmdline/cmdline.c:24 > > > > #9 0x0000555555fb667d in rdline_char_in (rdl=0x55556a8b2fb0, c=10 '\n') at ../lib/cmdline/cmdline_rdline.c:444 > > > > #10 0x0000555555fb19bd in cmdline_in (cl=0x55556a8b2fa0, buf=0x7fffffffe3f0 "fbarray_autotest\n", size=17) > > > > at ../lib/cmdline/cmdline.c:146 > > > > #11 0x0000555555636a34 in main (argc=2, argv=0x7fffffffe930) at ../app/test/test.c:208 > > > > > > > > thanks! > > > > > > Were hugepages setup before running the test? Was there enough memory available? > > > > hugepages are not setup on the system, i explicitly pass --no-huge or > > does that not do what i think it should? > > > > the vm has fixed 16GB memory, stepping through the code i do not see > > internal allocation calls fail prior to the failure. > > > > thanks > > Could be that the allocation gives bogus memory? i'm not sure i understand the question? do you mean the allocator has a bug and is giving me space that is in fact not allocated/mapped? i'm kind of sensing that maybe this is related to some hugepage code still running even when --no-huge. but i'm not familiar enough with the code paths to spot what doesn't belong. a couple of side thoughts. this is very easy to reproduce. maybe someone who has a vm hanging around and more knowledge can verify my observation that there is a problem and it isn't just finger trouble on my part? we could / should perhaps expand the CI to also run tests with hugepages disabled in both the system and during test passes. in the absence of anyone else taking a look i'll see if i can find time to walk through the code more carefully to understand what is actually breaking. thanks for the suggestions.