From owner-freebsd-current@freebsd.org Mon Jun 26 20:25: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 901EBD90EB9 for ; Mon, 26 Jun 2017 20:25:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 1C24F646D5 for ; Mon, 26 Jun 2017 20:25:30 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v5QKPOF1044664 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Jun 2017 23:25:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v5QKPOF1044664 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v5QKPO8U044663; Mon, 26 Jun 2017 23:25:24 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 26 Jun 2017 23:25:24 +0300 From: Konstantin Belousov To: Benjamin Kaduk Cc: Manfred Antar , FreeBSD Current Subject: Re: Current amd64 new error or warning from today's current with ruby r320323 Message-ID: <20170626202524.GY3437@kib.kiev.ua> References: <20170625012359.GS3437@kib.kiev.ua> <040BF7D1-2FDF-415B-9A17-ADD608503F14@pozo.com> <20170625020441.GT3437@kib.kiev.ua> <219E6B59-EF90-443D-8B53-4C39C4D6CFBD@pozo.com> <20170625134133.GA3437@kib.kiev.ua> <3FEA16E1-673F-4C58-8362-C1DCC0680698@pozo.com> <20170625145008.GB3437@kib.kiev.ua> <20170625164115.GD3437@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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 20:25:31 -0000 On Mon, Jun 26, 2017 at 02:53:14PM -0500, Benjamin Kaduk wrote: > On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov > wrote: > > > No need, I understood why MAP_STACK failed in this case, thanks to the > > ktrace log. This is indeed something ruby-specific, or rather, triggered > > by ruby special use of libthr. It is not related to the main stack > > split. > > > > It seems that ruby requested very small stack for a new thread, only 5 > > pages in size. This size caused the stack gap to be correctly calculated > > as having zero size, because the whole stack is allocated by initial grow. > > But then there is no space for the guard page, which caused mapping failure > > for it, and overall stack mapping failure. > > > > Try this. > > https://people.freebsd.org/~kib/misc/vm2.2.patch > > > > > I managed to get the "Cannot allocate red zone for initial thread" at the > start of installworld (doing CC feature detection, IIRC) going from r306247 > to r320328. > > Is it worth trying that patch out? Ensure that you run a kernel past r320344 and then show me ktrace of the failing process.