Date: Mon, 19 Oct 2015 11:38:12 -0400 From: Paul Mather <freebsd-lists@gromit.dlib.vt.edu> To: Mike Brown <mike@skew.org> Cc: freebsd-arm@freebsd.org Subject: Re: BeagleBone self-built 10-STABLE hangs, segfaults Message-ID: <EA53292F-0998-4660-B114-3F63742837E7@gromit.dlib.vt.edu> In-Reply-To: <20151019150459.GA57293@chilled.skew.org> References: <20151018162950.GA52948@chilled.skew.org> <1445187147.71631.59.camel@freebsd.org> <CA%2BK5SrMrbCvQZsftn2kvax2gShR%2B--2WG%2BVGvuiXi5L9jP5v%2BA@mail.gmail.com> <20151019150459.GA57293@chilled.skew.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 19, 2015, at 11:04 AM, Mike Brown <mike@skew.org> wrote: > On Sun, Oct 18, 2015 at 11:27:48PM +0300, Andrey Fesenko wrote: >>> I've seen those unknown attribute warnings before, I don't think >>> they're anything to worry about. I haven't tried running a = self-hosted >>> build on any armv6 for a long time, it's possible there's something >>> ugly like a code-generation bug that happens when running native but >>> not on a cross build. Things like that are pretty rare, though. >>>=20 >>=20 >> Confirm both Rpi and bb "Segmentation fault", i'm build with crochet >> and CURRENT-r289459 (builded 289522) >>=20 >> last lines sh -x crochet >> + _DTBINTERMEDIATEDIR=3D/usr/obj/fdt/fdt.kUEP6Z >> + _DTSIN=3D/usr/src/sys/boot/fdt/dts/arm/beaglebone.dts >> + _DTBINTERMEDIATE=3D/usr/obj/fdt/fdt.kUEP6Z >> + echo /usr/src/sys/tools/fdt/make_dtb.sh /usr/src/sys >> /usr/src/sys/boot/fdt/dts/arm/beaglebone.dts /usr/obj/fdt/fdt.kUEP6Z >> + cd /usr/src >> + make 'TARGET_ARCH=3Darmv6' buildenv >> + _DTSOUT=3Dbbone.dts >> + dtc -I dtb -O dts /usr/obj/fdt/fdt.kUEP6Z/beaglebone.dtb >> Segmentation fault >> root@des:/usr/src # pkg info | grep eabi >> arm-none-eabi-binutils-2.25.1 GNU binutils for bare metal arm = cross-development >> arm-none-eabi-gcc492-4.9.2_1 GNU Compiler Collection for bare metal >> arm cross-development >=20 > Does this happen at the same place very time? >=20 > My problems on 10-STABLE seem to happen at random, as if it were bad = RAM. In=20 > successive builds of the 'pkg' port, for example, I get different = results each=20 > time: a segmentation fault during 'configure', then no errors, then a = syntax=20 > error in some file, then a segmentation fault during 'cc' of something = small,=20 > then no errors. >=20 > I didn't see any such weirdness before the native build, though. >=20 > How can I diagnose this further? Re: the problems happening at random: are you powering the BBB via the = OTG USB connector or via the 5V barrel power supply connector? I found my BBB to be a bit flaky when powered via the OTG USB connector. = It is stable when powered via the 5V power supply connector, though. Just a thought... Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA53292F-0998-4660-B114-3F63742837E7>