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

[Dave Jones]

> I mean the simplefb driver in the kernel in the #3, I didn't know
there is a simplefb driver in the uboot too.

Ah, I'm afraid my lack of kernel knowledge is showing there: I didn't
realize the was a simplefb in the kernel! I should've thought given the
kernel starts off looking fine, and only shortly after starting de-syncs
the framebuffer (presumably the point where bcm2708_fb takes over).

Confirmed last night that the u-boot simplefb is largely doing the right
thing, although I did run across some bugs/bad assumptions in the
framebuffer mailbox handling, but nothing that should affect anything
here (it doesn't check the actual result of setting depth / alpha-mode /
pixel-order; I'll put together a patch for that later).

-- 
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