On 2017-Dec-12, at 2:02 PM, Andreas Schwarz <freebsd.asc at strcmp.org> wrote:
> On 12.12.17, Mark Millard wrote:
>> I initially jumped from -r326192 to -r326726 and
>> ended up with a rpi2 that would normally hang
>> somewhere around release APs being displayed.
>> (I have had a couple of completed boots but many
>> dozens of hung-up attempts.) Both a debug kernel
>> and a non-debug kernel hang the same way.
>> Bisecting the kernel (holding world -r326726
>> constant) showed:
>> -r326346 did not hang (nor did before)
>> -r326347 and later hung.
> JFYI, the latest kernel (and world) running at one of my
> RPI2-B is r326631, without any issues.
Interesting. (By the way: My context
is with a V1.1 Cortex-A7 based rpi2,
not V1.2 and Cortex-A53.)
I've almost always run the root file
system being on a USB SSD instead of
on mmcsd0 . I wonder if that is
somehow involved since it may be
unusual. UFS file system.
The USB SSD is on a powered hub that
is in turn plugged into the rpi2.
[I had the hang problem before the
following and after.]
The mechanism for holding mmcsd0 in
failed recently but the ejection
mechanism still works. So I hold
in mmcsd0 until after I get a USB
SSD boot now. (Interrupt boot, unload,
boot/autoboot, picks up the kernel
from the USB SSD.)
This means that I effectively can
not avoid the USB SSD any more
unless I get my hands on a different
markmi at dsl-only.net
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"