Bug 1883132 - grub2 crashes when booting on rk3399 devices
Summary: grub2 crashes when booting on rk3399 devices
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 33
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2020-09-28 06:53 UTC by Peter Robinson
Modified: 2020-10-03 12:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-03 12:40:11 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Peter Robinson 2020-09-28 06:53:05 UTC 
When trying to boot on F-33 with recent grub2 on a rk3399 device such as a RockPro64 or Pinebook Pro I get the crash below. If I copy the /boot/efi/EFI/fedora/grubaa64.efi from a F-32 install it works fine.

grub2-common-2.04-31.fc33.noarch
grub2-tools-minimal-2.04-31.fc33.aarch64
grub2-tools-2.04-31.fc33.aarch64
grub2-efi-aa64-2.04-31.fc33.aarch64

U-Boot 2020.10-rc5 (Sep 22 2020 - 00:00:00 +0000)
   
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 Pinebook Pro
DRAM:  3.9 GiB
PMIC:  RK808
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default environment
   
In:    serial
Out:   serial
Err:   serial
Model: Pine64 Pinebook Pro
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found EFI removable media binary efi/fedora/grubaa64.efi
Found DTB mmc 1:2 /dtb/rockchip/rk3399-pinebook-pro.dtb
60174 bytes read in 13 ms (4.4 MiB/s)
Card did not respond to voltage select!
Scanning disk mmc...
Disk mmc not ready
Scanning disk mmc...
** Unrecognized filesystem type **
Card did not respond to voltage select!
Scanning disk sdhci...
Disk sdhci not ready
Found 4 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
2676208 bytes read in 289 ms (8.8 MiB/s)
Booting /efi\fedora\grubaa64.efi
"Synchronous Abort" handler, esr 0x96000004
elr: fffffffffcf5435c lr : fffffffffcf4fecc (reloc)
elr: 00000000f3c9735c lr : 00000000f3c92ecc
x0 : f1000401b59da621 x1 : 00000000f3c9d608
x2 : 000000000000000d x3 : 00000000f3c9d800
x4 : 00000000f3b080c0 x5 : 0000000000008650
x6 : 00000000f3b0d1c0 x7 : 0000000000000000
x8 : 0000000000000000 x9 : 0000000000000008
x10: 00000000f3f191c8 x11: 00000000f3f19220
x12: 00000000f3b216e0 x13: 00000000f4f27d50
x14: 00000000f6f43cb8 x15: 00000000f4f27d08
x16: 00000000f6f47be4 x17: 0000000000000001
x18: 0000000000000000 x19: 00000000f6f43b88
x20: 00000000f4f27e70 x21: 0000000002080000
x22: 000000000028d5f0 x23: 00000000f4f50a80
x24: 00000000f6ff4984 x25: 0000000000000000
x26: 0000000000000000 x27: 0000000000000000
x28: 00000000f4f51340 x29: 00000000f4f27d10

Code: f94003e0 91000400 f90003e0 f94007e0 (39400000) 
UEFI image [0x00000000f3c82000:0x00000000f3f0dfff] pc=0x1535c '/efi\fedora\grubaa64.efi'
Resetting CPU ...

resetting ...
Note You need to log in before you can comment on or make changes to this bug.