From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 21:58:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3208365E; Wed, 28 Jan 2015 21:58:01 +0000 (UTC) Received: from darkthrone.kvedulv.de (darkthrone.kvedulv.de [IPv6:2001:1578:400:101::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darkthrone.kvedulv.de", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E754D8AF; Wed, 28 Jan 2015 21:58:00 +0000 (UTC) Received: by darkthrone.kvedulv.de (Postfix, from userid 666) id E80031F2; Wed, 28 Jan 2015 22:57:48 +0100 (CET) Date: Wed, 28 Jan 2015 22:57:48 +0100 From: Michael Moll To: Mark Felder Subject: Re: Memory corruption in a master perl process after child exits - only under FreeBSD 10.0 amd64 (not in 10.1 or 9.*) Message-ID: <20150128215748.GA53812@darkthrone.kvedulv.de> References: <1ac9f02be1360da3969ddb9501d0375a@mailbox.ijs.si> <1422482005.645595.220197745.53E86A68@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1422482005.645595.220197745.53E86A68@webmail.messagingengine.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2015 21:58:01 -0000 Hi, On Wed, Jan 28, 2015 at 03:53:25PM -0600, Mark Felder wrote: > > https://rt.perl.org/Ticket/Display.html?id=122199 > > Given the ability to reproduce this 100% it seems perfect for using git > bisect command to figure out which commit between 10.0 and 10.1 solves > this. Sorry for coming late to this thread, but depending on the CPU it might be worth a try if it's fixed on 10.0 with vm.pmap.pcid_enabled set to 0. Regards -- Michael Moll