From owner-freebsd-arm@freebsd.org Mon Oct 19 15:38:22 2015 Return-Path: Delivered-To: freebsd-arm@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 492D5A1974C for ; Mon, 19 Oct 2015 15:38:22 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2340D19C1 for ; Mon, 19 Oct 2015 15:38:22 +0000 (UTC) (envelope-from freebsd-lists@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 965929C9; Mon, 19 Oct 2015 11:38:12 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: BeagleBone self-built 10-STABLE hangs, segfaults From: Paul Mather In-Reply-To: <20151019150459.GA57293@chilled.skew.org> Date: Mon, 19 Oct 2015 11:38:12 -0400 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20151018162950.GA52948@chilled.skew.org> <1445187147.71631.59.camel@freebsd.org> <20151019150459.GA57293@chilled.skew.org> To: Mike Brown X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2015 15:38:22 -0000 On Oct 19, 2015, at 11:04 AM, Mike Brown 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.