From owner-freebsd-current@freebsd.org Mon Jun 26 11:28:09 2017 Return-Path: Delivered-To: freebsd-current@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 7C375DA7942 for ; Mon, 26 Jun 2017 11:28:09 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C482874712 for ; Mon, 26 Jun 2017 11:28:08 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MKZLb-1dRN3g2x8x-001w6b; Mon, 26 Jun 2017 13:27:59 +0200 Date: Mon, 26 Jun 2017 13:27:58 +0200 From: "O. Hartmann" To: Steven Hartland Cc: freebsd-current@freebsd.org Subject: Re: r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread' Message-ID: <20170626132758.7d90ab70@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <6bd6a816-dbe4-1abf-f01b-da3afb03930c@multiplay.co.uk> References: <20170625120731.GE1241@albert.catwhisker.org> <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de> <6bd6a816-dbe4-1abf-f01b-da3afb03930c@multiplay.co.uk> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:CRURqGJFEN0ZkWSL74BvoB7w3U9mcDeNBiGIVjS2FMweKf7t/tn 9UrcvFDt7RyOmw8qs4Mfq1PnC9a+LKO0wIzkQg3oeOFM/+cVQbYyKCUqegA0UhneDmjNuXF jhPbiJbEK41j4E8/x6k8iNpxs18TibBrP0tOKXC53grPj3jKhNkjn7scQusqpMjSRGZGnck E/4I0Dq+X9ytTwyXm46ow== X-UI-Out-Filterresults: notjunk:1;V01:K0:/W/SmeKTMbA=:HAJzMugsPxoGhuNRAVP+Wf BdsnJTH/l4fGnK6b1LdKYmSqy1zvo6/XUklk/WAwZ0EVhNka12hL+MMw3ThjX+RDP4c7tqjt6 FWk839iGvFzrM3SX2Gw7TdD6lwRZIq5UCfZXl9yNsGrrAIu5EXgMwSaCUNbsSXtWy/+d37mTV +5NsCxQklLrjz7blvKSPmqxYcoYjnWJHpVOj+RlzgHRDngOt4oHWmWHqiD5mPtWrRoJwdloOo KmB8fYo9UxoB3naO+SMqD0BhH90TxSQZMpjlnzlprYyZdppvm8/NK1tDRMce9AqFx01jGVPxz aZg7P2WCaDEY0yCxFxrHNELqa+xVX3X3a4Vtmtm2aeOOKtXdvfnkqxXNZTw/U3TMsVo1K1bBi /IwD1YEiU50BZipYgQhbiIfT6X9OMlHCTiwGtRy2QhWnmqYo50sb7Q77dfSS/X+hQtRZafKnt /iLBjfY5pIVk42aTaMNrOVgCYNEptxbgujWigK/RvwSXAqghdxaqmAc0/EiuHnEyGZUrRxhzP 4/wxvpHTq05SicvnTIto0qLMgnGCuFzFWY/QAayUYhPzQPBfR8/qaJXYrSl7/HVAMd+7sgBXx p9Hzb2LZ6u5DTUY22NhDilebJgp60eWt/eCheDWjCDAs9jM8vIiNv2ppnzsGNRmuj+CDZeqLy uBmoiUvXrCcAnibH8sJZbTohfL8Y6Cd3eJBlu12ffvd9PbqvdV7tbiH2Mj3b+mifiGUB5Ilhy iJWqaq8VsrGphpEIIrbVjQVRNK1g6AJXzpbVqqYeXWBsduZlrWq6kWm8Lu96v6MejMAYLWDdp YU+OWLs X-Mailman-Approved-At: Mon, 26 Jun 2017 13:52:30 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 26 Jun 2017 11:28:09 -0000 On Mon, 26 Jun 2017 12:22:50 +0100 Steven Hartland wrote: > Is this related to kib's additional fix over the weekend? > > https://svnweb.freebsd.org/changeset/base/320344 > > Regards > Steve > > On 26/06/2017 09:29, O. Hartmann wrote: > > Over the past week we did not update several 12-CURRENT running development > > hosts, so today is the first day of performing this task. > > > > First I hit the very same problem David Wolfskill reported earlier, a fatal > > trap 12, but fowllowing the thread, I did as advised: removing /usr/obj > > completely (we use filemon/WITH_META_MODE=YES all over the place) and > > recompiling world and kernel. > > > > Since tag 20170617 in /usr/src/UPDATING referred to the INO64 update and the > > INO64 update hasn't performed so far starting from r319971, I installed the > > kernel, rebooted the box in single user mode (this time smoothly), did a > > mergemaster and tried to do "make installworld" - but the box instantanously > > bails out: > > > > [...] > > Fatal error 'Cannot allocate red zone for initial thread' at line 392 in > > file /usr/src/lib/libthread/thr_init.c > > pid 60 (cc) uid0: exited on signal 6 ... > > > > [...] > > > > That way, I obviously can not install a world :-( > > > > What is wrong here? Is the problem resovable? > > > > Kind regards, > > > > Oliver [...] The very same happens from updating r320144 -> r320355