[Macchiato] Latest EFI hangs writing efivars

[Marcin Wojtas]

Hi Riku,

Thanks for your debug. It was a DT issue - I reproduced it and was
able to finalize installation of grub. Long story short, the SPI clock
remained not enabled (normally the mtd layer does that). It doesn't
happend with ACPI, where all clocks are enabled by default.

I worked-around the issue and pushed to the github
(https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commit/b316449f24fdac9fc14c87d23f4680dfd789c7b8)
- please try newest marvell-armada-wip and let know.

Thanks,
Marcin

2018-03-12 10:39 GMT+01:00 Riku Voipio <riku.voipio at linaro.org>:
> Hi,
>
> I had nice success with Marcin's armada-wip-variables branch with
> debian-installer. Not I tried to udpate my build to latest EFI for
> spectre fixes and updated device tree.
>
> Good news: updating EFI in spi using fupdate command works.
> Bad news: grub-install hangs
>
> Reading EFI variables seem to work, bit ,ami
>
> Stracing what grub-install does:
>
> [pid  1533] execve("/bin/efibootmgr", ["efibootmgr", "-q", "-c", "-d",
> "/dev/sda", "-p", "1", "-w", "-L", "debian", "-l",
> "\\EFI\\debian\\grubaa64.efi"], 0xaaaafb90f6f0 /* 14 vars */) = 0
> [pid  1533] close(3)                    = 0
> [pid  1533] openat(AT_FDCWD,
> "/sys/firmware/efi/efivars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c",
> O_WRONLY|O_CREAT|O_EXCL, 0644) = 3
> [pid  1533] ioctl(3, FS_IOC_GETFLAGS, 0xffffc2be8694) = 0
> [pid  1533] write(3,
> "\7\0\0\0\1\0\0\0d\0d\0e\0b\0i\0a\0n\0\0\0\4\1*\0\1\0\0\0"..., 124
> ... hang - hard enough that even magic sysrq doesn't respond in serial.
>
> This is both with latest debian-installer mini.iso (with 4.15 kernel)
> as well as with older 4.14 kernel.
>
> Build at:
>
> https://people.debian.org/~riku/mcbin/machhiatobin_uefi.bin
>
> EFI log from serial for versions etc:
>
> tarting CP-1 IOROM 1.07
> Booting from SPI NOR flash 1 (0x32)
> Found valid image at boot postion 0x000
> lNOTICE:  Starting binary extension
> NOTICE:  SVC: SW Revision 0x0. SVC is not supported
> mv_ddr: mv_ddr-armada-17.10.4-gcc280f0 (Mar 12 2018 - 10:16:49)
> mv_ddr: completed successfully
> NOTICE:  Cold boot
> NOTICE:  Booting Trusted Firmware
> NOTICE:  BL1: v1.3(release):armada-17.10.7:43965481
> NOTICE:  BL1: Built : 22:19:25, Feb  8 2018
> NOTICE:  BL1: Booting BL2
> lNOTICE:  BL2: v1.3(release):armada-17.10.7:43965481
> NOTICE:  BL2: Built : 22:19:25, Feb  8 2018
> BL2: Initiating SCP_BL2 transfer to SCP
> NOTICE:  SCP_BL2 contains 2 concatenated images
> NOTICE:  Load image to CP1 MSS
> NOTICE:  Loading MSS image from address 0x4023020 Size 0x1378 to MSS
> at 0xf4280000
> NOTICE:  Done
> NOTICE:  Load image to AP MSS
> NOTICE:  Loading MSS image from address 0x4024398 Size 0x1f68 to MSS
> at 0xf0580000
> 00
> N
>
> FreeRTOS 7.3.0 - Marvell cm3 - A8K release armada-17.10.1
>
> OTICE:  Done
> NOTICE:  SCP Image doesn't contain PM firmware
> NOTICE:  BL1: Booting BL31
> lNOTICE:  MSS PM is not supported in this build
> NOTICE:  BL31: v1.3(release):armada-17.10.7:43965481
> NOTICE:  BL31: Built : 22:19:25, Feb  8 2018
> lUEFI firmware (version MARVELL_EFI built at 10:14:47 on Mar 12 2018)
>
> Armada 8040 MachiatoBin Platform Init
>
> Comphy0-0: PCIE0         5 Gbps
> Comphy0-1: PCIE0         5 Gbps
> Comphy0-2: PCIE0         5 Gbps
> Comphy0-3: PCIE0         5 Gbps
> Comphy0-4: SFI           10.31 Gbps
> Comphy0-5: SATA1         5 Gbps
>
> Comphy1-0: SGMII1        1.25 Gbps
> Comphy1-1: SATA2         5 Gbps
> Comphy1-2: USB3_HOST0    5 Gbps
> Comphy1-3: SATA3         5 Gbps
> Comphy1-4: SFI           10.31 Gbps
> Comphy1-5: SGMII2        3.125 Gbps
>
> UTMI PHY 0 initialized to USB Host0
> UTMI PHY 1 initialized to USB Host1
> UTMI PHY 0 initialized to USB Host0
> RTC: Initialize controller 1
> Skip I2c chip 0
> Detected w25q32bv SPI flash with page size 256 B, erase size 4 KB, total 4 MB
> Succesfully installed protocol interfaces
> ramdisk:blckio install. Status=Success
> Tianocore/EDK2 firmware version MARVELL_EFI
> Press ESCAPE for boot options going to start mss_periodic_ihb_wa for mss
> ...error: no suitable video mode found.