16:56 <tlwoerner> thanks to the previous advice from robmur01 i switched all my builds to use UUIDs instead of hard-coding which block device to check for the root filesystem

16:57 <tlwoerner> all my rockchip boards work great… except my nanopi-m4

16:57 <tlwoerner> on that board i end up with "error -110 whilst initialising SD card"

16:57 <tlwoerner> interestingly enough, if i eject my uSD card and re-insert it at that point, everything magically works and the boot continues

16:59 <tlwoerner> this is on 5.14.6, urja reports a similar (same?) problem with veyron with 5.15-rc3 (although is unable to try to eject/reinsert trick)

17:00 <tlwoerner> i'll start a bisection to see what turns up, unless anyone has any suggestions

17:00 <urja> the thing is, 5.14.x boots fine for me (5.15-rc3 + patches for pinctrl to have it boot gets me to -110 for the eMMC.... the µSD gets detected okay)

17:01 <tlwoerner> okay, so probably not the same issue

17:02 <tlwoerner> my nanopi-m4 has an optional eMMC slot, but i haven't populated it

17:02 <tlwoerner> i also get a bunch of other error messages

17:02 <tlwoerner> mmc1: problem reading SD Status register

17:03 <tlwoerner> and lots of complaints about bus speeds (requested vs actual etc)

17:04 <tlwoerner> it's curious to me that reinserting the µSD card "fixes" the problem :-)

17:04 <urja> https://urja.dev/nextcloud/index.php/s/knei2Ayw2gafpCo/preview here's what the veyron-speedy 5.15-rc3 boot looks like (literally looks like as i dont have serial attached now)

17:05 <urja> anyways i thiink the req vs actual is not really really an error per se, just diagnostics (usually it hits dead on or is a bit slow because that's how the dividers end up)

17:09 <tlwoerner> i don't know if this is related, but between it not working and it working the following shows up on my console:

17:09 <tlwoerner> vcca0v9_s3: disabling

17:09 <tlwoerner> vcca1v8_s3: disabling

17:18 <tlwoerner> here's mine: https://paste.ee/p/Xnimd

17:20 <tlwoerner> it's also possible that i'm missing a config? (like i was with my rock64) i'm just using the in-kernel arm64 defconfig

17:21 <tlwoerner> however, i had no issues with this board prior to.. 5.13 (?) or maybe it was 5.10

17:21 <tlwoerner> anyway, starting my bisect now

17:27 <urja> hmm... i hadn't considered bisect for this yet, maybe i'll figure out a way tomorrow (it's just ... not what my build system setup was meant for... like at all... add to that the 1 or 3 patches one needs to add at every step (1 or 3 depending on where...) ... yeah thunking about it)

22:07 <punit> I've been away for a few days and was wondering if there's been any further progress on the rk3399 ethernet issue.

22:09 <punit> IIRC, mmind00 suggestion to partially revert the offending commit made things move again..