[bug] linux-aarch64-5.8.0-1 does not start on rock64 board

[mbakhterev]

Subject. UART log is following

$this->bbcode_second_pass_code('', 'DDR version 1.06 20170424
In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 127
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=14800MB
FwPartOffset=2000 , 2000
SdmmcInit=0 2
StorageInit ok = 20837
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x8b0ec
RunBL31 0x10000

NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 09:28:45, May 31 2017
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9


U-Boot 2018.03-1 (Apr 02 2018 - 19:14:47 -0600) Arch Linux ARM

Model: Rockchip RK3328 EVB
DRAM: 4 GiB
MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment

Failed (-5)
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Rockchip RK3328 EVB
Net:
Warning: ethernet@ff540000 (eth0) using random MAC address - ea:2f:54:3a:3b:6d
eth0: ethernet@ff540000
Hit any key to stop autoboot: 2  1  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
1269 bytes read in 17 ms (72.3 KiB/s)
## Executing script at 00500000
37171712 bytes read in 29273 ms (1.2 MiB/s)
50174 bytes read in 50 ms (979.5 KiB/s)
8102566 bytes read in 6588 ms (1.2 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to fc762000, end fcf1c2a6 ... OK
reserving fdt memory region: addr=1f00000 size=d000
Loading Device Tree to 00000000fc752000, end 00000000fc761fff ... OK

Starting kernel ...')

[gerardr]

I also have a Rockchip Armv8 device, but with the Rockchip RK3399, a Samsung Chromebook Plus (Kevin-gru).

The new 5.8 /boot/vmlinux.kpart is now greater in size than the 32MB Kernel partition the installation instructions suggest, so now there is about 4MB of vmlinux.kpart that cannot be copied into the kernel boot partition.

However, I took my backup micro-SD card, and rebuilt the partitions with a 48MB Kernel boot partition and the chromebook still won't boot, so perhaps there's another issue within vmlinux.kpart. Both Kernel partitions start at the same sector, the new one a bit longer, making the new Root partition just a bit smaller.

For me, the relevant package is 'linux-aarch64-chromebook-5.8.0-1-aarch64.pkg.tar.xz'.

Using the Chrome OS shell, I unpacked the three linux-aarch64 5.7.8 packages, and installed (dd'd) the 5.7.8 vmlinux.kpart into the 48MB Kernel partition. The boot back into Linux (ctrl-u) was successful. So, there definitely is an issue with the 5.8.0 vmlinux.kpart.

Any ideas?

[sehraf]

While probably not related to your problems, here is my story for the sake of record:

I had boot issues on my RockPi 4, too, after updating to 5.8.0.
The Console showed the problem: the kernel was waiting endlessly when trying to mount "/dev/disk/by-label/root". For some unknown reason the label could not be found. It is there and was working perfectly before.
To fix this, I've changed my bootloaders config to use "root=/dev/sda1" instead. Not perfect but works for now.