From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 00:54:39 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F3B54F3B for ; Sun, 19 Jan 2014 00:54:38 +0000 (UTC) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 822341FB3 for ; Sun, 19 Jan 2014 00:54:38 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hi8so2068083wib.3 for ; Sat, 18 Jan 2014 16:54:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XJjoxoO3SYygMco9oN3CxbQ5BwGyCRaGfizJqVbiHAU=; b=EaqYOD94G1AxZNM7PShKFTV/7WjOm/SJERpv444bv/cxNnDpY0R8WQiuNpAtqdEenb IAIbyD2sH1d7Foi5oBSCVS3WPF2jmJ3ik68xZXweIqGnRrlqXnLv75Ltd6YS9SuhB3Mq v8lH82bWWR2YwHDm1etN1aSvw51rBSlM5rEgI+I1Bqf7GQjGCf70TZ6V+AT4TIvPLH7M zBVBQGoRxxVJh+UlJkMCfbnXuX1Ihhru+1fhyWhFwk2W3u9I1ap8p8lCNXX8WKFqyHHB pzvSVRfEbUlSqBa2vTyl5a0HA3vQroMClmuWhq/3L+4A6iCrvezlCY5dAPOLqdCsFK6t ZTpg== X-Gm-Message-State: ALoCoQnc4F2GcvVSCO2Yb2rZAOD10Dz8Tb4mmBNYXUz3erDGsklaUCnxrAmhDQO9SgyhwMMVA7dk X-Received: by 10.180.107.136 with SMTP id hc8mr4302033wib.11.1390092550774; Sat, 18 Jan 2014 16:49:10 -0800 (PST) Received: from [192.168.0.2] (cpc8-cmbg15-2-0-cust169.5-4.cable.virginm.net. [86.30.140.170]) by mx.google.com with ESMTPSA id hy8sm14011759wjb.2.2014.01.18.16.49.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 16:49:09 -0800 (PST) Message-ID: <52DB2104.3070808@linaro.org> Date: Sun, 19 Jan 2014 00:49:08 +0000 From: Julien Grall User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ian Campbell Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <1389950962.6697.33.camel@kazak.uk.xensource.com> In-Reply-To: <1389950962.6697.33.camel@kazak.uk.xensource.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 00:54:39 -0000 On 01/17/2014 09:29 AM, Ian Campbell wrote: > On Fri, 2014-01-17 at 00:36 +0000, Julien Grall wrote: >> IanC: I was reading the linux binding documentation >> (devicetree/booting-without-of.txt VII.2) and it seems that the >> explanation differs from the implementation, right? > > I vaguely recall someone saying that the Linux behaviour was a quirk of > some real PPC system which supplied a DTB which required this behaviour > which has leaked into the other platforms. It does also sound like a > useful extension to the spec which makes the dtb easier to write. I've read twice the ePAR and did some test. I was completely wrong, this file is valid with the ePAR (there is even an example like that at the end at the specification). And FreeBSD doesn't complain about this since Nathan's ofw/fdt rework. Sorry for the waste time. -- Julien Grall From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 01:30:55 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00FF57D4; Sun, 19 Jan 2014 01:30:54 +0000 (UTC) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDBD511DD; Sun, 19 Jan 2014 01:30:54 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00D00JNT7T00@smtpauth3.wiscmail.wisc.edu>; Sat, 18 Jan 2014 19:30:47 -0600 (CST) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.11815, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM009AQK77M510@smtpauth3.wiscmail.wisc.edu>; Sat, 18 Jan 2014 19:30:46 -0600 (CST) Message-id: <52DB2AC3.5000206@freebsd.org> Date: Sat, 18 Jan 2014 19:30:43 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Julien Grall , Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> In-reply-to: <52DB1138.6010804@linaro.org> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 01:30:55 -0000 On 01/18/14 17:41, Julien Grall wrote: > > Hello Nathan, > > On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >> On 01/16/14 18:36, Julien Grall wrote: >>> >>> >>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>> As I understand, only the simple bus code (see simplebus_attach) is >>> translating the interrupts in the device on a resource. >>> So if you have a node directly attached to the root node with >>> interrupts and MMIO, the driver won't be able to retrieve and >>> translate the interrupts via bus_alloc_resources. > >> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. > > I have digged into the code to find the reason of my issue. FreeBSD is > receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. > > This is because the GIC is not yet initialized but FreeBSD asks to > unmask the IRQ (sys/arm/arm/gic.c:306). > > With this problem, all device nodes that are before the GIC in the > device tree can't have interrupts. For instance this simple device > will segfault on FreeBSD: > > / { > > mybus { > compatible = "simple-bus"; > > mynode { > interrupt-parent = &gic; > interrupts = <...>; > }; > > gic: gic@xxxx { > interrupt-controller; > } > }; > }; > > The node "mynode" will have to move after the GIC to be able to work > correctly. > Ah, that sounds like a bug in the interrupt handling code. The PPC code is designed to handle this problem by deferring interrupt setup, as well as a number of other latent issues, and I think would make a good match for ARM as well. I made an experimental branch to port it to MIPS (the code is almost entirely machine-independent) but am waiting for testing. A general solution to this problem has to involve deferred setup. -Nathan From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 02:44:51 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6F8FD253 for ; Sun, 19 Jan 2014 02:44:51 +0000 (UTC) Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com [209.85.213.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 34413160E for ; Sun, 19 Jan 2014 02:44:50 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id hl1so5041103igb.1 for ; Sat, 18 Jan 2014 18:44:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=miznZQsfRtjA5VuYPXfaIynv5+4GL60bP9kdQW9VNR0=; b=VlLMM0zSvCOAHnmIjKnoFSKuQtVf3Jn9ODKCLj6GR0knGCgSmK7Y2DtARVCHxp1nK7 OJix1bp65dhHqOR7knTtIYMKWhMXABMqLPxguiaqGhs8fJug3qXDwPVCPC8ZDfSNbQt7 S+22Q34NEaQ9bHuWLSpZ5GS97rM1kSzi7+A4mqgLlpCWe8eUamCO4sBZYcFR2oEx5zUT hGsFV4DYY/FTSE/ReVRRpZCjABGDUZRxeSAJi0E8wKDC4un5QyJm5or9fOI2/p2vOgsV 54K1NHfYaudbbQ/EbRH6/k7IQ0sUsqR6Z09+IhIkv3KscWI5mkmi0P2m4pFwcF1n/rBX /2Rw== X-Gm-Message-State: ALoCoQkJhIXd05igbnT/u0SksDKELdmjtzD1ZEHJsq/R6AxppAgv7AhUUVDvWfcEl8O27sqYmW8d X-Received: by 10.42.122.146 with SMTP id n18mr124691icr.41.1390099490219; Sat, 18 Jan 2014 18:44:50 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id gc2sm12532065igd.6.2014.01.18.18.44.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 18:44:49 -0800 (PST) Sender: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <52DB1138.6010804@linaro.org> Date: Sat, 18 Jan 2014 19:44:09 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> To: Julien Grall X-Mailer: Apple Mail (2.1085) Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 02:44:51 -0000 On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >=20 > Hello Nathan, >=20 > On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >> On 01/16/14 18:36, Julien Grall wrote: >>>=20 >>>=20 >>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>> As I understand, only the simple bus code (see simplebus_attach) is >>> translating the interrupts in the device on a resource. >>> So if you have a node directly attached to the root node with >>> interrupts and MMIO, the driver won't be able to retrieve and >>> translate the interrupts via bus_alloc_resources. >=20 >> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >=20 > I have digged into the code to find the reason of my issue. FreeBSD is = receiving a VM fault when the driver (xen-dt) is trying to setup the = IRQ. >=20 > This is because the GIC is not yet initialized but FreeBSD asks to = unmask the IRQ (sys/arm/arm/gic.c:306). >=20 > With this problem, all device nodes that are before the GIC in the = device tree can't have interrupts. For instance this simple device will = segfault on FreeBSD: >=20 > / { >=20 > mybus { > compatible =3D "simple-bus"; >=20 > mynode { > interrupt-parent =3D &gic; > interrupts =3D <...>; > }; >=20 > gic: gic@xxxx { > interrupt-controller; > } > }; > }; >=20 > The node "mynode" will have to move after the GIC to be able to work = correctly. This stems from a difference in enumeration between FreeBSD and Linux. = FreeBSD enumerates the devices in DTB order, while Linux does a partial = ordering based on dependencies. Warner= From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 03:01:29 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F05604FD; Sun, 19 Jan 2014 03:01:28 +0000 (UTC) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B8E2E1769; Sun, 19 Jan 2014 03:01:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00300OD1LZ00@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:01:21 -0600 (CST) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.25114, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM000JUOE5EZ10@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:01:20 -0600 (CST) Message-id: <52DB3FFD.2070503@freebsd.org> Date: Sat, 18 Jan 2014 21:01:17 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Warner Losh , Julien Grall Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> In-reply-to: <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:01:29 -0000 On 01/18/14 20:44, Warner Losh wrote: > On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: > >> Hello Nathan, >> >> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>> On 01/16/14 18:36, Julien Grall wrote: >>>> >>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>> As I understand, only the simple bus code (see simplebus_attach) is >>>> translating the interrupts in the device on a resource. >>>> So if you have a node directly attached to the root node with >>>> interrupts and MMIO, the driver won't be able to retrieve and >>>> translate the interrupts via bus_alloc_resources. >>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >> I have digged into the code to find the reason of my issue. FreeBSD is receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. >> >> This is because the GIC is not yet initialized but FreeBSD asks to unmask the IRQ (sys/arm/arm/gic.c:306). >> >> With this problem, all device nodes that are before the GIC in the device tree can't have interrupts. For instance this simple device will segfault on FreeBSD: >> >> / { >> >> mybus { >> compatible = "simple-bus"; >> >> mynode { >> interrupt-parent = &gic; >> interrupts = <...>; >> }; >> >> gic: gic@xxxx { >> interrupt-controller; >> } >> }; >> }; >> >> The node "mynode" will have to move after the GIC to be able to work correctly. > This stems from a difference in enumeration between FreeBSD and Linux. FreeBSD enumerates the devices in DTB order, while Linux does a partial ordering based on dependencies. > > Warner Enumerating in some other order doesn't necessarily help: since the interrupt and bus trees are independent, circular dependencies can happen. This is not a hypothetical: on most powermacs, the main interrupt controller is a functional unit on a PCI device -- a PCI device whose other units have interrupt lines that eventually connect back to itself. There is no way to fix that with ordering. So I think we still need to defer interrupt setup. It's not that bad -- PPC already does this to handle the powermac case. -Nathan From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 03:08:20 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF5FD68E for ; Sun, 19 Jan 2014 03:08:20 +0000 (UTC) Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9332517E1 for ; Sun, 19 Jan 2014 03:08:20 +0000 (UTC) Received: by mail-ig0-f171.google.com with SMTP id uy17so5059158igb.4 for ; Sat, 18 Jan 2014 19:08:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=mbUcM4/PJrGkwpKLpmtu9BaBYUSjMxuRVmYbi+PFN2U=; b=VCvbkRUzc4PYfN1IgIxoNHtggAstteYw5begx14fqaopVmGQmtZEpX0e2E9qCOi0lN EiuypgVo9Hj290ZcNb2pQK8ib+LezDFb/AeMq6KVsz1cDQBzepohT5Xym0twmMZXA2KM w1mWasX79EZVtKMavL/VFnDmGKsQZJBSAi+j7WXkVUCEwbTUtOM2uZXw8M3A3xvJI7V+ VxeNFnOaNbPAcS8PGJko2ZhrvJKyKSiMhotfw9qW5xDWYRTd9zZOInmdugOR4pLaqi17 QXG0X3r3H82we5kAtxNFh6cdwT7Q2/nvCR37A6TxN6FHpRIcGj4AHD0E4uiWrDIsfxC1 oWkA== X-Gm-Message-State: ALoCoQnw8idIGZGN54hKtTsz5wmyBKftjowyYLu6HiqumxaxU4pXrYAlRYAeNYv4hP7pmSKJ2Iav X-Received: by 10.50.79.228 with SMTP id m4mr5710692igx.47.1390100894534; Sat, 18 Jan 2014 19:08:14 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id g6sm12630791igg.9.2014.01.18.19.08.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Jan 2014 19:08:14 -0800 (PST) Sender: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <52DB3FFD.2070503@freebsd.org> Date: Sat, 18 Jan 2014 20:08:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> <52DB3FFD.2070503@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1085) Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:08:20 -0000 On Jan 18, 2014, at 8:01 PM, Nathan Whitehorn wrote: > On 01/18/14 20:44, Warner Losh wrote: >> On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >>=20 >>> Hello Nathan, >>>=20 >>> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>>> On 01/16/14 18:36, Julien Grall wrote: >>>>>=20 >>>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>>> As I understand, only the simple bus code (see simplebus_attach) = is >>>>> translating the interrupts in the device on a resource. >>>>> So if you have a node directly attached to the root node with >>>>> interrupts and MMIO, the driver won't be able to retrieve and >>>>> translate the interrupts via bus_alloc_resources. >>>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >>> I have digged into the code to find the reason of my issue. FreeBSD = is receiving a VM fault when the driver (xen-dt) is trying to setup the = IRQ. >>>=20 >>> This is because the GIC is not yet initialized but FreeBSD asks to = unmask the IRQ (sys/arm/arm/gic.c:306). >>>=20 >>> With this problem, all device nodes that are before the GIC in the = device tree can't have interrupts. For instance this simple device will = segfault on FreeBSD: >>>=20 >>> / { >>>=20 >>> mybus { >>> compatible =3D "simple-bus"; >>>=20 >>> mynode { >>> interrupt-parent =3D &gic; >>> interrupts =3D <...>; >>> }; >>>=20 >>> gic: gic@xxxx { >>> interrupt-controller; >>> } >>> }; >>> }; >>>=20 >>> The node "mynode" will have to move after the GIC to be able to work = correctly. >> This stems from a difference in enumeration between FreeBSD and = Linux. FreeBSD enumerates the devices in DTB order, while Linux does a = partial ordering based on dependencies. >>=20 >> Warner >=20 > Enumerating in some other order doesn't necessarily help: since the > interrupt and bus trees are independent, circular dependencies can > happen. This is not a hypothetical: on most powermacs, the main > interrupt controller is a functional unit on a PCI device -- a PCI > device whose other units have interrupt lines that eventually connect > back to itself. There is no way to fix that with ordering. So I think = we > still need to defer interrupt setup. It's not that bad -- PPC already > does this to handle the powermac case. I guess I've looked at simpler cases where interrupts and GPIO pins need = to be up before anything can work on Atmel... We kinda fake it now, but = there's some ordering issues that are solved in this way. But I've not = finished the work on bringing Atmel into the FDT world yet. Deferred = setup isn't always an option, but I'll keep that in mind in case I hit = that case... The other way to cope is to use the multi-pass enumeration stuff that = John Baldwin put into the tree a while ago. In that case, you could = enumerate bridges, interrupt controllers, gpio providers, etc first, and = then do a second pass that catches the rest of the devices and the = interrupt processing for the first pass devices. This is a variation on = the deferred enumeration stuff you are talking about, so that might be a = better, more general solution to these sorts of problems. Warner From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 03:23:54 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2412E94D; Sun, 19 Jan 2014 03:23:54 +0000 (UTC) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DE716190E; Sun, 19 Jan 2014 03:23:53 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZM00600OYGMO00@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:23:53 -0600 (CST) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.19.31515, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZM0080HPFQZ500@smtpauth4.wiscmail.wisc.edu>; Sat, 18 Jan 2014 21:23:52 -0600 (CST) Message-id: <52DB4546.504@freebsd.org> Date: Sat, 18 Jan 2014 21:23:50 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 To: Warner Losh Subject: Re: [RFC] Add support for Xen ARM guest on FreeBSD References: <1389733267-20822-1-git-send-email-julien.grall@linaro.org> <24851B79-7EC7-4E3A-94DB-4B9B86FDFFFC@bsdimp.com> <52D6B62A.9000208@linaro.org> <52D73C4E.2080306@freebsd.org> <52D87B15.5090208@linaro.org> <52D89DC9.7050303@freebsd.org> <52DB1138.6010804@linaro.org> <3AE8EDE6-D931-4F93-9BF7-ABFB297B5B96@bsdimp.com> <52DB3FFD.2070503@freebsd.org> <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> In-reply-to: <8C16C019-B9AF-417B-9B02-C016A202AAC7@bsdimp.com> X-Enigmail-Version: 1.6 Cc: ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org, freebsd-xen@freebsd.org, freebsd-arm@FreeBSD.org, gibbs@freebsd.org, roger.pau@citrix.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 03:23:54 -0000 On 01/18/14 21:08, Warner Losh wrote: > On Jan 18, 2014, at 8:01 PM, Nathan Whitehorn wrote: > >> On 01/18/14 20:44, Warner Losh wrote: >>> On Jan 18, 2014, at 4:41 PM, Julien Grall wrote: >>> >>>> Hello Nathan, >>>> >>>> On 01/17/2014 03:04 AM, Nathan Whitehorn wrote: >>>>> On 01/16/14 18:36, Julien Grall wrote: >>>>>> On 01/16/2014 01:56 AM, Nathan Whitehorn wrote: >>>>>> As I understand, only the simple bus code (see simplebus_attach) is >>>>>> translating the interrupts in the device on a resource. >>>>>> So if you have a node directly attached to the root node with >>>>>> interrupts and MMIO, the driver won't be able to retrieve and >>>>>> translate the interrupts via bus_alloc_resources. >>>>> Why not? nexus on ARM, MIPS, PowerPC, and sparc64 can do this. >>>> I have digged into the code to find the reason of my issue. FreeBSD is receiving a VM fault when the driver (xen-dt) is trying to setup the IRQ. >>>> >>>> This is because the GIC is not yet initialized but FreeBSD asks to unmask the IRQ (sys/arm/arm/gic.c:306). >>>> >>>> With this problem, all device nodes that are before the GIC in the device tree can't have interrupts. For instance this simple device will segfault on FreeBSD: >>>> >>>> / { >>>> >>>> mybus { >>>> compatible = "simple-bus"; >>>> >>>> mynode { >>>> interrupt-parent = &gic; >>>> interrupts = <...>; >>>> }; >>>> >>>> gic: gic@xxxx { >>>> interrupt-controller; >>>> } >>>> }; >>>> }; >>>> >>>> The node "mynode" will have to move after the GIC to be able to work correctly. >>> This stems from a difference in enumeration between FreeBSD and Linux. FreeBSD enumerates the devices in DTB order, while Linux does a partial ordering based on dependencies. >>> >>> Warner >> Enumerating in some other order doesn't necessarily help: since the >> interrupt and bus trees are independent, circular dependencies can >> happen. This is not a hypothetical: on most powermacs, the main >> interrupt controller is a functional unit on a PCI device -- a PCI >> device whose other units have interrupt lines that eventually connect >> back to itself. There is no way to fix that with ordering. So I think we >> still need to defer interrupt setup. It's not that bad -- PPC already >> does this to handle the powermac case. > I guess I've looked at simpler cases where interrupts and GPIO pins need to be up before anything can work on Atmel... We kinda fake it now, but there's some ordering issues that are solved in this way. But I've not finished the work on bringing Atmel into the FDT world yet. Deferred setup isn't always an option, but I'll keep that in mind in case I hit that case... > > The other way to cope is to use the multi-pass enumeration stuff that John Baldwin put into the tree a while ago. In that case, you could enumerate bridges, interrupt controllers, gpio providers, etc first, and then do a second pass that catches the rest of the devices and the interrupt processing for the first pass devices. This is a variation on the deferred enumeration stuff you are talking about, so that might be a better, more general solution to these sorts of problems. > > Warner > > I'm still not sure that helps. Take the powermac case. The PCI parent bridge assigns and routes interrupts as part of its probe stage. One device (called mac-io) is the one that actually has the interrupt controller, along with other things like ATA and sound. It has several interrupts to support e.g. ATA. How can the PCI bus attachment sensibly attach the macio device? If it delays attaching it until the interrupt controller registers, the bus probing will deadlock, since the interrupt controller is itself a child of macio! If it attaches it immediately, it will not be able to route the interrupts of the macio device. It's a catch-22. The only solution we were able to come up with when this situation arose was to treat the bus and interrupt trees as entirely separate things, built independently, which allows the kernel to break the loop. GPIOs can have similar problems. The basic issue is that newbus ultimately assumes that the system topology can be described by a single tree. Interconnections between the branches -- especially if it isn't even a DAG -- fundamentally break the model and multipass doesn't necessarily help. -Nathan From owner-freebsd-arm@FreeBSD.ORG Sun Jan 19 13:38:40 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5166BF65 for ; Sun, 19 Jan 2014 13:38:40 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E57501DA3 for ; Sun, 19 Jan 2014 13:38:39 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0JDcXeO021830 for ; Sun, 19 Jan 2014 08:38:38 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52DBD559.5040303@m5p.com> Date: Sun, 19 Jan 2014 08:38:33 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "freebsd-arm@freebsd.org" Subject: New Raspberry Pi panic Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 19 Jan 2014 08:38:38 -0500 (EST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jan 2014 13:38:40 -0000 With /usr/ports on a local "disk," I got most of the way through portmaster print/cups-base, until this undefined instruction panic: http://m5p.com/~george/pi/new-trace.txt (I had to make a few patches to the ports tree along the way, which I'll write about separately.) -- George From owner-freebsd-arm@FreeBSD.ORG Mon Jan 20 07:19:40 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75B39228; Mon, 20 Jan 2014 07:19:40 +0000 (UTC) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B2BC18A4; Mon, 20 Jan 2014 07:19:39 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id s0K7JWbx095062; Mon, 20 Jan 2014 02:19:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id s0K7JWRL095052; Mon, 20 Jan 2014 07:19:32 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Jan 2014 07:19:32 GMT Message-Id: <201401200719.s0K7JWRL095052@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 07:19:40 -0000 TB --- 2014-01-20 04:00:20 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-20 04:00:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-20 04:00:20 - starting HEAD tinderbox run for arm/arm TB --- 2014-01-20 04:00:20 - cleaning the object tree TB --- 2014-01-20 04:00:20 - /usr/local/bin/svn stat /src TB --- 2014-01-20 04:00:25 - At svn revision 260900 TB --- 2014-01-20 04:00:26 - building world TB --- 2014-01-20 04:00:26 - CROSS_BUILD_TESTING=YES TB --- 2014-01-20 04:00:26 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-20 04:00:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-20 04:00:26 - SRCCONF=/dev/null TB --- 2014-01-20 04:00:26 - TARGET=arm TB --- 2014-01-20 04:00:26 - TARGET_ARCH=arm TB --- 2014-01-20 04:00:26 - TZ=UTC TB --- 2014-01-20 04:00:26 - __MAKE_CONF=/dev/null TB --- 2014-01-20 04:00:26 - cd /src TB --- 2014-01-20 04:00:26 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Jan 20 04:00:35 UTC 2014 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Jan 20 07:02:47 UTC 2014 TB --- 2014-01-20 07:02:47 - generating LINT kernel config TB --- 2014-01-20 07:02:47 - cd /src/sys/arm/conf TB --- 2014-01-20 07:02:47 - /usr/bin/make -B LINT TB --- 2014-01-20 07:02:47 - cd /src/sys/arm/conf TB --- 2014-01-20 07:02:47 - /usr/sbin/config -m LINT TB --- 2014-01-20 07:02:47 - building LINT kernel TB --- 2014-01-20 07:02:47 - CROSS_BUILD_TESTING=YES TB --- 2014-01-20 07:02:47 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-20 07:02:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-20 07:02:47 - SRCCONF=/dev/null TB --- 2014-01-20 07:02:47 - TARGET=arm TB --- 2014-01-20 07:02:47 - TARGET_ARCH=arm TB --- 2014-01-20 07:02:47 - TZ=UTC TB --- 2014-01-20 07:02:47 - __MAKE_CONF=/dev/null TB --- 2014-01-20 07:02:47 - cd /src TB --- 2014-01-20 07:02:47 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 20 07:02:48 UTC 2014 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] uart_cpu_pxa.o: warning: multiple common of `uart_bus_space_mem' uart_cpu_fdt.o: warning: previous common is here uart_cpu_pxa.o: warning: multiple common of `uart_bus_space_io' uart_cpu_fdt.o: warning: previous common is here board_hl201.o: In function `board_init': /src/sys/arm/at91/board_hl201.c:(.text+0x174): undefined reference to `at91_enable_nand' board_sam9260ek.o: In function `board_init': /src/sys/arm/at91/board_sam9260ek.c:(.text+0x2a8): undefined reference to `at91_enable_nand' *** Error code 1 Stop. bmake[1]: stopped in /obj/arm.arm/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-20 07:19:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-20 07:19:32 - ERROR: failed to build LINT kernel TB --- 2014-01-20 07:19:32 - 9323.44 user 1842.94 system 11951.73 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-arm-arm.full From owner-freebsd-arm@FreeBSD.ORG Mon Jan 20 11:06:43 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05B499E2 for ; Mon, 20 Jan 2014 11:06:43 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA7BF1D5A for ; Mon, 20 Jan 2014 11:06:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0KB6gdN088275 for ; Mon, 20 Jan 2014 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0KB6gc4088273 for freebsd-arm@FreeBSD.org; Mon, 20 Jan 2014 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Jan 2014 11:06:42 GMT Message-Id: <201401201106.s0KB6gc4088273@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 11:06:43 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o arm/185617 arm 10.0-RC1, armv6: "pfctl -s state" crashes on BeagleBon o arm/185046 arm [armv6] issues with dhclient/sshd and jemalloc on rasp o arm/184078 arm cross installworld missing include files o arm/183926 arm Crash when ctrl-c while process is enter o arm/183740 arm mutex on some arm hardware requires dcache enabled o arm/183668 arm Panic when read unalign in ddb o arm/182544 arm [patch] ARM busdma_machdep-v6.c o arm/182060 arm make buildworld fails on Raspberry PI o arm/181722 arm gdb on ARM unable to sensibly debug core file from ass o arm/181718 arm threads caused hung on ARM/RPI o arm/181601 arm Sporadic failure of root mount on ARM/Raspberry o arm/180080 arm Unmapped buffers on ARMv7 big-RAM boards o arm/179688 arm [patch] [rpi] serial console eats some characters at m o arm/179532 arm wireless networking on ARM o arm/178495 arm buildworld fail on arm/raspberry pi o arm/177687 arm gdb gets installed but does not know the EABI version o arm/177686 arm assertion failed in ld-elf.so.1 when invoking telnet w o arm/177685 arm [kernel] [patch] Correct return type and usage of at91 o arm/177538 arm tunefs(8) and mount(8) can not access a newfs(8)'d fil o arm/175803 arm building xdev for arm failing o arm/173617 arm Dreamplug exhibits eSATA file corruption using network o kern/171096 arm [arm][xscale][ixp]Allow 16bit access on PCI bus o arm/166256 arm build fail in pmap.c o arm/162159 arm [panic] USB errors leading to panic on DockStar 9.0-RC o arm/161110 arm /usr/src/sys/arm/include/signal.h is bad o ports/161044 arm devel/icu does not build on arm o arm/158950 arm arm/sheevaplug fails fsx when mmap operations are enab o arm/155894 arm [patch] Enable at91 booting from SDHC (high capacity) p arm/155214 arm [patch] MMC/SD IO slow on Atmel ARM with modern large o arm/154227 arm [geli] using GELI leads to panic on ARM o arm/153380 arm Panic / translation fault with wlan on ARM o arm/150581 arm [irq] Unknown error generates IRQ address decoding err o arm/134368 arm [new driver] [patch] nslu2_led driver for the LEDs on 33 problems total. From owner-freebsd-arm@FreeBSD.ORG Mon Jan 20 19:10:18 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 364F0363; Mon, 20 Jan 2014 19:10:18 +0000 (UTC) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0BB0610F6; Mon, 20 Jan 2014 19:10:17 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id s0KJAGvJ043733; Mon, 20 Jan 2014 14:10:16 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id s0KJAGjO043722; Mon, 20 Jan 2014 19:10:16 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Jan 2014 19:10:16 GMT Message-Id: <201401201910.s0KJAGjO043722@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 19:10:18 -0000 TB --- 2014-01-20 15:50:22 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-20 15:50:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-01-20 15:50:22 - starting HEAD tinderbox run for arm/arm TB --- 2014-01-20 15:50:22 - cleaning the object tree TB --- 2014-01-20 15:51:45 - /usr/local/bin/svn stat /src TB --- 2014-01-20 15:51:48 - At svn revision 260909 TB --- 2014-01-20 15:51:49 - building world TB --- 2014-01-20 15:51:49 - CROSS_BUILD_TESTING=YES TB --- 2014-01-20 15:51:49 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-20 15:51:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-20 15:51:49 - SRCCONF=/dev/null TB --- 2014-01-20 15:51:49 - TARGET=arm TB --- 2014-01-20 15:51:49 - TARGET_ARCH=arm TB --- 2014-01-20 15:51:49 - TZ=UTC TB --- 2014-01-20 15:51:49 - __MAKE_CONF=/dev/null TB --- 2014-01-20 15:51:49 - cd /src TB --- 2014-01-20 15:51:49 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Jan 20 15:51:56 UTC 2014 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Jan 20 18:53:38 UTC 2014 TB --- 2014-01-20 18:53:38 - generating LINT kernel config TB --- 2014-01-20 18:53:38 - cd /src/sys/arm/conf TB --- 2014-01-20 18:53:38 - /usr/bin/make -B LINT TB --- 2014-01-20 18:53:38 - cd /src/sys/arm/conf TB --- 2014-01-20 18:53:38 - /usr/sbin/config -m LINT TB --- 2014-01-20 18:53:39 - building LINT kernel TB --- 2014-01-20 18:53:39 - CROSS_BUILD_TESTING=YES TB --- 2014-01-20 18:53:39 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-20 18:53:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-20 18:53:39 - SRCCONF=/dev/null TB --- 2014-01-20 18:53:39 - TARGET=arm TB --- 2014-01-20 18:53:39 - TARGET_ARCH=arm TB --- 2014-01-20 18:53:39 - TZ=UTC TB --- 2014-01-20 18:53:39 - __MAKE_CONF=/dev/null TB --- 2014-01-20 18:53:39 - cd /src TB --- 2014-01-20 18:53:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 20 18:53:39 UTC 2014 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] uart_cpu_pxa.o: warning: multiple common of `uart_bus_space_mem' uart_cpu_fdt.o: warning: previous common is here uart_cpu_pxa.o: warning: multiple common of `uart_bus_space_io' uart_cpu_fdt.o: warning: previous common is here board_hl201.o: In function `board_init': /src/sys/arm/at91/board_hl201.c:(.text+0x174): undefined reference to `at91_enable_nand' board_sam9260ek.o: In function `board_init': /src/sys/arm/at91/board_sam9260ek.c:(.text+0x2a8): undefined reference to `at91_enable_nand' *** Error code 1 Stop. bmake[1]: stopped in /obj/arm.arm/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2014-01-20 19:10:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-20 19:10:16 - ERROR: failed to build LINT kernel TB --- 2014-01-20 19:10:16 - 9319.49 user 1835.60 system 11993.62 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-arm-arm.full From owner-freebsd-arm@FreeBSD.ORG Tue Jan 21 05:38:31 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34F741AA for ; Tue, 21 Jan 2014 05:38:31 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 06A3E12F3 for ; Tue, 21 Jan 2014 05:38:31 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id lj1so7916414pab.40 for ; Mon, 20 Jan 2014 21:38:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=7/+oGmucVg+ekTA910ej+qAMUzk3FbYMQT23pYeaXkY=; b=miB2o+rDiYiwRm3p2OCxXmTkvC7sPC8Uh9u9HR9jGjMdVDyj6iekoPhwF0E56TJWq+ 75rBVxc1mSpbI/Nv55+FRwU7pXVBUtKaN3cc0k4ChSRqYdQcCeOTm1R9UUAYPh6R/UiJ bLGQe9A57LMy0ZjxvhI9mgAVrUgmn6Bl8/8t9GjrbTERiv+tKJDB7pv7Fbttj/IS4hHU S+JOUfV7RvnfUa1SewPcvOB9M1MCJP/jxAOGYUr3WuGMFG1YGQ1AKnVL4l1BarPb4D3Z ekwDeREkKsjky7Pz9zMmEnq7uyfypM+GJHbnvIR1+UYQc5nm7BCBDGPUwjrtxFwslqXG N1Gw== X-Received: by 10.68.91.3 with SMTP id ca3mr22620671pbb.20.1390282710668; Mon, 20 Jan 2014 21:38:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.49.34 with HTTP; Mon, 20 Jan 2014 21:38:15 -0800 (PST) From: Jordan Starcher Date: Tue, 21 Jan 2014 00:38:15 -0500 Message-ID: Subject: Raspberry Pi Binary Snapshot of 10.0? To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 05:38:31 -0000 Hi, I've been trying to build a Raspberry Pi Model B binary image of FreeBSD 10.0 using a 10.0 host and the crochet-freebsd script but have been failing. I can get built image to POST, but it gets stuck when attempting to initialize the kernel. Does anyone have a 10.0 image I can use? Thanks, Jordan From owner-freebsd-arm@FreeBSD.ORG Tue Jan 21 05:43:49 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46FD3214; Tue, 21 Jan 2014 05:43:49 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 19C861364; Tue, 21 Jan 2014 05:43:49 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 00CECD7F8; Tue, 21 Jan 2014 05:43:47 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 00CECD7F8 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 21 Jan 2014 00:43:46 -0500 From: Glen Barber To: Jordan Starcher Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140121054346.GA61932@glenbarber.us> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="veZQh2nSsG1B2+Ku" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 05:43:49 -0000 --veZQh2nSsG1B2+Ku Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > Hi, >=20 > I've been trying to build a Raspberry Pi Model B binary image of FreeBSD > 10.0 using a 10.0 host and the crochet-freebsd script but have been > failing. I can get built image to POST, but it gets stuck when attempting > to initialize the kernel. >=20 > Does anyone have a 10.0 image I can use? >=20 I have had some build failures with my release/10.0.0/ builds for RPI. Can you try this image, built from stable/10/ ? http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D aec511f434d551c95a53c979= add5b9b84d2618bbd2e2e012db9364e1985f5de3 Glen --veZQh2nSsG1B2+Ku Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS3gkSAAoJELls3eqvi17QRR0P/j2wy7tbTC76jCZQYfQ2PpYw H4u5SP1SoQt+SWgkTwbQZ3jO7RTMCjBX7ihPFJU68EqqbbPfxOUv40wUDkhgn0kI G+v3XCueHToKJPLulbeSWJ+kCFjoyWOGOShNQhrdDP7DfTTN6pMh35Y1PXnDzHl2 bDSWeRdoLs0YX7DHTGNgcMzd0FPH6WhfTfwRv7Dlu8LgtI78nLR1xHRBXY35GZiY HmW6NkjsdXt/xLgKl5BayFWC+1hnqqBUgdylVa0ycfl504wm+vQEfgztBYFgQO0k sjol4brwGYg5ODqDWgZaxXaKAuc2qcj5qnyVO1jrvwjVrC0QjQjNEerLXDI13k/x OvMCqbqxFYWJA/d/8uolavxXvzsHigOaXEeShTy+CH05tH+uqH2l2erybyF1dcFa xhHpNNG2B4xusv4FiXNBeK8vXgr/dgSxZBAUfcuhExeD7+ui7WDyCzvMLblTkycI I78DPSS3dJq386ocadZgzuva9WaoZjqppgxrkevt63KpBSk/NOSOejJxnOJzDLPW xVkPLvGc/P8gD+vyDwwIYlGan6fpQaJfw6W3xkdZLI2i/BPxEfCVG4Jiew98jOH4 VCm2q0qXwmRXJc/bindkwFdWmwTdv4Nr1MuufyfA0QDQWZSJsd/Tpqo7FG1u4iMn UEPxWh/szr/Z9RzNGwfL =zRP2 -----END PGP SIGNATURE----- --veZQh2nSsG1B2+Ku-- From owner-freebsd-arm@FreeBSD.ORG Tue Jan 21 06:09:15 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4C51CA39; Tue, 21 Jan 2014 06:09:15 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1CDE7153F; Tue, 21 Jan 2014 06:09:15 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id EF28DDB1F; Tue, 21 Jan 2014 06:09:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us EF28DDB1F Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 21 Jan 2014 01:09:12 -0500 From: Glen Barber To: Jordan Starcher Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140121060912.GB61932@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cC4dCx2W6DcYPM7t" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 06:09:15 -0000 --cC4dCx2W6DcYPM7t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I should have noted I have not personally tested the 10.0-PRERELEASE build. I have seen your issue in the past, however. I'm not clear on the cause. For experimentation purpose, can you try this build? http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 I'm mostly curious if the behavior is the same (i.e., if may be related to the SD card itself). SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) =3D a7722ef975a04a8a7c651b616c8= 02a7d7adf3811f768db65697b5a8e50c8300b Glen On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: > Hi Glen, >=20 > I seem to be running into the same error with your build. I checked the > sha256 hash and had the correct binary. See attached error. >=20 > Thanks, > Jordan >=20 > On Tuesday, January 21, 2014, Glen Barber wrote: >=20 > > On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > > > Hi, > > > > > > I've been trying to build a Raspberry Pi Model B binary image of Free= BSD > > > 10.0 using a 10.0 host and the crochet-freebsd script but have been > > > failing. I can get built image to POST, but it gets stuck when attemp= ting > > > to initialize the kernel. > > > > > > Does anyone have a 10.0 image I can use? > > > > > > > I have had some build failures with my release/10.0.0/ builds for RPI. > > > > Can you try this image, built from stable/10/ ? > > > > http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 > > > > SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D > > aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 > > > > Glen > > > > --cC4dCx2W6DcYPM7t Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS3g8IAAoJELls3eqvi17QqSgP/2J5kqIdm51Vhtgg65nX0kyT /usN6mr1x+6+MtoUbld3E8AjONweR00y3rGeoa0eESf9JG67nHpLsM09TuwW5LZ8 S0l4KAXcUu2whYNgpvxsq7TLa85PAnSj7A8JLlsttX52xGHW76wXsnBJQwdhqYDn DIXaitAk9rnL1HUb+c9D7DQ992oH7DIYc6G7Uy/OQhXOV2b9MJpl88X3Ij/PE3c/ Uwc4JIEz7ou8/QZSTGVxayYxYdMFf5dL5zim2B3rBQjNxvbzLZGFQxRJUBoWIsiL +RjIPF14X+lnpBWPRwuy4EZDAgqNV079Ol8Fk1Gsfz50KYjRDkjOPaU0DrzaPBzF YK7OlI2fKhWf3Ek+QyBdksv8vfw5OegD5XIMYCtwukZdbqtV+/StjKDELkrhVnhL YVuMgiwa/2eq8Eicm4RUSDK0i2fyvfkzEF6O8AIA7AT2ltCLIbEehMYliCIZH19p 1Njxi81u+1x+xdET4sHoWRKE4+HtAxUTQq1VameL6pPa1iYPwHBeUmO8r9Ta8hrr 4DXSrvV5t/DzMcyREw15gILqx2X+WU9UCljn8LEBbgjcMEFJ8ZUMPEaQBtokZAiU LscgTpqm/8x0GtcQ6dthFkDBjdrv2xmxvPPRIv8JKgaLDtkHsKJJ29qX5RgdzPKq pAiSh0/+DqjXTvkuSSzc =ahYC -----END PGP SIGNATURE----- --cC4dCx2W6DcYPM7t-- From owner-freebsd-arm@FreeBSD.ORG Tue Jan 21 08:36:43 2014 Return-Path: Delivered-To: arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B61672B0 for ; Tue, 21 Jan 2014 08:36:43 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94CD711B0 for ; Tue, 21 Jan 2014 08:36:43 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s0L8aaJm034910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Jan 2014 00:36:37 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s0L8aa0k034909 for arm@FreeBSD.org; Tue, 21 Jan 2014 00:36:36 -0800 (PST) (envelope-from jmg) Date: Tue, 21 Jan 2014 00:36:36 -0800 From: John-Mark Gurney To: arm@FreeBSD.org Subject: getting gdb working w/ EABI again... Message-ID: <20140121083636.GN75135@funkthat.com> Mail-Followup-To: arm@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 21 Jan 2014 00:36:37 -0800 (PST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 08:36:43 -0000 So, this started out to get kgdb working so I could figure out the size of vm_page_t, but I ended up making a armeb capabile cross debugger, and fixing gdb to work on armeb EABI binaries, and possibly others... The patch is at: https://www.funkthat.com/~jmg/gdb.arm.cross.patch The Makefile.inc1 hunk is there as I use xdev to build it, BUT I had to build and install a cross libkvm first: (cd lib/libkvm && make clean all install clean TARGET_ARCH=armeb) Then I could do the xdev, but it fails later. If someone who knows the build infrastructure wants to take a crack at making xdev install gdb, I'd be appreciative. I don't know enough of our build system to get it working right now. Comments? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 00:41:30 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4019E778; Wed, 22 Jan 2014 00:41:30 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F16B1A28; Wed, 22 Jan 2014 00:41:30 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id x10so7612045pdj.39 for ; Tue, 21 Jan 2014 16:41:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KVjpx6w9e4v21yf6JPrXJ+iV3R9ZN5KT9i+cjUt1xKI=; b=meCi8OFikgDqJHjbJO4dnc6OJ7XOF+TvS8pBkTqLZee2mDm2H7MnClDdG71bykyy0i KhrfziLq9xOhenfAogQOwyT+J6T+N5+wTgWUJ9BG09dj4tQLY8wOFsVe8Jh1CRNhUknQ lzZ8CL0FCiyoNiBTe+gLyopE9foLrKItz/J1J0GFhCTKUpEXEmfLkPuYpeoTtQKfRWJR qSftu50DKMZAh2IXBz2TJHQ+pL/Rl0fCOG78JppgDsDaj6vGyxJ1jVnd2Tq9bIfki1VA m9rYNp3MrqI/YmvgNqU4ZuK8+gVuaTknGGZWMSxLWeqwd6Qz5aB4nWp1bNZkc9ikyCMF xPcA== X-Received: by 10.66.150.69 with SMTP id ug5mr27902997pab.55.1390351289683; Tue, 21 Jan 2014 16:41:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.49.34 with HTTP; Tue, 21 Jan 2014 16:41:14 -0800 (PST) In-Reply-To: <20140121060912.GB61932@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> From: Jordan Starcher Date: Tue, 21 Jan 2014 19:41:14 -0500 Message-ID: Subject: Re: Raspberry Pi Binary Snapshot of 10.0? To: Glen Barber Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 00:41:30 -0000 Hi Glen, I tested with the 11.0-CURRENT image and had the same error: Mounting failed with error 19. I bought a new SD Card today and flashed your 10.0 image and it worked perfectly the first time! I guess these SD Cards are a bit finicky. Thank you very much for the help, your image seems to be working like a champ. I'll pickup another SD Card to test your 11.0 image as well. May I ask what build procedures you used? Best, Jordan On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber wrote: > I should have noted I have not personally tested the 10.0-PRERELEASE > build. > > I have seen your issue in the past, however. I'm not clear on the > cause. > > For experimentation purpose, can you try this build? > > http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 > > I'm mostly curious if the behavior is the same (i.e., if may be related > to the SD card itself). > > SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) = > a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b > > Glen > > On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: > > Hi Glen, > > > > I seem to be running into the same error with your build. I checked the > > sha256 hash and had the correct binary. See attached error. > > > > Thanks, > > Jordan > > > > On Tuesday, January 21, 2014, Glen Barber wrote: > > > > > On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > > > > Hi, > > > > > > > > I've been trying to build a Raspberry Pi Model B binary image of > FreeBSD > > > > 10.0 using a 10.0 host and the crochet-freebsd script but have been > > > > failing. I can get built image to POST, but it gets stuck when > attempting > > > > to initialize the kernel. > > > > > > > > Does anyone have a 10.0 image I can use? > > > > > > > > > > I have had some build failures with my release/10.0.0/ builds for RPI. > > > > > > Can you try this image, built from stable/10/ ? > > > > > > http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 > > > > > > SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) = > > > aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 > > > > > > Glen > > > > > > > > > From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 00:49:18 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBDE58F8; Wed, 22 Jan 2014 00:49:18 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BAC671A6B; Wed, 22 Jan 2014 00:49:18 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 42A93DEFD; Wed, 22 Jan 2014 00:49:17 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 42A93DEFD Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 21 Jan 2014 19:49:15 -0500 From: Glen Barber To: Jordan Starcher Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140122004915.GL35180@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HLsZ5Z1opAQvdr2J" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 00:49:19 -0000 --HLsZ5Z1opAQvdr2J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Great to hear. FWIW, I've moved the location of the images, so they are all in one directory (and checksums are included): http://people.freebsd.org/~gjb/RPI/ There is also an (untested by me yet, and *NOT* official) 10.0-RELEASE image there. I'm working on integrating this into the release build process, so it is very much "work in progress, may eat your cookies" kind of stuff. It is a wrapper around Crochet to do clean-room builds within a chroot. The in-progress stuff is located here: svn.freebsd.org/base/user/gjb/hacking/release-embedded Glen On Tue, Jan 21, 2014 at 07:41:14PM -0500, Jordan Starcher wrote: > Hi Glen, >=20 > I tested with the 11.0-CURRENT image and had the same error: Mounting > failed with error 19. >=20 > I bought a new SD Card today and flashed your 10.0 image and it worked > perfectly the first time! I guess these SD Cards are a bit finicky. >=20 > Thank you very much for the help, your image seems to be working like a > champ. I'll pickup another SD Card to test your 11.0 image as well. May I > ask what build procedures you used? >=20 > Best, > Jordan >=20 >=20 > On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber wrote: >=20 > > I should have noted I have not personally tested the 10.0-PRERELEASE > > build. > > > > I have seen your issue in the past, however. I'm not clear on the > > cause. > > > > For experimentation purpose, can you try this build? > > > > http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 > > > > I'm mostly curious if the behavior is the same (i.e., if may be related > > to the SD card itself). > > > > SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) =3D > > a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b > > > > Glen > > > > On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: > > > Hi Glen, > > > > > > I seem to be running into the same error with your build. I checked t= he > > > sha256 hash and had the correct binary. See attached error. > > > > > > Thanks, > > > Jordan > > > > > > On Tuesday, January 21, 2014, Glen Barber wrote: > > > > > > > On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > > > > > Hi, > > > > > > > > > > I've been trying to build a Raspberry Pi Model B binary image of > > FreeBSD > > > > > 10.0 using a 10.0 host and the crochet-freebsd script but have be= en > > > > > failing. I can get built image to POST, but it gets stuck when > > attempting > > > > > to initialize the kernel. > > > > > > > > > > Does anyone have a 10.0 image I can use? > > > > > > > > > > > > > I have had some build failures with my release/10.0.0/ builds for R= PI. > > > > > > > > Can you try this image, built from stable/10/ ? > > > > > > > > http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 > > > > > > > > SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D > > > > aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 > > > > > > > > Glen > > > > > > > > > > > > > > --HLsZ5Z1opAQvdr2J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS3xWLAAoJELls3eqvi17QHaQP/R+LA10A3ycw2tEuQF1eSpqA +zKTo+T0Q4nPKaZBjFZoB2cyYhjogjj4Xy09BAC31VAnIPOEhkLunWtH2Sgl0JR1 3sFsm0Mz+sLq6SnKo+tIaJ43PG+jBgBVAjbt0mHnRHlAlqvt1Ctq5fFENORy3OvT dKwk5rEOHWOuBDq3aZ8QkWZZHGZtMD4SlAo+4eZxu5hH9WajqkxBS9xweurH8qSO hcaLxx3Q5MbyVdyyfkuDKJ+qZWGbs5xrHxkhK4N1YI8OmY4SzS9ceBg//eAM4Mec x1p++9br27ocg8JAHEdn8nB0nXKI4UOzxydfTnORSoh7CkaUU/+3mlh2AUVNbmHd PcZ9Hl0WpCc7qCyN72V93rGNQUS294NlG+oWbhLiPWX764TNoywDK82Y/5ZvYlyF DOK40Bv21EvXZa3rIFbRjg18IMrIpCy0XpD3lZqGTeDkIheouzU1jz61zp9h5xEy /a6q45515iEsfQSWjOyogwMK+y87kc5TuA1p058UahTccS6omMJJjbf3BQgGdA69 bU07clgZw2XXFknSm9qAfOw0MY2U4sn8zyY5IoJf5CKkfzMZjCNZFjFQ71cxGSFR LemNtVi3M/EeGay4qvI1gutaX07CCLZtOZk5A8ynztc0U72bawwe0beuh0Vhzj1u +MDwaJjgGiFqMOvxnKeY =4j03 -----END PGP SIGNATURE----- --HLsZ5Z1opAQvdr2J-- From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 01:21:48 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C2583B09; Wed, 22 Jan 2014 01:21:48 +0000 (UTC) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8F2BA1DA9; Wed, 22 Jan 2014 01:21:48 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id w10so3654624pde.7 for ; Tue, 21 Jan 2014 17:21:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jqn7uxssCftn12kXOxxBk2vfL5FSCGlMs5ytg3ZvdCo=; b=Ke00G0w1DWZthRaKPj0VQkeJmO+gOP/j8ft4dMDY6BZwcEWsP5tDM86iFxs2xAgKlJ ruKf0EQ6ysUet16s0d3eZlgxxZZPTXb9VhjHDeTnldt2l2QigjpyGtsXWzDwImngxCx/ CbxNhRwFFiIorvtv0GdDca3OBC6akCmlqAnOtTpMOUryRoYia/Uh+8tNUnjh/j96UtJx AiyevVrTy0PO2QcfHxin6JUN22C4s2wtsv0nAt4h2zkm8nVwmtmDrdkiODnEcA61kdhx tXDZLHPuT9GiYB6nfxmSByVef5twg0dDifyW42MccO1oWFFrqQ/vZ0XO9yVTsxMwCY96 dx3g== X-Received: by 10.66.154.169 with SMTP id vp9mr27709357pab.39.1390353708205; Tue, 21 Jan 2014 17:21:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.49.34 with HTTP; Tue, 21 Jan 2014 17:21:33 -0800 (PST) In-Reply-To: <20140122004915.GL35180@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> From: Jordan Starcher Date: Tue, 21 Jan 2014 20:21:33 -0500 Message-ID: Subject: Re: Raspberry Pi Binary Snapshot of 10.0? To: Glen Barber Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 01:21:48 -0000 I gave the 10.0-RELEASE build a shot and it gets stuck early on in the boot kernel section. This is the same behavior I saw when I created a build using Crochet with the 10.0-RELEASE source. It's odd because it doesn't even make it far enough to hit the mounting error 19. I reflashed your 10.0-PRERELEASE and booted up perfectly. Also worth noting, the autosize_enable does work after the second boot. On Tue, Jan 21, 2014 at 7:49 PM, Glen Barber wrote: > Great to hear. > > FWIW, I've moved the location of the images, so they are all in one > directory (and checksums are included): > > http://people.freebsd.org/~gjb/RPI/ > > There is also an (untested by me yet, and *NOT* official) 10.0-RELEASE > image there. > > I'm working on integrating this into the release build process, so it is > very much "work in progress, may eat your cookies" kind of stuff. It is > a wrapper around Crochet to do clean-room builds within a chroot. > > The in-progress stuff is located here: > > svn.freebsd.org/base/user/gjb/hacking/release-embedded > > Glen > > On Tue, Jan 21, 2014 at 07:41:14PM -0500, Jordan Starcher wrote: > > Hi Glen, > > > > I tested with the 11.0-CURRENT image and had the same error: Mounting > > failed with error 19. > > > > I bought a new SD Card today and flashed your 10.0 image and it worked > > perfectly the first time! I guess these SD Cards are a bit finicky. > > > > Thank you very much for the help, your image seems to be working like a > > champ. I'll pickup another SD Card to test your 11.0 image as well. May I > > ask what build procedures you used? > > > > Best, > > Jordan > > > > > > On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber wrote: > > > > > I should have noted I have not personally tested the 10.0-PRERELEASE > > > build. > > > > > > I have seen your issue in the past, however. I'm not clear on the > > > cause. > > > > > > For experimentation purpose, can you try this build? > > > > > > http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 > > > > > > I'm mostly curious if the behavior is the same (i.e., if may be related > > > to the SD card itself). > > > > > > SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) = > > > a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b > > > > > > Glen > > > > > > On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: > > > > Hi Glen, > > > > > > > > I seem to be running into the same error with your build. I checked > the > > > > sha256 hash and had the correct binary. See attached error. > > > > > > > > Thanks, > > > > Jordan > > > > > > > > On Tuesday, January 21, 2014, Glen Barber wrote: > > > > > > > > > On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > > > > > > Hi, > > > > > > > > > > > > I've been trying to build a Raspberry Pi Model B binary image of > > > FreeBSD > > > > > > 10.0 using a 10.0 host and the crochet-freebsd script but have > been > > > > > > failing. I can get built image to POST, but it gets stuck when > > > attempting > > > > > > to initialize the kernel. > > > > > > > > > > > > Does anyone have a 10.0 image I can use? > > > > > > > > > > > > > > > > I have had some build failures with my release/10.0.0/ builds for > RPI. > > > > > > > > > > Can you try this image, built from stable/10/ ? > > > > > > > > > > > http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 > > > > > > > > > > SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) = > > > > > aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 > > > > > > > > > > Glen > > > > > > > > > > > > > > > > > > > > From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 01:25:30 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B181EC54; Wed, 22 Jan 2014 01:25:30 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7E9C21DC7; Wed, 22 Jan 2014 01:25:30 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id DCED5E261; Wed, 22 Jan 2014 01:25:28 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us DCED5E261 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 21 Jan 2014 20:25:27 -0500 From: Glen Barber To: Jordan Starcher Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140122012527.GM35180@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2YJj5f1P6Th4nBRw" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 01:25:30 -0000 --2YJj5f1P6Th4nBRw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Do you have console access to it? I'm curious where it gets stuck, and even more curious if there is network activity afterwards (in particular, I wonder if console output is being misdirected). Glen On Tue, Jan 21, 2014 at 08:21:33PM -0500, Jordan Starcher wrote: > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the bo= ot > kernel section. This is the same behavior I saw when I created a build > using Crochet with the 10.0-RELEASE source. It's odd because it doesn't > even make it far enough to hit the mounting error 19. I reflashed your > 10.0-PRERELEASE and booted up perfectly. Also worth noting, the > autosize_enable does work after the second boot. >=20 >=20 > On Tue, Jan 21, 2014 at 7:49 PM, Glen Barber wrote: >=20 > > Great to hear. > > > > FWIW, I've moved the location of the images, so they are all in one > > directory (and checksums are included): > > > > http://people.freebsd.org/~gjb/RPI/ > > > > There is also an (untested by me yet, and *NOT* official) 10.0-RELEASE > > image there. > > > > I'm working on integrating this into the release build process, so it is > > very much "work in progress, may eat your cookies" kind of stuff. It is > > a wrapper around Crochet to do clean-room builds within a chroot. > > > > The in-progress stuff is located here: > > > > svn.freebsd.org/base/user/gjb/hacking/release-embedded > > > > Glen > > > > On Tue, Jan 21, 2014 at 07:41:14PM -0500, Jordan Starcher wrote: > > > Hi Glen, > > > > > > I tested with the 11.0-CURRENT image and had the same error: Mounting > > > failed with error 19. > > > > > > I bought a new SD Card today and flashed your 10.0 image and it worked > > > perfectly the first time! I guess these SD Cards are a bit finicky. > > > > > > Thank you very much for the help, your image seems to be working like= a > > > champ. I'll pickup another SD Card to test your 11.0 image as well. M= ay I > > > ask what build procedures you used? > > > > > > Best, > > > Jordan > > > > > > > > > On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber wrote: > > > > > > > I should have noted I have not personally tested the 10.0-PRERELEASE > > > > build. > > > > > > > > I have seen your issue in the past, however. I'm not clear on the > > > > cause. > > > > > > > > For experimentation purpose, can you try this build? > > > > > > > > http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 > > > > > > > > I'm mostly curious if the behavior is the same (i.e., if may be rel= ated > > > > to the SD card itself). > > > > > > > > SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) =3D > > > > a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b > > > > > > > > Glen > > > > > > > > On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: > > > > > Hi Glen, > > > > > > > > > > I seem to be running into the same error with your build. I check= ed > > the > > > > > sha256 hash and had the correct binary. See attached error. > > > > > > > > > > Thanks, > > > > > Jordan > > > > > > > > > > On Tuesday, January 21, 2014, Glen Barber wrote: > > > > > > > > > > > On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I've been trying to build a Raspberry Pi Model B binary image= of > > > > FreeBSD > > > > > > > 10.0 using a 10.0 host and the crochet-freebsd script but have > > been > > > > > > > failing. I can get built image to POST, but it gets stuck when > > > > attempting > > > > > > > to initialize the kernel. > > > > > > > > > > > > > > Does anyone have a 10.0 image I can use? > > > > > > > > > > > > > > > > > > > I have had some build failures with my release/10.0.0/ builds f= or > > RPI. > > > > > > > > > > > > Can you try this image, built from stable/10/ ? > > > > > > > > > > > > > > http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 > > > > > > > > > > > > SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D > > > > > > aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 > > > > > > > > > > > > Glen > > > > > > > > > > > > > > > > > > > > > > > > > > --2YJj5f1P6Th4nBRw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS3x4GAAoJELls3eqvi17QehoP/1aSjg3Tl7qGBIpxLvoiZsj0 Raswd/PvICUNukpFcdg6JhFVV2k/GCI/SFJvTpoANFNKlm6m5TWmWV7nbiwnlWTY pGheFwaCyCpUHn88bvB/eu+eOj4Wj35TGW5erfOek7qvepO6POAYeCF9qXtSIzaM az3PLw5iY60D2j0pPUKki4CXI4U131f0boKUFK8O1bQnxnyIAQWJJZb7IlO0Mhwg kw2e+KKgkmskM4jF4GYHXXfwy77MDitOEObxJM84RsDUE/mxnICkvKpzUDiUjgg/ DLC3P8/VKQGd6W2dqFU82/XNaXQKPWWrrEEtiS+wIq0/6UgbgiLyn29p5xezWCQ0 IL3FvNB5vEsb59Cfi86v9gAIkfpr01NhiyFA0ZLLMgWO7AaQEE/gZQSRNty5HY7G eYb0bFz/LOlHq568sgTV8t4lQG/yMe50F5pr64DLEE1+0s3WZFugSMxgWmeL3GE0 9wC9u2TuCGPxTha/pRmhDP6+VSygdK/XLRCcuskGeE/hgKx8Ylj/0mEfeyQ+1vj2 jt2Z+ynFkMXvzM1+x+noCrWFlg0LK7C1mzVgf1E4qgOZK7tqeGXk7atqK55vKO1P C5iVf8S8tcEjCofXxcbTuJDEbUQfOzpe37jseZLPM6AbiXELgSSSig8O20FliX7I 3d7FG+8gZ8CFx+SegQ4J =d5wj -----END PGP SIGNATURE----- --2YJj5f1P6Th4nBRw-- From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 01:42:34 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 95E8DB9; Wed, 22 Jan 2014 01:42:34 +0000 (UTC) Received: from opossum.schwarzes.net (opossum.schwarzes.net [IPv6:2a01:c08::14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD4C1EF0; Wed, 22 Jan 2014 01:42:33 +0000 (UTC) Received: from [62.109.78.35] (mosquito.schwarzes.net [62.109.78.35]) (authenticated bits=0) by opossum.schwarzes.net (8.14.7/8.14.7) with ESMTP id s0M1gVCo077839; Wed, 22 Jan 2014 02:42:31 +0100 (CET) (envelope-from freebsd.asc@strcmp.org) From: Andreas Schwarz To: Jordan Starcher Mail-Reply-To: Andreas Schwarz Mail-Followup-To: freebsd-arm@FreeBSD.org Date: Wed, 22 Jan 2014 02:42:30 +0100 (CET) Message-ID: <43d2f0f860c.1e368b20@mail.schwarzes.net> In-Reply-To: References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> User-Agent: YAM/2.9 (MorphOS; PPC; rv:20131224r7420) Subject: Re: Raspberry Pi Binary Snapshot of 10.0? MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (opossum.schwarzes.net [62.109.93.232]); Wed, 22 Jan 2014 02:42:31 +0100 (CET) Cc: Glen Barber , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 01:42:34 -0000 On 21.01.14, Jordan Starcher wrote: > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the boot > kernel section. This is the same behavior I saw when I created a build > using Crochet with the 10.0-RELEASE source. It's odd because it doesn't > even make it far enough to hit the mounting error 19. I reflashed your > 10.0-PRERELEASE and booted up perfectly. Also worth noting, the > autosize_enable does work after the second boot. Have you tried to add set hw.bcm2835.sdhci.hs="0" set hw.bcm2835.min_freq="8000000" to your /boot/loader.rc ? best regards, Andreas From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 03:50:57 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF16A631 for ; Wed, 22 Jan 2014 03:50:57 +0000 (UTC) Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8BD2718D8 for ; Wed, 22 Jan 2014 03:50:57 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so4841899pdj.1 for ; Tue, 21 Jan 2014 19:50:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DpSIfHPIKUomgVl2Lh09B261HcUG1Ta9RAPoZcDmfv0=; b=i7nGYkqcUd8EbVtAqgp5/31FS818t1YeDRPURm6uPcrVQnr2MrFuBMJ/1M/5u0Wqj+ gtZqqFAdJPtlduNWfXfHXT+DtVrhAnJxjANyXBOYz0jI3eqLAq975RXCFY66JS7tr+qR RUN585FEFB43E7h63smNsZ+BAi5ZJt9GQ5wpeh9iyd2LAdvurbjZZirj3AR1qSuf2Pye 9vSydrq1oi4BUxSJxrqYcUba+KCDLIPfd4go3XUtPS18+9TVJ63d9vTqg2R3VYsc+qkX /Wka1PSoVQqpXkJVF99yf9sjJNGLp3AQGIJrZQx50G9TrZSzPxcLzOZdAKWukHvo/nw1 8AXg== X-Gm-Message-State: ALoCoQmTZBoINHF84fyalsuDq56CMB60kfVlU2xguClSngHKbfiuWzGFN9RTjgXIaftcUdP5OtXn X-Received: by 10.68.134.98 with SMTP id pj2mr28868794pbb.110.1390362656531; Tue, 21 Jan 2014 19:50:56 -0800 (PST) Received: from [192.168.1.2] (c-24-6-182-22.hsd1.ca.comcast.net. [24.6.182.22]) by mx.google.com with ESMTPSA id yd4sm17475910pbc.13.2014.01.21.19.50.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 19:50:55 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Raspberry Pi Binary Snapshot of 10.0? From: Tim Kientzle In-Reply-To: Date: Tue, 21 Jan 2014 19:50:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> To: Jordan Starcher X-Mailer: Apple Mail (2.1827) Cc: Glen Barber , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 03:50:57 -0000 On Jan 21, 2014, at 5:21 PM, Jordan Starcher = wrote: > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the = boot > kernel section. Can you provide more details? > This is the same behavior I saw when I created a build > using Crochet with the 10.0-RELEASE source. It's odd because it = doesn't > even make it far enough to hit the mounting error 19. I reflashed your > 10.0-PRERELEASE and booted up perfectly. Also worth noting, the > autosize_enable does work after the second boot. This is a pretty well-known bug at this point. Autosizing requires resizing two partitions: one is inside the other. For some reason, FreeBSD=92s =91geom resize=92 will successfully grow the outer partition but the new size isn=92t being fully honored until after a reboot. So two resize operations requires two boots. Does anyone have any ideas why geom isn=92t picking up the new size correctly after a resize? > On Tue, Jan 21, 2014 at 7:49 PM, Glen Barber wrote: >=20 >> Great to hear. >>=20 >> FWIW, I've moved the location of the images, so they are all in one >> directory (and checksums are included): >>=20 >> http://people.freebsd.org/~gjb/RPI/ >>=20 >> There is also an (untested by me yet, and *NOT* official) = 10.0-RELEASE >> image there. >>=20 >> I'm working on integrating this into the release build process, so it = is >> very much "work in progress, may eat your cookies" kind of stuff. It = is >> a wrapper around Crochet to do clean-room builds within a chroot. >>=20 >> The in-progress stuff is located here: >>=20 >> svn.freebsd.org/base/user/gjb/hacking/release-embedded >>=20 >> Glen >>=20 >> On Tue, Jan 21, 2014 at 07:41:14PM -0500, Jordan Starcher wrote: >>> Hi Glen, >>>=20 >>> I tested with the 11.0-CURRENT image and had the same error: = Mounting >>> failed with error 19. >>>=20 >>> I bought a new SD Card today and flashed your 10.0 image and it = worked >>> perfectly the first time! I guess these SD Cards are a bit finicky. >>>=20 >>> Thank you very much for the help, your image seems to be working = like a >>> champ. I'll pickup another SD Card to test your 11.0 image as well. = May I >>> ask what build procedures you used? >>>=20 >>> Best, >>> Jordan >>>=20 >>>=20 >>> On Tue, Jan 21, 2014 at 1:09 AM, Glen Barber = wrote: >>>=20 >>>> I should have noted I have not personally tested the = 10.0-PRERELEASE >>>> build. >>>>=20 >>>> I have seen your issue in the past, however. I'm not clear on the >>>> cause. >>>>=20 >>>> For experimentation purpose, can you try this build? >>>>=20 >>>> http://people.freebsd.org/~gjb/FreeBSD-11.0-CURRENT-RPI-B.img.bz2 >>>>=20 >>>> I'm mostly curious if the behavior is the same (i.e., if may be = related >>>> to the SD card itself). >>>>=20 >>>> SHA256 (FreeBSD-11.0-CURRENT-RPI-B.img.bz2) =3D >>>> a7722ef975a04a8a7c651b616c802a7d7adf3811f768db65697b5a8e50c8300b >>>>=20 >>>> Glen >>>>=20 >>>> On Tue, Jan 21, 2014 at 01:00:44AM -0500, Jordan Starcher wrote: >>>>> Hi Glen, >>>>>=20 >>>>> I seem to be running into the same error with your build. I = checked >> the >>>>> sha256 hash and had the correct binary. See attached error. >>>>>=20 >>>>> Thanks, >>>>> Jordan >>>>>=20 >>>>> On Tuesday, January 21, 2014, Glen Barber wrote: >>>>>=20 >>>>>> On Tue, Jan 21, 2014 at 12:38:15AM -0500, Jordan Starcher wrote: >>>>>>> Hi, >>>>>>>=20 >>>>>>> I've been trying to build a Raspberry Pi Model B binary image of >>>> FreeBSD >>>>>>> 10.0 using a 10.0 host and the crochet-freebsd script but have >> been >>>>>>> failing. I can get built image to POST, but it gets stuck when >>>> attempting >>>>>>> to initialize the kernel. >>>>>>>=20 >>>>>>> Does anyone have a 10.0 image I can use? >>>>>>>=20 >>>>>>=20 >>>>>> I have had some build failures with my release/10.0.0/ builds for >> RPI. >>>>>>=20 >>>>>> Can you try this image, built from stable/10/ ? >>>>>>=20 >>>>>>=20 >> http://people.freebsd.org/~gjb/FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2 >>>>>>=20 >>>>>> SHA256 (FreeBSD-10.0-PRERELEASE-RPI-B.img.bz2) =3D >>>>>> aec511f434d551c95a53c979add5b9b84d2618bbd2e2e012db9364e1985f5de3 >>>>>>=20 >>>>>> Glen >>>>>>=20 >>>>>>=20 >>>>=20 >>>>=20 >>>>=20 >>=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 03:59:17 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7131B6FC; Wed, 22 Jan 2014 03:59:17 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3ABF118FF; Wed, 22 Jan 2014 03:59:16 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 80C18EE54; Wed, 22 Jan 2014 03:59:15 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 80C18EE54 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 21 Jan 2014 22:59:13 -0500 From: Glen Barber To: Tim Kientzle Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140122035913.GO35180@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WoqaC9TUMqqIOlla" Content-Disposition: inline In-Reply-To: <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Jordan Starcher , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 03:59:17 -0000 --WoqaC9TUMqqIOlla Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2014 at 07:50:42PM -0800, Tim Kientzle wrote: >=20 > On Jan 21, 2014, at 5:21 PM, Jordan Starcher wrote: >=20 > > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the = boot > > kernel section. >=20 > Can you provide more details? >=20 >=20 > > This is the same behavior I saw when I created a build > > using Crochet with the 10.0-RELEASE source. It's odd because it doesn't > > even make it far enough to hit the mounting error 19. I reflashed your > > 10.0-PRERELEASE and booted up perfectly. Also worth noting, the > > autosize_enable does work after the second boot. >=20 > This is a pretty well-known bug at this point. Autosizing > requires resizing two partitions: one is inside the other. > For some reason, FreeBSD=E2=80=99s =E2=80=98geom resize=E2=80=99 will suc= cessfully > grow the outer partition but the new size isn=E2=80=99t being > fully honored until after a reboot. So two resize operations > requires two boots. >=20 > Does anyone have any ideas why geom isn=E2=80=99t picking up > the new size correctly after a resize? I *think* this is a geom bug that was fixed in head/, but did not make it to the release. Glen --WoqaC9TUMqqIOlla Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS30IRAAoJELls3eqvi17Q2NMP/0OTB3rNn+rtnNLVuK0LWreW PhasbpopM6r2P3ilYaBU7McQMZThNZaZ5y3UgJgv+OiHbnTJq/fRnZLHj7t0B4sn xPlxNPuPwpJrYmBBA4TNKE2jwY/7Avxi8rNKPODfwLoTVBOiedHg3IfAWCvdvohL 2hPkvLtt481aQxk5mMDuiqOcVFfu2PyZPr4XlDXW6HtksO/iKkK0KKtXb1dRYyCa ZLSRK04FuD6EPzBHz/fU1VZBdwVg/R62E+x+enR5o+x8F72PBtXs5JJ/0kWjAM91 dEv37xO5lKhrMrt+o9Zn101ejkZ8aJWgL6TMIygE4N4uHlREUhlej9sB2sqfdlsl ikQEpiHCoVwgBlH4X+4gDYqtC/QbMOx53fSxLNvCbH9FgYxYnknDoY+FGggpAHbJ kWejAr8sPOzm+AnQ5PoM2kJGugf8Dtyh/Y27RDEGB0gP5KInqmlQWX4gnHT0cnZP FvVOmUynMJUwvhUWOlxd4GqHSS8/h3CK+j02H3BuMuzzanWv8zSg+zN9v9LqRo3q /Bmp9AvpoQwQWrcb5XnHgTJxlDXIFUSPZQoHWljTzRVl+U9zwDZ/Z1C6Xnn3+01M zTTm10Mrh8l2nn4SCFITSmsHK2B77rFLLKe7DXERTJr4zHuGZEvxhr37ijwik1lf xFpCcDvB4lliMqwoB9W1 =LvjH -----END PGP SIGNATURE----- --WoqaC9TUMqqIOlla-- From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 10:02:23 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 56F9D1E2 for ; Wed, 22 Jan 2014 10:02:23 +0000 (UTC) Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5EE15F0 for ; Wed, 22 Jan 2014 10:02:22 +0000 (UTC) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id 8578B8B159 for ; Wed, 22 Jan 2014 19:02:16 +0900 (JST) Date: Wed, 22 Jan 2014 19:00:31 +0900 (JST) Message-Id: <20140122.190031.29969140.shigeru@os-hackers.jp> To: freebsd-arm@freebsd.org Subject: my private build RaspberryPi Image is available From: shigeru@os-hackers.jp X-Mailer: Mew version 3.3 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 10:02:23 -0000 Hi all, I build new RaspberryPi image of 11.0-current (r260998). Please try it if you have interested in. My image featreus are: - show mount/unmount status at LED - VIMAGE enabled - set to use my private pkg repository (unofficial) -- available 'screen', 'bash', 'sudo', etc... - fix elf header information to show dynamic object dependencies by 'ldd' - minimam setup at first root login (or 'su -') -- change password, set hostname, set timezone, 'pkg add' pkg binary It is available at, - tool -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/tools/freebsd_pi/ - SD image: -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20140122/ --- root password is 'freebsd-pi' --- rpi password is 'freebsd-pi' - pkg images repository: -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/ports/freebsd\:11\:armv6\:32\:el\:eabi\:softfp/latest/ --- selected options are ---- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/ports/freebsd\:11\:armv6\:32\:el\:eabi\:softfp/var/db/ports/ Thanks, --- YAMAMOTO Shigeru From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 13:46:12 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CAD86BD2 for ; Wed, 22 Jan 2014 13:46:12 +0000 (UTC) Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id 9B40819B3 for ; Wed, 22 Jan 2014 13:46:11 +0000 (UTC) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id EC7458E1AF for ; Wed, 22 Jan 2014 22:46:10 +0900 (JST) Date: Wed, 22 Jan 2014 22:44:25 +0900 (JST) Message-Id: <20140122.224425.103076338.shigeru@os-hackers.jp> To: freebsd-arm@freebsd.org Subject: Re: my private build RaspberryPi Image is available From: shigeru@os-hackers.jp In-Reply-To: <20140122.190031.29969140.shigeru@os-hackers.jp> References: <20140122.190031.29969140.shigeru@os-hackers.jp> X-Mailer: Mew version 3.3 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 13:46:12 -0000 Sorry, I send invalid URL. I send right URLs. - tool -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/tools/freebsd_pi/ - SD image: -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20140122/ --- root password is 'freebsd-pi' --- rpi password is 'freebsd-pi' - pkg images repository: -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/freebsd:11:armv6:32:el:eabi:softfp/latest/ --- selected options are ---- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/freebsd:11:armv6:32:el:eabi:softfp/var/db/ports/ Thanks, --- YAMAMOTO Shigeru From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 19:07:26 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71DCBEB8 for ; Wed, 22 Jan 2014 19:07:26 +0000 (UTC) Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 09A171886 for ; Wed, 22 Jan 2014 19:07:25 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id c13so5128592eek.17 for ; Wed, 22 Jan 2014 11:07:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0MYS1RS/wwa1IXoOrsp4w8m4S5z0xinJpRepfo7MkZg=; b=y34ZwZAwTH95/wCOC4XzN6SoO28D3mmyD3mJW+wEqdLG9GEE2Ab/SqD+cLkl/MOPLq aOc63hvSAnkVoKKXZEb/TkkBp222iJQuIIbJgJKriM0g/JVba5EWMu9uXgKwBQkHafvP E+jwHjMTWe6jYeehZtIH/AeT8l3X5AYXjTNCAPzGo3j/yGcKDDMPjkjSVmN6ozxwayHR qcrIMMZNM8UT7Da3DDuD6wvYHa8sHPZoUQTs6dL9H1dQJxNihZTiJ9566rSzZ1XMEwkc Hxi5VPmialIaH0vmDswDCq7iXevvDD8iAz8Cc/8U6dGLv897wNx+JCYMNkQhWRchX5mb QQyQ== MIME-Version: 1.0 X-Received: by 10.14.215.68 with SMTP id d44mr1679307eep.90.1390417644155; Wed, 22 Jan 2014 11:07:24 -0800 (PST) Received: by 10.14.2.66 with HTTP; Wed, 22 Jan 2014 11:07:24 -0800 (PST) In-Reply-To: <20140122.224425.103076338.shigeru@os-hackers.jp> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> Date: Wed, 22 Jan 2014 11:07:24 -0800 Message-ID: Subject: Re: my private build RaspberryPi Image is available From: hiren panchasara To: "shigeru@os-hackers.jp" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 19:07:26 -0000 On Wed, Jan 22, 2014 at 5:44 AM, shigeru@os-hackers.jp wrote: > > Sorry, I send invalid URL. > I send right URLs. > > - tool > -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/tools/freebsd_pi/ > - SD image: > -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/snapshots/20140122/ > --- root password is 'freebsd-pi' > --- rpi password is 'freebsd-pi' > - pkg images repository: > -- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/freebsd:11:armv6:32:el:eabi:softfp/latest/ > --- selected options are > ---- http://freebsd-current.os-hackers.jp/pub/FreeBSD/ports/freebsd:11:armv6:32:el:eabi:softfp/var/db/ports/ Nice work. Would you mind sharing how you created the packages? On RPi itself or you have some sort of cross-build setup? Cheers, Hiren From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 23:58:01 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BD5091E for ; Wed, 22 Jan 2014 23:58:01 +0000 (UTC) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6DA11F9 for ; Wed, 22 Jan 2014 23:58:00 +0000 (UTC) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 44FB176D6A; Thu, 23 Jan 2014 08:57:54 +0900 (JST) Date: Thu, 23 Jan 2014 08:56:09 +0900 (JST) Message-Id: <20140123.085609.53072279.shigeru@os-hackers.jp> To: hiren.panchasara@gmail.com Subject: Re: my private build RaspberryPi Image is available From: shigeru@os-hackers.jp In-Reply-To: References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> X-Mailer: Mew version 3.3 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 23:58:01 -0000 >>>>> "hiren" == hiren panchasara writes: hiren> Nice work. Would you mind sharing how you created the packages? On hiren> RPi itself or you have some sort of cross-build setup? I create pkg binaries on RaspberyPi, not on cross build environment. You, maybe, have a question: "why not use cross compile enviromnet?". It is for checking -current FreeBSD/RaspberryPi is stable or not. #unfortunately, -current is not stable ;-( And I think, stable system should be build itself on itself! How to build pkg binaries are, 1) svn checkout http://svn.freebsd.org/ports/head /usr/ports 2) change to target directory 3) do 'make package' (or 'make package-recursive') 4) do 'pkg repo /usr/ports/packages' to create a pkg catalog 5) copy/rsync pkg binaries to my web site Unfortunately, there are some ports which I can't compile on -current FreeBSD/RaspberryPi. These ports requires GCC, but gcc ports in -current does not support arm/armv6. I fix some ports to compile on -current clang/llvm/FreeBSD/RaspberryPi. #It is quick hack. Currently, I do not open patches, and I think how to open information/patches. Thanks, --- YAMAMOTO Shigeru From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 00:05:19 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89735F2B for ; Thu, 23 Jan 2014 00:05:19 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3DBE912CF for ; Thu, 23 Jan 2014 00:05:19 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0N05CfP049902 for ; Wed, 22 Jan 2014 19:05:17 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52E05CB8.8010201@m5p.com> Date: Wed, 22 Jan 2014 19:05:12 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: my private build RaspberryPi Image is available References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> In-Reply-To: <20140123.085609.53072279.shigeru@os-hackers.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Wed, 22 Jan 2014 19:05:17 -0500 (EST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 00:05:19 -0000 On 01/22/14 18:56, shigeru@os-hackers.jp wrote: > [...] > Unfortunately, there are some ports which I can't compile > on -current FreeBSD/RaspberryPi. > These ports requires GCC, but gcc ports in -current does not support > arm/armv6. > I fix some ports to compile on -current clang/llvm/FreeBSD/RaspberryPi. > #It is quick hack. > Currently, I do not open patches, and I think how to open > information/patches. > [...] The way I got around this problem was to build base with: WITH_GCC=yes in /etc/src.conf. The base GCC works with at least some of the ports that require GCC. -- George From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 00:16:04 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9FE4556D for ; Thu, 23 Jan 2014 00:16:04 +0000 (UTC) Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3804213A1 for ; Thu, 23 Jan 2014 00:16:04 +0000 (UTC) Received: by mail-ee0-f46.google.com with SMTP id c13so91941eek.5 for ; Wed, 22 Jan 2014 16:16:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZhTjimmKJBTBDIMvrC0OWawIb6ur9xWWaNbj+nFFcU4=; b=pMyxmz8qTezQyOi6/stFm8QtYR9MfG9lxe3TLHlreX6scru10Igdhe/LjPIq3FUtPe vlBLpHW5jgHIRxBA6XQL3R9Lyov9uEO8QEK6/LjNAUIeNi1aeNHQE6r7D6+KiqeB99UQ FoOP50wyWw0Zz8sWneSDXAg3BlsXHgg7ousdCeKvAEV9bZl8DHbyoHOvk+FaBkumDqQC xaHW5CgLFZjxmzDgKCChtL87qhZ2cAqrTsosVGEJqbQZTxUP3jHGi1sLDGhEz5xWaAjI 90xH7jXvfy7s2vXd8V00Vxzijx7pG7T2mtDJk3Tx2y0eNZ9t8bM6DpR0ux9yAdxIQU9s 8g+g== MIME-Version: 1.0 X-Received: by 10.14.32.132 with SMTP id o4mr4511389eea.14.1390436162566; Wed, 22 Jan 2014 16:16:02 -0800 (PST) Received: by 10.14.2.66 with HTTP; Wed, 22 Jan 2014 16:16:02 -0800 (PST) In-Reply-To: <20140123.085609.53072279.shigeru@os-hackers.jp> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> Date: Wed, 22 Jan 2014 16:16:02 -0800 Message-ID: Subject: Re: my private build RaspberryPi Image is available From: hiren panchasara To: "shigeru@os-hackers.jp" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 00:16:04 -0000 On Wed, Jan 22, 2014 at 3:56 PM, shigeru@os-hackers.jp wrote: > I fix some ports to compile on -current clang/llvm/FreeBSD/RaspberryPi. > #It is quick hack. > Currently, I do not open patches, and I think how to open > information/patches. Please file pr's with patches that you have via http://www.freebsd.org/send-pr.html. This way those port maintainers know about the problem and integrate your patches. Thanks, Hiren From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 05:00:47 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03E1D3D4 for ; Thu, 23 Jan 2014 05:00:47 +0000 (UTC) Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AC26D1D9D for ; Thu, 23 Jan 2014 05:00:46 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id o15so1641861qap.16 for ; Wed, 22 Jan 2014 21:00:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Bsxzfjbsnxt/wttQm9bUnH/fhkjegUwvori/jFwD++E=; b=cLdGcAe6YNgU3HaL6Okw2HEJgkTr5PoDn73xfH1ZdMXJpH14Pv2vHbPAnA7YGftAWD +aVP1j2VWNvZbsiYEizRtpLGeSY1F/WNvGJ2dEb2tK80vF9odSK0dEk1+N93iqyquRXZ LcELeyN0H7GDGMgedw0V+mxuwOy1HeGZ2SjjJYeRPQQyIs9qS6W6zIbhu1rwCZwt4SsJ BxqZGWdSoPmNjD55Kc5gkfEMDpbsXlT3w3CLwZai2pkHXQN9OkmbebfNvSlle2oHYwi2 N3I9qjcTJrI5TH1v1ICuvWXtDl5kJ2Fo1PTS5xHLJnRrayI22yLTuv5F5zEvWHlEnpvY BO4g== MIME-Version: 1.0 X-Received: by 10.140.102.204 with SMTP id w70mr7891182qge.110.1390453245778; Wed, 22 Jan 2014 21:00:45 -0800 (PST) Received: by 10.96.100.129 with HTTP; Wed, 22 Jan 2014 21:00:45 -0800 (PST) In-Reply-To: References: Date: Wed, 22 Jan 2014 21:00:45 -0800 Message-ID: Subject: Re: FreeBSD on Pandaboard? From: "Alex T." To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Tim Kientzle X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 05:00:47 -0000 Hi, having similar issues with running FreeBSD 10 on Pandaboard (OMAP 4430). Used crochet script from github for building the image. Starts booting as expected but then kernel panics on vm_pageout. Used clang toolchain for building. Did try other release of FreeBSD (9.2 + gcc toolchain) but had kernel panic as well, though in a different place, uart_tty_init. On 30 December 2013 18:49, Lundberg, Johannes < johannes@brilliantservice.co.jp> wrote: > Hi Tim > > I can't seem to get past mmc detection. > This is what I get: > > ti_sdma0: mem 0x4a056000-0x4a056fff irq 44,45,46,47 on > simplebus0 > ti_sdma0: sDMA revision 00010900 > ti_mmchs0: mem 0x4809c000-0x4809cfff > irq 115 on simplebus0 > mmc0: on ti_mmchs0 > Timecounters tick every 10.000 msec > panic: rw_wlock() by idle thread 0xc3818320 on rwlock pmap pv global @ > /usr/src-releng10/sys/arm/arm/pmap-v6.c:1406 > KDB: enter: panic > [ thread pid 10 tid 100002 ] > Stopped at $d: ldrb r15, [r15, r15, ror r15]! > db> bt > Tracing pid 10 tid 100002 td 0xc3818320 > db_trace_self() at db_trace_self > pc = 0xc0443114 lr = 0xc020a024 (db_stack_trace+0xec) > sp = 0xd63bc8a8 fp = 0xd63bc8c0 > r10 = 0xc0503790 > db_stack_trace() at db_stack_trace+0xec > pc = 0xc020a024 lr = 0xc0209980 (db_command+0x268) > sp = 0xd63bc8c8 fp = 0xd63bc968 > r4 = 0xc0209f38 r5 = 0x00000000 > r6 = 0xc048db50 > db_command() at db_command+0x268 > pc = 0xc0209980 lr = 0xc02096e8 (db_command_loop+0x60) > sp = 0xd63bc970 fp = 0xd63bc980 > r4 = 0xc04760a6 r5 = 0xc048731d > r6 = 0xc06a00d4 r7 = 0xd63bcb50 > r8 = 0xc3818320 r9 = 0xc053d8b4 > r10 = 0xc0503a00 > db_command_loop() at db_command_loop+0x60 > pc = 0xc02096e8 lr = 0xc020c1a0 (db_trap+0xdc) > sp = 0xd63bc988 fp = 0xd63bcaa8 > r4 = 0x00000000 r5 = 0xd63bc990 > r6 = 0xc053d8e0 > db_trap() at db_trap+0xdc > pc = 0xc020c1a0 lr = 0xc02f6e58 (kdb_trap+0xdc) > sp = 0xd63bcab0 fp = 0xd63bcad0 > r4 = 0x00000000 r5 = 0x00000001 > r6 = 0xc053d8e0 r7 = 0xd63bcb50 > kdb_trap() at kdb_trap+0xdc > pc = 0xc02f6e58 lr = 0xc0455a28 (undefinedinstruction+0x2b0) > sp = 0xd63bcad8 fp = 0xd63bcb48 > r4 = 0x00000000 r5 = 0xc04556d0 > r6 = 0x00000000 r7 = 0xe7ffffff > r8 = 0xc3818320 r9 = 0xd63bcb50 > r10 = 0xc02f66c4 > undefinedinstruction() at undefinedinstruction+0x2b0 > pc = 0xc0455a28 lr = 0xc0444acc (exception_exit) > sp = 0xd63bcb50 fp = 0xd63bcba8 > r4 = 0xffffffff r5 = 0xffff1004 > r6 = 0xc04868f7 r7 = 0xc052fdf0 > r8 = 0xc3818320 r9 = 0xc052fc50 > r10 = 0xc06a128c > exception_exit() at exception_exit > pc = 0xc0444acc lr = 0xc02f66b8 (kdb_enter+0x40) > sp = 0xd63bcba4 fp = 0xd63bcba8 > r0 = 0xc053d8c4 r1 = 0x00000000 > r2 = 0xc048ad43 r3 = 0x000000ab > r4 = 0xc0487380 r5 = 0xd63bcbfc > r6 = 0xc04868f7 r7 = 0xc052fdf0 > r8 = 0xc3818320 r9 = 0xc052fc50 > r10 = 0xc06a128c r12 = 0xc02fc80c > $a() at $a > pc = 0xc02f66c8 lr = 0xc02bfa30 (vpanic+0xb8) > sp = 0xd63bcbb0 fp = 0xd63bcbd0 > r4 = 0x00000100 > vpanic() at vpanic+0xb8 > pc = 0xc02bfa30 lr = 0xc02bf968 ($d) > sp = 0xd63bcbd8 fp = 0xd63bcbf0 > r4 = 0xc052fcf0 r5 = 0xc04868f7 > r6 = 0xd63bcbfc r7 = 0xc052fc50 > r8 = 0xc04acaf7 r9 = 0x00000000 > r10 = 0xc069eff0 > $d() at $d > pc = 0xc02bf968 lr = 0xc02bd450 (_rw_wlock_cookie+0x134) > sp = 0xd63bcc08 fp = 0xd63bcc28 > r4 = 0x0000057e r5 = 0xc04acaf7 > r6 = 0xc069f060 r7 = 0xc069f070 > _rw_wlock_cookie() at _rw_wlock_cookie+0x134 > pc = 0xc02bd450 lr = 0xc044a0e8 (pmap_fault_fixup+0x3c) > sp = 0xd63bcc30 fp = 0xd63bcc60 > r4 = 0x00000001 r5 = 0xc06a0b7c > r6 = 0x00000000 r7 = 0x00000005 > pmap_fault_fixup() at pmap_fault_fixup+0x3c > pc = 0xc044a0e8 lr = 0xc0454390 (data_abort_handler+0x228) > sp = 0xd63bcc68 fp = 0xd63bcd08 > r4 = 0x00000001 r5 = 0xc3818320 > r6 = 0x00000000 r7 = 0x00000005 > r8 = 0xd63bcd10 r9 = 0x000002c0 > r10 = 0xc06a0ac0 > data_abort_handler() at data_abort_handler+0x228 > pc = 0xc0454390 lr = 0xc0444acc (exception_exit) > sp = 0xd63bcd10 fp = 0xd63bcd68 > r4 = 0xffffffff r5 = 0xffff1004 > r6 = 0xc3818320 r7 = 0xc048147f > r8 = 0xc0481458 r9 = 0x00000001 > r10 = 0x00000000 > exception_exit() at exception_exit > pc = 0xc0444acc lr = 0xc02c6674 (critical_exit+0x6c) > sp = 0xd63bcd64 fp = 0xd63bcd68 > r0 = 0x00000000 r1 = 0x00000008 > r2 = 0xc048798b r3 = 0x000000d3 > r4 = 0xc3818320 r5 = 0xc048798b > r6 = 0xc3818320 r7 = 0xc048147f > r8 = 0xc0481458 r9 = 0x00000001 > r10 = 0x00000000 r12 = 0x00000000 > critical_exit() at critical_exit+0x6c > pc = 0xc02c6674 lr = 0xc0292ee4 (intr_event_handle+0x154) > sp = 0xd63bcd70 fp = 0xd63bcd98 > r4 = 0xc36f2800 r5 = 0xd63bcdb8 > intr_event_handle() at intr_event_handle+0x154 > pc = 0xc0292ee4 lr = 0xc0445d88 (arm_handler_execute+0x50) > sp = 0xd63bcda0 fp = 0xd63bcdb0 > r4 = 0xd63bcdb8 r5 = 0x00000073 > r6 = 0xc0526980 r7 = 0xc069d608 > r8 = 0x0022ee80 r9 = 0xc0528184 > r10 = 0xc0757004 > arm_handler_execute() at arm_handler_execute+0x50 > pc = 0xc0445d88 lr = 0xc0462068 (irq_entry+0x9c) > sp = 0xd63bcdb8 fp = 0xd63bce10 > r4 = 0xffffffff r5 = 0xffff1004 > r6 = 0xc06a1490 r7 = 0xc053d44c > irq_entry() at irq_entry+0x9c > pc = 0xc0462068 lr = 0xc044644c (cpu_idle+0x40) > sp = 0xd63bce0c fp = 0xd63bce10 > r0 = 0x00000000 r1 = 0xc0461d70 > r2 = 0x00000002 r3 = 0x00000000 > r4 = 0x00000001 r5 = 0xc04894a7 > r6 = 0xc06a1490 r7 = 0xc053d44c > r8 = 0x0022ee80 r9 = 0xc0528184 > r10 = 0xc0757004 r12 = 0x00000000 > arm11_sleep() at arm11_sleep+0x8 > pc = 0xc0461d78 lr = 0xc044644c (cpu_idle+0x40) > sp = 0xd63bce0c fp = 0xd63bce10 > Unwind failure (no registers changed) > > > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. > > > On Fri, Dec 27, 2013 at 3:10 AM, Tim Kientzle wrote: > > > > > On Dec 22, 2013, at 1:25 AM, Lundberg, Johannes < > > johannes@brilliantservice.co.jp> wrote: > > > > > Hi > > > > > > I have seen some blogs etc that claims to have successfully run FreeBSD > > on > > > Pandaboard ES but I can't seem to be able to duplicate the results. > > > > > > I tried with 10.0-releng and 11.0-current source and latest version of > > > crochet. Building is done on an amd64 machine. > > > > I got my PandaBoard ES to (minimally) boot a long time ago > > and used that to put support into Crochet. > > > > But I$B!G(Bve not had time to try it recently. > > > > > Creating image is no problem but boot halts early at USB / MMC > routine.. > > > > So basically, it sounds like: > > * Crochet is correctly building the boot bits and assembling the image. > > * The kernel is broken. > > > > I would suggest you next try adjusting > > sys/arm/conf/PANDABOARD: > > > > * Uncomment INVARIANTS, WITNESS, and DIAGNOSTIC > > Maybe you can get more information about exactly what is > > failing. > > > > * Remove drivers and see if the boot gets any further. > > > > I would love to get the PandaBoard working; with a gigabyte > > of RAM and a dual-core processor, it should have significantly > > better performance than the RPi and BeagleBones. > > > > Tim > > > > > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > $BHkL)J];}$K$D$$$F!'$3$NEE;R%a!<%k$O!"L>08?M$KAw?.$7$?$b$N$G$"$j!"HkF?FC8"$NBP>]$H$J$k>pJs$r4^$s$G$$$^$9!#(B > $B$b$7!"L>08?M0J30$NJ}$,l9g!"$3$N%a!<%k$NGK4~!"$*$h$S$3$N%a!<%k$K4X$9$k0l@Z$N3+<(!"(B > $BJ#$NMxMQ!"$^$?$O5-:\FbMF$K4p$E$/$$$+$J$k9TF0$b$5$l$J$$$h$&$*4j$$?=$7>e$2$^$9!#(B > --- > CONFIDENTIALITY NOTE: The information in this email is confidential > and intended solely for the addressee. > Disclosure, copying, distribution or any other action of use of this > email by person other than intended recipient, is prohibited. > If you are not the intended recipient and have received this email in > error, please destroy the original message. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 10:58:10 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57BA1817; Thu, 23 Jan 2014 10:58:10 +0000 (UTC) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 062311F87; Thu, 23 Jan 2014 10:58:09 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id s0NAw8WZ043405; Thu, 23 Jan 2014 10:58:08 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id s0NAw8nf043404; Thu, 23 Jan 2014 10:58:08 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 23 Jan 2014 10:58:08 GMT Message-Id: <201401231058.s0NAw8nf043404@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 10:58:10 -0000 TB --- 2014-01-23 09:35:23 - tinderbox 2.20 running on freebsd-stable.sentex.ca TB --- 2014-01-23 09:35:23 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2014-01-23 09:35:23 - starting RELENG_9 tinderbox run for arm/arm TB --- 2014-01-23 09:35:23 - cleaning the object tree TB --- 2014-01-23 09:35:23 - /usr/local/bin/svn stat /src TB --- 2014-01-23 09:35:28 - At svn revision 261074 TB --- 2014-01-23 09:35:29 - building world TB --- 2014-01-23 09:35:29 - CROSS_BUILD_TESTING=YES TB --- 2014-01-23 09:35:29 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-23 09:35:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-23 09:35:29 - SRCCONF=/dev/null TB --- 2014-01-23 09:35:29 - TARGET=arm TB --- 2014-01-23 09:35:29 - TARGET_ARCH=arm TB --- 2014-01-23 09:35:29 - TZ=UTC TB --- 2014-01-23 09:35:29 - __MAKE_CONF=/dev/null TB --- 2014-01-23 09:35:29 - cd /src TB --- 2014-01-23 09:35:29 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 23 09:35:31 UTC 2014 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Jan 23 10:55:33 UTC 2014 TB --- 2014-01-23 10:55:33 - cd /src/sys/arm/conf TB --- 2014-01-23 10:55:33 - /usr/sbin/config -m AVILA TB --- 2014-01-23 10:55:33 - building AVILA kernel TB --- 2014-01-23 10:55:33 - CROSS_BUILD_TESTING=YES TB --- 2014-01-23 10:55:33 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-23 10:55:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-23 10:55:33 - SRCCONF=/dev/null TB --- 2014-01-23 10:55:33 - TARGET=arm TB --- 2014-01-23 10:55:33 - TARGET_ARCH=arm TB --- 2014-01-23 10:55:33 - TZ=UTC TB --- 2014-01-23 10:55:33 - __MAKE_CONF=/dev/null TB --- 2014-01-23 10:55:33 - cd /src TB --- 2014-01-23 10:55:33 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Thu Jan 23 10:55:33 UTC 2014 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_rule.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_vfsops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_vnops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/fifofs/fifo_vnops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/nfs/nfs_commonkrpc.c In file included from /src/sys/rpc/rpc.h:70, from /src/sys/fs/nfs/nfs_commonkrpc.c:61: /src/sys/rpc/svc.h:330: error: field 'sp_lock' has incomplete type *** Error code 1 Stop in /obj/arm.arm/src/sys/AVILA. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2014-01-23 10:58:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-23 10:58:08 - ERROR: failed to build AVILA kernel TB --- 2014-01-23 10:58:08 - 3078.30 user 586.55 system 4964.96 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-arm-arm.full From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 17:37:25 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1656D6E4; Thu, 23 Jan 2014 17:37:25 +0000 (UTC) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC52016B4; Thu, 23 Jan 2014 17:37:24 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id s0NHbNZL030438; Thu, 23 Jan 2014 17:37:23 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id s0NHbNOB030437; Thu, 23 Jan 2014 17:37:23 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 23 Jan 2014 17:37:23 GMT Message-Id: <201401231737.s0NHbNOB030437@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 17:37:25 -0000 TB --- 2014-01-23 16:15:21 - tinderbox 2.20 running on freebsd-stable.sentex.ca TB --- 2014-01-23 16:15:21 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2014-01-23 16:15:21 - starting RELENG_9 tinderbox run for arm/arm TB --- 2014-01-23 16:15:21 - cleaning the object tree TB --- 2014-01-23 16:15:46 - /usr/local/bin/svn stat /src TB --- 2014-01-23 16:15:49 - At svn revision 261079 TB --- 2014-01-23 16:15:50 - building world TB --- 2014-01-23 16:15:50 - CROSS_BUILD_TESTING=YES TB --- 2014-01-23 16:15:50 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-23 16:15:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-23 16:15:50 - SRCCONF=/dev/null TB --- 2014-01-23 16:15:50 - TARGET=arm TB --- 2014-01-23 16:15:50 - TARGET_ARCH=arm TB --- 2014-01-23 16:15:50 - TZ=UTC TB --- 2014-01-23 16:15:50 - __MAKE_CONF=/dev/null TB --- 2014-01-23 16:15:50 - cd /src TB --- 2014-01-23 16:15:50 - /usr/bin/make -B buildworld >>> World build started on Thu Jan 23 16:15:53 UTC 2014 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Jan 23 17:35:08 UTC 2014 TB --- 2014-01-23 17:35:08 - cd /src/sys/arm/conf TB --- 2014-01-23 17:35:08 - /usr/sbin/config -m AVILA TB --- 2014-01-23 17:35:08 - building AVILA kernel TB --- 2014-01-23 17:35:08 - CROSS_BUILD_TESTING=YES TB --- 2014-01-23 17:35:08 - MAKEOBJDIRPREFIX=/obj TB --- 2014-01-23 17:35:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-01-23 17:35:08 - SRCCONF=/dev/null TB --- 2014-01-23 17:35:08 - TARGET=arm TB --- 2014-01-23 17:35:08 - TARGET_ARCH=arm TB --- 2014-01-23 17:35:08 - TZ=UTC TB --- 2014-01-23 17:35:08 - __MAKE_CONF=/dev/null TB --- 2014-01-23 17:35:08 - cd /src TB --- 2014-01-23 17:35:08 - /usr/bin/make -B buildkernel KERNCONF=AVILA >>> Kernel build for AVILA started on Thu Jan 23 17:35:09 UTC 2014 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_rule.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_vfsops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/devfs/devfs_vnops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/fifofs/fifo_vnops.c cc -mbig-endian -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcpu=xscale -ffreestanding -Werror /src/sys/fs/nfs/nfs_commonkrpc.c In file included from /src/sys/rpc/rpc.h:70, from /src/sys/fs/nfs/nfs_commonkrpc.c:61: /src/sys/rpc/svc.h:330: error: field 'sp_lock' has incomplete type *** Error code 1 Stop in /obj/arm.arm/src/sys/AVILA. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2014-01-23 17:37:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2014-01-23 17:37:23 - ERROR: failed to build AVILA kernel TB --- 2014-01-23 17:37:23 - 3064.91 user 587.29 system 4921.78 real http://tinderbox.freebsd.org/tinderbox-freebsd9-build-RELENG_9-arm-arm.full From owner-freebsd-arm@FreeBSD.ORG Thu Jan 23 19:38:56 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1DCF968A; Thu, 23 Jan 2014 19:38:56 +0000 (UTC) Received: from wp376.webpack.hosteurope.de (wp376.webpack.hosteurope.de [IPv6:2a01:488:42::50ed:8591]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CF5A611EF; Thu, 23 Jan 2014 19:38:55 +0000 (UTC) Received: from xdsl-78-34-171-233.netcologne.de ([78.34.171.233] helo=dijkstra.cruwe.de); authenticated by wp376.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1W6Q72-0005je-Ss; Thu, 23 Jan 2014 20:38:53 +0100 Date: Thu, 23 Jan 2014 20:38:51 +0100 From: "Christopher J. Ruwe" To: freebsd-arm@freebsd.org Subject: ports-mgmt/pkg failing to link when cross-compiling with qemu Message-ID: <20140123203851.0eed5088@dijkstra.cruwe.de> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;cjr@cruwe.de;1390505935;62afb0a8; Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 19:38:56 -0000 When trying the instructions on https://wiki.freebsd.org/QemuUserModeHowTo, I encountered a fairly basic port (ports-mgmt/pkg) failing to link properly: [... - everything fine until here] cc -static -O -pipe -DPORTSDIR=\"/usr/ports\" -I../libpkg -I/usr/ports/ports-mg/work/pkg-1.2.5/pkg/../external/expat/lib -std=gnu99 -Qunused-arguments -Wsystemprototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwritepts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-int -static -o pkg-static add.o annotate.o audit.o autoremove.o backup.o check.ock.o main.o plugins.o progressmeter.o query.o register.o repo.o rquery.o update.otch.o shell.o stats.o ssh.o -L/usr/ports/ports-mgmt/pkg/work/pkg-1.2.5/pkg/../lib -lcrypto -lmd -lz -lbz2 -llzma -ljail -lelf -larchive -lsbuf -lfetch -lpt add.o: In function `exec_add': add.c:(.text+0x11c): undefined reference to `pkgdb_access' add.c:(.text+0x13c): undefined reference to `pkgdb_open' add.c:(.text+0x164): undefined reference to `pkg_manifest_keys_new' add.c:(.text+0x344): undefined reference to `pkg_fetch_file' add.c:(.text+0x364): undefined reference to `pkg_add' add.c:(.text+0x42c): undefined reference to `pkg_manifest_keys_free' add.c:(.text+0x434): undefined reference to `pkgdb_close' [ ... - they are all alike] version.o: In function `print_version': version.c:(.text+0x14fc): undefined reference to `pkg_get2' version.c:(.text+0x1514): undefined reference to `pkg_version_cmp' version.c:(.text+0x1590): undefined reference to `pkg_asprintf' version.c:(.text+0x15a4): undefined reference to `pkg_asprintf' version.c:(.text+0x1650): undefined reference to `pkg_printf' which.o: In function `exec_which': which.c:(.text+0xe8): undefined reference to `pkgdb_open' which.c:(.text+0xf8): undefined reference to `pkgdb_close' which.c:(.text+0x18c): undefined reference to `pkgdb_query_which' which.c:(.text+0x1ac): undefined reference to `pkgdb_it_next' which.c:(.text+0x250): undefined reference to `pkg_printf' which.c:(.text+0x260): undefined reference to `pkg_printf' which.c:(.text+0x284): undefined reference to `pkg_printf' which.c:(.text+0x298): undefined reference to `pkgdb_it_next' which.c:(.text+0x2a8): undefined reference to `pkg_free' which.c:(.text+0x2b0): undefined reference to `pkgdb_it_free' which.c:(.text+0x2b8): undefined reference to `pkgdb_close' fetch.o: In function `exec_fetch': fetch.c:(.text+0xa4): undefined reference to `pkg_config_bool' fetch.c:(.text+0xb0): undefined reference to `pkg_config_bool' fetch.c:(.text+0x1e8): undefined reference to `pkgdb_set_case_sensitivity' fetch.c:(.text+0x2c0): undefined reference to `pkgdb_access' fetch.c:(.text+0x2e0): undefined reference to `pkgdb_access' fetch.c:(.text+0x314): undefined reference to `pkgdb_open' fetch.c:(.text+0x330): undefined reference to `pkg_jobs_new' fetch.c:(.text+0x34c): undefined reference to `pkg_jobs_set_repository' fetch.c:(.text+0x360): undefined reference to `pkg_jobs_set_flags' fetch.c:(.text+0x37c): undefined reference to `pkg_jobs_add' fetch.c:(.text+0x38c): undefined reference to `pkg_jobs_solve' fetch.c:(.text+0x39c): undefined reference to `pkg_jobs_count' fetch.c:(.text+0x418): undefined reference to `pkg_jobs_apply' fetch.c:(.text+0x420): undefined reference to `pkg_jobs_free' fetch.c:(.text+0x428): undefined reference to `pkgdb_close' shell.o: In function `exec_shell': shell.c:(.text+0x54): undefined reference to `pkgdb_cmd' stats.o: In function `exec_stats': stats.c:(.text+0xe8): undefined reference to `pkgdb_open' stats.c:(.text+0x120): undefined reference to `pkgdb_stats' stats.c:(.text+0x13c): undefined reference to `pkgdb_stats' stats.c:(.text+0x1cc): undefined reference to `pkg_repos_total_count' stats.c:(.text+0x1e8): undefined reference to `pkgdb_stats' stats.c:(.text+0x204): undefined reference to `pkgdb_stats' stats.c:(.text+0x220): undefined reference to `pkgdb_stats' stats.c:(.text+0x23c): undefined reference to `pkgdb_stats' stats.c:(.text+0x294): undefined reference to `pkgdb_close' ssh.o: In function `exec_ssh': ssh.c:(.text+0x98): undefined reference to `pkg_sshserve' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[3]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.2.5/pkg *** Error code 1 Stop. make[2]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.2.5 *** Error code 1 Stop. make[1]: stopped in /usr/ports/ports-mgmt/pkg *** Error code 1 Stop. make: stopped in /usr/ports/ports-mgmt/pkg Has anybody encountered something similar and would know how to fix that? Thanks and cheers, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 cjr@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: "Lets eat Grandma." or "Lets eat, Grandma." - Punctuation saves lives. "A panda eats shoots and leaves." or "A panda eats, shoots, and leaves." - Punctuation teaches proper biology. "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." (RFC 1925) From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 01:01:10 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EF8EACD6; Fri, 24 Jan 2014 01:01:10 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BBA771104; Fri, 24 Jan 2014 01:01:10 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id hz1so2572858pad.22 for ; Thu, 23 Jan 2014 17:01:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fSsn+THHPm0PdSMT3g5AJlxehNPOyzC8s/gTHAomIFo=; b=eURfXzID8Bxe6Lb1Cy2QNlUGlgAp22OhKqp6L7XZURRwTOOUZRGwCcEqDOxTyJLaVi bdxK4AbbxtQEy0Gaw7MgQIyzrtJEJ3HqV9e8xJLjhKSYQzG8J2c/Om/nlLTSSE+BntNX yoryRkLMRjRKaRpOlH6sqvPYMERSuvrY/y9EA3F0bntEO6/pamHZUUOlR0cMqXZDn8IT 2rdUGBlDxcQxgtw1WSAo6lHtJ3eokH9C6uKA4SmFB5/2RdE/SAEYtTVB7gYwnLbRjfoq CPQum5Oz4u2IO2w1im1mOOjSIp3JbdAFCc8TbJzSri8Z5o6xQJ8ydMb0LYbP/MOO8mC2 61Og== X-Received: by 10.66.142.170 with SMTP id rx10mr11212443pab.117.1390525270387; Thu, 23 Jan 2014 17:01:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.49.34 with HTTP; Thu, 23 Jan 2014 17:00:53 -0800 (PST) In-Reply-To: <20140122035913.GO35180@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> <20140122035913.GO35180@glenbarber.us> From: Jordan Starcher Date: Thu, 23 Jan 2014 20:00:53 -0500 Message-ID: Subject: Re: Raspberry Pi Binary Snapshot of 10.0? To: Glen Barber Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Tim Kientzle , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 01:01:11 -0000 > > Do you have console access to it? I'm curious where it gets stuck, and > even more curious if there is network activity afterwards (in > particular, I wonder if console output is being misdirected). I have it connected to my TV. It doesn't appear to have network access after getting stuck. The keyboard also doesn't do anything. See the image linked below for details. > Have you tried to add > set hw.bcm2835.sdhci.hs="0" > set hw.bcm2835.min_freq="8000000" > to your /boot/loader.rc ? > best regards, > Andreas I have not tried this as I don't have a FreeBSD machine with an SD Card reader to edit the files in the UFS mount. > I gave the 10.0-RELEASE build a shot and it gets stuck early on in the > boot > > kernel section. > Can you provide more details? http://imgur.com/UGRZAuA Another interesting note. I purchased a brand new SanDisk Class 10 16gb SD Card today and flashed the 10.0-PRERELEASE image. I was surprised when I went to boot the new card and it got stuck at Error 19 when mounting UFS partition. I figured out a trick: I moved the lock switch on the card to the middle of the card, ever slightly biased toward the unlocked side, rebooted and it mounted without issue. Perhaps the SD Card reader on these are picky about where the lock switch is? I knew this trick because my MacBook Pro card reader acts the same way. From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 01:01:05 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DFA9BCD2; Fri, 24 Jan 2014 01:01:05 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9519B1102; Fri, 24 Jan 2014 01:01:05 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0O10wnq058953; Thu, 23 Jan 2014 20:01:03 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52E1BB4A.1040807@m5p.com> Date: Thu, 23 Jan 2014 20:00:58 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Raspberry Pi: still getting prefetch aborts References: <52BB73B4.5030000@m5p.com> <52D5D0F8.9050205@m5p.com> <1389794207.1230.27.camel@revolution.hippie.lan> <52D72ABC.4080502@m5p.com> In-Reply-To: <52D72ABC.4080502@m5p.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Thu, 23 Jan 2014 20:01:04 -0500 (EST) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 01:01:05 -0000 On 01/15/14 19:41, George Mitchell wrote: > On 01/15/14 08:56, Ian Lepore wrote: >> [...] >> I've been consistantly unable to reproduce the userland crash you see on >> rpi, even though the tracebacks and all make it look a lot like the >> wrong-endian kernel crashes I see on Wandboard (although my gut tells me >> it's not really the same problem). My setup is a lot like yours, with >> nfs-mounted filesystems, but when I build ports that way it either works >> fine, or the port builds die for other reasons. >> >> -- Ian >> [...] It's definitely because my /usr/ports directory was NFS-mounted by the automounter. When I just do fixed NFS mounts via /etc/fstab, I don't get the prefetch aborts any more. Don't ask me why automounts vs. static mounts should make any difference here ... -- George From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 01:18:16 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B8A9528; Fri, 24 Jan 2014 01:18:16 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 655A4120D; Fri, 24 Jan 2014 01:18:16 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 30773101D8; Fri, 24 Jan 2014 01:18:14 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 30773101D8 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 23 Jan 2014 20:18:12 -0500 From: Glen Barber To: Jordan Starcher Subject: Re: Raspberry Pi Binary Snapshot of 10.0? Message-ID: <20140124011812.GL52955@glenbarber.us> References: <20140121054346.GA61932@glenbarber.us> <20140121060912.GB61932@glenbarber.us> <20140122004915.GL35180@glenbarber.us> <7E354C58-96C5-4497-8F29-197BE3BA1619@kientzle.com> <20140122035913.GO35180@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Jbyekxk18hnEXT0m" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Tim Kientzle , "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 01:18:16 -0000 --Jbyekxk18hnEXT0m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 23, 2014 at 08:00:53PM -0500, Jordan Starcher wrote: > > > > Do you have console access to it? I'm curious where it gets stuck, and > > even more curious if there is network activity afterwards (in > > particular, I wonder if console output is being misdirected). >=20 >=20 > I have it connected to my TV. It doesn't appear to have network access > after getting stuck. The keyboard also doesn't do anything. See the image > linked below for details. >=20 Ugh. :( Is this HDMI, or RCA? While I'm interested in the answer, I'm mostly curious at this point if changing which external video is in use. (Ideally, it shouldn't, or at least, not based on my testing on head/.) But if you can't test this, no worries. Glen --Jbyekxk18hnEXT0m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS4b9UAAoJELls3eqvi17QWZkP/0+v3OkBvBu7LngSl45J00k5 4wm55FUeBwwO7hqlzL0rIi3yoyvzabHp4t64wR5izKZ9Sxh+cvrUfRHXfir84uSS lhySUAJXiapGAAWranhfKlbY+0miGrKzczi5t3Id/UhUD9MYVSVPLV3vlGJvUyJ3 zoQgbYWldS/VTZ1+lGTiNu0jtXg1o8nWGjU5hxioC6Md6YtCm5axghZgFaGP0v2b GOYrCDe757cs1wHD+jNQO4ni277FkuE8e+P/Eq5EFRxgxgcTm8cqFXxx/e3TKu/x O5LjNHLcDvM4IHY4FHbfVs//IwpSEOYnTXaEMCBVEAe4OhzPPWN0SYBbrAVaete3 +5YHh8a9/BxbiPWmXmMcHnlSQT40XVc//AaCEuzA6XCwOFZvOcaJk0732aE5I9xn +5UHMFrY7TiFBwN7MpVsAqvopo1uWMSvLZleQvqJFq9qAIINisQQYYSssKG8tke7 o4TNs9QbeORgig15P9nL+jcpPBYmoxREBqc/IFwixhpZQaE+BteTe56FitIArTL7 R8RlpuITsgjMw1VfATpgdFSXVXaAIzsB9SNuked1NzjFplFyc1g0yG0Ev4fHZLdJ +7PqGbNaWA1dDqGcUBqyCHKj9FjL9WGy5oas+uv+VYZQ7Vvc3qw+DOVDrRRnnbQT 5/dB5FOtAEE0BeewFtPm =SrB7 -----END PGP SIGNATURE----- --Jbyekxk18hnEXT0m-- From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 04:31:57 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C403860 for ; Fri, 24 Jan 2014 04:31:57 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 360DE11CB for ; Fri, 24 Jan 2014 04:31:57 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id z10so2664723pdj.33 for ; Thu, 23 Jan 2014 20:31:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=Ghm4uLDvHhmD7HZo4KCASwc3Q3Sf5G6MQnhQazRYmHI=; b=pnVub/PzbXAnpKsdt9SrTKonVT3NC/M/ps3AKyJ7bPOuEFORulULjRuf4f6xE2vy66 6tSuXrT63LlnWbVzxyBnJ/tIJTQJExLWlD+ATp2avw1FGXI/9eeq+LGGCQDebQxlZvC5 LcK7ENx42xSEFXO3tP9qGtCnDmb/NSo9gZU57AE6nla8d41CBbKWgc14NaI/lp5e6Q0z iXTdWOMc6BEr2PEnXUOiCGUEmJhMlibgWlWUNNYV6R9bh/I7RryJUS8V2fhx6u9ZaP+q b8jzA6AstlX5EUA//T72p2F+m2qfsgdAKJ3FINxA4uV3m2Gdaofyp4bWR9LlKVIpxB50 f/kg== X-Received: by 10.68.203.163 with SMTP id kr3mr12201155pbc.33.1390537916831; Thu, 23 Jan 2014 20:31:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.70.49.34 with HTTP; Thu, 23 Jan 2014 20:31:41 -0800 (PST) From: Jordan Starcher Date: Thu, 23 Jan 2014 23:31:41 -0500 Message-ID: Subject: Raspberry Pi Clock Frequency To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 04:31:57 -0000 Hi, I was wondering if it is possible to adjust the CPU frequency on the Raspberry Pi under FreeBSD 10.0-RELEASE? I've been trying to find what the clock is currently set at using sysctl but I cannot seem to find any values that show the frequency. I also checked the FreeBSD kernel source and did not see any related tunable aside from hw.bcm2835.min_freq. Is this the tunable I would use? Thanks, Jordan From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 13:37:50 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AFAFF458 for ; Fri, 24 Jan 2014 13:37:50 +0000 (UTC) Received: from smtp.hs-karlsruhe.de (smtp.HS-Karlsruhe.DE [193.196.64.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 753A31D83 for ; Fri, 24 Jan 2014 13:37:50 +0000 (UTC) Received: from iz-wera01.hs-karlsruhe.de ([193.196.65.46]) by smtp.hs-karlsruhe.de with esmtp (Exim 4.80.1) (envelope-from ) id 1W6gx2-006Gys-Pp; Fri, 24 Jan 2014 14:37:40 +0100 X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Ralf Wenk To: freebsd-arm@freebsd.org Subject: RaspberryPi pinic with CURRENT r260558 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Jan 2014 14:37:40 +0100 Message-Id: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 13:37:50 -0000 Hello, while updating the ports DB my RPi panics because of an undefined instruction. /usr/ports ist located on an USB-stick, /usr/local is located on the SDHC card. I do not file a bug report because the problem is not reliable repeatable= . The RPi tends to crash while or after doing the following: - NFS mounting a /usr/ports tree from a i386 Machine - rsyc(1)-ing that tree to the local copy - fetching the INDEX-file and finally calling portversion(1). Till today it never panics the first time after booting but rarely surviv= ed the fourth. This time the UFS journals got damaged preventing multi user boot so I ha= d to fsck(8) all filesystems manually bypassing the journals. Ralf =23 portversion -v -L =3D =5BReading data from pkg(8) ... - 58 packages found - done=5D =5BUpdating the portsdb in /usr/ports ... - 24591 port= =20 entries found .........1000.........2000.........3000.........4000..... ....5000.........6000.........7000.........8000.........9000.........10 000.........11000.........12000.........13000.........14000.........150 00.........16000 panic: Undefined instruction in kernel. KDB: enter: panic =5B thread pid 13666 tid 100110 =5D Stopped at =24d: ldrb r15, =5Br15, r15, ror r15=5D=21 db> bt Tracing pid 13666 tid 100110 td 0xc5082960 db_trace_self() at db_trace_self pc =3D 0xc04a47e8 lr =3D 0xc01344bc (db_stack_trace+0xf4) sp =3D 0xddcda980 fp =3D 0xddcda998 r10 =3D 0xc0578a20 db_stack_trace() at db_stack_trace+0xf4 pc =3D 0xc01344bc lr =3D 0xc0133e6c (db_command+0x264) sp =3D 0xddcda9a0 fp =3D 0xddcdaa40 r4 =3D 0x00000000 r5 =3D 0x00000000 r6 =3D 0xc050f606 db_command() at db_command+0x264 pc =3D 0xc0133e6c lr =3D 0xc0133bdc (db_command_loop+0x60) sp =3D 0xddcdaa48 fp =3D 0xddcdaa58 r4 =3D 0xc04e244e r5 =3D 0xc04f608a r6 =3D 0xc05c10bc r7 =3D 0xddcdac40 r8 =3D 0xc5082960 r9 =3D 0xc05b7ae4 r10 =3D 0xc0578c90 db_command_loop() at db_command_loop+0x60 pc =3D 0xc0133bdc lr =3D 0xc01366ac (db_trap+0xdc) sp =3D 0xddcdaa60 fp =3D 0xddcdab80 r4 =3D 0x00000000 r5 =3D 0xddcdaa68 r6 =3D 0xc05b7b10 db_trap() at db_trap+0xdc pc =3D 0xc01366ac lr =3D 0xc02c1f48 (kdb_trap+0xd4) sp =3D 0xddcdab88 fp =3D 0xddcdaba8 r4 =3D 0x00000000 r5 =3D 0x00000001 r6 =3D 0xc05b7b10 r7 =3D 0xddcdac40 kdb_trap() at kdb_trap+0xd4 pc =3D 0xc02c1f48 lr =3D 0xc04b9740 (undefinedinstruction+0x310= ) sp =3D 0xddcdabb0 fp =3D 0xddcdac38 r4 =3D 0x00000000 r5 =3D 0xc04b938c r6 =3D 0x00000000 r7 =3D 0xe7ffffff r8 =3D 0xc5082960 r9 =3D 0xddcdac40 r10 =3D 0xc02c17f8 undefinedinstruction() at undefinedinstruction+0x310 pc =3D 0xc04b9740 lr =3D 0xc04a65f8 (exception_exit) sp =3D 0xddcdac40 fp =3D 0xddcdac98 r4 =3D 0xc04f60e4 r5 =3D 0xc0510c61 r6 =3D 0xc05c2b40 r7 =3D 0xc05aa018 r8 =3D 0xc5082960 r9 =3D 0xc05a9fa0 r10 =3D 0xddcdaccc exception_exit() at exception_exit pc =3D 0xc04a65f8 lr =3D 0xc02c17ec (kdb_enter+0x40) sp =3D 0xddcdac94 fp =3D 0xddcdac98 r0 =3D 0xc05b7af4 r1 =3D 0x00000000 r2 =3D 0x00000001 r3 =3D 0x00000001 r4 =3D 0xc04f60e4 r5 =3D 0xc0510c61 r6 =3D 0xc05c2b40 r7 =3D 0xc05aa018 r8 =3D 0xc5082960 r9 =3D 0xc05a9fa0 r10 =3D 0xddcdaccc r12 =3D 0x00000000 =24a() at =24a pc =3D 0xc02c17fc lr =3D 0xc02836cc (panic+0xc8) sp =3D 0xddcdaca0 fp =3D 0xddcdacc0 r4 =3D 0x00000100 panic() at panic+0xc8 pc =3D 0xc02836cc lr =3D 0xc04b97a0 (=24d) sp =3D 0xddcdacd8 fp =3D 0xddcdad60 r4 =3D 0x00000000 r5 =3D 0xc04ba28c r6 =3D 0xc05c0f64 r7 =3D 0xeee12a10 r8 =3D 0xc5082960 r9 =3D 0xddcdad68 r10 =3D 0xc04ba36c =24d() at =24d pc =3D 0xc04b97a0 lr =3D 0xc04a65f8 (exception_exit) sp =3D 0xddcdad68 fp =3D 0xddcdadc8 r4 =3D 0x00000010 r5 =3D 0x00000000 r6 =3D 0x00000000 r7 =3D 0xec828b10 r8 =3D 0xc5082960 r9 =3D 0xddcdae60 r10 =3D 0x20310f30 exception_exit() at exception_exit pc =3D 0xc04a65f8 lr =3D 0xc04b9534 (undefinedinstruction+0x104= ) sp =3D 0xddcdadbc fp =3D 0xddcdadc8 r0 =3D 0x00000000 r1 =3D 0xddcdaff0 r2 =3D 0x00000000 r3 =3D 0x00000010 r4 =3D 0x00000010 r5 =3D 0x00000000 r6 =3D 0x00000000 r7 =3D 0xec828b10 r8 =3D 0xc5082960 r9 =3D 0xddcdae60 r10 =3D 0x20310f30 r12 =3D 0x2021ffa0 vfp_bounce() at vfp_bounce+0xe0 pc =3D 0xc04ba36c lr =3D 0xc04b9534 (undefinedinstruction+0x104= ) sp =3D 0xddcdadd0 fp =3D 0xddcdae58 r4 =3D 0x00000010 r5 =3D 0xc04ba28c r6 =3D 0xc05c0f70 undefinedinstruction() at undefinedinstruction+0x104 pc =3D 0xc04b9534 lr =3D 0xc04a65f8 (exception_exit) sp =3D 0xddcdae60 fp =3D 0xbfffccc0 r4 =3D 0x20c03600 r5 =3D 0x20e4b000 r6 =3D 0x2112d050 r7 =3D 0x00000000 r8 =3D 0x00000021 r9 =3D 0x210541a0 r10 =3D 0x20c03600 exception_exit() at exception_exit pc =3D 0xc04a65f8 lr =3D 0x2041352c (0x2041352c) sp =3D 0xddcdaeb4 fp =3D 0xbfffccc0 r0 =3D 0xbfffcb90 r1 =3D 0x4278f502 r2 =3D 0xbfffcc10 r3 =3D 0x2042de98 r4 =3D 0x20c03600 r5 =3D 0x20e4b000 r6 =3D 0x2112d050 r7 =3D 0x00000000 r8 =3D 0x00000021 r9 =3D 0x210541a0 r10 =3D 0x20c03600 r12 =3D 0x2021ffa0 Unable to unwind into user mode db> show proc 13666 Process 13666 (ruby19) at 0xc485dc80: state: NORMAL uid: 0 gids: 0, 5 parent: pid 896 at 0xc26db000 ABI: FreeBSD ELF32 arguments: /usr/local/bin/ruby19 threads: 2 100483 S select 0xc485ec64 ruby19 100110 Run CPU 0 ruby19 db> show thread 100483 Thread 100483 at 0xc5082320: proc (pid 13666): 0xc485dc80 name: ruby19 stack: 0xddcdf000-0xddce0fff flags: 0xc pflags: 0 state: INHIBITED: =7BSLEEPING=7D wmesg: select wchan: 0xc485ec64 priority: 145 container lock: sleepq chain (0xc05b8a64) db> show thread 100110 Thread 100110 at 0xc5082960: proc (pid 13666): 0xc485dc80 name: ruby19 stack: 0xddcd9000-0xddcdafff flags: 0x1000004 pflags: 0x20 state: RUNNING (CPU 0) priority: 140 container lock: sched lock (0xc05c2d00) db>=20 From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 22:42:35 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6A164BE for ; Fri, 24 Jan 2014 22:42:35 +0000 (UTC) Received: from smtp.hs-karlsruhe.de (smtp.HS-Karlsruhe.DE [193.196.64.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7AFDA10BD for ; Fri, 24 Jan 2014 22:42:35 +0000 (UTC) Received: from iz-wera01.hs-karlsruhe.de ([193.196.65.46]) by smtp.hs-karlsruhe.de with esmtp (Exim 4.80.1) (envelope-from ) id 1W6pSL-0057aY-Df; Fri, 24 Jan 2014 23:42:33 +0100 X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Ralf Wenk To: freebsd-arm@freebsd.org Subject: Re: RaspberryPi panic with CURRENT r260558 In-reply-to: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Jan 2014 23:42:33 +0100 Message-Id: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 22:42:35 -0000 Oops, what a typo. s/pinic/panic/ Sorry, Ralf From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 04:40:46 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E46BE229; Sat, 25 Jan 2014 04:40:46 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BA1341DAA; Sat, 25 Jan 2014 04:40:46 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 0CB1712FC6; Sat, 25 Jan 2014 04:40:45 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 0CB1712FC6 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 24 Jan 2014 23:40:43 -0500 From: Glen Barber To: freebsd-arm@FreeBSD.org Subject: Rasbperry Pi, what should TARGET_ARCH be? Message-ID: <20140125044043.GT52955@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xPLL5cPndR2UZ7Mw" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 04:40:47 -0000 --xPLL5cPndR2UZ7Mw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I've been working on adding support for embedded systems to the release scripts, which set up a chroot to ensure a clean build environment, then runs Tim's Crochet scripts. For the RPI-B, recent updates to the build scripts work fine for 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to boot. I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image, and was suspicious that the output showed 'arm arm', not 'arm armv6'. Warner had the same impression it should be 'arm armv6'. Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=arm' is set for the RaspberryPi board by default. As a "just in case" experiment, I retried the 10.0-RELEASE code (release/10.0.0/) with TARGET_ARCH=armv6, and sure enough, it works. But, I don't know *why*. Is this a change between head/ and stable/10/ versus releng/10.0/ ? I can handle a differentiation between the branches with regard to this (sort of), but I want to make sure the correct TARGET_ARCH is being set across the different branches, so it can be handled properly in the build scripts, and usable images can be produced. So, what should be used? And where? Thanks for any input, Glen --xPLL5cPndR2UZ7Mw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS40BLAAoJELls3eqvi17Q4ooQAIzRhVxImuQIyS27wxL4q3d0 gPBZYU4V4GpbKa8ZJXXsyHZSjanDPQw0mZ5L8g3edJVeHb/PRk97T5N2/quirar+ vFzY2XNXOPBCIX1EyJuRAGp2VYTT/3+Rzw4MLj2exSgqTzi/HM15QQBBYQJGP+3t Jk4hQcQEyuRlP5GR6QR7OWLj9js6oJFY1rPMLOAkceH6deKArQ6gYUvdquZF0uJQ Sc8tuOQWUKo+wcnS3ysouwY7jZllBOjeBofSV8/Wgaqjc+2aGqKQC/WtxzJm9jGH IrN2CdaqBT/FyM2sOjR54W+Xzka9qNidWqTlvzLBlvFX6CnGSVzCCtZIFVmzM1nf UtM+I/nqAlwwhlaOfMaZ8FIMNid+J6SAd4vD9dlZzuNf9JXWZ8f6ImH7GLqXHEHd dWlsYhgxg0uffHSbIssY+DzxOrYjO8+voxHwf/asonZAlvw1CTkxpB3sSRPecsM0 M/DdMcLuaZbSTgTAjJj/EhoVL+D1W32ttPqQlKGWr3bXbXPJTtA1E33c/FlZz8y6 XXZNYOTZRGYGiFrl+5rdWhg937qrghjws/mtQE4K7dHDfXjMYmou6hUOv0dB6vCB pJm/HNRM6IeHclWnhSc32yfBXPFCPnTQB6ce7sxO85NdjpgM4OsMOf4a4QESewXs fHT96tVM2CFLeCQzNhAn =LiZo -----END PGP SIGNATURE----- --xPLL5cPndR2UZ7Mw-- From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 11:46:08 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9EEF58A0 for ; Sat, 25 Jan 2014 11:46:08 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id 11D3D19AB for ; Sat, 25 Jan 2014 11:46:07 +0000 (UTC) Received: from bender.Home (97e07ba1.skybroadband.com [151.224.123.161]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id A0F9E5DFFE; Sat, 25 Jan 2014 11:39:01 +0000 (UTC) Date: Sat, 25 Jan 2014 11:38:54 +0000 From: Andrew Turner To: Ralf Wenk Subject: Re: RaspberryPi pinic with CURRENT r260558 Message-ID: <20140125113854.083d5f30@bender.Home> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 11:46:08 -0000 On Fri, 24 Jan 2014 14:37:40 +0100 Ralf Wenk wrote: > Hello, > > while updating the ports DB my RPi panics because of an undefined > instruction. /usr/ports ist located on an USB-stick, /usr/local is > located on the SDHC card. > > I do not file a bug report because the problem is not reliable > repeatable. > > The RPi tends to crash while or after doing the following: > - NFS mounting a /usr/ports tree from a i386 Machine > - rsyc(1)-ing that tree to the local copy > - fetching the INDEX-file > and finally calling portversion(1). > > Till today it never panics the first time after booting but rarely > survived the fourth. > This time the UFS journals got damaged preventing multi user boot so > I had to fsck(8) all filesystems manually bypassing the journals. > Can you try updating to at least r261137. There was a bug where backtrace may not work correctly when it passes through exception_exit. This won't fix your problem, but it may help track it down. Andrew From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 17:50:53 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14F38AB3 for ; Sat, 25 Jan 2014 17:50:53 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D295513BB for ; Sat, 25 Jan 2014 17:50:52 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id lx4so4253637iec.27 for ; Sat, 25 Jan 2014 09:50:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=FwIddvpqIjYudh5iDzDGgwyYVQRNn+LL6gYZTf+fcz8=; b=cSmdUTcwaNGs39ZKLiVMX12TyCFnawpNenYE1Vr7Qq6jkQWSA9mb2QhdU71cM+vrEj xDX6AES/xLzmnN0YkJ6HqgtjUXSkL/F1qZWnVk0KkGlDy55B80AomCGze1Mfy0ql0si1 8knSrDdjY0GvVz6tASyKQjzM/1iPMxLL7k36OTBltmIA1S1LNZVQr/ZvR45WFg6Wo124 D2X3J7Hyipq/3TTB/o3PoJm7lgWdaYhUEyrN7bEWn8WHJJFAlTHbYadbxtBjLDlRSwYX oxK4JPxYUU25edCs9LS53g9PteJmCZH/Qa89P13V44zi9YETBEaHD7aBJCvqOIF8hlyl cXnw== X-Gm-Message-State: ALoCoQkFjvzOqstFlkBz/8Wy0w9Xg4n34ktBBFBP9mrywn7riN2JVdBp7aJsBojSUuWIyFHUwb1w X-Received: by 10.50.122.38 with SMTP id lp6mr2054375igb.30.1390672245858; Sat, 25 Jan 2014 09:50:45 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id u1sm23653834ige.1.2014.01.25.09.50.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 09:50:45 -0800 (PST) Sender: Warner Losh Subject: Re: Rasbperry Pi, what should TARGET_ARCH be? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20140125044043.GT52955@glenbarber.us> Date: Sat, 25 Jan 2014 10:50:45 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140125044043.GT52955@glenbarber.us> To: Glen Barber X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 17:50:53 -0000 On Jan 24, 2014, at 9:40 PM, Glen Barber wrote: > Hi, >=20 > I've been working on adding support for embedded systems to the = release > scripts, which set up a chroot to ensure a clean build environment, = then > runs Tim's Crochet scripts. >=20 > For the RPI-B, recent updates to the build scripts work fine for > 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to > boot. If that worked, it worked by accident. > I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image, > and was suspicious that the output showed 'arm arm', not 'arm armv6'. > Warner had the same impression it should be 'arm armv6'. >=20 > Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=3Darm' = is > set for the RaspberryPi board by default. This is incorrect. > As a "just in case" experiment, I retried the 10.0-RELEASE code > (release/10.0.0/) with TARGET_ARCH=3Darmv6, and sure enough, it works. >=20 > But, I don't know *why*. It works because that's the architecture that the RPi runs. > Is this a change between head/ and stable/10/ versus releng/10.0/ ? >=20 > I can handle a differentiation between the branches with regard to = this > (sort of), but I want to make sure the correct TARGET_ARCH is being = set > across the different branches, so it can be handled properly in the > build scripts, and usable images can be produced. The definition should be the same on both branches. You must use = TARGET_ARCH=3Darmv6 on all known branches to produce working code. You = might get lucky and get TARGET_ARCH=3Darm and have it work, but that's = most definitely not a supported configuration. > So, what should be used? And where? For RPi, TARGET_ARCH=3Darmv6 everywhere on all branches >=3D 9. RPi = isn't supported 8 and lower. Warner > Thanks for any input, >=20 > Glen >=20 From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 17:52:36 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5B6DBA0 for ; Sat, 25 Jan 2014 17:52:36 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A678A147A for ; Sat, 25 Jan 2014 17:52:36 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id ar20so4090319iec.24 for ; Sat, 25 Jan 2014 09:52:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=lnrEdO8Xzk3ubyvAeLdxNrVNyxsOEsu/3artXpUq6V0=; b=Rr46mODnPiRi/v5B72WpvCTnVzFtQYDt0oAZN8UlqGlA6zHj+T2C9QESdl54kkzOB1 B11EbI/M+RsR6HB6KgQFVxDN41MAuUkaP/NB/72YwXiiLEtlj2JFCdgciVs/qLpZjmsT JJf0fmihVYQMMpOW87Ya9u9eu8GnHEMye9DCmRfigA8KncmXgrMCuh2vPuwLwE5IFvrM oJice0MDhT7NE2o5XbR9qvHaw8v7VoXHDg6Fx7ms/EcSGaD+xi+/RUKvwIX3PjmG4uVk wYBH789MFYufC+sx3DzMBrqmkg1FHTYEdg1t2mx57jWPNp5q0CB+vMBc20JKpmS5u/ua FGkw== X-Gm-Message-State: ALoCoQm3uqtaVwDxLQyeejZwUbhhA5FFViZjuiLJU6gweryDlqjoWU93z3lRnVCC799oKrkMLSqY X-Received: by 10.50.159.194 with SMTP id xe2mr10333831igb.13.1390672350336; Sat, 25 Jan 2014 09:52:30 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id f15sm22361938igd.3.2014.01.25.09.52.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 09:52:29 -0800 (PST) Sender: Warner Losh Subject: Re: Rasbperry Pi, what should TARGET_ARCH be? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20140125044043.GT52955@glenbarber.us> Date: Sat, 25 Jan 2014 10:52:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140125044043.GT52955@glenbarber.us> To: Glen Barber X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 17:52:37 -0000 On Jan 24, 2014, at 9:40 PM, Glen Barber wrote: > But, I don't know *why*. There were some changes to the tagging of memory after the branch point = that might have had the side effect of making TARGET_ARCH=3Darm work, = but that's sub-optimal for RPi for a variety of reasons... Warner From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 18:13:01 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 699653A2; Sat, 25 Jan 2014 18:13:01 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 430FA162D; Sat, 25 Jan 2014 18:13:00 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s0PICv1B022342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Jan 2014 10:12:57 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s0PICvEk022341; Sat, 25 Jan 2014 10:12:57 -0800 (PST) (envelope-from jmg) Date: Sat, 25 Jan 2014 10:12:57 -0800 From: John-Mark Gurney To: Warner Losh Subject: Re: Rasbperry Pi, what should TARGET_ARCH be? Message-ID: <20140125181256.GE13704@funkthat.com> Mail-Followup-To: Warner Losh , Glen Barber , freebsd-arm@freebsd.org References: <20140125044043.GT52955@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Sat, 25 Jan 2014 10:12:57 -0800 (PST) Cc: Glen Barber , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 18:13:01 -0000 Warner Losh wrote this message on Sat, Jan 25, 2014 at 10:50 -0700: > On Jan 24, 2014, at 9:40 PM, Glen Barber wrote: > > > Hi, > > > > I've been working on adding support for embedded systems to the release > > scripts, which set up a chroot to ensure a clean build environment, then > > runs Tim's Crochet scripts. > > > > For the RPI-B, recent updates to the build scripts work fine for > > 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to > > boot. > > If that worked, it worked by accident. > > > I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image, > > and was suspicious that the output showed 'arm arm', not 'arm armv6'. > > Warner had the same impression it should be 'arm armv6'. > > > > Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=arm' is > > set for the RaspberryPi board by default. > > This is incorrect. > > > As a "just in case" experiment, I retried the 10.0-RELEASE code > > (release/10.0.0/) with TARGET_ARCH=armv6, and sure enough, it works. > > > > But, I don't know *why*. > > It works because that's the architecture that the RPi runs. > > > Is this a change between head/ and stable/10/ versus releng/10.0/ ? > > > > I can handle a differentiation between the branches with regard to this > > (sort of), but I want to make sure the correct TARGET_ARCH is being set > > across the different branches, so it can be handled properly in the > > build scripts, and usable images can be produced. > > The definition should be the same on both branches. You must use TARGET_ARCH=armv6 on all known branches to produce working code. You might get lucky and get TARGET_ARCH=arm and have it work, but that's most definitely not a supported configuration. > > > So, what should be used? And where? > > For RPi, TARGET_ARCH=armv6 everywhere on all branches >= 9. RPi isn't supported 8 and lower. May I propose this patch: https://www.funkthat.com/~jmg/kerncheckarch.patch This uses either TARGET[_ARCH] or uname -[mp] to make sure that the they match w/ the new kernel being built... I believe I did get the -m and -p w/ the correct order, but as I don't have a machine where they different, I can't confirm... This would prevent the issue that Glen experienced... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 18:29:29 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC620AFF for ; Sat, 25 Jan 2014 18:29:29 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8497F1719 for ; Sat, 25 Jan 2014 18:29:29 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id ar20so4263270iec.10 for ; Sat, 25 Jan 2014 10:29:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=xEx+V7lsldatcPQfQWFu9X5fXlJj1q3GoB+Ug/M9NDE=; b=j67m9C6H5ZE9UehKLHhz7j8vkbL0Bz1dKts679S09lfsNjVjRqvuwo5MsOrVRVVOiF 0CiCamrmXAqFiifml6Q9aQsRnUZpIjsU3iiEYubxsPGMR9p6YqfEBmqYWXe6oeEKVi7d 4enr85/y15K/fz9sj1qtbbuEfoUHeXBQMDOE4obDfCQmxYe7grsI+SV/CyGPKC5s2XcD Znn7VGJBSjGLUNH/McrjUPFdWQfl14VtQdijL7O1xIzbrirSztDHYOSZBiycg9UTbR+U Og7806Wc4zZY0R6fUheidokBn1WraRbX7w4nt+74h5OLC1NF3PBfmf3JWrg0Qu2j+9kx Hh5g== X-Gm-Message-State: ALoCoQmqj227nCKI10QCkd+AW/S8pTu1GXKOc6HxDiuqDiOGqNxPV4ohTN91GXPZOUj97OIeiK+k X-Received: by 10.42.121.147 with SMTP id j19mr15735349icr.13.1390674167797; Sat, 25 Jan 2014 10:22:47 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id kz4sm8118940igb.4.2014.01.25.10.22.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 10:22:47 -0800 (PST) Sender: Warner Losh Subject: Re: Rasbperry Pi, what should TARGET_ARCH be? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20140125181256.GE13704@funkthat.com> Date: Sat, 25 Jan 2014 11:22:47 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140125044043.GT52955@glenbarber.us> <20140125181256.GE13704@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1085) Cc: Glen Barber , freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 18:29:29 -0000 On Jan 25, 2014, at 11:12 AM, John-Mark Gurney wrote: > Warner Losh wrote this message on Sat, Jan 25, 2014 at 10:50 -0700: >> On Jan 24, 2014, at 9:40 PM, Glen Barber wrote: >>=20 >>> Hi, >>>=20 >>> I've been working on adding support for embedded systems to the = release >>> scripts, which set up a chroot to ensure a clean build environment, = then >>> runs Tim's Crochet scripts. >>>=20 >>> For the RPI-B, recent updates to the build scripts work fine for >>> 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to >>> boot. >>=20 >> If that worked, it worked by accident. >>=20 >>> I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT = image, >>> and was suspicious that the output showed 'arm arm', not 'arm = armv6'. >>> Warner had the same impression it should be 'arm armv6'. >>>=20 >>> Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=3Darm' = is >>> set for the RaspberryPi board by default. >>=20 >> This is incorrect. >>=20 >>> As a "just in case" experiment, I retried the 10.0-RELEASE code >>> (release/10.0.0/) with TARGET_ARCH=3Darmv6, and sure enough, it = works. >>>=20 >>> But, I don't know *why*. >>=20 >> It works because that's the architecture that the RPi runs. >>=20 >>> Is this a change between head/ and stable/10/ versus releng/10.0/ ? >>>=20 >>> I can handle a differentiation between the branches with regard to = this >>> (sort of), but I want to make sure the correct TARGET_ARCH is being = set >>> across the different branches, so it can be handled properly in the >>> build scripts, and usable images can be produced. >>=20 >> The definition should be the same on both branches. You must use = TARGET_ARCH=3Darmv6 on all known branches to produce working code. You = might get lucky and get TARGET_ARCH=3Darm and have it work, but that's = most definitely not a supported configuration. >>=20 >>> So, what should be used? And where? >>=20 >> For RPi, TARGET_ARCH=3Darmv6 everywhere on all branches >=3D 9. RPi = isn't supported 8 and lower. >=20 > May I propose this patch: > https://www.funkthat.com/~jmg/kerncheckarch.patch >=20 > This uses either TARGET[_ARCH] or uname -[mp] to make sure that the > they match w/ the new kernel being built... I believe I did get the > -m and -p w/ the correct order, but as I don't have a machine where > they different, I can't confirm... >=20 > This would prevent the issue that Glen experienced... I hate uname checks. They are almost always wrong. I've been burned too = many times in the past by them, and strongly oppose them on general = principals.=20 TARGET won't necessarily be defined when building the kernel, so this = patch can't possibly do what you want it to do. Any place outside of = Makefile and Makefile.inc1 that checks for it is generally wrong (with = the exception of some of the cross tools that support being built = standalone outside of makeworld). I believe that at most it will detect = when you are cross building and fail. Better to check the arch line in the kernel config file matches the = MARCHINE_ARCH. This can likely be done with a tiny bit of config magic = in one of the generated files so the build will check the right = preprocessor defines. There's some magic to do something similar for the = universe builds. Warner= From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 19:24:41 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 68632129 for ; Sat, 25 Jan 2014 19:24:41 +0000 (UTC) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 384E21B4C for ; Sat, 25 Jan 2014 19:24:40 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id rq2so4428318pbb.17 for ; Sat, 25 Jan 2014 11:24:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=JwHLaGyfcAPB44rm/dqkdiY523+Xg4ofOaMpv7qTUJs=; b=Tib7t/DKQdAKoCiX7Z0oNZZFPhaHtLCx+MV6IPxbCzjAZm4CAD8zrFbJAH8rqopSF4 GAczt6oaYlfxxfCVr0xAWkDomFVZXzrvlK2fB3Zb78NowbFDL/1KfbqNCY+FSMimswRI LAxlce3X42XEi5UQAIqbs4EiuqU7nUGbzWbvrPNFWk6E5eYJutfr/yFlQavS7vP9tFoK hpyqamEb2gE6hMwHFhgJFF/6KjIx90577waUuzDl1HRpLcy/IRe0PdrK8Eldv65qaG+3 ogGdG0Bc9aDrWZde6gcunsr0G+7yeCoVtcavo0LQBxG+vmmb1mcIgY4t6UQx1/Q9X3y5 jCtg== X-Gm-Message-State: ALoCoQlkNe78s8htycfbO/JzT3SVrfMl059c5KOjQgp7awSjIAfYvs12B7Y5QETtd1sqol4zsg+k X-Received: by 10.68.219.202 with SMTP id pq10mr21402463pbc.23.1390677874691; Sat, 25 Jan 2014 11:24:34 -0800 (PST) Received: from [192.168.2.123] (99-74-169-43.lightspeed.sntcca.sbcglobal.net. [99.74.169.43]) by mx.google.com with ESMTPSA id iq10sm15627680pbc.14.2014.01.25.11.24.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 11:24:34 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: my private build RaspberryPi Image is available From: Tim Kientzle In-Reply-To: <20140123.085609.53072279.shigeru@os-hackers.jp> Date: Sat, 25 Jan 2014 11:24:31 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> To: shigeru@os-hackers.jp X-Mailer: Apple Mail (2.1827) Cc: freebsd-arm ml X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 19:24:41 -0000 On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: > Unfortunately, there are some ports which I can't compile > on -current FreeBSD/RaspberryPi. > These ports requires GCC, but gcc ports in -current does not support > arm/armv6. Why not? Any suggestion how to fix that? Tim From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 19:40:16 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02DDD9BA for ; Sat, 25 Jan 2014 19:40:16 +0000 (UTC) Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C18951D73 for ; Sat, 25 Jan 2014 19:40:15 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MZZ009002LJZ500@smtpauth2.wiscmail.wisc.edu> for freebsd-arm@freebsd.org; Sat, 25 Jan 2014 13:40:13 -0600 (CST) X-Spam-PmxInfo: Server=avs-2, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.1.25.192715, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from comporellon.tachypleus.net (adsl-76-208-68-77.dsl.mdsnwi.sbcglobal.net [76.208.68.77]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MZZ00J1S2N0A510@smtpauth2.wiscmail.wisc.edu>; Sat, 25 Jan 2014 13:40:13 -0600 (CST) Message-id: <52E4131C.7080904@freebsd.org> Date: Sat, 25 Jan 2014 13:40:12 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: Tim Kientzle , shigeru@os-hackers.jp Subject: Re: my private build RaspberryPi Image is available References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> In-reply-to: Cc: freebsd-arm ml X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 19:40:16 -0000 On 01/25/14 13:24, Tim Kientzle wrote: > On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: > >> Unfortunately, there are some ports which I can't compile >> on -current FreeBSD/RaspberryPi. >> These ports requires GCC, but gcc ports in -current does not support >> arm/armv6. > Why not? Any suggestion how to fix that? > > We have a couple of platforms like this. Powerpc64 is not supported without GCC 4.8, for example. That one might also support armv6. If so, maybe it's worth changing the default version? -Nathan From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:04:17 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECE7992A for ; Sat, 25 Jan 2014 20:04:17 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B292F1146 for ; Sat, 25 Jan 2014 20:04:17 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id tp5so4159396ieb.7 for ; Sat, 25 Jan 2014 12:04:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=zJQvU5zM43Fif7Y4woJSFkPmzS/XqCO7fM+xx+zoUAI=; b=QsPiYozeVgxl3K1vnB6LGbA+IE0YvTzSobXR5V+K9zD8Ri7Lqw8wYe5y3z+L9FIOGQ ypGA365twLa9klK2QG3jAV7TNheVOyv1ULSoGoRYO5HAIsZlbZPQoa20YirxtGTll+od Mt4nCsRLcKrVrnv1C3fMZEBJ/NcZgz2F9wZnhhAruzG+eJ2wOgLKiY5D8II8/X2CTXmw nA8i+DpOwQdVwkm5zBIxYSs3+1ouDi56NifFBZGc5+EWi5VjKCRVEp7R8Hd16JZ7w1N7 FbJvqziDKvoxfvjRTX0IKN/ASIZZ4kOikPMv64fMA5qKplHTup7puRJ6gdU275WJhV9u /0Vg== X-Gm-Message-State: ALoCoQlB9q+j30Jv8reyWqrKFU9btQuRfl/L7tCp+eqdOQenx5O9mj0+uwq+47glaQhYHIAZqvAJ X-Received: by 10.50.225.67 with SMTP id ri3mr10818359igc.16.1390680251653; Sat, 25 Jan 2014 12:04:11 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id h6sm24732884igy.8.2014.01.25.12.04.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 12:04:11 -0800 (PST) Sender: Warner Losh Subject: Re: my private build RaspberryPi Image is available Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Sat, 25 Jan 2014 13:04:10 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <35BA5BC1-069E-49E9-8ECE-7BDC5B57EE61@bsdimp.com> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> To: Tim Kientzle X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm ml X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 20:04:18 -0000 On Jan 25, 2014, at 12:24 PM, Tim Kientzle wrote: >=20 > On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: >=20 >> Unfortunately, there are some ports which I can't compile >> on -current FreeBSD/RaspberryPi. >> These ports requires GCC, but gcc ports in -current does not support >> arm/armv6. >=20 > Why not? Any suggestion how to fix that? I have some forward ports of the FreeBSD patches to gcc that matter for = stuff like this that might help. Warner From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:08:16 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64A57995 for ; Sat, 25 Jan 2014 20:08:16 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 185E5115F for ; Sat, 25 Jan 2014 20:08:15 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0PJuGrg080657 for ; Sat, 25 Jan 2014 14:56:21 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52E416E0.7060204@m5p.com> Date: Sat, 25 Jan 2014 14:56:16 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: my private build RaspberryPi Image is available References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sat, 25 Jan 2014 14:56:22 -0500 (EST) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 20:08:16 -0000 On 01/25/14 14:24, Tim Kientzle wrote: > > On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: > >> Unfortunately, there are some ports which I can't compile >> on -current FreeBSD/RaspberryPi. >> These ports requires GCC, but gcc ports in -current does not support >> arm/armv6. > > Why not? Any suggestion how to fix that? > > Tim > [...] For me, specifying WITH_GCC="yes" in src.conf at the time I built the world gave me a gcc that works for at least the ports I needed. (And any port that specifies USES_GCC=any). -- George From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:14:00 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1EFED2C for ; Sat, 25 Jan 2014 20:14:00 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 812AA11E5 for ; Sat, 25 Jan 2014 20:14:00 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so4537430pab.10 for ; Sat, 25 Jan 2014 12:13:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=owC8TWmlkYHDdGDiAZAwKoLhAHKSdKDzw1yFKBXNbAI=; b=D0r/KC8q7reNvFFzzve6HF0nbzR3mdRjutMbSkd9zmnXLwCSzuHZF0i3MZ0g7FqOam J42DeuR97OadJg5jo+H5mJe0jS9x482hUuINsfKboBpJFNmUsWobdU6tud3jHmiS5rHe LUPtARO7IKPRj9k339MIHpOQKYKRKmxa2/Q0dDgFY21tV5iP+PcbfHikcmBaoP2DJwCj V9m1Qu+zEgsDoVgkBaqziGuOWCJzX+mNoYrWgx4LZyDMbZkEHLnPVOGS5QI4GAzmHXGB Z0ifZw7NJJ7C9Bhy2AOR575o3L4yJDw2JCvM0TTP3wzSBefpfjAaLeDYJjEAAzz7Ih/7 vXJA== X-Gm-Message-State: ALoCoQlEk4qiZOj1NwKgD3dB6p+tBhpWQMV8CelUP2M0AHZQyxIqOJfnHg/i+a12yb+jkiIq3wpX X-Received: by 10.68.172.37 with SMTP id az5mr21378815pbc.139.1390680839827; Sat, 25 Jan 2014 12:13:59 -0800 (PST) Received: from [192.168.2.123] (99-74-169-43.lightspeed.sntcca.sbcglobal.net. [99.74.169.43]) by mx.google.com with ESMTPSA id sq7sm15869213pbc.19.2014.01.25.12.13.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 12:13:59 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: my private build RaspberryPi Image is available From: Tim Kientzle In-Reply-To: <52E416E0.7060204@m5p.com> Date: Sat, 25 Jan 2014 12:14:06 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> <52E416E0.7060204@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.1827) Cc: freebsd-arm ml X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 20:14:00 -0000 On Jan 25, 2014, at 11:56 AM, George Mitchell = wrote: > On 01/25/14 14:24, Tim Kientzle wrote: >>=20 >> On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: >>=20 >>> Unfortunately, there are some ports which I can't compile >>> on -current FreeBSD/RaspberryPi. >>> These ports requires GCC, but gcc ports in -current does not support >>> arm/armv6. >>=20 >> Why not? Any suggestion how to fix that? >>=20 >> Tim >> [...] >=20 > For me, specifying WITH_GCC=3D"yes" in src.conf at the time I built > the world gave me a gcc that works for at least the ports I needed. > (And any port that specifies USES_GCC=3Dany). -- George That works today, but isn't a particularly good long-term answer: * Ports that demand GCC will increasingly expect something newer than = GCC 4.2. * Someday (FreeBSD 11? FreeBSD 12?) we will no longer have GCC = in-tree. So it's certainly worth exploring how to build ports that require GCC without using the in-tree GCC. Tim From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:40:46 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3BF6D98 for ; Sat, 25 Jan 2014 20:40:46 +0000 (UTC) Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 98CE31482 for ; Sat, 25 Jan 2014 20:40:46 +0000 (UTC) Received: by mail-ig0-f171.google.com with SMTP id uy17so5577448igb.4 for ; Sat, 25 Jan 2014 12:40:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=/nbNhgJxgO+N4BTa+KUyKqEp7i0u6gJj52m4RmcAAJ8=; b=mSBYJlyZbPodnbTB+Ofv3qqKfAuu7FdL3fmRsxKYW2T8SCiWFLmqjzcsT/zsADZ1x+ FCaWEsyq3baWpqBl8crmiljvE5wqD1IhHtV2yBKeqsrT1z8FhkgzdKEvg/ZDCek86BIQ PkiETIIkm9sTuVNCYTHutE83N2gcGeJMWJ0BBLMPvMJmWcQ3lkTg9uE3GEaAkzsfYNWe YAmmAzQwx/hFg9dQhq76J2y8eygTMD//W0ijufkah7GGJonCHu3cVgf1FPwn75m8wJgc Cd+DX74WECEtvUg9MaDcbTuFL3vbojQu/01TT1sPN/eGcaf1/6yFlZ5iu8nItozfMZ6W uknw== X-Gm-Message-State: ALoCoQlcWpAX3+H+B6huImpcZBrX/NxPMfQ6yVh3D0ssMNV7OF8BqV7O9R6FGkbElxTEk0VHUvja X-Received: by 10.50.27.103 with SMTP id s7mr10586192igg.33.1390682440303; Sat, 25 Jan 2014 12:40:40 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id f2sm25043790igt.6.2014.01.25.12.40.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 12:40:39 -0800 (PST) Sender: Warner Losh Subject: Re: my private build RaspberryPi Image is available Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> Date: Sat, 25 Jan 2014 13:40:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> <52E416E0.7060204@m5p.com> <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm ml X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 20:40:46 -0000 On Jan 25, 2014, at 1:14 PM, Tim Kientzle wrote: > On Jan 25, 2014, at 11:56 AM, George Mitchell = wrote: >=20 >> On 01/25/14 14:24, Tim Kientzle wrote: >>>=20 >>> On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: >>>=20 >>>> Unfortunately, there are some ports which I can't compile >>>> on -current FreeBSD/RaspberryPi. >>>> These ports requires GCC, but gcc ports in -current does not = support >>>> arm/armv6. >>>=20 >>> Why not? Any suggestion how to fix that? >>>=20 >>> Tim >>> [...] >>=20 >> For me, specifying WITH_GCC=3D"yes" in src.conf at the time I built >> the world gave me a gcc that works for at least the ports I needed. >> (And any port that specifies USES_GCC=3Dany). -- George >=20 > That works today, but isn't a particularly good long-term answer: > * Ports that demand GCC will increasingly expect something newer than = GCC 4.2. > * Someday (FreeBSD 11? FreeBSD 12?) we will no longer have GCC = in-tree. >=20 > So it's certainly worth exploring how to build ports that require GCC > without using the in-tree GCC. Step 1 is getting my patches into the ports tree so that we can = configure for freebsd/arm and freebsd/armv6 (among others). Let me go = looking for them... Warner From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 22:19:12 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 151504CE; Sat, 25 Jan 2014 22:19:12 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C4F581D1E; Sat, 25 Jan 2014 22:19:11 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 4ECE413792; Sat, 25 Jan 2014 22:19:10 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 4ECE413792 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Sat, 25 Jan 2014 17:19:08 -0500 From: Glen Barber To: Warner Losh Subject: Re: Rasbperry Pi, what should TARGET_ARCH be? Message-ID: <20140125221908.GX52955@glenbarber.us> References: <20140125044043.GT52955@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Y48FV0AvvvAm5Iyr" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 22:19:12 -0000 --Y48FV0AvvvAm5Iyr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 25, 2014 at 10:50:45AM -0700, Warner Losh wrote: >=20 > On Jan 24, 2014, at 9:40 PM, Glen Barber wrote: >=20 > > Hi, > >=20 > > I've been working on adding support for embedded systems to the release > > scripts, which set up a chroot to ensure a clean build environment, then > > runs Tim's Crochet scripts. > >=20 > > For the RPI-B, recent updates to the build scripts work fine for > > 11.0-CURRENT and 10.0-STABLE. However, 10.0-RELEASE images fail to > > boot. >=20 > If that worked, it worked by accident. >=20 > > I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image, > > and was suspicious that the output showed 'arm arm', not 'arm armv6'. > > Warner had the same impression it should be 'arm armv6'. > >=20 > > Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=3Darm' is > > set for the RaspberryPi board by default. >=20 > This is incorrect. >=20 > > As a "just in case" experiment, I retried the 10.0-RELEASE code > > (release/10.0.0/) with TARGET_ARCH=3Darmv6, and sure enough, it works. > >=20 > > But, I don't know *why*. >=20 > It works because that's the architecture that the RPi runs. >=20 > > Is this a change between head/ and stable/10/ versus releng/10.0/ ? > >=20 > > I can handle a differentiation between the branches with regard to this > > (sort of), but I want to make sure the correct TARGET_ARCH is being set > > across the different branches, so it can be handled properly in the > > build scripts, and usable images can be produced. >=20 > The definition should be the same on both branches. You must use TARGET_A= RCH=3Darmv6 on all known branches to produce working code. You might get l= ucky and get TARGET_ARCH=3Darm and have it work, but that's most definitely= not a supported configuration. >=20 > > So, what should be used? And where? >=20 > For RPi, TARGET_ARCH=3Darmv6 everywhere on all branches >=3D 9. RPi isn't= supported 8 and lower. >=20 Thanks Warner. I appreciate it. Glen --Y48FV0AvvvAm5Iyr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS5DhcAAoJELls3eqvi17QK9YP/0eDQiSiK+8P8kDqxWb5mtl9 FG0LSyD8YHeQVEdmXAfUeWZ0BecgMyliiYU5ObLm2Lb+sHptjYsH5O0sELFq5fbI 61FCLPyQrhZBI243zlOS0rOntYVAoc6HxzFOThX8PLx7+vNtFgv8gBXUqJ+QHixc 2n08/dRPbIEwCtiObVbhBxAY1R8p/3SonWIMxdEjMejQMIrNwANDldyNNlOXZxVp Tzo/rM+arxQCahf6kJUcxZ3fX9s47nWOtWUOdSRGpKnVVaL8pyrHYymZIUw+TTuJ rvqMjDY0MYFagCC52agx4wOnnm3DMfphrk2p90B7zB6lDecboZyl7JunRymhF+Da iZ9eP7CeX4sQGdgjL3M1npDAR7Tasp8AtUP1mu170hrLl9MjuF4kot/6jy8rvlSk 2dGedKZktlo/jXRJu609v4OPO8NBQGJa1RZQtQfmNAFahgi6r3U9muaPA0IcFqvE XmXyWsTgMa6n6HVJULDZWnwWcYcWWVVGmXMcumFZeD5OC+CA1FRzPZVYH1Ol6zaj 5gCTyhHpDzxoWJMrFvth8Zt+5inFvFJoflfkP8JLgX4qEARYnjFdaLWJUW9tuika I9DPSPPJVe5/67vNeeI6Yz5RwU3YL0jddeBuD4NHJD8yh8gaJGtxGlTcrlXh+MeB f9hY8TxpMW9EG3FIveie =eLlb -----END PGP SIGNATURE----- --Y48FV0AvvvAm5Iyr--