From owner-freebsd-arm@freebsd.org Sun Jul 2 02:25:11 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E02C6D99B94 for ; Sun, 2 Jul 2017 02:25:11 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id ACCD27B445 for ; Sun, 2 Jul 2017 02:25:11 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v621tIbQ014873 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Jul 2017 18:55:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v621tI0X014872; Sat, 1 Jul 2017 18:55:18 -0700 (PDT) (envelope-from fbsd) Date: Sat, 1 Jul 2017 18:55:17 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 Message-ID: <20170702015517.GA14839@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 02:25:12 -0000 After a source upgrade to 12.0-CURRENT #6 r320526 my RPI2 reported pid 514 (ntpdate), uid 0: exited on signal 11 (core dumped) pid 554 (testparm), uid 0: exited on signal 11 (core dumped) pid 555 (testparm), uid 0: exited on signal 11 (core dumped) pid 556 (testparm), uid 0: exited on signal 11 (core dumped) pid 557 (testparm), uid 0: exited on signal 11 (core dumped) pid 630 (sshd), uid 0: exited on signal 11 pid 1751 (svnlite), uid 0: exited on signal 11 (core dumped) The serial console still works and allows logins, but otherwise it seems I'm locked out. Is there a way to unshoot my foot? Thanks for reading, bob prohaska From owner-freebsd-arm@freebsd.org Sun Jul 2 04:31:57 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5785D9CF3D for ; Sun, 2 Jul 2017 04:31:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 470177F8CC for ; Sun, 2 Jul 2017 04:31:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29868 invoked from network); 2 Jul 2017 04:33:25 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 2 Jul 2017 04:33:25 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Sun, 02 Jul 2017 00:31:54 -0400 (EDT) Received: (qmail 23751 invoked from network); 2 Jul 2017 04:31:54 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Jul 2017 04:31:54 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id B899DEC894C; Sat, 1 Jul 2017 21:31:53 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 From: Mark Millard In-Reply-To: <20170702015517.GA14839@www.zefox.net> Date: Sat, 1 Jul 2017 21:31:53 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <20170702015517.GA14839@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 04:31:57 -0000 On 2017-Jul-1, at 6:55 PM, bob prohaska wrote: > After a source upgrade to 12.0-CURRENT #6 r320526 my RPI2 reported > > pid 514 (ntpdate), uid 0: exited on signal 11 (core dumped) > pid 554 (testparm), uid 0: exited on signal 11 (core dumped) > pid 555 (testparm), uid 0: exited on signal 11 (core dumped) > pid 556 (testparm), uid 0: exited on signal 11 (core dumped) > pid 557 (testparm), uid 0: exited on signal 11 (core dumped) > pid 630 (sshd), uid 0: exited on signal 11 > pid 1751 (svnlite), uid 0: exited on signal 11 (core dumped) > > The serial console still works and allows logins, but otherwise > it seems I'm locked out. > > Is there a way to unshoot my foot? I'm building and testing but it may be that the following powerpc64 example is the same basic issue (ntpd and sshd signal 11's being examples): https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066469.html https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066470.html https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066471.html The last of those has a fix suggested by Konstantin Belousov. It is associated with his -r320509 changes for: > In the stdio cleanup push and pop wrappers, always call libc stubs for > __pthread_cleanup_push/pop_imp instead of symbols also exported from > libthr. > > This prevents calls into libthr if libthr is not yet initialized. The > situation occurs e.g. when an LD_PRELOADed object is not linked > against libthr, but the main binary is. But it turns out that -r320509 was incomplete. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Jul 2 20:36:50 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D769DAC864 for ; Sun, 2 Jul 2017 20:36:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6677875B46 for ; Sun, 2 Jul 2017 20:36:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v62KaqgK017712 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 2 Jul 2017 13:36:53 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v62KaqUX017711; Sun, 2 Jul 2017 13:36:52 -0700 (PDT) (envelope-from fbsd) Date: Sun, 2 Jul 2017 13:36:51 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 Message-ID: <20170702203651.GA17014@www.zefox.net> References: <20170702015517.GA14839@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 20:36:50 -0000 > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066471.html > > The last of those has a fix suggested by Konstantin Belousov. > I'm tempted to try the fix but the diff does not look compatible with a self hosted system. Will removing the a/ and b/ make the paths digestible to patch? bob From owner-freebsd-arm@freebsd.org Sun Jul 2 21:29:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B80C0DADA29 for ; Sun, 2 Jul 2017 21:29:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8FF477714 for ; Sun, 2 Jul 2017 21:28:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28243 invoked from network); 2 Jul 2017 21:28:57 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 2 Jul 2017 21:28:57 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Sun, 02 Jul 2017 17:28:57 -0400 (EDT) Received: (qmail 12652 invoked from network); 2 Jul 2017 21:28:56 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Jul 2017 21:28:56 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 45738EC7C08; Sun, 2 Jul 2017 14:28:56 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 From: Mark Millard In-Reply-To: <20170702203651.GA17014@www.zefox.net> Date: Sun, 2 Jul 2017 14:28:55 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> References: <20170702015517.GA14839@www.zefox.net> <20170702203651.GA17014@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 21:29:00 -0000 On 2017-Jul-2, at 1:36 PM, bob prohaska wrote: >> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066471.html >> >> The last of those has a fix suggested by Konstantin Belousov. >> > > I'm tempted to try the fix but the diff does not look compatible with > a self hosted system. Will removing the a/ and b/ make the paths > digestible to patch? A problem may be that far too many programs fail for the original code: lots of programs are broken. It is not clear that buildworld is viable self-hosted for builds of -r320509 through -r320561 for head (inclusive of both ends). Head has had the code checked in since then: -r320570 has the fix. So you can get the source from there. Or patch has a -p option for stripping a prefix from the paths it uses (by a count of /'s removed by deleting the prefix): See man patch. Or copy/paste the + text lines and delete the +'s in the first column --and delete the original lines that are shown as - lines. The patch is small so this should be easy to to reliably. I happen to cross build and to be able to boot from an alternate FreeBSD with the disk in question available to mount from there. So I did not have to deal with fully self hosted. So I'm not sure what happens if one tries to buildworld from the messed up context. I'd not be surprised at a program-crash failure. FYI: there is a separate issue noted in bugzilla 220404 that prevents a production style kernel build from completing a normal boot sequence for TARGET_ARCH=powerpc: fatal kernel trap. The basic type of issue is memory aliasing in a union in struct socket being mishandled. The detailed mishandling results likely vary from TARGET_ARCH to TARGET_ARCH so appearing to work is an accident but does happen. I've been able to boot and use a debug kernel build on TARGET_ARCH=powerpc but again it is likely an accident. (The machine is actually also 64-bit capable but I use 32-bit FreeBSD on it as well.) I've been able to "boot -s" (single user) TARGET_ARCH=powerpc for a production kernel but have had other problems in that context that I've not described anywhere yet. As stands I'm not sure that what I could say would be useful to anyone: more investigation needed. I've been lucky in that TARGET_ARCH=powerpc64 accidentally seems to work for this issue, even with a production kernel. Also lucky that amd64 works by accident so that I have that as my primary cross-build environment still. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Jul 2 21:34:40 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73C53DADBE9 for ; Sun, 2 Jul 2017 21:34:40 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 296A477A3A for ; Sun, 2 Jul 2017 21:34:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7680 invoked from network); 2 Jul 2017 21:36:09 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 2 Jul 2017 21:36:09 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Sun, 02 Jul 2017 17:34:38 -0400 (EDT) Received: (qmail 16218 invoked from network); 2 Jul 2017 21:34:37 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Jul 2017 21:34:37 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 55020EC7C08; Sun, 2 Jul 2017 14:34:37 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 From: Mark Millard In-Reply-To: <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> Date: Sun, 2 Jul 2017 14:34:36 -0700 Cc: freebsd-arm Content-Transfer-Encoding: 7bit Message-Id: <38241DC9-8A8D-4B90-A678-5A4F7511029B@dsl-only.net> References: <20170702015517.GA14839@www.zefox.net> <20170702203651.GA17014@www.zefox.net> <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 21:34:40 -0000 [Fixing some poor wording.] On 2017-Jul-2, at 2:28 PM, Mark Millard wrote: > On 2017-Jul-2, at 1:36 PM, bob prohaska wrote: > >>> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066471.html >>> >>> The last of those has a fix suggested by Konstantin Belousov. >>> >> >> I'm tempted to try the fix but the diff does not look compatible with >> a self hosted system. Will removing the a/ and b/ make the paths >> digestible to patch? > > A problem may be that far too many programs fail > for the original code: lots of programs are > broken. It is not clear that buildworld is > viable self-hosted for builds of -r320509 > through -r320561 for head (inclusive of both > ends). "builds *started from* -r320509 through -r320561" would have been a better wording for the purpose: The problem is that once one is running one of those things may be very messed up in that lots of programs may fail. > Head has had the code checked in since then: > -r320570 has the fix. So you can get the > source from there. > > Or patch has a -p option for stripping a prefix > from the paths it uses (by a count of /'s removed > by deleting the prefix): See man patch. > > Or copy/paste the + text lines and delete the +'s > in the first column --and delete the original lines > that are shown as - lines. The patch is small so > this should be easy to to reliably. > > > > I happen to cross build and to be able to boot > from an alternate FreeBSD with the disk in > question available to mount from there. So I > did not have to deal with fully self hosted. > > So I'm not sure what happens if one tries to > buildworld from the messed up context. I'd > not be surprised at a program-crash failure. > > > > FYI: there is a separate issue noted in > bugzilla 220404 that prevents a production > style kernel build from completing a normal > boot sequence for TARGET_ARCH=powerpc: fatal > kernel trap. The basic type of issue is > memory aliasing in a union in struct socket > being mishandled. The detailed mishandling > results likely vary from TARGET_ARCH to > TARGET_ARCH so appearing to work is an > accident but does happen. > > I've been able to boot and use a debug kernel > build on TARGET_ARCH=powerpc but again it is > likely an accident. (The machine is actually > also 64-bit capable but I use 32-bit FreeBSD > on it as well.) > > I've been able to "boot -s" (single user) > TARGET_ARCH=powerpc for a production kernel > but have had other problems in that context > that I've not described anywhere yet. As stands > I'm not sure that what I could say would be > useful to anyone: more investigation needed. > > I've been lucky in that TARGET_ARCH=powerpc64 > accidentally seems to work for this issue, > even with a production kernel. > > Also lucky that amd64 works by accident so > that I have that as my primary cross-build environment still. === Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Sun Jul 2 23:43:50 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30BB39B1DC9 for ; Sun, 2 Jul 2017 23:43:50 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B8E47AA2F for ; Sun, 2 Jul 2017 23:43:49 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v62Nhqq6018130 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 2 Jul 2017 16:43:53 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v62Nhqsa018129; Sun, 2 Jul 2017 16:43:52 -0700 (PDT) (envelope-from fbsd) Date: Sun, 2 Jul 2017 16:43:51 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 Message-ID: <20170702234351.GB17014@www.zefox.net> References: <20170702015517.GA14839@www.zefox.net> <20170702203651.GA17014@www.zefox.net> <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> <38241DC9-8A8D-4B90-A678-5A4F7511029B@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <38241DC9-8A8D-4B90-A678-5A4F7511029B@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 23:43:50 -0000 On Sun, Jul 02, 2017 at 02:34:36PM -0700, Mark Millard wrote: > > > > Or patch has a -p option for stripping a prefix > > from the paths it uses (by a count of /'s removed > > by deleting the prefix): See man patch. > > Patch -p1 seemed to apply the diff successfully, but as you warned other parts of userland are too broken to function. Somewhat to my surprise, using single user mode it was possible to run make in /usr/src/lib/libc, but make install failed with install -C -o root -g wheel -m 444 libc.a /usr/lib/ install -C -o root -g wheel -m 444 libc_p.a /usr/lib/ install -s -o root -g wheel -m 444 -fschg -S libc.so.7 /lib/ pid 377 (strip), uid 0: exited on signal 11 (core dumped) install: strip command strip failed on /lib/INS@bbHX *** Error code 70 I believe strip is to some extent optional, is it possible (and would it help) to somehow turn off the strip function? Thank you very much! bob prohaska From owner-freebsd-arm@freebsd.org Sun Jul 2 23:57:22 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CFEC9B2365 for ; Sun, 2 Jul 2017 23:57:22 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-15.reflexion.net [208.70.210.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 11B227AE1E for ; Sun, 2 Jul 2017 23:57:21 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 17001 invoked from network); 2 Jul 2017 23:58:51 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 Jul 2017 23:58:51 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Sun, 02 Jul 2017 19:57:20 -0400 (EDT) Received: (qmail 10338 invoked from network); 2 Jul 2017 23:57:19 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Jul 2017 23:57:19 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 3C824EC8171; Sun, 2 Jul 2017 16:57:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 From: Mark Millard In-Reply-To: <20170702234351.GB17014@www.zefox.net> Date: Sun, 2 Jul 2017 16:57:18 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <76AA57AF-8D5E-461E-A756-F71A9F84B1EE@dsl-only.net> References: <20170702015517.GA14839@www.zefox.net> <20170702203651.GA17014@www.zefox.net> <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> <38241DC9-8A8D-4B90-A678-5A4F7511029B@dsl-only.net> <20170702234351.GB17014@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 23:57:22 -0000 On 2017-Jul-2, at 4:43 PM, bob prohaska wrote: > On Sun, Jul 02, 2017 at 02:34:36PM -0700, Mark Millard wrote: >>>=20 >>> Or patch has a -p option for stripping a prefix >>> from the paths it uses (by a count of /'s removed >>> by deleting the prefix): See man patch. >>>=20 >=20 > Patch -p1 seemed to apply the diff successfully, but as you > warned other parts of userland are too broken to function. >=20 > Somewhat to my surprise, using single user mode it was possible > to run make in /usr/src/lib/libc, but make install failed with > install -C -o root -g wheel -m 444 libc.a /usr/lib/ > install -C -o root -g wheel -m 444 libc_p.a /usr/lib/ > install -s -o root -g wheel -m 444 -fschg -S libc.so.7 /lib/ > pid 377 (strip), uid 0: exited on signal 11 (core dumped) > install: strip command strip failed on /lib/INS@bbHX > *** Error code 70 >=20 > I believe strip is to some extent optional, is it possible > (and would it help) to somehow turn off the strip function? man install reports: -s install exec's the command strip(1) to strip binaries so = that install can be portable over a large number of systems and = binary types. See below for how install can be instructed to use another program to strip binaries. It also reports in the ENVIRONMENT section: If the DONTSTRIP environment variable is present, install will = ignore any specification of the -s option. This is mainly for use in = debugging the FreeBSD Ports Collection. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-arm@freebsd.org Mon Jul 3 01:00:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00B839C7479 for ; Mon, 3 Jul 2017 01:00:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE3197C1C0 for ; Mon, 3 Jul 2017 00:59:59 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id v63100sT018329 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 2 Jul 2017 18:00:01 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id v63100RQ018328; Sun, 2 Jul 2017 18:00:00 -0700 (PDT) (envelope-from fbsd) Date: Sun, 2 Jul 2017 18:00:00 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm Subject: Re: Signal 11 on RPI2 running 12.0-CURRENT #6 r320526 Message-ID: <20170703010000.GC17014@www.zefox.net> References: <20170702015517.GA14839@www.zefox.net> <20170702203651.GA17014@www.zefox.net> <1AAA5539-C81F-407E-8310-8F446665E7FC@dsl-only.net> <38241DC9-8A8D-4B90-A678-5A4F7511029B@dsl-only.net> <20170702234351.GB17014@www.zefox.net> <76AA57AF-8D5E-461E-A756-F71A9F84B1EE@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76AA57AF-8D5E-461E-A756-F71A9F84B1EE@dsl-only.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 01:00:00 -0000 On Sun, Jul 02, 2017 at 04:57:18PM -0700, Mark Millard wrote: > > man install reports: > > -s install exec's the command strip(1) to strip binaries so that > install can be portable over a large number of systems and binary > types. See below for how install can be instructed to use > another program to strip binaries. > > It also reports in the ENVIRONMENT section: > > If the DONTSTRIP environment variable is present, install will ignore any > specification of the -s option. This is mainly for use in debugging the > FreeBSD Ports Collection. > > === Looks like the jig is up. Setting DONTSTRIP results in /lib/libc.so.7: invalid file format Looks like something got corrupted, the ls command does the same. Thanks again for your help and patience! bob prohaska From owner-freebsd-arm@freebsd.org Mon Jul 3 15:58:02 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E34879E9911 for ; Mon, 3 Jul 2017 15:58:02 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 921AC75A67 for ; Mon, 3 Jul 2017 15:58:02 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.16.0.19/8.15.2) with ESMTPSA id v63FvsKr071682 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 3 Jul 2017 11:58:01 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Received: from [IPv6:2001:420:2710:1330:d063:146f:18a:849c] ([IPv6:2001:420:2710:1330:d063:146f:18a:849c]) (authenticated bits=0) by mail.distal.com (8.15.2/8.15.2) with ESMTPSA id v63FvqSc008881 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 3 Jul 2017 11:57:53 -0400 (EDT) (envelope-from cross+freebsd@distal.com) From: Chris Ross Content-Type: multipart/signed; boundary="Apple-Mail=_9C1FC8DA-8D03-4F8D-A800-7C11396C87A5"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Raspberry Pi WiFi Message-Id: Date: Mon, 3 Jul 2017 11:57:47 -0400 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 15:58:03 -0000 --Apple-Mail=_9C1FC8DA-8D03-4F8D-A800-7C11396C87A5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello. I=E2=80=99ve started working on a RPi (Zero W) project, and am = happy to use Raspbian for the units I=E2=80=99m building. But, I have = FreeBSD (amd64) running on all of my real machines, so wanted to look = into it for the Pi=E2=80=99s. I notice looking on = https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi that the Zero looks = to mostly work, but that the WiFi on the Pi 3 and the Pi Zero W is = =E2=80=9CUnsupported (SDIO)=E2=80=9D. That would be needed for me to be = able to use it. I wanted to ask if there=E2=80=99s a plan for that, or = more details on the impediment. I would be happy to help get it = supported if I can. - Chris --Apple-Mail=_9C1FC8DA-8D03-4F8D-A800-7C11396C87A5 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZWml7AAoJEPFBDnXvoNg0g24QAJAsIqUz6BvrhEr+hseqDdk0 MD4BpHvwrVLBOFuEL2NVPkQKj2PVnpQWrCyZL5hOdXrrOMBGf3ogcU67BQh2NLB+ R0V1iI59/E7nxNlegusiHa30s+2Rd8gthV36JL8xXWd8ODH+c17UFeUG6ieR3RBE yEX790/mQ6r/WgCIX98EoRKvfEi7/BV5qTcKQV2f5tmxWP5hQRtlwLupxLci0SKX xRu6UjeGIxTobRAMkBlInqbnL198MMVN4k7BSYLtmGeNbMgHwtkf7cOP+d0XdY46 3blpUWoawZfliMJhi0uJqCFf+koqdu0AI0vHBHWUbLt90GKapDVrXw/WSas9gXcJ a1w5yHNIx93Y+itjmYo2x+VQBCem0kda7XrXhY0sjklPXfiDeJNuqhpsiZd0CNhK H9CmB6X1S+foGun7DP5bAlnyIvDI5ZqggbxKDTJgfvfRoCiTPaFGL3op4XspT+Yp GnCSvcfClZzDu9pP9Wk3ARTJjXtY2zo2v2fwoN7CB4pw/qfj95VZAnHA6PqssZYh ww6XCZbFKl9AWSdSMmo/eOiXxdiD3TYQi9mk10U0rc4W8azY+K1CMDjhNKS1Bb8e LQAjDL7IE3Lx857wIfKuVP4WLFfqjQ73Xo92PGjRKsMAQxMUOBS/JpMSW0S8MEzC TNTX6RnJehFyFwqipRLE =F/BU -----END PGP SIGNATURE----- --Apple-Mail=_9C1FC8DA-8D03-4F8D-A800-7C11396C87A5-- From owner-freebsd-arm@freebsd.org Mon Jul 3 16:26:47 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A2E69EA1CA for ; Mon, 3 Jul 2017 16:26:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59ED676836 for ; Mon, 3 Jul 2017 16:26:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id v202so89754182itb.0 for ; Mon, 03 Jul 2017 09:26:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=U574+5E+5CvylasyEH2vUTmjWwm6+kmTlRMh3A61xiI=; b=kI7iya3/FFKm6/k8nR9k/rcUNKV9Xvk55z0XE5vpF8QktanNjcTxz7l02a1MXVXCgc PVH+J/p556HCRe7xKaOmKUQO+3nqNReKdp2LZxYjglr7lbLQyNR4JVQayin1tNnrL7Zr rMwFYWoTaKMq1d6sEdgQJI+POtCyKAnk+vF6+ATlFJPGtVxjUSSfsaM4spRsbK+7M3sm CG1AUwNa0yh5RXHSkDSLCHgzgyXPiMMAXi1xEoqeivnHLNXLE2lJofwOxx6taBFlHd2f 37Q1yJEEEeX+5j+ZWdpU7+AaEcSKQ3FBSKxqjvHqR2lnMbrPm1kjn4iKxWOFJLFtC+6r W+AQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=U574+5E+5CvylasyEH2vUTmjWwm6+kmTlRMh3A61xiI=; b=AhKHyxdN5JqMNnWCqlNgOCQftiP3qU+FJhVQ2ZGY5biASDvkWwaZRDmNaBVnhHyJ4l pYQRrDbSrfYkRkgxsnshQ7eJIdqeSXJsPDie8qzSB4xKIvjq5ZLlfo73yCWPVfLsHqN4 EcdNnxMuGn2JIA8O6UITZRTBbI+Lmu+SWUeKE7TV6cBpSsW0JsDPh/eBYgMHBzd9kKP0 gRiRbdqP5HQejQ1yNwSoXJCwM985Ctki5ZnfIZMZDL186lEN1rtvMS82h34Lu+F3VpG3 ABlxuc5C1f1dhWX/89WSUaP0FpU9r+I/g8g3ZT+gvAtrtH+yz36yRG1MxPZDZeSmHDiB 6htg== X-Gm-Message-State: AIVw113eTcSUzKjaKBqBuAfQ9d2MYJSE5kRTAw/il39hP2Hx5fdfza7v rJhvzdBW7lyCuEYtHvrGmTPpneEzphWw X-Received: by 10.36.163.198 with SMTP id p189mr9266536ite.64.1499099206589; Mon, 03 Jul 2017 09:26:46 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.212.167 with HTTP; Mon, 3 Jul 2017 09:26:46 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Mon, 3 Jul 2017 10:26:46 -0600 X-Google-Sender-Auth: 29UfcI3g1jQBb3GNAdEDr44njy0 Message-ID: Subject: Re: Raspberry Pi WiFi To: Chris Ross Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 16:26:47 -0000 On Mon, Jul 3, 2017 at 9:57 AM, Chris Ross wrote= : > > Hello. I=E2=80=99ve started working on a RPi (Zero W) project, and am = happy to > use Raspbian for the units I=E2=80=99m building. But, I have FreeBSD (am= d64) > running on all of my real machines, so wanted to look into it for the Pi= =E2=80=99s. > > I notice looking on https://wiki.freebsd.org/FreeBSD/arm/Raspberry%20Pi > that the Zero looks to mostly work, but that the WiFi on the Pi 3 and the > Pi Zero W is =E2=80=9CUnsupported (SDIO)=E2=80=9D. That would be needed = for me to be able > to use it. I wanted to ask if there=E2=80=99s a plan for that, or more d= etails on > the impediment. I would be happy to help get it supported if I can. > The SDIO stack should be going in very soon... I'm not sure about drivers after that though... FWIW, I have a Pi Zero W as well... Warner From owner-freebsd-arm@freebsd.org Mon Jul 3 17:47:01 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CCC99EBF53 for ; Mon, 3 Jul 2017 17:47:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2640779522 for ; Mon, 3 Jul 2017 17:47:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v63Hl1Bl064319 for ; Mon, 3 Jul 2017 17:47:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 220452] Kernel panic in soisconnected during sysinit: invalid instruction Date: Mon, 03 Jul 2017 17:47:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sylvain@sylvaingarrigues.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2017 17:47:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220452 Bug ID: 220452 Summary: Kernel panic in soisconnected during sysinit: invalid instruction Product: Base System Version: CURRENT Hardware: arm OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: sylvain@sylvaingarrigues.com Hello, When compiled without INVARIANTS and INVARIANT_SUPPORT, my production armv6 kernel updated as of yesterday's latest commit panics (cf screenshot). When I compile with INVARIANTS and INVARIANT_SUPPORT, I don't have the pani= c, everything boots fine till the login prompt. I suspect the culprit might be https://reviews.freebsd.org/rS319722 Gleb, any idea? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Tue Jul 4 09:17:18 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4D82D8B391 for ; Tue, 4 Jul 2017 09:17:18 +0000 (UTC) (envelope-from bounce_YPt7oVRExLxd87Cz_WMjUTU4nq1JgBtNM_bd8e3c6e2387cb32_10@m-tdevelopment-mail.com) Received: from mail38.outbound.mta-3.com (mail38.outbound.mta-3.com [69.63.158.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FE58741B0 for ; Tue, 4 Jul 2017 09:17:18 +0000 (UTC) (envelope-from bounce_YPt7oVRExLxd87Cz_WMjUTU4nq1JgBtNM_bd8e3c6e2387cb32_10@m-tdevelopment-mail.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=mykey2; d=mta-3.com; h=Reply-To:Sender:List-Unsubscribe:From:To:Subject:MIME-Version:Date:Message-Id:Content-Type; bh=67pBsAWkvDUsJ40aWDasVRI+OLI=; b=qEahvSNQProOwY0GpYq91MS9kWfjtO8j+GnI5sGOj9xbadQ8gnUKHHlS94xkRA3UKWl6JUhfFteb YU0a9YONaqrn4ibekGQQ0giASPPrg8nbDG+Op81otCyTSjL89XYhUIcYespwWhqX5zeUbQoZ43pA +p84zqvAc0GNTXnz8AuIQf7tYuv6fjsKn24SWbfDvmuYNV67mliOgK1aW4R035MLDswWAcuY9T5h /98UbhMGQz9ZDjcrUaGTXjnP8Bp2ic1lKmD1H+SKHIaZ3K1ZRNxXg4C3N850imdGqoLppsDGlCpn 4pTSHAT5bNrVSsKjrckcodvWzY/rGuvr8WUP1A== Received: from localhost (10.10.204.20) by mail38.outbound.mta-3.com id hbdehs29cjoo for ; Tue, 4 Jul 2017 11:17:16 +0200 (envelope-from ) Reply-To: newsletter@m-t.co.za X-Priority: 3 Sender: "M&T Marketing" X-Report-Abuse: X-Data: WMjUTU4nq1JgBtNM.bd8e3c6e2387cb32 X-Data-EUID: 7d00488b38097631f826dd8ab2e47a13 X-Data-Rating: 60 X-Contact-Score: 0 From: M&T Marketing To: freebsd-arm@freebsd.org Subject: Development in Centurion MIME-Version: 1.0 Date: Tue, 04 Jul 2017 11:17:01 +0200 Message-Id: <201707041111416.11884.557@m-t.co.za> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2017 09:17:19 -0000 M%26T_Header.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344203 ) Centurion Peach_Orchard__Logo.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344204 ) Facilities.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344205 ) Peach_Orchard_Stacks_image.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344206 ) Peach_Orchard_Prices.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344207 ) Ben 078 784 9901 ben@m-t.co.za ( ben@m-t.co.za?subject=Peach%20Orchard%20e-mail%20newsletter%20enquiry ) Key_places_in_the_area.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344208 ) Peach-Orchard_MAP.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344209 ) Show_Times.jpg ( http://comms.m-tdevelopment-mail.com/servlet/link/9695/31907/58966528/344210 ) From owner-freebsd-arm@freebsd.org Tue Jul 4 18:26:10 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFA9FD97A66 for ; Tue, 4 Jul 2017 18:26:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DBA883A85 for ; Tue, 4 Jul 2017 18:26:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v64IQA6e064422 for ; Tue, 4 Jul 2017 18:26:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 220452] Kernel panic in soisconnected during sysinit: invalid instruction Date: Tue, 04 Jul 2017 18:26:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2017 18:26:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220452 Hans Petter Selasky changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #26 from Hans Petter Selasky --- Please re-open if this is still an issue with the latest version of FreeBSD-12-current. Thank you! --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-arm@freebsd.org Wed Jul 5 12:01:29 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19084DA9B33 for ; Wed, 5 Jul 2017 12:01:29 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDC3C7E378 for ; Wed, 5 Jul 2017 12:01:28 +0000 (UTC) (envelope-from sanpei.ml@gmail.com) Received: by mail-yw0-x236.google.com with SMTP id v193so25919149ywg.2 for ; Wed, 05 Jul 2017 05:01:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=KXJ7LG2LUpKtWk+zVcg/OPeTFLD/yWc9rQcim/DZPpE=; b=M9Q5wuaSeu6HpKl9yHIHUfhp9TgrsiO/MXfiHpj+pV1/cD3rsl49YtweBAlzrmj4oO B6tuQ+FeLLtSSEpkUY0DzrHrbgG4KnJ9RT5apTaA36cyRmTS1lXWajXGzYcYh+fdN16F glhBVQLZx3+N7ixPIw4vp5xnthz22jSfIjVhXNVYopABxP5dmGiE1n0ZsMl63WuF4jw7 oLO/BJ8+FyVwUbE6wAYe2Is9/zsnXgoy1fq9la2gT/2+/DfmZkKglhSJtAj/p8fpIsxK aUoKDBuAMKaUjXndicsHXBoyiy+9XUoO8tfrIpF7HVonYyxHOVxGxnwJNnl325c6JrE9 Yq1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=KXJ7LG2LUpKtWk+zVcg/OPeTFLD/yWc9rQcim/DZPpE=; b=DBW837QzweJNho2Pk5UwLFojQMAiaVvv+6vOpqDLNbIES0/dHuwwSBtdXiQ62nVoZg Ut7SDsIfJQNyFR+GeayF2GOqGYGSseRAJoHLzgjTaIEsJR/XL79qZVJGj1cYz6v+TsFs SA9uee4KM5jzrBMyWRdQteDGkEFfEWxrnGW5pOWSChcp+kptO9B9FJ2wnUX+GpMQqIbK EjWdhCA19eMipB6BSQuk1mkv/IlsxZZ0Tjavwp2Wn+IeuhGLOWmJ9ct2EWYH88JB1ZUd WlSBxXuQ6V9aVcSowbaPDof/zkDZ86Ndzr+a/P6wdaqElsMYrv9rSX75+9qeWLB8JlL+ LI0Q== X-Gm-Message-State: AKS2vOxR4XrnBNjxXM3tI1aIw3R3RLeDBEP+MzbXwogNup9mTQCTtoOL fsiL4nym1XBucldGjPzq1ZmkzqaFgw== X-Received: by 10.13.214.150 with SMTP id y144mr33894241ywd.303.1499256087727; Wed, 05 Jul 2017 05:01:27 -0700 (PDT) MIME-Version: 1.0 From: Yoshiro MIHIRA Date: Wed, 05 Jul 2017 12:01:17 +0000 Message-ID: Subject: HummingBoard-i2 does not boot from install image To: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 12:01:29 -0000 I have HummingBoard-i2 and I could not boot 12.0-CURRENT boot image. Please let me know to boot 12.0-CURRENT with HummingBoard. I tested FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170619-r320095.img And it does not boot up with below message[NG]. U-Boot SPL 2017.01-rc3 (Jun 13 2017 - 02:16:03) SPL: Unsupported Boot Device! SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### I have a old image as FreeBSD-11.0-STABLE-arm-armv6-CUBOX-HUMMINGBOARD-20161221-r310359.img it can boot[OK]. Consoles: U-Boot console Compatible U-Boot API signature found @0x4f7708a8 FreeBSD/armv6 U-Boot loader, Revision 1.2 (root@releng2.nyi.freebsd.org, Wed Dec 21 18:14:05 UTC 2016) DRAM: 1024MB Number of U-Boot devices: 2 U-Boot env: loaderdev='mmc 0' Found U-Boot device: disk Checking unit=0 slice= partition=... good. Booting from disk0s2a: /boot/kernel/kernel data=0x6ec964+0x14b69c syms=[0x4+0x7cef0+0x4+0x90376] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 4 seconds... Thanks Yoshiro MIHIRA From owner-freebsd-arm@freebsd.org Wed Jul 5 12:13:24 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52A21DAA06B for ; Wed, 5 Jul 2017 12:13:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A7EE47E91A for ; Wed, 5 Jul 2017 12:13:22 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id e35000ba; Wed, 5 Jul 2017 14:13:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=4PsXP0kAEG6X41Mb03cxifQFv38=; b=SOI4Z5piLJth7+mx+5OZPSTs+qVj HtV+ZXOyX5sxZh20dB358eW5XXuG/JsxtKRTe5HsYD1n/N2DMRCjE0wdNCS47TIs iSUmnLrXzTyCmByzuEOq0gvCipDbInE0iD/AMsdsl75RLYM4mXy9N1nm5R1sipcw NswXbu7s7PvSDAc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=atolRGjvZfjBn9fo+POG+Ojt4agZ5fDHQV4n6APnISoUB9+XE+SX0434 GkeqOH86iEYMkhASR6Uv4olQY2qEaG4Gic/nKAN8CHvu1iyh0DQVu7+WktC/tkml cQYw/IaywW3PMpttnre5h3brN/6dOFV+uaMikOQO1aWyVTJ/XDE= Received: from arcadia (evadot.gandi.net [217.70.181.36]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 8dbb0336 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Wed, 5 Jul 2017 14:13:14 +0200 (CEST) Date: Wed, 5 Jul 2017 14:13:14 +0200 From: Emmanuel Vadot To: Yoshiro MIHIRA Cc: freebsd-arm , Warner Losh Subject: Re: HummingBoard-i2 does not boot from install image Message-Id: <20170705141314.df91849fa89d767e9d01c25e@bidouilliste.com> In-Reply-To: References: X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) 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.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 12:13:24 -0000 On Wed, 05 Jul 2017 12:01:17 +0000 Yoshiro MIHIRA wrote: > I have HummingBoard-i2 and I could not boot 12.0-CURRENT boot image. > Please let me know to boot 12.0-CURRENT with HummingBoard. > > I tested > FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170619-r320095.img > > And it does not boot up with below message[NG]. > > U-Boot SPL 2017.01-rc3 (Jun 13 2017 - 02:16:03) > SPL: Unsupported Boot Device! > SPL: failed to boot from all boot devices > ### ERROR ### Please RESET the board ### > > I have a old image > as FreeBSD-11.0-STABLE-arm-armv6-CUBOX-HUMMINGBOARD-20161221-r310359.img > it can boot[OK]. > > Consoles: U-Boot console > Compatible U-Boot API signature found @0x4f7708a8 > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > (root@releng2.nyi.freebsd.org, Wed Dec 21 18:14:05 UTC 2016) > > DRAM: 1024MB > Number of U-Boot devices: 2 > U-Boot env: loaderdev='mmc 0' > Found U-Boot device: disk > Checking unit=0 slice= partition=... good. > Booting from disk0s2a: > /boot/kernel/kernel data=0x6ec964+0x14b69c syms=[0x4+0x7cef0+0x4+0x90376] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel] in 4 seconds... > > Thanks > Yoshiro MIHIRA Hello, Can you check the U-Boot version on the 11-STABLE image ? I guess that it's an older version (before we switched the ports to use u-boot-master). I don't have this board so I cannot help more right now, but it seems that it is a u-boot problem. cc imp@ as he made the u-boot switch. Warner do you have this board to test U-Boot on ? -- Emmanuel Vadot From owner-freebsd-arm@freebsd.org Wed Jul 5 20:31:00 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8984CD90FED for ; Wed, 5 Jul 2017 20:31:00 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6DA8C6F70F for ; Wed, 5 Jul 2017 20:30:59 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: d871a72f-61c0-11e7-bfcf-afd4446ba3af X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id d871a72f-61c0-11e7-bfcf-afd4446ba3af; Wed, 05 Jul 2017 20:30:55 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v65KUpCR001791; Wed, 5 Jul 2017 14:30:51 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1499286651.4402.40.camel@freebsd.org> Subject: Re: HummingBoard-i2 does not boot from install image From: Ian Lepore To: Yoshiro MIHIRA , freebsd-arm Date: Wed, 05 Jul 2017 14:30:51 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 20:31:00 -0000 On Wed, 2017-07-05 at 12:01 +0000, Yoshiro MIHIRA wrote: > I have HummingBoard-i2 and I could not boot 12.0-CURRENT boot image. > Please let me know to boot 12.0-CURRENT with HummingBoard. > > I tested > FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170619- > r320095.img > > And it does not boot up with below message[NG]. > > U-Boot SPL 2017.01-rc3 (Jun 13 2017 - 02:16:03) > SPL: Unsupported Boot Device! > SPL: failed to boot from all boot devices > ### ERROR ### Please RESET the board ### > > I have a old image > as FreeBSD-11.0-STABLE-arm-armv6-CUBOX-HUMMINGBOARD-20161221- > r310359.img > it can boot[OK]. > > Consoles: U-Boot console > Compatible U-Boot API signature found @0x4f7708a8 > > FreeBSD/armv6 U-Boot loader, Revision 1.2 > (root@releng2.nyi.freebsd.org, Wed Dec 21 18:14:05 UTC 2016) > > DRAM: 1024MB > Number of U-Boot devices: 2 > U-Boot env: loaderdev='mmc 0' > Found U-Boot device: disk >   Checking unit=0 slice= partition=... good. > Booting from disk0s2a: > /boot/kernel/kernel data=0x6ec964+0x14b69c > syms=[0x4+0x7cef0+0x4+0x90376] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel] in 4 seconds... > > Thanks > Yoshiro MIHIRA I just downloaded that same 20170619 image and it boots fine on my Cubox, but its build date/time are different: U-Boot SPL 2017.01-rc3 (Jun 19 2017 - 20:54:45) I don't have a hummingboard to test, but u-boot has always been able to use the same image to boot a cubox and a hummingboard. -- Ian From owner-freebsd-arm@freebsd.org Wed Jul 5 22:04:25 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7AB23D935CE for ; Wed, 5 Jul 2017 22:04:25 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0178E73032; Wed, 5 Jul 2017 22:04:25 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id h22so1184858lfk.3; Wed, 05 Jul 2017 15:04:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7ag9G1HzpQz8SW4xKV4sHLclSkPrLVEOIi+Hvg6MXVc=; b=uIk2fgVjqPHKN4tJ+hTvA5K54/lnkMmrlTeBHcg9DdGzrWTU5E7uXt+i8zot2jFpe+ Ya+pp8reX99M06mEd6CIAzwD+p+cMxaCFRZf0hmEKE9WxnP6eYr1R9VAxfmvaXXOwvhy C8bgXiF+JdC+DYXPv9dcTYhK8kUTiA0ZKL5QM2eFy0pYFT0FAaYa0fxusuPx3wsvG7rN VlZSXqYf7M+7N5Q1YEEON0LEo3YUsAReH22TihXEJfXKvjJ4soKcxfSjfHxfUkYIQTBo DLYlheoNfLo5lR2P24KWXa9jiWM4C24EF0rgGL5CxUf2nFWj+/zKlU+Qu4Um1nh0nJ1W go2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7ag9G1HzpQz8SW4xKV4sHLclSkPrLVEOIi+Hvg6MXVc=; b=KboH8YkU/NEALTxMTB5co6CvEAvlCfVlsAHJYBWtzOgzo1BGH/+avzxfQUJavjMWYc Ca7xyM68A2LlwYIYpX13wVwlElD0Tl9K5HnSCF3Yz0plgQaskU6D4aC5XaaCq4mVw7TZ lmowFD7eJpWtWbS93SQNtPhMdKK1jNCkEVyj8BdJy5DUmxb+P2P/RaXDNk5zG6RoMEMf FmImeQxf3YFyOJTIm9BM5K9/XjtwTrqtHSs6hWI3FkX181CQ1DIg1L1j3ux8xcNcV3K5 YUEjFUfgUMmMa6MUyDt97BENQaiEl9DT/xM0ZKkKetnDHKjItCybLFy6Qt8m3NB7Nr13 iWZg== X-Gm-Message-State: AKS2vOxcWk0pElEYF5Bt7cCi2Fb9Qp/iLwSs06A1U+gW+F3BRIOscSF+ g1Iz3K0wfvSiPzaa3oh2MLqDeLWL8w== X-Received: by 10.25.149.71 with SMTP id x68mr15621592lfd.136.1499292261327; Wed, 05 Jul 2017 15:04:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.82.211 with HTTP; Wed, 5 Jul 2017 15:04:20 -0700 (PDT) In-Reply-To: <1499286651.4402.40.camel@freebsd.org> References: <1499286651.4402.40.camel@freebsd.org> From: Russell Haley Date: Wed, 5 Jul 2017 15:04:20 -0700 Message-ID: Subject: Re: HummingBoard-i2 does not boot from install image To: Ian Lepore Cc: Yoshiro MIHIRA , freebsd-arm Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2017 22:04:25 -0000 On Wed, Jul 5, 2017 at 1:30 PM, Ian Lepore wrote: > On Wed, 2017-07-05 at 12:01 +0000, Yoshiro MIHIRA wrote: >> I have HummingBoard-i2 and I could not boot 12.0-CURRENT boot image. >> Please let me know to boot 12.0-CURRENT with HummingBoard. >> >> I tested >> FreeBSD-12.0-CURRENT-arm-armv6-CUBOX-HUMMINGBOARD-20170619- >> r320095.img >> >> And it does not boot up with below message[NG]. >> >> U-Boot SPL 2017.01-rc3 (Jun 13 2017 - 02:16:03) >> SPL: Unsupported Boot Device! >> SPL: failed to boot from all boot devices >> ### ERROR ### Please RESET the board ### >> >> I have a old image >> as FreeBSD-11.0-STABLE-arm-armv6-CUBOX-HUMMINGBOARD-20161221- >> r310359.img >> it can boot[OK]. >> >> Consoles: U-Boot console >> Compatible U-Boot API signature found @0x4f7708a8 >> >> FreeBSD/armv6 U-Boot loader, Revision 1.2 >> (root@releng2.nyi.freebsd.org, Wed Dec 21 18:14:05 UTC 2016) >> >> DRAM: 1024MB >> Number of U-Boot devices: 2 >> U-Boot env: loaderdev='mmc 0' >> Found U-Boot device: disk >> Checking unit=0 slice= partition=... good. >> Booting from disk0s2a: >> /boot/kernel/kernel data=0x6ec964+0x14b69c >> syms=[0x4+0x7cef0+0x4+0x90376] >> >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [/boot/kernel/kernel] in 4 seconds... >> >> Thanks >> Yoshiro MIHIRA > > I just downloaded that same 20170619 image and it boots fine on my > Cubox, but its build date/time are different: > > U-Boot SPL 2017.01-rc3 (Jun 19 2017 - 20:54:45) > > I don't have a hummingboard to test, but u-boot has always been able to > use the same image to boot a cubox and a hummingboard. There are different hummingboard baseboards and different hummingboard SOMs and they can be mixed and matched. The SOMs come in single, dual-lite, dual, and quad core configurations. The dual-lite and dual SOMs ARE NOT THE SAME architecture and require different uboot 'stuffs'. I don't remember off the top of my head, but I seem to remember having to build two parts of U-boot and then create one binary? I would wager that you have a dual-lite SOM and there is some 'stuffs' you will need to do with u-boot? I remember thinking I dodged a bullet by buying the dual and not dual-lite SOM so the stock image worked on my board. Sorry, I'm pinned busy right now so I can't look up what 'stuffs' means. It should be on the wiki or in the mailing list archives. Or was it in the u-boot readme in ports? :( Russ From owner-freebsd-arm@freebsd.org Thu Jul 6 21:40:21 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4FDFD927B2 for ; Thu, 6 Jul 2017 21:40:21 +0000 (UTC) (envelope-from rj@obsigna.com) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46A3D806C7 for ; Thu, 6 Jul 2017 21:40:20 +0000 (UTC) (envelope-from rj@obsigna.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1499377218; l=4555; s=domk; d=obsigna.com; h=To:References:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From: Subject:Mime-Version:Content-Type; bh=JMpSsc2iRiGCaNi4Xx9PwOw6ckCmWNk/2xsvtN20wRI=; b=o9bBUy76yQJw9FU6xL4vuSOjVXxXe5g7CxXG6mn0q7Tz5aL3qBFqjrdPLAPV6jH+eX 3vjr0EnzYqoc2pc5zckz/UqGHeV27bNTwpEuTjqh6KYZ/h9Bc49Nud1cLDKfs8IJGBj2 0dVluZ8eHhi1TzXJ09Zrl0diO6N789YJB2tws= X-RZG-AUTH: :O2kGeEG7b/pS1EK7WHa0hxqKZr4lnx6UhT0M0o35iAdWtoM07Gt3wQHFGhIl99Xr7A== X-RZG-CLASS-ID: mo00 Received: from mail.obsigna.com (bb02b03a.virtua.com.br [187.2.176.58]) by smtp.strato.de (RZmta 41.1 DYNA|AUTH) with ESMTPSA id I08966t66LeHPbZ (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Thu, 6 Jul 2017 23:40:17 +0200 (CEST) Received: from rolf.projectworld.net (rolf.projectworld.net [192.168.222.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.obsigna.com (Postfix) with ESMTPSA id EF307292D701; Thu, 6 Jul 2017 18:40:13 -0300 (BRT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Enabling ADC on a Beaglebone Black running FreeBSD 12.0-CURRENT (BEAGLEBONE) From: "Dr. Rolf Jansen" In-Reply-To: <79EE9798-BCF0-4585-93F5-4E604142561F@obsigna.com> Date: Thu, 6 Jul 2017 18:40:13 -0300 Content-Transfer-Encoding: quoted-printable Message-Id: <6DE3312D-BA5B-4192-88C4-1F0C800CBFF6@obsigna.com> References: <0C4DCBB9-2642-4B0F-B15B-4139D5D8B249@obsigna.com> <271AFD8F-BD2C-445C-AB95-D7D07593E487@obsigna.com> <5D2FEB0D-64F3-488C-8458-85E7DF10EFB7@obsigna.com> <20170330202858.GA22253@bluezbox.com> <79EE9798-BCF0-4585-93F5-4E604142561F@obsigna.com> To: freebsd-arm@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 21:40:21 -0000 > Am 30.03.2017 um 18:11 schrieb Dr. Rolf Jansen : >=20 > Am 30.03.2017 um 17:28 schrieb Oleksandr Tymoshenko = : >> Dr. Rolf Jansen (rj@obsigna.com) wrote: >>> Today I updated once again my Beaglebone Black by >>> merging-in the latest FreeBSD 12.0-CURRENT (BEAGLEBONE) >>> snapshot, and once again I enabled the ADCs on the >>> Beaglebone in the device tree blob am335x-boneblack.dtb, >>> and the ADC is still working fine. >>>=20 >>> Even if it is not that a big hassle to modify the device >>> tree blob, I am curious on why the ADC has been disabled >>> in the blob in the first place, end even more, given the >>> fact that the device ti_adc driver is built-in to kernel >>> and once enabled, the ADC is functional. >>>=20 >>> Didn't it work at some time in the past? Now it is. >>>=20 >>> What is missing to activate the ADC in the device tree >>> blob by default? >>=20 >> Few months ago FreeBSD switched to using upstream DTB files >> instead of custom-made ones. For some reason ADC is disabled >> in upstream. If you're running recent FreeBSD you can use >> dtb overlays to enable ADC without hassle of maintaining >> custom dts file. You can do following: >>=20 >> 1. Create am335x-beaglebone-tscadc.dts with following >> content: >>=20 >> /dts-v1/; >> /plugin/; >>=20 >> / { >> compatible =3D "ti,am335x-bone-green", "ti,am335x-bone-black", = "ti,am335x-bone", "ti,am33xx"; >>=20 >> fragment@0 { >> target =3D <&tscadc>; >> __overlay__ { >> status =3D "okay"; >> adc { >> ti,adc-channels =3D <0 1 2 3 4 5 6>; >> }; >> }; >> }; >> }; >>=20 >> 2. Compile overlay: >> $ dtc -I dts -O dtb -o am335x-beaglebone-tscadc.dtbo = am335x-beaglebone-tscadc.dts >>=20 >> 3. Copy it to /boot/dtb/ directory on your BBB >>=20 >> 4. Enable overlay in /boot/loader.conf by adding following line: >>=20 >> fdt_overlays=3D"am335x-beaglebone-tscadc.dtbo" >=20 >=20 > Oleksandr, thank you very much for drawing my attention to the dtb = overlay facility. >=20 > I created and enabled the adc-dtb-overlay file as you explained above, = and it works. >=20 > Best regards >=20 > Rolf With the last two 12.0-CURRENT BBB snapshots (r320360 and r320599), the = dtb oberlay facility is broken. I can get the above overlay working only = if I compile it with the dtc tool from the previous June, 19th snapshot = (r320095), and in addition it is necessary to re-add the phandle to the = tscadc@44e0d000 definitions of the base dtb file. Said phandle was = removed together with almost all phandles of other device definitions = between r320095 and r320360. Since I need to edit the base dtb anyway, for the time being, I enable = the ADC and its channels right in there. This one can be compiled with = the new dtc, and in addition the ADC phandle is not necessary. By the way, the decompiler of the new dtc commes with a formatting = glitch. The sections are no more devided by an empty line, instead an = empty line is introduced below the section headers -- this looks spoiled = somehow. Anyway, here are my working changes:=20 --- am335x-boneblack.dts.orig 2017-07-06 18:32:10.321019000 -0300 +++ am335x-boneblack.dts 2017-07-06 16:00:22.255994000 -0300 @@ -1711,7 +1711,7 @@ interrupt-parent =3D <0x1>; interrupts =3D <0x10>; ti,hwmods =3D "adc_tsc"; - status =3D "disabled"; + status =3D "okay"; dmas =3D <0x29 0x35 0x0 0x29 0x39 0x0>; dma-names =3D "fifo0", "fifo1"; tsc { @@ -1722,8 +1722,19 @@ =20 #io-channel-cells =3D <0x1>; compatible =3D "ti,am3359-adc"; + ti,adc-channels =3D <0 1 2 3 4 5 6 7>; }; }; + pruss@4A300000 { + + compatible =3D "ti,pruss-v2"; + ti,deassert-hard-reset =3D "pruss", "pruss"; + reg =3D <0x4a300000 0x80000>; + ti,pintc-offset =3D <0x20000>; + interrupt-parent =3D <0x1>; + interrupts =3D <0x14 0x15 0x16 0x17 0x18 0x19 = 0x1A 0x1B>; + status =3D "okay"; + }; gpmc@50000000 { =20 compatible =3D "ti,am3352-gpmc"; @@ -1969,6 +1980,7 @@ ehrpwm2_tbclk =3D = "/ocp/l4_wkup@44c00000/scm@210000/scm_conf@0/clocks/ehrpwm2_tbclk@44e10664= "; ehrpwm0_tbclk =3D = "/ocp/l4_wkup@44c00000/scm@210000/scm_conf@0/clocks/ehrpwm0_tbclk@44e10664= "; tscadc =3D "/ocp/tscadc@44e0d000"; + pruss =3D "/ocp/pruss@4A300000"; clkout2_pin =3D = "/ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_clkout2_pin"; aes0_fck =3D = "/ocp/l4_wkup@44c00000/scm@210000/scm_conf@0/clocks/aes0_fck"; gpio3_dbclk =3D = "/ocp/l4_wkup@44c00000/prcm@200000/clocks/gpio3_dbclk@b4"; From owner-freebsd-arm@freebsd.org Fri Jul 7 11:56:06 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDD6ADA121A for ; Fri, 7 Jul 2017 11:56:06 +0000 (UTC) (envelope-from diizzyy@gmail.com) Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9953F77341 for ; Fri, 7 Jul 2017 11:56:06 +0000 (UTC) (envelope-from diizzyy@gmail.com) Received: by mail-vk0-x22b.google.com with SMTP id r125so16128801vkf.1 for ; Fri, 07 Jul 2017 04:56:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=rcDjGYCJnk+zUrkmfMsNUQXhkTxZlO1IHfv6OH8KdmY=; b=jQG/RNJs16roeXTMAEb64sdBgAbXAzcwMM/5r7HVpinMoBO4B2FOY29qIHjVA609LA 8gAjOTPgCbudoLP5VoMonBuopsetBZskt+qxgnSLJS/YN401a0GjT8fGUKmwY54BtSEq O5ck/Ek6WGpVqy7reqhUppFC9ZMzghIXJb477a+wRAF5gydQuDeK3ITntwtcnWuPrHnE 3EXES0mdOZgAHjgY2Fu5oDUVk2pfxtjCxZCtn7sKqBaEi4hu9o6BfFijPtnBTglXP17f 68tHwxwtYMolrx/E8zlwkICzhkzXE66ka6t/UAgt9fnFllLZ+D9AxMcwouR6dJ9vV2kU z40A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rcDjGYCJnk+zUrkmfMsNUQXhkTxZlO1IHfv6OH8KdmY=; b=GBOH+RrcaNfqpbQlEYh7M3uLc834BYyoDR1z0JsGKdEV6eRbJLnPQ/Lio8MCsYP1Qr qg0byvz+Hg8yW+JLmYfKV23v4gmaIdbemHV3wJArV7CEkzOowL1m/vn7kq5nO378KJXW OWBnpiGUlAvdidqx65aCBrObHq+ySImplqQZBFlppWwwW6ybUlNBlYatkaofslofCO1g y3PkUXat3rD0fCEe7y5Hfzdn7sMHDxe+5JzyxbODoZOqhYCxBkWTi2NqwiDf1gEqTXCz 6TXFdvG/FTermT/2cENMpQBOctDs6lFSEtB6xfNhCXM4ffTSdULL+x/6sdE3SpubP5/K hCqA== X-Gm-Message-State: AIVw113o8tJTTOihy3Y68IVWgk9W825tzvce9VygloznG80IU1Jkl/65 RiOd/7GwEhnEHsTZJbquAD680HmBUA== X-Received: by 10.31.237.193 with SMTP id l184mr398044vkh.147.1499428565573; Fri, 07 Jul 2017 04:56:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.65.15 with HTTP; Fri, 7 Jul 2017 04:56:05 -0700 (PDT) From: Daniel Engberg Date: Fri, 7 Jul 2017 13:56:05 +0200 Message-ID: Subject: Re: HEADS UP: Marvell Armada 38x support in the tree To: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 11:56:07 -0000 Hi, Great work seeing this in the FreeBSD tree, many thanks to those involved making this happen. This also made me interested in the possibility of running FreeBSD on consumer hardware. While I do understand that NAND support is still no available and also WIFI would it possible to get FreeBSD running on a Linksys WRT1900ACS using external storage? It pretty much shares the same hardware as listed as far as I can tel. It would be really nice if we could have something widely available in a case. WRT1900ACS and/or WRT1200AC? https://wikidevi.com/wiki/Linksys_WRT1900ACS https://wikidevi.com/wiki/Linksys_WRT1200AC_v2 These are also supported in LEDE (OpenWrt fork) if you need further information. Thanks in advance! Best regards, Daniel From owner-freebsd-arm@freebsd.org Fri Jul 7 13:10:57 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49E2CDA2FDD for ; Fri, 7 Jul 2017 13:10:57 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D8BDF79B01 for ; Fri, 7 Jul 2017 13:10:56 +0000 (UTC) (envelope-from jim@netgate.com) Received: by mail-lf0-x22a.google.com with SMTP id t72so23399555lff.1 for ; Fri, 07 Jul 2017 06:10:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DlyxDSYDEUEjdSNfWmNEPy9fmLjvDRtpRp4SPAsSgq0=; b=bu+Y1xwnqN7PGbIQzrBjrszo1aaRGVViuzw++ziBqGvivZVLuPU0cJm+R74pj6lLah /ZS2hTFUrUXxuQKrcekZHhgVTDQYMskcMoK14xyc6HyGAppQ9oNiYysTklAsPMp404V4 8K2W+wU8xVE7lypPJf7l0bGMfrlwpThiFZGdw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DlyxDSYDEUEjdSNfWmNEPy9fmLjvDRtpRp4SPAsSgq0=; b=bq6y4yauvlIEzWZWE10wM+SEOmKtleI+qg3fbO7sajuvLcCB2ZJyDNVdRBkjWYA+WP kaqu4dVxDR0p/xz43K4rU6/H8d941BMCpPw4zlD0eRxJTHwbZ1hxf/sWrXdRyN5Iw1V2 gXRhZ/TbQF+HYPPBqoqAh0mJhdA2tYjuh0x0ViS5rblEF0U5WoqKOvc/OCVmAwn0uwYa HKWUaEyAFdt2JpOB9RPcRHsjkfbIqF8I5SowYKMmuUBHlrX/nWDjrLZsA7prDGafGrG0 ceYVu8JYvXjNMI9RG2KWp8vdwHI+/v+LrBXxNtp7nd/LnyryU9AsJIMD9IHG/tZ8teS8 yhDg== X-Gm-Message-State: AIVw111+GD+H+n/fvjFLNn+Lw2mDkMZnEtSqS16rNegC22Cp/Psw5Aut 9pJVgrL+aPVfDyx0 X-Received: by 10.46.20.19 with SMTP id u19mr438672ljd.113.1499433054759; Fri, 07 Jul 2017 06:10:54 -0700 (PDT) Received: from [192.168.1.2] ([93.185.30.136]) by smtp.gmail.com with ESMTPSA id q90sm743974lfb.36.2017.07.07.06.10.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Jul 2017 06:10:53 -0700 (PDT) Mime-Version: 1.0 (1.0) Subject: Re: HEADS UP: Marvell Armada 38x support in the tree From: Jim Thompson X-Mailer: iPhone Mail (14F89) In-Reply-To: Date: Fri, 7 Jul 2017 16:10:52 +0300 Cc: freebsd-arm@freebsd.org Message-Id: References: To: Daniel Engberg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 13:10:57 -0000 > On Jul 7, 2017, at 2:56 PM, Daniel Engberg wrote: >=20 > It would be really nice if we could have something widely available in a c= ase. Both Stormshield and Netgate will be offering product based on Armada 38x.=20= Here is ours: https://www.netgate.com/blog/lord-vader-your-firewall-is-ready.html Jim=20= From owner-freebsd-arm@freebsd.org Fri Jul 7 14:11:03 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDDDFDA40CA for ; Fri, 7 Jul 2017 14:11:03 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 970967BAE2 for ; Fri, 7 Jul 2017 14:11:03 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-it0-x231.google.com with SMTP id m68so32459592ith.1 for ; Fri, 07 Jul 2017 07:11:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZUxsH0MJM1VxdjFq6E8PZ7T9ikI971pnzm4/wOuLve0=; b=bB28nEiXomT/YRkK8yF7tByj5AxVB4m7y+/cYcbNTuC0+sDh2o/RrmdfqUxq/squbp jWrsbtGOM6LHcAlmf43QyhOaPjbvebqwYOCLZNV5GqLTB4KMwsxCh4FWMUNKWhG4mfbF pGzDJZpuzjjl0gEDYxSd0+x03ekzSq+xb02TXDaK3KKswJ4XxKXVKNFTxfM7zPtiVRfT sspAsoDxfH49HBb/usuTNONUKr0FsLMwkMghUOl9CpHAZpQexM1KkzUzEKd9/VKr8b2X ocwkKKJHgByGXgAbaHE6u5m+tgssc3p2v9CB/FZYik9cOi8M3cYSppTwaXvXW8vF+fa8 faHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZUxsH0MJM1VxdjFq6E8PZ7T9ikI971pnzm4/wOuLve0=; b=Nq804TRMMWuvPdUMPvxKnRlAl9kK4KezfrCZJA0Kedwk7JMMfgvzjTnieg1MxxdOUl aN/tCl1NaGAmitmTHJ4i+uBrz2TYfYobnqJTEnuuM5A118tU9Y4vVDEW+fuBNlck3Quc 3YJ1NYok+Usw60R1SFlhgCLPjWmA5tB5fDO6YAaQsIBpQcUNa2xhwX5sWP7wpxZ2pTKd 87+AaZY3wuKzVI0PquaZ7qey1Slmn5ScwCEMfxdUiilBCKPv/W5YG6eVI6TuSxygZA+2 HlEVQ57G6V+YcaqcrlK76PEoErWyi6u4nUkseWLA0gl4o4COeDuPcB91fl2k1i8PDMjs N47g== X-Gm-Message-State: AKS2vOyrRVSM76pRU24zBdDVo3ygjUc0AXA9qgx1Ht1KKnnjNDaEMyd8 oP/HZoLFXe9HSY0naPItBmPtkQWZPPxP/zXb4g== X-Received: by 10.107.8.215 with SMTP id h84mr54063720ioi.69.1499436662790; Fri, 07 Jul 2017 07:11:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.151.16 with HTTP; Fri, 7 Jul 2017 07:11:02 -0700 (PDT) In-Reply-To: References: From: Marcin Wojtas Date: Fri, 7 Jul 2017 16:11:02 +0200 Message-ID: Subject: Re: HEADS UP: Marvell Armada 38x support in the tree To: Daniel Engberg Cc: freebsd-arm@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 14:11:03 -0000 Hi Daniel, 2017-07-07 13:56 GMT+02:00 Daniel Engberg : > Hi, > > Great work seeing this in the FreeBSD tree, many thanks to those involved > making this happen. > > This also made me interested in the possibility of running FreeBSD on > consumer hardware. > While I do understand that NAND support is still no available and also > WIFI would it possible to get FreeBSD running on a Linksys WRT1900ACS using > external storage? It pretty much shares the same hardware as listed as far > as I can tel. It would be really nice if we could have something widely > available in a case. > > WRT1900ACS and/or WRT1200AC? > > https://wikidevi.com/wiki/Linksys_WRT1900ACS > https://wikidevi.com/wiki/Linksys_WRT1200AC_v2 > Basing on the wiki sites and linux armada-385-linksys-cobra/shelby.dts from Linux, both devices should easily work (network, e6172 switch, sata, usb, pcie). NAND indeed is not supported, however you may use USB stick for the OS. PCIe ports should work, but I don't know 88W8864 WIFI controller support status in FreeBSD. Best regards, Marcin > > These are also supported in LEDE (OpenWrt fork) if you need further > information. > > Thanks in advance! > > Best regards, > Daniel >