From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 8577614EC; Mon, 28 May 2018 17:25:21 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 28 May 2018 15:25:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 18.05 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: reshma.pattan@intel.com X-Bugzilla-Status: CONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://dpdk.org/tracker/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 53] rte abort issue on FreeBSD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 15:25:21 -0000 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.=