** Changed in: snapd
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ does not boot with core20
Status in pi2-kernel-sna
@ plars
How come you manage to use Bionic classic, Focal classic, UC18 on that
Pi 3A+ without adjusting config.txt and believe that this is a UC20
regression?
Given that my understanding is that 3A+ needs that manual adjustment on
all our other targets.
** Changed in: linux-raspi (Ubuntu)
** Changed in: snapd
Status: New => Invalid
** Changed in: snapd
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ do
dtoverlay=vc4-fkms-v3d,cma-256
Telling the kernel to allocate/reserve 256MB of contiguous memory for
DMA operations is not a sensible thing to do on a device that only has
512MB of memory available.
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Invalid
--
You received this bug
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-raspi2 (Ubuntu)
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages
Looks like https://bugs.launchpad.net/ubuntu/+source/linux-firmware-
raspi2/+bug/1848247 might be the bug pwlars is referring to in #4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs
I hadn't realized it at first, but this is actually similar to something
we've seen in the past. There's some contiguous memory that is allocated
and locked if vc4-fkms-v3d is enabled in the config.txt. This is ok for
platforms with more RAM, but the RPI3A+ is too constrained. Removing
that line wi
Note that I reproduced this in an amd64 VM with today's beta snaps
booted with -m 512 MB, so I think this is just that uc20 currently
requires more than 512 MB of RAM to boot at all...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
Earlier
## Warning: Input data exceeds 1048576 bytes - truncated
sounds already scary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ does not boot with cor
I disabled quiet and enabled early printk and was able to get a full
capture of the panic. (see attachment)
** Attachment added: "boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878432/+attachment/5371037/+files/boot.log
--
You received this bug notification because yo
** Also affects: pi2-kernel-snap
Importance: Undecided
Status: New
** Also affects: snapd
Importance: Undecided
Status: New
** Tags added: core20
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
11 matches
Mail list logo