From owner-freebsd-current@freebsd.org Sun Jun 25 17:36:39 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 95873D96425 for ; Sun, 25 Jun 2017 17:36:39 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [50.197.129.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "pozo.com", Issuer "pozo.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A82C7787F for ; Sun, 25 Jun 2017 17:36:39 +0000 (UTC) (envelope-from null@pozo.com) Received: from 50-197-129-138-static.hfc.comcastbusiness.net (octo.pozo.com [192.168.0.2]) (authenticated bits=128) by pozo.com (8.15.2/8.15.2) with ESMTPA id v5PHYPkG000168; Sun, 25 Jun 2017 10:34:25 -0700 (PDT) (envelope-from null@pozo.com) From: Manfred Antar Message-Id: <2BB1817F-A1CF-44A9-8520-332E2D565EAB@pozo.com> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Current amd64 new error or warning from today's current with ruby r320323 Date: Sun, 25 Jun 2017 10:34:25 -0700 In-Reply-To: <20170625172144.GE3437@kib.kiev.ua> Cc: FreeBSD Current To: Konstantin Belousov 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> <6579B80B-5581-4EBC-895F-5E7ED1D33641@pozo.com> <20170625172144.GE3437@kib.kiev.ua> X-Mailer: Apple Mail (2.3273) X-Spam-Status: No, score=-102.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, HTML_MESSAGE,J_CHICKENPOX_62,RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.1, No X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: v5PHYPkG000168 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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: Sun, 25 Jun 2017 17:36:39 -0000 > On Jun 25, 2017, at 10:21 AM, Konstantin Belousov w= rote: >=20 > On Sun, Jun 25, 2017 at 10:09:07AM -0700, Manfred Antar wrote: >>=20 >>> On Jun 25, 2017, at 9:41 AM, Konstantin Belousov = wrote: >>>=20 >>> On Sun, Jun 25, 2017 at 08:21:33AM -0700, Manfred Antar wrote: >>>>=20 >>>>> On Jun 25, 2017, at 7:50 AM, Konstantin Belousov wrote: >>>>>=20 >>>>> 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 >>>>>=20 >>>>>> you could cc root@pozo.com , that way i have = copy on freebsd box and on mac. >>>>>=20 >>>>> https://people.freebsd.org/~kib/misc/vm2.1.patch >>>>=20 >>>> 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 >>>>=20 >>>> also i???ll put a copy of my kernel config in same directory: >>>>=20 >>>> http://www.pozo.com/kernel/pozo >>>>=20 >>>> 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=20 >>>>=20 >>>> I can disable nvidia if it helps as I really only access this machine = over the net or serial console. >>>>=20 >>> 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. >>>=20 >>> 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 calculat= ed >>> as having zero size, because the whole stack is allocated by initial gr= ow. >>> But then there is no space for the guard page, which caused mapping fai= lure >>> for it, and overall stack mapping failure. >>>=20 >>> Try this. >>> https://people.freebsd.org/~kib/misc/vm2.2.patch >>=20 >> Seems to have worked: >>=20 >> (~)4933}ruby -v >> ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12] >> (~)4934} >>=20 >> No more message. Do you want new ktrace ? >=20 > Thanks for testing. You might post the trace. New trace at : http://www.pozo.com/kernel/kdump-working.txt Thanks --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.