[Bug 1848247] Re: 3A+ boot failure on Eoan

[Hui Wang]

So far, what I got from investigation is:

After setting vc4-fkms-v3d, the fb driver's sequence is bootloader ->
simplefb -> drm_vc4 fb

Without vc4-fkms-v3d, the sequence is bootloader -> simplefb ->
bcm2708_fb (the screen will flicker when bcm2708_fb takeover the
display)

I will continue looking at the bcm2708_fb.

And for 3A+ booting issue, after adding vc4-fkms-v3d, the system need
much memory, but 3A+ only have 512M physical memory, looks like the 512M
is not enough for drm_vc4, so the kernel crash with "out of memory
errors".

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848247

Title:
  3A+ boot failure on Eoan

Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged

Bug description:
  The current Eoan image hits a kernel panic when booting on a Raspberry
  Pi 3A+. Unfortunately it does so before the serial console has been
  enabled so there's no useful output beyond what scrolls by rapidly on
  the framebuffer console.

  It is notable that the start.elf bootloader (prior to u-boot), loads
  the device-tree for the 3B+ because no device-tree specific to the 3A+
  exists (in the 27*.dtb set; there is one in the 28*.dtb set but I'm
  not convinced those are used by anything); u-boot proceeds
  successfully but then the kernel panics.

  This occurs on both the armhf and arm64 architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1848247/+subscriptions