From owner-freebsd-current@freebsd.org Sun Jun 25 02:20:04 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 A7C52D86AB4 for ; Sun, 25 Jun 2017 02:20:04 +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 86528804B3 for ; Sun, 25 Jun 2017 02:20:04 +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 v5P2JPc8065173; Sat, 24 Jun 2017 19:19:25 -0700 (PDT) (envelope-from null@pozo.com) Content-Type: text/plain; charset=us-ascii 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 From: Manfred Antar In-Reply-To: <20170625020441.GT3437@kib.kiev.ua> Date: Sat, 24 Jun 2017 19:19:25 -0700 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <219E6B59-EF90-443D-8B53-4C39C4D6CFBD@pozo.com> 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> To: Konstantin Belousov X-Mailer: Apple Mail (2.3273) X-Spam-Status: No, score=-102.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD,TW_LR,TW_RW,TW_WX,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: v5P2JPc8065173 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com 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 02:20:04 -0000 > On Jun 24, 2017, at 7:04 PM, Konstantin Belousov wr= ote: >=20 > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: >>=20 >>> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov = wrote: >>>=20 >>> On Sat, Jun 24, 2017 at 06:08:50PM -0700, Manfred Antar wrote: >>>> New world and kernel r320323 >>>> I get a new error or message when using ruby: >>>>=20 >>>>=20 >>>> /usr/local/sbin/portupgrade -av >>>>
: warning: pthread_create failed for timer: Resource temporarily= unavailable, scheduling broken >>>>=20 >>>> everything works just this message when using ruby. I recompiled ruby = , still same message >>>>=20 >>>> /usr/local/bin/ruby -v >>>>
: warning: pthread_create failed for timer: Resource temporarily= unavailable, scheduling broken >>>> ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12] >>>>=20 >>>> Not sure what???s changed, I noticed some commits to vm stuff, maybe t= hats it. >>>=20 >>> ktrace your failing ruby invocation, then post output of kdump -H somew= here. >>>=20 >>=20 >> Ok not sure if this is right , but this is what i did: >>=20 >> (tmp)4637}ktrace /usr/local/bin/ruby -v >>
: warning: pthread_create failed for timer: Resource temporarily u= navailable, scheduling broken >> ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12] >>=20 >> (tmp)4638}kdump -H -f ./ktrace.out > kdump.txt >>=20 >> you can get kdump.txt at: >>=20 >> http://www.pozo.com/kernel/kdump .txt >>=20 >> It???s not failing, I don???t think , I can do portupgrade and it works = fine. >> I just get this new message >=20 > I see what is going on, but it is somewhat strange that it happens. >=20 > Do you run ruby in a jail with old (say, stable/10) libthr ? > Or do you have environment variable LIBPTHREAD_SPLITSTACK_MAIN set in > your environment ? >=20 > Anyway, the rework of the stack grow indeed have incompatibility with the > old (pre-11) libthr, which tries to split main thread stack into smaller > stacks for the new threads. New stack grow code was specifically designed > to prevent this. Some hack would be needed there, to allow reuse of > the main stack gap. >=20 Not running any jails all libraries are current as of today locate libthr. |xargs ls -l -r--r--r-- 1 root wheel 120240 Jun 24 12:50 /lib/libthr.so.3 -r--r--r-- 1 root wheel 256072 Jun 24 12:50 /usr/lib/libthr.a lrwxr-xr-x 1 root wheel 21 Jun 24 12:50 /usr/lib/libthr.so -> ../../= lib/libthr.so.3 ldd /usr/local/bin/ruby -rwxr-xr-x 1 root wheel 2677552 Jun 24 18:22 /usr/local/lib/libruby23.so= .2 -rwxr-xr-x 1 root wheel 43832 Jun 24 19:10 /usr/local/lib/libunwind.so.8= .0.1 /usr/local/bin/ruby: libruby23.so.23 =3D> /usr/local/lib/libruby23.so.23 (0x800a00000) libelf.so.2 =3D> /lib/libelf.so.2 (0x800e9d000) libunwind.so.8 =3D> /usr/local/lib/libunwind.so.8 (0x8010b5000) libexecinfo.so.1 =3D> /usr/lib/libexecinfo.so.1 (0x8012ce000) libprocstat.so.1 =3D> /usr/lib/libprocstat.so.1 (0x8014d1000) libcrypt.so.5 =3D> /lib/libcrypt.so.5 (0x8016db000) libm.so.5 =3D> /lib/libm.so.5 (0x8018f9000) libthr.so.3 =3D> /lib/libthr.so.3 (0x801b26000) libc.so.7 =3D> /lib/libc.so.7 (0x801d4e000) libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x802335000) liblzma.so.5 =3D> /usr/lib/liblzma.so.5 (0x80254b000) libkvm.so.7 =3D> /lib/libkvm.so.7 (0x802774000) libutil.so.9 =3D> /lib/libutil.so.9 (0x802982000) no LIBPTHREAD_SPLITSTACK_MAIN set anywhere This is a fresh buildworld - installworld from noon today California time. here are env in make.conf: DEFAULT_VERSIONS=3D mysql=3D5.7 apache=3D2.4 python2=3D2.7 python3=3D3.4 ru= by=3D2.3 perl5=3D5.24 php=3D5.6 tcltk=3D8.6 samba=3D4.4 ssl=3Dbase ncurses= =3Dbase MALLOC_PRODUCTION=3Dyes WITH_BDB_VERSION=3D5 env in src.conf: WITHOUT_DYNAMICROOT=3Dyes=20 WITHOUT_UNBOUND=3Dyes WITHOUT_CASPER=3Dyes WITHOUT_CAPSICUM=3Dyes WITHOUT_DMAGENT=3Dyes WITHOUT_PROFILE=3Dyes WITHOUT_TESTS=3Dyes WITHOUT_KERNEL_SYMBOLS=3Dyes WITHOUT_DEBUG_FILES=3D1 WITHOUT_LIB32=3Dyes INSTALL_NODEBUG=3Dyes # Don't die on warnings NO_WERROR=3D WERROR=3D KERNCONF=3Dpozo WITH_CCACHE_BUILD=3Dyes Manfred --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.