Date: Mon, 26 Jun 2017 14:53:14 -0500 From: Benjamin Kaduk <bjkfbsd@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Manfred Antar <null@pozo.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Current amd64 new error or warning from today's current with ruby r320323 Message-ID: <CAJ5_RoDd8%2BOXPfeQ10U3f3-ZozhshWBUXdSVFpnx_ZkhO_n4bw@mail.gmail.com> In-Reply-To: <20170625164115.GD3437@kib.kiev.ua> References: <44028FBF-C8B1-4A69-B798-F4E28CFCD779@pozo.com> <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> <D94B09A1-9090-4C6A-8EC4-19D2AFBBA316@pozo.com> <20170625164115.GD3437@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 25, 2017 at 11:41 AM, Konstantin Belousov <kostikbel@gmail.com> 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? -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ5_RoDd8%2BOXPfeQ10U3f3-ZozhshWBUXdSVFpnx_ZkhO_n4bw>