3A+ boot failure on Eoan
Bug #1848247 reported by
Dave Jones
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-firmware-raspi2 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Eoan |
Won't Fix
|
High
|
Unassigned |
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.
tags: | added: eoan rls-ee-incoming |
Changed in linux-firmware-raspi2 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: id-5da7195077417327157503f8 |
Changed in linux-firmware-raspi2 (Ubuntu Eoan): | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | removed: rls-ee-incoming |
Changed in linux-firmware-raspi2 (Ubuntu Eoan): | |
status: | Triaged → Fix Committed |
Changed in linux-firmware-raspi2 (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in linux-firmware-raspi2 (Ubuntu): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Related to #1847596 - commenting out the vc4-fkms-v3d overlay in config.txt permits the 3A+ to boot, albeit with corrupted framebuffer. In other words, solving #1847596 "properly" should also yield a fix for this.