From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from delivery.mailspamprotection.com (delivery.mailspamprotection.com [184.154.58.230]) by dpdk.org (Postfix) with ESMTP id 13B8B1B1F2 for ; Thu, 14 Feb 2019 15:15:33 +0100 (CET) Received: from ns1.es18.siteground.eu ([37.60.250.193] helo=es18.siteground.eu) by se10.mailspamprotection.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1guHnN-0009jH-C4; Thu, 14 Feb 2019 08:15:32 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=filipjaniszewski.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=cg0ZCkax1uQmgmPzWK2TNFE1ksQ2YOEmxMg+Gp/3zkk=; b=lrGKunifSUaQQIVwbh59rvph1M 7n2/xH/m4H6IF0Y3SVFAM/uCkw0EvLU0e5Qlb+qUFI1mqAqcR2B29qT5Chm/20IOxBxRfH3VFSu0y wS7rKV/20xPmrGw0dIHQriRYWU28BqaN1MyaDpgQG87LN6RLi6cCOCHtQjW9bMYZQ5+n9VC5YKaya nXD6u7GjS1ULw1qwF9N4Wenv3dY3ukG5X5aumvfiLKtzxED9ymtKx1Fdh1ObRAJhA1XjnrjGj8cBc et90C8Q+HFlgKjp3rSPtNtjBGDED8zYX+oP5Ia/1gibOUDUfMriQwd9bV2SXT98afWi8ziLYTvuOm 7tdNdInQ==; Received: from [89.64.173.160] (port=47884 helo=localhost.localdomain) by es18.siteground.eu with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_34-9f6032f-XX) (envelope-from ) id 1guHnL-0009Ej-4g; Thu, 14 Feb 2019 15:15:19 +0100 To: "Wiles, Keith" Cc: "users@dpdk.org" References: <61d2793d-ca13-fdb3-e54f-4db40d95e9e0@filipjaniszewski.com> From: Filip Janiszewski Message-ID: Date: Thu, 14 Feb 2019 15:15:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: 37.60.250.193 X-SpamExperts-Domain: es18.siteground.eu X-SpamExperts-Username: 37.60.250.193 Authentication-Results: mailspamprotection.com; auth=pass smtp.auth=37.60.250.193@es18.siteground.eu X-SpamExperts-Outgoing-Class: unsure X-SpamExperts-Outgoing-Evidence: Combined (0.40) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5m0Iql/BZvuo7jaOprrhZ/F602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO/HgfYHNbHMZNn8uVEcaq0hO+JUrlpL+1xYGDni+Jm/nMXmrtlkagZCNRsz8za2guufH zJ6mVE7ewsipSVIfs4Y1kUBMF+7/Fm+2AVERNdYm1UoIZHeGiHTv13xbWqFGxfhpP1cvJDAY+VL9 7vvSgJYE/Xy9bqh2t87xwDNJ1ZQnDqV4HU/4GDpeJT9NA5fR9xljVqhxdXV3gQ/G9r9dUY+lrSS0 fOiU9O1ORZHe1ORqYSVLZvpS1kfaFtfjDudEZAMNwzSRr9TIm+vd5LtfSQMNa8sh5qcKvYnsSa35 QuNHGAFJ+4Vi0UkThksNRn9ICrsGOlWN3pRsVlO7BnVTW2964Bn/xFW1Emq7hJ1ivG4zukmd9wS3 TgOUAKXMmP2Nlqf2DNGP0n3HGosnygm28SP9hzvcC9WHTdL2y0kPKFsQeA6scZZwpzkCo4WoBCri 0gDAVE0LDqavceS6CUDOisguC54qR0DXEHm1B53l7yqVVzAFWiDMirclXJp1oBKOouidX4Ts4xdG +C13IyWeZaLC+hgdJnaNSwoYgJdy2z4N1/LPqWrl5xj0cfQm93CPpr8cWo7G3+wFFT3AIPPqlOxN +GexdZ58vH9EssKvvZn4VaDrik4fiMgKLi2enPUJDH7FMEP7qu/SPchpJyDbwRE7P1quDtp86hRV Bo77uuViolsjsKmEpxnUW3Jcsko0PrE8eE9A1b+cthrSSS2pEcfm50YjvGNn3s3M2vWqR2efKC6w HSGGAcD5hWLVwhNTLYsEMysPur9wmiDBurOy6iSVi7mjjEL2SlA9qXhzazmzs7s3T7E6W05I1ycv b4ZU+EMnAABZkz+F3APcd+vy/KmYUuytO1W65F23AA3P1fMgUV8ShebT8U8Xw9HTDfreWZBctMKK Gr7UW+abLI0J238qh6yfkXwqJrCRXYUh1YDrdLe11NKTA+JH4xuOSs8ucgNB8zFwqLHgp8Rw3SVX teRSoTE2v39zKLN72C6LMWVlYXsY7pPpudi7bULX4gWpY5PWzCAF99oTFEGQzm0y0S3TV0IKNdUB YEAlOVmg0AeqTWgMhWeRR1AfHEhZki7BEvY4ocfmWv3Fe9Iziczdq+A= X-Report-Abuse-To: spam@quarantine1.mailspamprotection.com Subject: Re: [dpdk-users] Segfault while running on older CPU X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2019 14:15:34 -0000 Hi, I prepared a simple test application with only a call to rte_eal_init and it crashes, DPDK version is 18.05 and apparently the problem is with the BMI2 instruction set, the faulty line is: . │0x57fec9 shrx %eax,%edx,%eax . I'm attempting to disable those instructions by setting march to corei7 which according to gcc does not include BMI2, but still when opening the asm list of the binary can see that instruction. If I understand correctly how the DPDK building process works then I should be able to set this 'corei7' switch by just changing mk/machine/default/rte.vars.mk and then setting CONFIG_RTE_MACHINE="default" in the x86_64-native-linuxapp-gcc/.config file, but I'm not sure whether it's picking it up while building (make T=x86_64-native-linuxapp-gcc DESTDIR=. -j28). Il 14/02/19 14:34, Wiles, Keith ha scritto: > > >> On Feb 14, 2019, at 7:04 AM, Filip Janiszewski wrote: >> >> Hi All, >> >> We've just encountered the same issue on a new server with a couple of >> Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, stack trace the same: >> > > What version of DPDK? >> . >> Program received signal SIGILL, Illegal instruction. >> >> 0x0000000000557ce9 in rte_cpu_get_flag_enabled () >> >> Missing separate debuginfos, use: debuginfo-install >> glibc-2.17-260.el7.x86_64 libaio-0.3.109-13.el7.x86_64 >> libgcc-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 >> numactl-libs-2.0.9-7.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 >> zlib-1.2.7-18.el7.x86_64 >> >> (gdb) bt >> >> #0 0x0000000000557ce9 in rte_cpu_get_flag_enabled () >> #1 0x000000000046076e in rte_acl_init () >> #2 0x000000000085f56d in __libc_csu_init () >> #3 0x00007ffff6636365 in __libc_start_main () from /lib64/libc.so.6 >> #4 0x00000000004650de in _start () >> . >> >> I'm building DPDK with x86_64-native-linuxapp-gcc, nothing else, plain >> config from DPDK. I've attempted to recompile with CONFIG_RTE_EXEC_ENV >> set to 'native' instead of 'linuxapp' but nothing changes. > > Not sure what this means it looks like you already compiled it as native. >> >> Did anybody had a similar issue? Any suggestion? > > maybe compile with -g for debug symbols. i use ‘make install T=$RTE_TARGET EXTRA_CFLAGS=“-g”’ you can also try reducing the optimization, but I do not think that is the problem. > > Does this happen every time, what OS version, what is the application yours or one of the examples? > If testpmd works then it maybe your application. I can not tell for sure but could this be the first time this routine is called? > Are you calling some thing in DPDK before rte_eal_init() is called? > > With -g you should them be able to location the line in DPDK where it is failing. >> >> Thanks >> >> Il 06/02/19 11:47, Filip Janiszewski ha scritto: >>> Hi Everybody, >>> >>> We have one 'slightly' older machine (well, very old CPU.) in our Lab >>> that seems to crash DPDK on every execution attempt, I was wondering if >>> anybody encountered a similar issue and if there's a change in the DPDK >>> config that might remedy the problem, this is the stack trace of the fault: >>> >>> . >>> #0 0x000000000057bd19 in rte_cpu_get_flag_enabled () >>> #1 0x000000000046067e in rte_acl_init () >>> #2 0x000000000088359d in __libc_csu_init () >>> #3 0x00007ffff6642cf5 in __libc_start_main () from /lib64/libc.so.6 >>> #4 0x0000000000464fee in _start () >>> . >>> >>> The CPU on this machine is: "Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz >>> (fam: 06, model: 3a, stepping: 09)" running with "3.10.0-862.el7.x86_64". >>> >>> Our builds are running fine on newest hardware, nevertheless the >>> segfault seems a bit weird even for an unsupported CPU (some error >>> prompt would be more friendly), any suggestion on what the problem might be? >>> >>> Thanks >>> >> >> -- >> BR, Filip >> +48 666 369 823 > > Regards, > Keith > -- BR, Filip +48 666 369 823