From owner-freebsd-threads@freebsd.org Mon Feb 1 13:34:33 2016 Return-Path: Delivered-To: freebsd-threads@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAEB5A97411 for ; Mon, 1 Feb 2016 13:34:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C8411975 for ; Mon, 1 Feb 2016 13:34:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u11DYXxt072622 for ; Mon, 1 Feb 2016 13:34:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Date: Mon, 01 Feb 2016 13:34:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rblayzor@inoc.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2016 13:34:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #24 from rblayzor@inoc.net --- (In reply to Konstantin Belousov from comment #23) These VM's boot diskless and mount their root file system as RO.=20 Trying to mount root from nfs: []... NFS ROOT: 10.0.0.211:/vol/bsdroot/v0f Where "v0f" is nothing more than subdir for a new rootfs. "bsdroot" is jus= t a NetApp volume RO volume from these hosts. There is a VMDK (virtual disk) that is mounted at boot time; which is a thin provision disk 10GB in size. 2GB a 2Gbps swap partition and a 8Gb scratch = disk for things like /var or /var/tmp da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device bootpc_init: wired to interface 'vmx0' da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da0: Command Queueing enabled da0: 10240MB (20971520 512 byte sectors: 255H 63S/T 1305C) da0: quirks=3D0x40 The port binaries are built on a another FreeBSD 10.2 platform (same VM con= fig) and then we rsync /usr/local to be part of the rootfs. We always keep the port builds and the base system fresh and in sync. Typic= ally when we want roll out a new version of FreeBSD we'll upgrade the build VM first, then create a new subdir for rootfs and install there. Followed by a complete port rebuild and resync. This has always worked for us since FreeB= SD 8.x just fine... Only recently we've seen these random, strange, unexplainable core dumps. --=20 You are receiving this mail because: You are the assignee for the bug.=