Date: Fri, 21 Feb 2020 05:21:08 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: =?utf-8?Q?No_ufs_remount=3A_panic=60=C3=ACng_aarch64_boot_from_SD?= =?utf-8?Q?-card_vfs=5Fmountroot?= Message-ID: <075ED1FC-CF15-406D-B5E1-F23AFB93FD8B@googlemail.com>
next in thread | raw e-mail | index | archive | help
panic`=C3=ACng aarch64 boot from SD-card since approx. 1-2 weeks on head =
13-current:
I could `make installkernel`for months on many boards without =
problems=E2=80=A6
Now panics, whereas 'boot boot / kernel.old' continues to be able to =
boot,
regardless of submarine version or dtb / dts.
Well, something significantly must have been changed the last days / =
weeks in GEOM / vfs / mount_ufs
or elsewhere ...
Just a "wild guess" (because of the many changes in that area in src):
--The mountroot issue began with -r356776-- .. just a guess (because =
that happened on RPI4)
This output is from r358133-xyimage.xz fresh installed / downloaded =
SD-card ( dd`d zero-cleaned with / dev / zero before) (RockPro64)=E2=80=A6=
No way to boot with 'ufs: / dev / mmcsd0xxx', `tried every possible =
combination:
=E2=80=94output----
Loader variables:
vfs.root.mountfrom=3Dufs:/dev/ufs/rootfs
vfs.root.mountfrom.options=3Drw
Manual root filesystem specification:
<fstype>:<device> [options]
Mount <device> using filesystem <fstype>
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:zroot/ROOT/default
cd9660:/dev/cd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
<empty line> Abort manual input
mountroot> ?
List of GEOM managed disk devices:
=20
mountroot> =E2=80=9EEnter"
mountroot> filesystem specification:
panic: mountroot: unable to (re-)mount root.
cpuid =3D 0nt <device> using filesystem <fstype>
time =3D 105with the specified (optional) option list.
KDB: stack backtrace:
db_trace_self() at db_trace_self_wrapper+0x28
pc =3D 0xffff000000750e2c lr =3D 0xffff000000106bc8
sp =3D 0xffff00004027b370 fp =3D 0xffff00004027b580
(which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
db_trace_self_wrapper() at vpanic+0x194
? pc =3D 0xffff000000106bc8 lr =3D 0xffff00000040e0ac
. sp =3D 0xffff00004027b590 fp =3D 0xffff00004027b640
<empty line> Abort manual input
vpanic() at panic+0x44
mountroo pc =3D 0xffff00000040e0ac lr =3D 0xffff00000040de54
sp =3D 0xffff00004027b650 fp =3D 0xffff00004027b6d0
List of GEOM managed disk devices:
panic() at vfs_mountroot+0x1558
pc =3D 0xffff00000040de54 lr =3D 0xffff0000004d795c
mountroo sp =3D 0xffff00004027b6e0 fp =3D 0xffff00004027b880
vfs_mountroot() at start_init+0x28
pc =3D 0xffff0000004d795c lr =3D 0xffff0000003a3e44
sp =3D 0xffff00004027b890 fp =3D 0xffff00004027b940
start_init() at fork_exit+0x7c
pc =3D 0xffff0000003a3e44 lr =3D 0xffff0000003cb7fc
sp =3D 0xffff00004027b950 fp =3D 0xffff00004027b980
fork_exit() at fork_trampoline+0x10
pc =3D 0xffff0000003cb7fc lr =3D 0xffff00000076e514
sp =3D 0xffff00004027b990 fp =3D 0x0000000000000000
KDB: enter: panic
[ thread pid 1 tid 100002 ]
Stopped at 0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?075ED1FC-CF15-406D-B5E1-F23AFB93FD8B>