RPi2 snapshot for armv7 won't boot.
Michal Meloun
melounmichal at gmail.com
Fri Nov 3 16:21:36 UTC 2017
On 02.11.2017 17:35, Kyle Evans wrote:
> On Thu, Nov 2, 2017 at 11:31 AM, Warner Losh <imp at bsdimp.com
> <mailto:imp at bsdimp.com>> wrote:
>
> On Wed, Nov 1, 2017 at 11:28 PM, Michal Meloun
> <melounmichal at gmail.com <mailto:melounmichal at gmail.com>>
> wrote:
>
> >
> >
> > On 02.11.2017 2:53, Kyle Evans wrote:
> > > On Nov 1, 2017 6:24 PM, "Mark Millard" <markmi at dsl-only.net
> <mailto:markmi at dsl-only.net>> wrote:
> > >
> > > On 2017-Nov-1, at 3:51 PM, Carl Johnson <carlj at peak.org
> <mailto:carlj at peak.org>> wrote:
> > >
> > >> I had previously tried to upgrade my RPi2 12.0-CURRENT system
> from armv6
> > >> to armv7, but it then refused to boot. This time I downloaded the
> > >> latest snapshot (r325156 from 20171030) and it also refuses to
> boot for
> > >> exactly the same reason. In every case the kernel loads, but
> then it
> > >> reports that init has died, and then panics and drops into kdb. It
> > >> gives a stack backtrace, but that doesn't mean anything to me.
> > >>
> > >> Is this just me, or is anybody else having this problem? If
> others have
> > >> the problem, is there some workaround to get it working?
> > >>
> > >> Thanks in advance for any ideas.
> > >
> > > Others are also seeing the problem, not just on
> > > RPI2's.
> > >
> > > It looks like it broke between:
> > >
> > > -r324743 and -r325156
> > >
> > > someplace relative to whatever is causing the
> > > init problem.
> > >
> > > Details that lead me to that conclusion, if
> > > you care. . .
> > >
> >
> > The r324938 breaks all statically linked binaries (init,
> /rescue/*, ...).
> > I have prepared patch, but I need a day or two for more testing on
> other
> > arches.
> >
> https://github.com/strejda/tegra/commit/67ea3325c50770b5031ef02882b2dc
> <https://github.com/strejda/tegra/commit/67ea3325c50770b5031ef02882b2dc>
> > cdd1f7611f
> >
> > Michal
>
>
> To be extra sure, have we tried to back out this one change against
> the tip
> of -head to confirm? It's pretty trivial.
>
> Warner
>
>
> For what it's worth: I didn't try backing out the change, but I can
> confirm that the above-mentioned patch does fix it -- I applied it just
> a bit ago.
I just committed this, so current after r325364 should be again usable.
Michal
More information about the freebsd-arm
mailing list