From owner-freebsd-arm@freebsd.org Tue Jul 16 00:38:47 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 58291C7EE4 for ; Tue, 16 Jul 2019 00:38:47 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [18.222.6.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E9FB87E84 for ; Tue, 16 Jul 2019 00:38:46 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (unknown [18.188.142.31]) by mail.soaustin.net (Postfix) with ESMTPSA id 0C2A01FCE1; Tue, 16 Jul 2019 00:38:46 +0000 (UTC) Date: Tue, 16 Jul 2019 00:38:44 +0000 From: Mark Linimon To: Dennis Clarke Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD 11.3-RELEASE and 11.2-RELEASE images fail to boot on BeagleBone Black Message-ID: <20190716003844.GB19462@lonesome.com> References: <8352f841-0522-9f45-148d-d2948e97857e@gmail.com> <20190713152404.GJ1503@dendrobates> <6b3dcec02b425a8559605b4e6c5ada19ee642728.camel@freebsd.org> <20190713194256.GK1503@dendrobates> <85e35455-793a-84fe-c8cf-39b89ade7c11@gmail.com> <26864b34-624a-075f-4a10-859314649d2f@blastwave.org> <20190714172816.GA26897@lonesome.com> <3e91570f-69b4-1d29-ada9-bd13d42e236a@blastwave.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3e91570f-69b4-1d29-ada9-bd13d42e236a@blastwave.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Rspamd-Queue-Id: 0E9FB87E84 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-0.53 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.53)[-0.535,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.44)[0.442,0]; IP_SCORE(-0.25)[ip: (0.03), ipnet: 18.220.0.0/14(0.14), asn: 16509(-1.34), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[lonesome.com]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.88)[-0.883,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[11.6.222.18.list.dnswl.org : 127.0.5.2]; RCPT_COUNT_TWO(0.00)[2]; MX_GOOD(-0.01)[cached: mail.soaustin.net]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16509, ipnet:18.220.0.0/14, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2019 00:38:47 -0000 On Mon, Jul 15, 2019 at 08:29:06PM -0400, Dennis Clarke wrote: > Essentially one may checkout the sources and do a clean build only to > see the kernel panic on ppc64 hardware. I don't understand. What hardware? We are doing a lot of work on Power8 and Power9 hardware from various manufacturers, and both 12 and -CURRENT behave well, even under stress. (I have powered down my Power5 machine; I know of two cases where I cannot move to 12.X, and since I have Power9 in-house, I probably will not pursue it.) > Strangely I have [a RISC-V] instance that boots neatly inside a qemu > vm and that even includes a ZFS zpool. If you've built ports on it, you may be the first. You are definitely at the bleeding edge in this case. I know of no user documentation for FreeBSD/RISC-V. mcl