Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Nov 2017 11:23:27 -0200
From:      "Dr. Rolf Jansen" <rj@obsigna.com>
To:        freebsd-arm@freebsd.org
Subject:   Re: RPi2 snapshot for armv7 won't boot.
Message-ID:  <3F969D4C-1399-45C1-ACCC-02FC937CD388@obsigna.com>

next in thread | raw e-mail | index | archive | help
> On Nov 1, 2017 5:51 PM, "Carl Johnson" <carlj at peak.org> wrote:
>=20
> 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.
>=20
> Is this just me, or is anybody else having this problem?  If others =
have
> the problem, is there some workaround to get it working?
>=20
> Thanks in advance for any ideas.

I just ran into the same issue after updating my Beaglebone Black using =
the latest ARMv7 12.0-CURRENT snapshot from October, 30th (see the =
respective excerpt of the log from serial console below).

I didn't have time for a full rollback, and I only replaced the =
/sbin/init binary with the one from the previous ARMv7 snapshot from =
October, 19th. This resolved the booting issue of the BBB, however, I am =
not too much convinced that there are no other issues, and before doing =
anything serious with it, I will do a complete rollback.

Best regards

Rolf

...
WARNING: WITNESS option enabled, expect reduced performance.
Trying to mount root from ufs:/dev/ufs/SYSTEM [rw,noatime]...
Warning: no time-of-day clock registered, system time will not be set =
accurately
init died (signal 0, exit 1)
panic: Going nowhere without my init!
cpuid =3D 0
time =3D 1509627241
KDB: stack backtrace:
db_trace_self() at db_trace_self
	 pc =3D 0xc055d8b4  lr =3D 0xc005ed40 =
(db_trace_self_wrapper+0x30)
	 sp =3D 0xcd1f7c00  fp =3D 0xcd1f7d18
db_trace_self_wrapper() at db_trace_self_wrapper+0x30
	 pc =3D 0xc005ed40  lr =3D 0xc0269984 (vpanic+0x158)
	 sp =3D 0xcd1f7d20  fp =3D 0xcd1f7d40
	 r4 =3D 0x00000100  r5 =3D 0x00000001
	 r6 =3D 0xc06a08bb  r7 =3D 0xc0927530
vpanic() at vpanic+0x158
	 pc =3D 0xc0269984  lr =3D 0xc02699f4 (kproc_shutdown)
	 sp =3D 0xcd1f7d48  fp =3D 0xcd1f7d4c
	 r4 =3D 0xc2ce9000  r5 =3D 0x00000000
	 r6 =3D 0x00000001  r7 =3D 0x00000000
	 r8 =3D 0x00000000  r9 =3D 0xc2cf2000
	r10 =3D 0xc2cf2000
kproc_shutdown() at kproc_shutdown
	 pc =3D 0xc02699f4  lr =3D 0xc022ba8c (exit1+0xde8)
	 sp =3D 0xcd1f7d54  fp =3D 0xcd1f7da8
	 r4 =3D 0xc02699f4  r5 =3D 0xcd1f7d54
exit1() at exit1+0xde8
	 pc =3D 0xc022ba8c  lr =3D 0xc022aca4 (exit1)
	 sp =3D 0xcd1f7db0  fp =3D 0xcd1f7db0
	 r4 =3D 0x00000001  r5 =3D 0xc081a0e4
	 r6 =3D 0xc2ce9000  r7 =3D 0x00000000
	 r8 =3D 0x00000000  r9 =3D 0xc2cf2000
	r10 =3D 0xc2cf2290
exit1() at exit1
	 pc =3D 0xc022aca4  lr =3D 0xc0580aac (swi_handler+0x2c4)
	 sp =3D 0xcd1f7db8  fp =3D 0xcd1f7e40
	 r4 =3D 0xc2ce9000  r5 =3D 0x00000000
	 r6 =3D 0x00000000  r7 =3D 0xc2cf2000
	 r8 =3D 0xc2cf2290  r9 =3D 0xcd1f7db0
	r10 =3D 0xc022aca4
swi_handler() at swi_handler+0x2c4
	 pc =3D 0xc0580aac  lr =3D 0xc0560284 (swi_exit)
	 sp =3D 0xcd1f7e48  fp =3D 0xbfbfee20
	 r4 =3D 0x00000001  r5 =3D 0xbfbfee28
	 r6 =3D 0x00000000  r7 =3D 0x00000001
	 r8 =3D 0xbfbfeec4  r9 =3D 0x0011c1d0
	r10 =3D 0xbfbfeed0
swi_exit() at swi_exit
	 pc =3D 0xc0560284  lr =3D 0xc0560284 (swi_exit)
	 sp =3D 0xcd1f7e48  fp =3D 0xbfbfee20
KDB: enter: panic
[ thread pid 1 tid 100001 ]
Stopped at      $d.3:   ldrb    r15, [r15, r15, ror r15]!



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F969D4C-1399-45C1-ACCC-02FC937CD388>