From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 53] rte abort issue on FreeBSD
Date: Mon, 28 May 2018 15:25:21 +0000
Message-ID: <bug-53-3@http.dpdk.org/tracker/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://dpdk.org/tracker/show_bug.cgi?id=3D53

            Bug ID: 53
           Summary: rte abort issue on FreeBSD
           Product: DPDK
           Version: 18.05
          Hardware: All
                OS: FreeBSD
            Status: CONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: reshma.pattan@intel.com
  Target Milestone: ---

DPDK processes now allocates a large area of virtual memory address space,
 with this change during rte_abort FreeBSD now dumps the contents of the
 whole reserved memory range, not just the used portion, to a core dump fil=
e.
 Write this large core file can take a significant amount of time, causing
 processes to appear hung on the system.

 The work around for the issue is to set the system resource limits for core
 dumps before running any tests e.g."limit coredumpsize 0". This will
 effectively disable core dumps on FreeBSD. If they are not to be completely
 disabled, a suitable limit, e.g. 1G might be specified instead of 0. This
 needs to be run per-shell session, or before every test run. This change
 can also be made persistent by adding "kern.coredump=3D0" to /etc/sysctl.c=
onf

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