@lcard - That's good to hear. Also your previous post provided some valuable information. So much thanks for the info/update.
For full disclosure, I found that my eMMC chip is probably the same as Sagittarius'. When I peeled off the red sticker, I found that it was actually a 5.1 HS400 and was not the chip advertised on Ameridroid (i.e. I'm guessing they simply stuck a red sticker on their "black" chip). So when you couple that with your info that some eMMC chips work and others don't, my total guess is that it's these newer/faster chips that have the problem.
Now... perhaps the bigger issue is that the BayLibre folks that are doing most of the Amlogic heavy lifting for the mainline kernel seem to have very few eMMC chips, and I'm guessing none of these faster ones.
After I reported this issue upstream, they had me try their latest (unshipped) kernel, but it still failed. After reporting this result to them, there's been nothing but radio silence.
Their lack of eMMC chips is a shame because they've created a wonderful test environment that would probably catch this type of problem early:
https://baylibre.com/intro-kernelci/
https://www.youtube.com/watch?v=kSe5GMJvqOI
Reviewing these ODroid C2 test results at https://kernelci.org/stats/, I've not found any tests that are using an eMMC chip, but I didn't check them all.
But I've been intermittently following BayLibre's kernel changes and there are a ton of them (these few folks are very busy):
https://git.kernel.org/pub/scm/linux/ke ... mlogic.git
There are many code changes near our problem area (pin bias) scheduled for the 5.3 release. But I (and probably they,) don't know if it's going to fix this issue for those of us with these chips.
Here's their mailing list if you want to follow along:
http://lists.infradead.org/mailman/list ... ux-amlogic
Possibly the best, in the near and long term, would be for some kind soul to donate eMMC chip(s) to these BayLibre folks. I currently don't have the funds or I would.
Also, I think it's highly admirable to tackle a kernel compile, but I've been bypassing that by simply using the "dtc" utility to disassemble the /boot/dtbs/amlogic/meson-gxbb-odroidc2.dtb file, then editing the result, and recompiling. But it's a personal choice, and there are multiple options.