Comment 42 for bug 1818407

Tried with the latest "generic" kernel, i.e. 5.2.11.

Once you reproduced it, reboot setting eMMC Max Speed to HS200, and run:
   journalctl -kb -1 | nc termbin.com 9999
to post your kernel log from the last but one (-1) boot (the one where
the eMMC failed) to termbin.com. Then send along the termbin.com URL
that was returned on the terminal and update your bug report with your
new findings (affected mainline kernel version).

It doesn't seem to show the failed boot. Perhaps this is due to not being able to access the eMMC?

Attaching photos of the display.

Attached is 1 of 2.