Date: Mon, 22 Jul 2019 10:12:51 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Emmanuel Vadot <manu@bidouilliste.com> Cc: Ian Lepore <ian@freebsd.org>, arm@FreeBSD.org Subject: Re: 13-CURRENT snapshot 20190718 r350103 doesn't boot on BeagleBone White Message-ID: <20190722171251.GU2342@funkthat.com> In-Reply-To: <20190722102652.abde19a9fb609451cb618fde@bidouilliste.com> References: <20190721180510.GQ2342@funkthat.com> <415c9b4760029235cd62bf95a35a736f7566cb9d.camel@freebsd.org> <20190721205557.GR2342@funkthat.com> <20190722102652.abde19a9fb609451cb618fde@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Emmanuel Vadot wrote this message on Mon, Jul 22, 2019 at 10:26 +0200:
> On Sun, 21 Jul 2019 13:55:57 -0700
> John-Mark Gurney <jmg@funkthat.com> wrote:
>
> > 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...
>
> That would be a pain for the next updates.
Well, IMO, better than leaving a platform broken for months...
> > Or add an overlay that undoes the changes?
> >
> > I can do some testing...
>
> Could be possible but that will probably break in a few updates of the
> DTS files.
>
> We need a TI maintainer that's all.
I'd recommend we disconnect the builds then or something so that people
know not even to bother to try the images instead of wasting hours of
time trying to figure out what's wrong w/ the images...
At least then I'd post where's the images, and you would have replied
that things aren't working...
> > > 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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190722171251.GU2342>