Re: Current amd64 new error or warning from today's current with ruby r320323

> On Jun 24, 2017, at 7:04 PM, Konstantin Belousov <kostikbel_at_gmail.com> wrote:
> 
> On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote:
>> 
>>> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov <kostikbel_at_gmail.com> wrote:
>>> 
>>> 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:
>>>> 
>>>> 
>>>> /usr/local/sbin/portupgrade -av
>>>> <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
>>>> 
>>>> everything works just this message when using ruby. I recompiled ruby , still same message
>>>> 
>>>> /usr/local/bin/ruby -v
>>>> <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
>>>> ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12]
>>>> 
>>>> Not sure what???s changed, I noticed some commits to vm stuff, maybe thats it.
>>> 
>>> ktrace your failing ruby invocation, then post output of kdump -H somewhere.
>>> 
>> 
>> Ok not sure  if this is right , but this is what i did:
>> 
>> (tmp)4637}ktrace /usr/local/bin/ruby -v
>> <main>: warning: pthread_create failed for timer: Resource temporarily unavailable, scheduling broken
>> ruby 2.3.4p301 (2017-03-30 revision 58214) [amd64-freebsd12]
>> 
>> (tmp)4638}kdump -H -f ./ktrace.out >  kdump.txt
>> 
>> you can get kdump.txt at:
>> 
>> http://www.pozo.com/kernel/kdump <http://www.pozo.com/kernel/kdump>.txt
>> 
>> It???s not failing, I don???t think , I can do portupgrade and it works fine.
>> I just get this new message
> 
> I see what is going on, but it is somewhat strange that it happens.
> 
> 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 ?
> 
> 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.
> 

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 => /usr/local/lib/libruby23.so.23 (0x800a00000)
	libelf.so.2 => /lib/libelf.so.2 (0x800e9d000)
	libunwind.so.8 => /usr/local/lib/libunwind.so.8 (0x8010b5000)
	libexecinfo.so.1 => /usr/lib/libexecinfo.so.1 (0x8012ce000)
	libprocstat.so.1 => /usr/lib/libprocstat.so.1 (0x8014d1000)
	libcrypt.so.5 => /lib/libcrypt.so.5 (0x8016db000)
	libm.so.5 => /lib/libm.so.5 (0x8018f9000)
	libthr.so.3 => /lib/libthr.so.3 (0x801b26000)
	libc.so.7 => /lib/libc.so.7 (0x801d4e000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x802335000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x80254b000)
	libkvm.so.7 => /lib/libkvm.so.7 (0x802774000)
	libutil.so.9 => /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= mysql=5.7 apache=2.4 python2=2.7 python3=3.4 ruby=2.3 perl5=5.24 php=5.6 tcltk=8.6 samba=4.4 ssl=base ncurses=base
MALLOC_PRODUCTION=yes
WITH_BDB_VERSION=5

env in src.conf:
WITHOUT_DYNAMICROOT=yes 
WITHOUT_UNBOUND=yes
WITHOUT_CASPER=yes
WITHOUT_CAPSICUM=yes
WITHOUT_DMAGENT=yes
WITHOUT_PROFILE=yes
WITHOUT_TESTS=yes
WITHOUT_KERNEL_SYMBOLS=yes
WITHOUT_DEBUG_FILES=1
WITHOUT_LIB32=yes
INSTALL_NODEBUG=yes

# Don't die on warnings
NO_WERROR=
WERROR=
KERNCONF=pozo
WITH_CCACHE_BUILD=yes

Manfred



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.