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

2017-06-24 Thread Manfred Antar 

> On Jun 24, 2017, at 7:04 PM, Konstantin Belousov  wrote:
> 
> On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote:
>> 
>>> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov  
>>> 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
 : 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
 : 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
>> : 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 .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 (0x800a0)
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.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2017-06-24 Thread Manfred Antar 

> On Jun 24, 2017, at 6:55 PM, David Wolfskill  wrote:
> 
> On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote:
>> ... 
>>> 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
> 
> You might want to re-do that, specifying the "-di" flags to ktrace (if
> the output fails to include activities from child processes, and tracing
> those is of interest).

Ok did:
ktrace -di /usr/local/bin/ruby -v

kdump -H -f ./ktrace.out >kdump-new.txt

File is at :

http://www.pozo.com/kernel/kdump-new.txt 


smaller than the first one.

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2017-06-24 Thread Konstantin Belousov 
On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote:
> 
> > On Jun 24, 2017, at 6:23 PM, Konstantin Belousov  
> > 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
> >> : 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
> >> : 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
> : 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 .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.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2017-06-24 Thread Manfred Antar 

> On Jun 24, 2017, at 6:23 PM, Konstantin Belousov  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
>> : 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
>> : 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
: 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 .txt

It’s not failing, I don’t think , I can do portupgrade and it works fine.
I just get this new message



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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2017-06-24 Thread Konstantin Belousov 
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
> : 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
> : 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.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2017-06-24 Thread Manfred Antar 
New world and kernel  r320323
I get a new error or message when using ruby:


/usr/local/sbin/portupgrade -av
: 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
: 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.

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Ports still broken by ino64?

2017-06-24 Thread Thomas Mueller 
> Maybe not, but I think so. synth(8) requires the ada compiler which means
> lang/gcc6-aux or lang/gcc5-aux and those DID require work to install on
> ino64. I believe that this is now resolved, but I would seriously consider
> simply installing synth from the package. It has no run or lib depends, so
> installing the package is risk-free.
 
> synth is the only package I install on my development system,though I do
> consider installing chromium and libreoffice from packages now and then...
> like every time I have to rebuild either. (libreoffice is awaiting for a
> rebuild right now. Maybe tomorrow. I built Chromium yesterday.)

> Kevin Oberman, Part time kid herder and retired Network Engineer

I remember synth required specifically the latest Ada compiler, gcc6-aux.

Part of the attraction is the Ada compiler suite in gcc(5,6)-aux, for the 
possibility of cross-compiling Linux toolchains including gcc with Ada.

Other dependencies would likely be needed sooner or later, anyway.

But I was successful on 11.1-PRERELEASE.

I never ran Chrome or Chromium, might want to try; also Midori and Netsurf (and 
of course, Mozilla Firefox or Seamonkey).

One attraction of Midori is the facility to fudge the useragent string, and 
hopefully thumb my nose on websites that require specific browsers/versions.

I would also like to try John Marino's port of synth to NetBSD, see if that, 
along with pkg, works better than regular pkgsrc tools.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: compiler-metadata.mk for main arch deleted when crossbuilding

2017-06-24 Thread Guy Yur 
On 23 June 2017 at 21:50, Bryan Drewery  wrote:
> On 6/23/2017 11:28 AM, Bryan Drewery wrote:
>> On 6/23/2017 11:00 AM, Guy Yur wrote:
>>> Hi Bryan,
>>>
>>> I use a script for building both amd64 and armv6 on an amd64 machine.
>>> Basically,
>>> export TARGET=amd64 TARGET_ARCH=amd64
>>> make -j2 -DNO_CLEAN buildworld
>>> export TARGET=arm TARGET_ARCH=armv6
>>> make -j2 -DNO_CLEAN buildworld
>>>
>>> The amd64 build creates /usr/obj/usr/src/compiler-metadata.mk
>>> The armv6 build deletes it and creates
>>> /usr/obj/arm.armv6/usr/src/compiler-metadata.mk
>>>
>>> If I rebuild just amd64 I get /usr/obj/usr/src/compiler-metadata.mk again.
>>>
>>> Does _cross-tools target's "@rm -f ${.OBJDIR}/compiler-metadata.mk"
>>> not respect TARGET and TARGET_ARCH?
>>>
>>
>> Yes, it is fixed now in r320286. Thanks for the report!
>>
>>
>
> This may have been the reason release.sh failed earlier.  Is release.sh
> still failing for you now?

Hi,

It fixed my problem.
My problem was that I couldn't do installworld or distributeworld
for the main arch after buildworld + cross buildworld.
I thought it was the same problem as the release.sh failure
when I replied to the other thread, sorry for the confusion.

>
> --
> Regards,
> Bryan Drewery
>

Thanks,
Guy
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"