DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ophir Munk <ophirmu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"jianfeng.tan@intel.com" <jianfeng.tan@intel.com>,
	"shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] testpmd crashes on startup
Date: Fri, 4 May 2018 10:12:29 +0000	[thread overview]
Message-ID: <HE1PR0501MB23149A6715469E91E1ADBA30D1860@HE1PR0501MB2314.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <HE1PR0501MB23141E88A2B8E5643C0A2A7CD1860@HE1PR0501MB2314.eurprd05.prod.outlook.com>

The error printed with the crash:

*** Error in `/download/dpdk/x86_64-native-linuxapp-gcc/build/app/test-pmd/testpmd': corrupted double-linked list: 0x00000000010f1200 ***

> -----Original Message-----
> From: Ophir Munk
> Sent: Friday, May 04, 2018 12:38 PM
> To: dev@dpdk.org; jianfeng.tan@intel.com; shreyansh.jain@nxp.com
> Cc: Ferruh Yigit <ferruh.yigit@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; Olga Shern <olgas@mellanox.com>; Shahaf
> Shuler <shahafs@mellanox.com>
> Subject: testpmd crashes on startup
> 
> Hi Jianfeng,
> 
> Following commit 3d09a6e26d ("eal: fix threads block on barrier") I am
> seeing testpmd crashes on startups.
> The crashes occur 10% of the time with a regular compilation:
> 
> make install T=x86_64-native-linuxapp-gcc
> 
> and 70% of the time when using "-g" and "-o0" flags:
> 
> make install T=x86_64-native-linuxapp-gcc EXTRA_CFLAGS+=-g
> EXTRA_CFLAGS+=-O0
> 
> config/common_base:
> CONFIG_RTE_LIBRTE_MLX4_PMD=y
> 
> I am running with an mlx4 Mellanox NIC on an Azure VM.
> 
> Please note the crash back trace in [1].
> 
> Have you witnessed similar reports?
> I can provide more details if needed.
> 
> [1]
> Thread 1 "testpmd" received signal SIGABRT, Aborted.
> 0x00007ffff6ae4428 in GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0 0x00007ffff6ae4428 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/unix/sysv/linux/raise.c:54
> #1 0x00007ffff6ae602a in __GI_abort () at abort.c:89
> #2 0x00007ffff6b267ea in __libc_message (do_abort=do_abort@entry=2,
> fmt=fmt@entry=0x7ffff6c3fed8 "*** Error in `%s': %s: 0x%s ***\n") at
> ../sysdeps/posix/libc_fatal.c:175
> #3 0x00007ffff6b2d6ed in malloc_printerr (ar_ptr=0x7ffff6e73b20
> <main_arena>, ptr=<optimized out>, str=0x7ffff6c3cc92 "corrupted double-
> linked list", action=<optimized out>) at malloc.c:5006
> #4 malloc_consolidate (av=av@entry=0x7ffff6e73b20 <main_arena>) at
> malloc.c:4183
> #5 0x00007ffff6b30cde in _int_malloc (av=av@entry=0x7ffff6e73b20
> <main_arena>, bytes=bytes@entry=1968) at malloc.c:3450
> #6 0x00007ffff6b33184 in __GI_libc_malloc (bytes=1968) at malloc.c:2913
> #7 0x000000000057a939 in pci_scan_one (dirname=0x7fffffffd120
> "/sys/bus/pci/devices/0002:00:02.0", addr=0x7fffffffd100) at ***/dpdk-
> branches/drivers/bus/pci/linux/pci.c:226
> #8 0x000000000057b3d8 in rte_pci_scan () at ***/dpdk-
> branches/drivers/bus/pci/linux/pci.c:463
> #9 0x0000000000554bce in rte_bus_scan () at ***/dpdk-
> branches/lib/librte_eal/common/eal_common_bus.c:77
> #10 0x000000000053e3e8 in rte_eal_init (argc=17, argv=0x7fffffffe428) at
> ***/dpdk-branches/lib/librte_eal/linuxapp/eal/eal.c:783
> #11 0x0000000000470279 in main (argc=17, argv=0x7fffffffe428) at
> ***/dpdk-branches/app/test-pmd/testpmd.c:2597

      reply	other threads:[~2018-05-04 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  9:37 Ophir Munk
2018-05-04 10:12 ` Ophir Munk [this message]

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=HE1PR0501MB23149A6715469E91E1ADBA30D1860@HE1PR0501MB2314.eurprd05.prod.outlook.com \
    --to=ophirmu@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=thomas@monjalon.net \
    /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).