From owner-freebsd-current@freebsd.org Mon Jun 26 12:01:03 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 0FA3FDA8A08 for ; Mon, 26 Jun 2017 12:01:03 +0000 (UTC) (envelope-from ohartmann@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 E382375B31 for ; Mon, 26 Jun 2017 12:01:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id E2D22DA8A06; Mon, 26 Jun 2017 12:01:02 +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 E27DBDA8A05 for ; Mon, 26 Jun 2017 12:01:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 49F8975B2C for ; Mon, 26 Jun 2017 12:01:01 +0000 (UTC) (envelope-from ohartmann@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 0MGWR2-1dToGr1SaG-00DFsW; Mon, 26 Jun 2017 14:00:53 +0200 Date: Mon, 26 Jun 2017 14:00:48 +0200 From: "O. Hartmann" To: Gary Jennejohn Cc: current@freebsd.org, David Wolfskill , Boris Samorodov , Konstantin Belousov Subject: Re: r319971 -> r320351: Fatal error 'Cannot allocate red zone for initial thread' Message-ID: <20170626140048.6d033c7e@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20170626132608.03eab0cf@ernst.home> References: <20170625120731.GE1241@albert.catwhisker.org> <20170626102942.274b42e6@freyja.zeit4.iv.bundesimmobilien.de> <20170626132608.03eab0cf@ernst.home> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ymkUFHCgADa06/w2o1aHsKYS95J35odIb40jXv/41PQzqappo6u Zh/CIE1bqTnNbn+5TasR5pcFM/ScLhTZy7m05t875T6XJOD9bmihBW3OBV3XTn5e0N3o6CV dOOVLkuRp+tx9XdoBH0xT8EStFvw/BkoG/Bx3sQS+WyrA3ahB8FLxPgU0VM12OiJbAOkeV+ Dn7NxQ2y9VmDFCBJoTBAQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:qEqZUptGTNY=:bGXQaQfX78MkK3K0KciUxp gFjThC8tCczZal/Loae1RKSAlzKQ3wVJBAN03PCjoK6G3Yz2WqRqGGsOwUgZzE2eW7dD0NcjO jHaNnNrJ4Gp+dsh+QCHZS/V6iGrNYkeZSpfwtKGKhDluICtIGRCi+LTYUIwHumqMfsFnF/DOZ tLeKez5Hyfmq+aOZjL6lRZWaX1T6v7TuILIx9OyL15aJQ0UvldIAsxrnbiutPDHUj9ld6LYOW JXSkvTRAbTaeA6cmf2JltPM9nwIMiuaKmvzuM4lrRTtMhRPurtTluoK+oRICecVpOlDvEvENI oPvTkEUKJWNMkgm7Xn1uTZOXCXC9UD/KU7jNb2Ti1/d+D4X54tyswJWSvEo4lJwIsM/GXswys oHrmThdy694/kxVYmhlUF7AHesiQukYo1qpHCZdCxPKc5PiyL4PeRUweXU6WlOzKRWmA4+aZ5 KkaAHS2eO3wFtwT0+9xZpsHjX3UM+HBAMcrq1Qg1O4w/X02D6wPoEAB5UsdanOAI7vhK/iBFI b9msPP6wdkXvK66+aJrA16ytKAWw3eXIQgmN40/ROXKL7GqKerrSfJAkgPSgyTzWRCmSQbtNn e9G3JmuTlXov4WHMB4oPb6HMa/pAGu8wqIt0A604bI0qxFk897/fcOkjLglVzRQDDgm1jZcv9 YVeMXBuWb0MVcKN68TkO/zuP/arUhhFOjR8SNa+YvHrEd5hL8gO/Fl/eU8gWoTEhrLojOlblF 58eCO3F7StQrUC6CBQOXXf3oRipVB8sLfUtwdPLtQ3dQ5MfZhZadmnd6TMmqIOoxoOmfKLFiU 9VP+ic7 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 12:01:03 -0000 On Mon, 26 Jun 2017 13:26:08 +0200 Gary Jennejohn wrote: > On Mon, 26 Jun 2017 10:29:47 +0200 > "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? > > > > How recent was your last update? Some changes were made just a few > hours ago to fix a stack growth problem in threads. Well, what do you mean by "... source is not up to date ..."? Performing an svn update of /usr/src should suffice, shouldn't it? If not, then ... please correct me. I think the sources are up to date as of the moment the bug occured. I consider the sources up to date, it is on the latest updated box r320355. There are so far two variations: one is r319971 -> 320351 as the subject indicates, the second box is r320144 -> 320355. > > Either your source is not up to date, or a new bug was introduced by > the intended fix. > As described earlier, I ran into a coredump by not having built world and kernel from scratch but with filemon. That was r320251. Cleaning (deleting) /usr/obj/* and rebuilding world and kernel and performing the update of the system as required (install the new kernel, boot the new kernel in single user mode) succeeded, but installworld then failed.