07:55 <plaes> c

16:29 <zavorka> Hello. When I try to boot 5.16 (5.13+) kernel on my A64 board, it gets stuck on 'Waiting for root device /dev/mmcblk0p1...' unless fw_devlink is disabled. Also, I had to enable 'earlycon' to see any output.

16:29 <zavorka> Except for cfg80211 and brcmfmac, all drivers are built into the Image.

16:30 <zavorka> Is this expected?

16:54 <jernej> zavorka: try adding status = "disabled"; to mbus node

17:28 <zavorka> jernej: yeah, I found your thread on the linux-kernel mailing list. Disabling the node has, however, no effect. Perhaps having the `pr_debug` statements printed will shed some more light on where it gets stuck

17:30 <jernej> I think you can find reason why drivers didn't probe somewhere in sysfs, I guess under /sys/kernel/debug

18:10 <zavorka> jernej: Yes, but sysfs can only be accessed once the kernel boots.

18:10 <jernej> ah, true

18:11 <jernej> based on my experience, easiest way to debug this is to disable drivers which you think caused the issue

18:11 <jernej> there is rarely any useful output

18:12 <apritzel> zavorka: are you supplying a specific root= device? And the numbering does not match the kernel's enumeration?

18:13 <apritzel> also: can you try "rootwait" on the command line? At least in the past this was sometimes needed, because the kernel was too impatient

18:15 <zavorka> jernej: fortunately, `pr_debug` did help a ton. I had CONFIG_RTC_DRV_SUN6I disabled, hence 'platform 1c20000.clock: error -EPROBE_DEFER: supplier 1f00000.rtc not ready'.

18:15 <jernej> oh, you don't want to disable RTC driver for Allwinner SoCs :)

18:16 <jernej> it provides pretty important clock

18:16 <jernej> so issue solved?

18:20 <zavorka> Ah, yes. I didn't realize until now that the RTC actually provides those clocks

18:20 <zavorka> Yes, that was it