From owner-freebsd-current@freebsd.org Mon Jun 26 08:35:31 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 1EB09DA4786 for ; Mon, 26 Jun 2017 08:35:31 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 001B26F6B3 for ; Mon, 26 Jun 2017 08:35:30 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id F31A8DA4785; Mon, 26 Jun 2017 08:35:30 +0000 (UTC) Delivered-To: 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 F0FB8DA4783 for ; Mon, 26 Jun 2017 08:35:30 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 4FA5C6F6B2 for ; Mon, 26 Jun 2017 08:35:29 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MAloF-1dbH7A3GGZ-00BsI9; Mon, 26 Jun 2017 10:29:55 +0200 Date: Mon, 26 Jun 2017 10:29:47 +0200 From: "O. Hartmann" To: current@freebsd.org Cc: David Wolfskill , Boris Samorodov , Konstantin Belousov Subject: r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread' Message-ID: <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20170625120731.GE1241@albert.catwhisker.org> References: <20170625120731.GE1241@albert.catwhisker.org> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:cVQnWl2h9IcH7SFdQ8JTwFPiMradkCPBT3NHg+Mw6Ie7voeVrH5 D2cZmGcNaBMzgUmXr4PwD2N+lkQ4HoiOXuVI0Np8GwXTvrnLbmoQP8VyqEswmO9rOj0vdp7 Xruqv19JwRGo5iyHEVxRmX8p+fiR6+qRNOAXhkP/8Z5QpvTkKG0GtwUfDdMc8aoKM6HmBml ljJW5zudjXz7MeKLlKTow== X-UI-Out-Filterresults: notjunk:1;V01:K0:1kquu7xfLuo=:5pgUDKOwGuM6j7aJ9GJGXk W0M1CUp/bqxZuLlM017Dw+3A1l970lC2x4l9gg6CKynDf9U+sFJcMBf3yfyuQWfS81VbKskaa U6RMQyRFFcpQnypBjYp9wtKdMfmWU6wzidP5oLI4l12U8UPzEHGj7SYYoa0rm2v4oaaOFUkUa E9adSCHm2CCo4OYANRSBagUTDjVUV9+O+LLOxbdaOP36HdNn2c9/BQMfGIF2feLUYeuObI/TE 6XLEnIOxpGQ6d7jFYZ50cUBC5DKSa2d4lMLbTYbubo+D1aj7K/HQ6F/m7Jhxjxmg9ZElfnIPe 2BuaPEQqUZnKWsa6jJ+CWNMLWFXvTMFyRIwcj3MTKRrRvbRXUzF2iKqPS7y6zzG3dCzZ0lhO7 6t7d10TERhMvim3gaxasqzDbbaRUfEW0eYjDp6pPUIXS7vcYTVCQGO3k0LROpgLAmd3bWWISX likLDQrV5Bl8oQvUMA1fKl43VdnFM3Ug9UnC6ODYR2j8tIcAj5DAnracn11U4eQnxMWFkdxiq vjGPBp6r/q91GPsTnaQcDUw4oXdbOOFWJuWlr6eRwhbGByeYXxn2YU8146OQnLus7+4CH9bIW B37Lzy1pywF462gwDvjb5Ruy15h5JrOwCkkkPFMUWEkSIaFGYb5joa0YD1Bm16SKb8/hxd5Id dfbFxfa40TY2bdjoqFRZeUPHdSww/2Oe5vo0FcbMlHXDs2pxV3SrsvyrIKMCiJCuaRqBLI88F uGH4CSUD7/gjkvHLnHO2SS3t0cpYgPgKB63GVm7rtn0ccu9EqVmN+0KB09Lu18qJFtfePSzA1 v3gHr+n X-Mailman-Approved-At: Mon, 26 Jun 2017 10:58:58 +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 08:35:31 -0000 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