Date: Sun, 25 Jun 2017 20:21:44 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Manfred Antar <null@pozo.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Current amd64 new error or warning from today's current with ruby r320323 Message-ID: <20170625172144.GE3437@kib.kiev.ua> In-Reply-To: <6579B80B-5581-4EBC-895F-5E7ED1D33641@pozo.com> 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> <D94B09A1-9090-4C6A-8EC4-19D2AFBBA316@pozo.com> <20170625164115.GD3437@kib.kiev.ua> <6579B80B-5581-4EBC-895F-5E7ED1D33641@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 25, 2017 at 10:09:07AM -0700, Manfred Antar wrote: > > > On Jun 25, 2017, at 9:41 AM, Konstantin Belousov <kostikbel@gmail.com> wrote: > > > > On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: > >> > >>> On Jun 25, 2017, at 7:50 AM, Konstantin Belousov <kostikbel@gmail.com> wrote: > >>> > >>> On Sun, Jun 25, 2017 at 07:43:25AM -0700, Manfred Antar wrote: > >>>> maybe message got reformatted in mail program (mac mail). > >>>> could you send me a tar file of the patch? > >>>> also not sure if ???patch -p1 <patchfile??? is the correct invocation of patch > >>>> > >>>> you could cc root@pozo.com <mailto:root@pozo.com> , that way i have copy on freebsd box and on mac. > >>> > >>> https://people.freebsd.org/~kib/misc/vm2.1.patch <https://people.freebsd.org/~kib/misc/vm2.1.patch>; > >> > >> OK patched and built new kernel \ > >> rebooted, > >> same ruby message. So it must be a ruby thing. > >> new kdump.txt at http://www.pozo.com/kernel/kdump.txt <http://www.pozo.com/kernel/kdump.txt>; > >> > >> also i???ll put a copy of my kernel config in same directory: > >> > >> http://www.pozo.com/kernel/pozo <http://www.pozo.com/kernel/pozo>; > >> > >> only one module is being loaded at boot: > >> (kernel)4908}kldstat > >> Id Refs Address Size Name > >> 1 5 0xffffffff80200000 10380a8 kernel > >> 2 1 0xffffffff8123a000 e13f50 nvidia.ko > >> > >> I can disable nvidia if it helps as I really only access this machine over the net or serial console. > >> > > 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 > > Seems to have worked: > > (~)4933}ruby -v > ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12] > (~)4934} > > No more message. Do you want new ktrace ? Thanks for testing. You might post the trace.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170625172144.GE3437>