Guest15217 has quit [Read error: Connection reset by peer]
warpme has joined #linux-sunxi
<spawacz>
I'm using Debian's stock kernel, the only configs that have been enabled between 6.13-rc7 and 6.13.8 (there are no more intermediate prebuilt ones) are CONFIG_THEAD_TH1520_MBOX, CONFIG_DWMAC_THEAD, CONFIG_THEAD_C900_ACLINT_SSWI. May that be teh cause?
<spawacz>
I think I'll build kernel on my own to check it
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
warpme has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
<apritzel>
spawacz: what is the effect of "does not boot"? No output at all, or hangs somewhere in the middle, or crashes?
<spawacz>
hard reboot few seconds after kernel starts. I see sometimes none, sometiems 50 dmesg messages
hentai has quit [Read error: Connection reset by peer]
<apritzel>
spawacz: could that be a watchdog issue? I remember we had to disable it in U-Boot, since the max period is 16 seconds, which is too short to reach the Linux driver, typically, and the UEFI spec says it must be longer anyway
<spawacz>
that sounds like black magic, what should I try?
<apritzel>
that's from 2021, so predates your U-Boot version, but I see "WDT: Started watchdog@6011000 with servicing every 1000ms (16s timeout)" in your log
<apritzel>
it might be due to the confusion of ARCH_SUNXI being ARM specific, IIRC smaeul_ defined a different symbol to use for RISC-V? Which means this patch wouldn't work
<spawacz>
what does it mean "to reach Linux driver"? I'm not a hardware guy
<spawacz>
at what point is it reached?
<apritzel>
U-Boot programs the watchdog, to reset the system in 16 seconds, unless reset (periodically) by some code. While you are in U-Boot, this should be taken care of, but when you boot the kernel, the kernel must take over this chore
<spawacz>
hmm but if I wait in grub for long time, it does not reboot
<apritzel>
which means you a) need the watchdog driver in the kernel, and b) it must load and activate before those 16 seconds elapse
<apritzel>
grub runs as an UEFI boot service, so U-Boot would still be in charge
<apritzel>
I guess you compiled U-Boot yourself? Then just disable CONFIG_WATCHDOG_AUTOSTART manually in your config, for instance, or put that in your _defconfig file
<spawacz>
I'll try. Btw it takes 30 seconds +- from the moment i select the kernel in grub until first dmesg message pops up
<apritzel>
"select the kernel in grub" means selecting a menu entry? That would then first trigger the load, I guess, which is extra slow due to a bug in the MMC clock code we recently fixed: