On 2020-11-22, Vagrant Cascadian wrote: > On 2020-11-22, Benedikt Spranger wrote: >> after a fresh install of Debian "bullseye" the first reboot got stuck >> after "Starting kernel ..." ... >> U-Boot 2020.10+dfsg-1+b1 (Nov 19 2020 - 03:18:11 +0000) Allwinner >> Technology ... >> Scanning mmc 1:1... >> Found U-Boot script /boot.scr >> 2225 bytes read in 2 ms (1.1 MiB/s) >> ## Executing script at 4fc00000 >> 22744944 bytes read in 1003 ms (21.6 MiB/s) >> 28403 bytes read in 5 ms (5.4 MiB/s) >> 30071341 bytes read in 1326 ms (21.6 MiB/s) >> Booting Debian 5.9.0-2-arm64 from mmc 1:1... >> Moving Image from 0x40080000 to 0x40200000, end=41850000 >> ## Flattened Device Tree blob at 4fa00000 >> Booting using the fdt blob at 0x4fa00000 >> EHCI failed to shut down host controller. >> Loading Ramdisk to 48352000, end 49fffa2d ... OK >> Loading Device Tree to 0000000048348000, end 0000000048351ef2 ... OK >> >> Starting kernel ... ... > I'll test on a few of my systems to see if I can reproduce the issue.
I can confirm similar behavior on a pinebook, although the kernel does boot and actually load, and eventually displays on the LCD display (if I "setenv console" from u-boot commandline). It even responds appropriately to ctrl-alt-delete, so it is not a completely hung kernel... It definitely gets as far as the initrd for me, as setting break=top in the boot arguments stalls out with a blank screen, and setting break=premount it actually manages to load the LCD and keyboard drivers ... and then stalls out before giving me a shell where it would be easier to do some actualy debugging... :/ So I doubt it is u-boot misbehaving, but have not yet identified where exactly the problem is... though I have some suspicions in the boot script and thus flash-kernel. live well, vagrant
signature.asc
Description: PGP signature
