From owner-freebsd-arm@freebsd.org Sun Jul 14 16:04:36 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D83AC15E546C for ; Sun, 14 Jul 2019 16:04:35 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2572875EA3 for ; Sun, 14 Jul 2019 16:04:34 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1563120273; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=cT2Ll+kX7PG2KwVp3oUC8LZ+LDuzuTtwPVQ5GQaFtF+aYDvakz7rf7cBPWuPcGdmG+7NUXvRwQ4hi N4Pqf3XEGmGHvater6lBg90CO8TCr+tS+7VhH/tz3/YJdplJedzgz9V3//iblofY4HSC93FXxOkDUI L7tf1xAfeoridIvsML/uHT71ZohE45uSYiLgeO54kljNMWiHjIlemt5Yn6LBGTcy5oKC+wycKb0Vug MANv0iYezSAQKMnfPLvoHzFlXXzrDo0tSbGeg4fVMSZxW43CWgQgkmzamOUdM2kKcGvGt7pwM2Dcoc RurtVnYUQY6Ctn11U2zStvjCVSePmzw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=mYd2d/2akOP3WPmPRCxrb4bgg/mXPBbYEbcMXjfj8L8=; b=SkCMEGuIqH+c7fYnE+YX3GR5HbX3v8cOCDXFMPPwnIsQEboPws+NA8XIYVvMIIUZtSw/cM4a9MzVg pkznRD5Ih16sUGftjk6qpwzQyxor9WDVjXiEvLfBkJnATJoO81+WTrbYWX3TCsAKkkIQPOEiDGWsqD sqTAAni2tD7H+F7WiEF8GrsqyJmzzP3obc2tfJ34h2EROZh5gaq1/gQ0V+Q/m1brwh7sXimgEMuMNV Uv374rcs87vxpNQkMa+rkaKmv47a7qkJoCJKou/UDv+vScFcfat8EkXFKavK3n04JjBGOdX3mxzTZh iDSX8JhhEwWAFtY2oFZPmFSvlK3bGWg== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=mYd2d/2akOP3WPmPRCxrb4bgg/mXPBbYEbcMXjfj8L8=; b=myJK4rSFIXOspO1y3irMazwnH+3VqCdxxeXUa8IjJjxpK82s/3Pcv8+HNTlKdmumS/90/w+w1ywMQ 8YZWhKGxwaNYHaciUI7phUi9WiHXyZQcmTJLUA7uUyiHYAWRsGxX277HNtHv5ooUij2xTPs0sU2wkQ NNiO6qghkAfQ/j5i1wKI8EggAwabEMGEzsHdBD7wmKzVVmt+KbxaHO98gbsezfWqfdLEC2GnxcNIr1 9CiiHDS96KiItjJ6vLatL4627bbRpYusEMBMeL+kxpz5WKQLxrGFgILBTcKtXDiXkN+nz7/qN9eg4l 85IeokHh2FOzAntaBsCnorFxaAVG0Uw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 102854d1-a651-11e9-907a-1ba68abff17b X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 102854d1-a651-11e9-907a-1ba68abff17b; Sun, 14 Jul 2019 16:04:32 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x6EG4U34028978; Sun, 14 Jul 2019 10:04:30 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <900bc3467c7e28f58e8e6cf17e881bdefcb3b751.camel@freebsd.org> Subject: Re: FreeBSD 11.3-RELEASE and 11.2-RELEASE images fail to boot on BeagleBone Black From: Ian Lepore To: Denis Polygalov , Sergey Manucharian Cc: freebsd-arm@freebsd.org Date: Sun, 14 Jul 2019 10:04:30 -0600 In-Reply-To: <85e35455-793a-84fe-c8cf-39b89ade7c11@gmail.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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 2572875EA3 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.994,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] 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: Sun, 14 Jul 2019 16:04:36 -0000 On Sun, 2019-07-14 at 10:34 +0900, Denis Polygalov wrote: > Does FreeBSD-12.0-RELEASE-arm64-aarch64-PINE64.img.xz works > out of the box or only it's bleeding edge snapshot? Right there, I think, is the root of your confusion. FreeBSD-NN- RELEASE is not bleeding edge. In fact, it's the exact opposite of that, it's a moment frozen in time that will never change again, so if it's broken, it will be broken forever. That's why I've talked several times in terms of "weekly snapshots" and "12-STABLE" which is NOT 12-RELEASE. For any given freebsd "release" it's kinda likely, sad to say, that one or several or even all the arm boards are broken. Then, the weekly snapshot that comes out for the corresponding -STABLE branch the week after the release may be fixed and work just fine. Such is life for a tier-2 platform. Two or three years ago it looked like arm was at the point where it should be a tier-1 platform, and I put a lot of effort into things like testing releases, because releases that actually work seem like an important thing for a tier-1 platform. Eventually it became clear to me that arm was never going to be a tier- 1 platform in freebsd. We had met all the requirements as near as I could tell, but no matter how many times it was brought up, it just got ignored. Politics or something, I guess, I dunno. But it was 100% demotivating, and so now I put 0% effort into things like worrying about whether something-RELEASE actually works. -- Ian