Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

Hey, at least some people think these systems are interesting.

I gave up trying to build much of anything on the Ubiquiti USG.  I really
bought it to give me some play time with it over christmas to new year
holiday.

At work I have a USG Pro and it is capable of building GCC and LLVM,
albeit you have to size /usr/ports/pobj partition large enough to
build LLVM.

I am using a Rocketek Aluminum USB 3.0 Portable Memory Card Reader
Adapterfor Micro SD Card with a Sandisk Ultra 128GB Micro SDXC UHS-I Card 
for storage.  The combox works well, whereas I believed I thrashed the

128GB USB thumb drive on the home USG.

The system works well enough to allow me to do some ports debugging 
with Stuart Henderson; Asterisk and tshark.


diana



Past hissy-fits are not a predictor of future hissy-fits.
Nick Holland(06 Dec 2005)

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Tom Smyth]

Hi Diana,
Have you tried the Ubiquiti Edge Router Lite / Pro...
They have a USB adapter inside on the PCB to allow for reasonably easy
Loading of install.fs etc

it may be worth trying as it uses a similar architecture as the UBiquiti USG...

I hope this is some help to you ...

I was using them a little bit before moving onto the PC Engines x86 APU C2

Thanks

Tom Smyth


On 21 February 2018 at 18:18, Diana Eichert  wrote:
> Hey, at least some people think these systems are interesting.
>
> I gave up trying to build much of anything on the Ubiquiti USG.  I really
> bought it to give me some play time with it over christmas to new year
> holiday.
>
> At work I have a USG Pro and it is capable of building GCC and LLVM,
> albeit you have to size /usr/ports/pobj partition large enough to
> build LLVM.
>
> I am using a Rocketek Aluminum USB 3.0 Portable Memory Card Reader
> Adapterfor Micro SD Card with a Sandisk Ultra 128GB Micro SDXC UHS-I Card
> for storage.  The combox works well, whereas I believed I thrashed the
> 128GB USB thumb drive on the home USG.
>
> The system works well enough to allow me to do some ports debugging with
> Stuart Henderson; Asterisk and tshark.
>
> diana
>
>
>
> Past hissy-fits are not a predictor of future hissy-fits.
> Nick Holland(06 Dec 2005)
>



-- 
Kindest regards,
Tom Smyth

Mobile: +353 87 6193172
The information contained in this E-mail is intended only for the
confidential use of the named recipient. If the reader of this message
is not the intended recipient or the person responsible for
delivering it to the recipient, you are hereby notified that you have
received this communication in error and that any review,
dissemination or copying of this communication is strictly prohibited.
If you have received this in error, please notify the sender
immediately by telephone at the number above and erase the message
You are requested to carry out your own virus check before
opening any attachment.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Bryan Vyhmeister]

I have had a few discussions with visa@ about builds on OpenBSD/octeon.
For ports builds, 1GB of memory like in the EdgeRouter 4 and 6 is too
little to build big things like gcc which is required for quite a few
things. The EdgeRouter Lite, EdgeRouter PoE, and USG are even worse with
512MB of memory. Also, the EdgeRouter 4 and 6 have some issues with the
USB 3.0 controller that visa@ has not been able to work out yet. It's
pretty difficult to get any insight into what is happening with the USB
3.0 controller. The ER4 and ER6 work reasonably well with Samsung USB
Fit USB 3.0 flash drive but occasionally weird errors happen and the
system freezes up or panics. I was not able to get a Samsung T3 or T5
USB SSD to work with the ER4 or ER6.

The best route for a readily available machine for OpenBSD/octeon builds
is either the USG Pro 4 or the EdgeRouter Pro. They both come with 2GB
of memory but can be upgraded with up to 8GB of memory. Unlike the USB
flash drives in the USG and EdgeRouter Lite/PoE, the internal storage is
soldered on as was said in this thread already. The best route for
storage I have found thus far is a USB SSD like the Samsung T3 or T5. I
have not tested any others at this point but others probably work as
well.

For the EdgeRouter Pro, I have it running from a 250GB Samsung T3 USB
SSD and have upgraded it with an 8GB SODIMM of DDR3 1333MHz memory. The
part number that worked for the EdgeRouter Pro is Patriot PSD38G13332S.
I found this information from the UBNT forums.

For the USG Pro 4, I bought the same Patriot memory but had all sorts of
crashes and problems. I'm not sure if the memory chip is bad or if it is
just expecting different memory (have not had time to test) but I looked
at the factory memory in the USG Pro 4 and bought similar memory which
works fine. The factory chip is Kingston KVR16S11S6/2. I bought a set of
Kingston KVR16S11K2/16 which is two 8GB chips. They work perfectly and I
plan to get another USG Pro 4 for a second build machine to utilize the
second 8GB chip I have.

With 8GB of memory, most ports builds work fine including gcc but
occasionally I see some weird error that usually disappears with
restarting the dpb(1) build.

Bryan

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[john slee]

I also had a similar experience trying to build gcc6 on my Edgerouter Lite
(same model
as linked on tedu's blog page, which is how I discovered this little
machine initially) on
a snapshot from ~2 weeks ago. MP kernel, with the ERL's /usr/ports on an
NFS volume
hosted by an amd64 OpenBSD system.

I had a 'vmstat 15' running in another terminal throughout and it did dip
down into low
double-digits a few minutes before the segfault

I realise this post is not terribly useful other than being a "me too". If
it's worth my trying
a non-MP kernel I'll do that and report back

John


On 1 January 2018 at 05:52, Janne Johansson  wrote:
>
> 2017-12-30 5:01 GMT+01:00 Diana Eichert :
>
> > Hi misc@ long time since I posted
> >
> > collect2: error: ld terminated with signal 11 [Segmentation fault]
> >
> > while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway
> >
> > I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel.
> >
> > System built 109 packages before Seg Fault when building gcc-4.9.4
> >
> >
> I think I got those on my Octeon also, but I thought gcc had figured out a
> way to drive my
> box into swap and die so I just stopped trying to build gcc from ports.
>
>
> --
> May the most significant bit of your life be positive.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

Just used J00 screwdriver to open my USG-PRO 4, worked great.

Unfortunately I found the USG-PRO 4 uses a soldered SanDisk SDIN7DP2-4G
eMMC Flash Drive.  No way to replace internal storage.  ;-)


On Sat, 6 Jan 2018, Diana Eichert wrote:


thanks, I had come to a similar conclusion, though I think they are
JIS screws.

diana

On Sat, 6 Jan 2018, Mihai Popescu wrote:


the PH00 screws don't want to turn with my jeweler's screwdriver.


They may be PZ00. Take care not to mix different types of screws and
bits! PH and PZ look very much alike.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

thanks, I had come to a similar conclusion, though I think they are
JIS screws.

diana

On Sat, 6 Jan 2018, Mihai Popescu wrote:


the PH00 screws don't want to turn with my jeweler's screwdriver.


They may be PZ00. Take care not to mix different types of screws and
bits! PH and PZ look very much alike.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Mihai Popescu]

> the PH00 screws don't want to turn with my jeweler's screwdriver.

They may be PZ00. Take care not to mix different types of screws and
bits! PH and PZ look very much alike.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

All I hear is crickets, so I guess the SDNA Shasta is not available to 
mortals.


I just rebuilt the OpenBSD build on my Ubiquiti USG with 5 GB swap.
Reminds me of running FreeBSD on 486 systems back in the 90's. ;-)
I have it building telephony/asterisk package, which has a LOT
of dependencies.

I just got my USG Pro at work.  I'm having fun opening it, the PH00
screws don't want to turn with my jeweler's screwdriver.  So I'm
going to try to find a PH00 bit for my impact screwdriver.

diana

On Tue, 2 Jan 2018, Jordan Geoghegan wrote:

I too have have tried contacting them, but with no response. Does anyone have 
any info on the Shasta or even the Edgerouter6 availability?


Jordan

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Jordan Geoghegan]

I too have have tried contacting them, but with no response. Does anyone 
have any info on the Shasta or even the Edgerouter6 availability?


Jordan


On 01/02/18 09:42, Diana Eichert wrote:

On Mon, 1 Jan 2018, Visa Hankala wrote:


On Mon, Jan 01, 2018 at 07:53:20AM -0700, Diana Eichert wrote:


Would that be an SGI Origin 3000 model?


The machine is an SDNA Shasta with OCTEON III CN7130 SoC.


I tried to contact Rhino Labs several months ago about getting an
SDNA Shasta.  I never heard back from them.  Do you or someone
else on OpenBSD project have a contact for Rhino Labs?

thanks for the info you have provided,
diana

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

On Mon, 1 Jan 2018, Visa Hankala wrote:


On Mon, Jan 01, 2018 at 07:53:20AM -0700, Diana Eichert wrote:


Would that be an SGI Origin 3000 model?


The machine is an SDNA Shasta with OCTEON III CN7130 SoC.


I tried to contact Rhino Labs several months ago about getting an
SDNA Shasta.  I never heard back from them.  Do you or someone
else on OpenBSD project have a contact for Rhino Labs?

thanks for the info you have provided,
diana

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Visa Hankala]

On Mon, Jan 01, 2018 at 07:53:20AM -0700, Diana Eichert wrote:
> On Mon, 1 Jan 2018, Visa Hankala wrote:
> 
> > On Sun, Dec 31, 2017 at 09:35:35PM -0700, Diana Eichert wrote:
> > > I'm wondering if the system is to resource constrainted.  Do you know 
> > > which
> > > system was used to build octeon release?
> > 
> > Latest snapshots of big-endian mips64 packages have been built
> > using a quad-core machine with 4 GiB of RAM.
> 
> Would that be an SGI Origin 3000 model?

The machine is an SDNA Shasta with OCTEON III CN7130 SoC.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

On Mon, 1 Jan 2018, Visa Hankala wrote:


On Sun, Dec 31, 2017 at 09:35:35PM -0700, Diana Eichert wrote:

I'm wondering if the system is to resource constrainted.  Do you know which
system was used to build octeon release?


Latest snapshots of big-endian mips64 packages have been built
using a quad-core machine with 4 GiB of RAM.


Would that be an SGI Origin 3000 model?  I might be able to find one
at work, that is if they haven't already been sent to the scrap heap.

thanks for your input,

diana

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Visa Hankala]

On Sun, Dec 31, 2017 at 09:35:35PM -0700, Diana Eichert wrote:
> I'm wondering if the system is to resource constrainted.  Do you know which
> system was used to build octeon release?

Latest snapshots of big-endian mips64 packages have been built
using a quad-core machine with 4 GiB of RAM.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

Since the default kernel is single proc I've reverted to GENERIC bsd and 
I'm still having issues building package.


I'm wondering if the system is to resource constrainted.  Do you know 
which system was used to build octeon release?


thanks

On Sat, 30 Dec 2017, Visa Hankala wrote:


On Fri, Dec 29, 2017 at 09:01:06PM -0700, Diana Eichert wrote:

Hi misc@ long time since I posted

collect2: error: ld terminated with signal 11 [Segmentation fault]

while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway

I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel.

System built 109 packages before Seg Fault when building gcc-4.9.4

When posting dmesg I just noticed all the "write failed: errno 14" messages


There are SMP-related bugs in the low-level machine-dependent memory
management code. The current workaround is to restart the build.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Janne Johansson]

2017-12-30 5:01 GMT+01:00 Diana Eichert :

> Hi misc@ long time since I posted
>
> collect2: error: ld terminated with signal 11 [Segmentation fault]
>
> while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway
>
> I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel.
>
> System built 109 packages before Seg Fault when building gcc-4.9.4
>
>
I think I got those on my Octeon also, but I thought gcc had figured out a
way to drive my
box into swap and die so I just stopped trying to build gcc from ports.


-- 
May the most significant bit of your life be positive.

Re: gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Visa Hankala]

On Fri, Dec 29, 2017 at 09:01:06PM -0700, Diana Eichert wrote:
> Hi misc@ long time since I posted
> 
> collect2: error: ld terminated with signal 11 [Segmentation fault]
> 
> while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway
> 
> I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel.
> 
> System built 109 packages before Seg Fault when building gcc-4.9.4
> 
> When posting dmesg I just noticed all the "write failed: errno 14" messages

There are SMP-related bugs in the low-level machine-dependent memory
management code. The current workaround is to restart the build.

gcc-4.9.4 package build signal 11 [Segmentation fault] on Ubiquiti Unifi Security Gateway

[Diana Eichert]

Hi misc@ long time since I posted

collect2: error: ld terminated with signal 11 [Segmentation fault]

while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway

I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel.

System built 109 packages before Seg Fault when building gcc-4.9.4

When posting dmesg I just noticed all the "write failed: errno 14" 
messages


any/all pointers are appreciated.

/usr/ports/pobj/gcc-4.9.4/bin/egcc -c -g  -gnatp -gnatws -nostdinc -I- -I. 
-Iada -I/usr/ports/pobj/gcc-4.9.4/gcc-4.9.4/gcc/ada 
-I/usr/ports/pobj/gcc-4.9.4/gcc-4.9.4/gcc/ada/gcc-interface \

ada/b_gnat1.adb -o ada/b_gnat1.o
/usr/ports/pobj/gcc-4.9.4/bin/eg++ -g -DIN_GCC -fno-exceptions -fno-rtti 
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
-Wcast-qual -Wno-format -Wmissing-format-attribute -pedantic 
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common 
-DHAVE_CONFIG_H -static-libstdc++ -static-libgcc  -o gnat1 ada/adadecode.o 
ada/adaint.o ada/argv.o ada/cio.o ada/cstreams.o ada/env.o ada/init.o 
ada/initialize.o ada/raise.o ada/seh_init.o ada/targext.o ada/cuintp.o 
ada/decl.o ada/misc.o ada/utils.o ada/utils2.o ada/trans.o ada/targtyps.o 
ada/a-charac.o ada/a-chlat1.o ada/a-elchha.o ada/a-except.o ada/a-ioexce.o 
ada/ada.o ada/spark_xrefs.o ada/ali.o ada/alloc.o ada/aspects.o 
ada/atree.o ada/butil.o ada/casing.o ada/checks.o ada/comperr.o 
ada/csets.o ada/cstand.o ada/debug.o ada/debug_a.o ada/einfo.o 
ada/elists.o ada/err_vars.o ada/errout.o ada/erroutc.o ada/eval_fat.o 
ada/exp_aggr.o ada/exp_spark.o ada/exp_atag.o ada/exp_attr.o ada/exp_cg.o 
ada/exp_ch11.o ada/exp_ch12.o ada/exp_ch13.o ada/exp_ch2.o ada/exp_ch3.o 
ada/exp_ch4.o ada/exp_ch5.o ada/exp_ch6.o ada/exp_ch7.o ada/exp_ch8.o 
ada/exp_ch9.o ada/exp_code.o ada/exp_dbug.o ada/exp_disp.o ada/exp_dist.o 
ada/exp_fixd.o ada/exp_imgv.o ada/exp_intr.o ada/exp_pakd.o ada/exp_prag.o 
ada/exp_sel.o ada/exp_smem.o ada/exp_strm.o ada/exp_tss.o ada/exp_util.o 
ada/exp_vfpt.o ada/expander.o ada/fmap.o ada/fname-uf.o ada/fname.o 
ada/freeze.o ada/frontend.o ada/g-byorma.o ada/g-hesora.o ada/g-htable.o 
ada/g-spchge.o ada/g-speche.o ada/g-u3spch.o ada/get_spark_xrefs.o 
ada/get_targ.o ada/gnat.o ada/gnatvsn.o ada/hostparm.o ada/impunit.o 
ada/inline.o ada/interfac.o ada/itypes.o ada/krunch.o ada/layout.o 
ada/lib-load.o ada/lib-util.o ada/lib-writ.o ada/lib-xref.o ada/lib.o 
ada/live.o ada/namet-sp.o ada/namet.o ada/nlists.o ada/nmake.o ada/opt.o 
ada/osint-c.o ada/osint.o ada/output.o ada/par.o ada/par_sco.o ada/prep.o 
ada/prepcomp.o ada/put_spark_xrefs.o ada/put_scos.o ada/repinfo.o 
ada/restrict.o ada/rident.o ada/rtsfind.o ada/s-addope.o ada/s-assert.o 
ada/s-bitops.o ada/s-carun8.o ada/s-casuti.o ada/s-conca2.o ada/s-conca3.o 
ada/s-conca4.o ada/s-conca5.o ada/s-conca6.o ada/s-conca7.o ada/s-conca8.o 
ada/s-conca9.o ada/s-crc32.o ada/s-crtl.o ada/s-excdeb.o ada/s-except.o 
ada/s-exctab.o ada/s-htable.o ada/s-imenne.o ada/s-imgenu.o ada/s-mastop.o 
ada/s-memory.o ada/s-os_lib.o ada/s-parame.o ada/s-purexc.o ada/s-restri.o 
ada/s-secsta.o ada/s-soflin.o ada/s-sopco3.o ada/s-sopco4.o ada/s-sopco5.o 
ada/s-stache.o ada/s-stalib.o ada/s-stoele.o ada/s-strcom.o ada/s-strhas.o 
ada/s-string.o ada/s-strops.o ada/s-traent.o ada/s-unstyp.o ada/s-utf_32.o 
ada/s-valint.o ada/s-valuns.o ada/s-valuti.o ada/s-wchcnv.o ada/s-wchcon.o 
ada/s-wchjis.o ada/scans.o ada/scil_ll.o ada/scn.o ada/scng.o ada/scos.o 
ada/sdefault.o ada/sem.o ada/sem_aggr.o ada/sem_attr.o ada/sem_aux.o 
ada/sem_case.o ada/sem_cat.o ada/sem_ch10.o ada/sem_ch11.o ada/sem_ch12.o 
ada/sem_ch13.o ada/sem_ch2.o ada/sem_ch3.o ada/sem_ch4.o ada/sem_ch5.o 
ada/sem_ch6.o ada/sem_ch7.o ada/sem_ch8.o ada/sem_ch9.o ada/sem_dim.o 
ada/sem_disp.o ada/sem_dist.o ada/sem_elab.o ada/sem_elim.o ada/sem_eval.o 
ada/sem_intr.o ada/sem_mech.o ada/sem_prag.o ada/sem_res.o ada/sem_scil.o 
ada/sem_smem.o ada/sem_type.o ada/sem_util.o ada/sem_vfpt.o ada/sem_warn.o 
ada/set_targ.o ada/sinfo-cn.o ada/sinfo.o ada/sinput-d.o ada/sinput-l.o 
ada/sinput.o ada/snames.o ada/sprint.o ada/stand.o ada/stringt.o 
ada/style.o ada/styleg.o ada/stylesw.o ada/switch-c.o ada/switch.o 
ada/system.o ada/table.o ada/targparm.o ada/tbuild.o ada/tree_gen.o 
ada/tree_in.o ada/tree_io.o ada/treepr.o ada/treeprs.o ada/ttypes.o 
ada/types.o ada/uintp.o ada/uname.o ada/urealp.o ada/usage.o ada/validsw.o 
ada/warnsw.o ada/widechar.o ada/back_end.o ada/gnat1drv.o ada/b_gnat1.o 
libbackend.a main.o tree-browser.o libcommon-target.a libcommon.a 
../libcpp/libcpp.a ../libdecnumber/libdecnumber.a attribs.o \
  libcommon-target.a libcommon.a ../libcpp/libcpp.a 
../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a 
../libdecnumber/libdecnumber.a-L/usr/local/lib -lmpc -lmpfr -lgmp 
-rdynamic  -lz -g

collect2: error: ld terminated with signal 11 [Segmentation fault]


Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights