From owner-freebsd-arm@freebsd.org Sun Jul 21 20:56:18 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 2EAE1BE0FD for ; Sun, 21 Jul 2019 20:56:18 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 644376BFDF for ; Sun, 21 Jul 2019 20:56:17 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.nyi.freebsd.org (Postfix) id 631A2BE0F1; Sun, 21 Jul 2019 20:56:17 +0000 (UTC) Delivered-To: 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 62B6BBE0F0 for ; Sun, 21 Jul 2019 20:56:17 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A1B66BFBB; Sun, 21 Jul 2019 20:56:01 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id x6LKtvJo024889 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Jul 2019 13:55:57 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id x6LKtvHZ024888; Sun, 21 Jul 2019 13:55:57 -0700 (PDT) (envelope-from jmg) Date: Sun, 21 Jul 2019 13:55:57 -0700 From: John-Mark Gurney To: Ian Lepore Cc: arm@FreeBSD.org Subject: Re: 13-CURRENT snapshot 20190718 r350103 doesn't boot on BeagleBone White Message-ID: <20190721205557.GR2342@funkthat.com> Mail-Followup-To: Ian Lepore , arm@FreeBSD.org References: <20190721180510.GQ2342@funkthat.com> <415c9b4760029235cd62bf95a35a736f7566cb9d.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <415c9b4760029235cd62bf95a35a736f7566cb9d.camel@freebsd.org> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sun, 21 Jul 2019 13:55:58 -0700 (PDT) X-Rspamd-Queue-Id: 2A1B66BFBB X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] 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, 21 Jul 2019 20:56:18 -0000 Ian Lepore wrote this message on Sun, Jul 21, 2019 at 12:31 -0600: > On Sun, 2019-07-21 at 11:05 -0700, John-Mark Gurney wrote: > > The microSD card that I was using on my BeagleBone white got > > corrupted, > > so I decided to update to the latest version. The latest snapshot > > fails > > to boot. It loads the kernel, but then when starting the kernel, it > > hangs, and eventually it will reset. > > > > The latest 12 snapshot boots fine: BEAGLEBONE-20190718-r350087. > > > > Any ideas? I tried all three available 13 snaps, and they all behave > > the same. > > > > This happened with the latest DTS import (which was months ago). A > couple people have speculated that we just need a trivial do-nothing > driver for the new ti,sysc device, but when I tried that a couple > months ago it didn't work, so instead I just reverted sys/dts to the > old source and got on with what I needed to do. Can we revert the dts in the tree then? Doesn't help when we know the fix, but don't apply it... Or add an overlay that undoes the changes? I can do some testing... > This is just the latest in a years-long string of breakages because the > linux TI folks just never stop tinkering with their device-tree source. > I'm sure they're doing it because it gets them some benefits, but for > us the changes add no value and have a high maintenance cost. A hang > before the copyright banner appears is especially painful to debug > (doubly so because there's no existing EARLY_PRINTF support in the ti > code). [...] -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."