Ugh -- Pi2 problem that appears to have come from a roll-forward of microcode

[Karl Denninger]

I've seen this one before....

Some months back I started playing with newer bootcode and dtb files on
the RPI2, and rolled them back after running into serious problems with
the unit not always progressing beyond the "ue0" device probe.  That is,
the unit would get to the "ue0" line, print it, and then lock up.

^C was ineffective on the console and sometimes - but not always - after
a couple of minutes it would unlock.  The rest of the time, however, you
were dead unless you pulled power and restarted.

This is back on 11.STABLE builds, and it appears to be linked to the
roll-forward of the bootcode and DTB files that was somewhat-recently
committed.  I was forced to go back to the older files.

IMHO this needs some attention as a lockup during the device probe is a
bad thing, obviously.

-- 
Karl Denninger
karl at denninger.net <mailto:karl at denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4897 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20171220/2e3da869/attachment.bin>