Re: No ufs remount: panic`ìng aarch64 boot from SD-card vfs_mountroot

[Warner Losh]

On Thu, Feb 20, 2020, 9:21 PM Klaus Küchemann via freebsd-arm <
freebsd-arm at freebsd.org> wrote:

> panic`ìng 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…
> 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)…
> No way to boot with 'ufs: / dev / mmcsd0xxx', `tried every possible
> combination:
>
>
> —output----
> Loader variables:
>   vfs.root.mountfrom=ufs:/dev/ufs/rootfs
>   vfs.root.mountfrom.options=rw
>
> 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:
>
>
> mountroot>  „Enter"
> mountroot>  filesystem specification:
> panic: mountroot: unable to (re-)mount root.
> cpuid = 0nt <device> using filesystem <fstype>
> time = 105with the specified (optional) option list.
> KDB: stack backtrace:
> db_trace_self() at db_trace_self_wrapper+0x28
>          pc = 0xffff000000750e2c  lr = 0xffff000000106bc8
>          sp = 0xffff00004027b370  fp = 0xffff00004027b580
>           (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /)
> db_trace_self_wrapper() at vpanic+0x194
>   ?      pc = 0xffff000000106bc8  lr = 0xffff00000040e0ac
>   .      sp = 0xffff00004027b590  fp = 0xffff00004027b640
>   <empty line>    Abort manual input
> vpanic() at panic+0x44
> mountroo pc = 0xffff00000040e0ac  lr = 0xffff00000040de54
>          sp = 0xffff00004027b650  fp = 0xffff00004027b6d0
> List of GEOM managed disk devices:
> panic() at vfs_mountroot+0x1558
>          pc = 0xffff00000040de54  lr = 0xffff0000004d795c
> mountroo sp = 0xffff00004027b6e0  fp = 0xffff00004027b880
>
> vfs_mountroot() at start_init+0x28
>          pc = 0xffff0000004d795c  lr = 0xffff0000003a3e44
>          sp = 0xffff00004027b890  fp = 0xffff00004027b940
>
> start_init() at fork_exit+0x7c
>          pc = 0xffff0000003a3e44  lr = 0xffff0000003cb7fc
>          sp = 0xffff00004027b950  fp = 0xffff00004027b980
>
> fork_exit() at fork_trampoline+0x10
>          pc = 0xffff0000003cb7fc  lr = 0xffff00000076e514
>          sp = 0xffff00004027b990  fp = 0x0000000000000000
>
> KDB: enter: panic
> [ thread pid 1 tid 100002 ]
> Stopped at      0
>

Is mmcsd0 probed?

Warner

_______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>