[Bug 1878432] Re: rpi3a+ does not boot with core20
** Changed in: snapd Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
** Tags removed: core20 ** Tags added: uc20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
Since it behaves very differently from this on a+, I filed a new bug for the issues with pi2/pi3 here: https://bugs.launchpad.net/snapd/+bug/1878943 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
Just one additional bit of info regarding the purpose of vc4-fkms-v3d being in Core 18 in the first place: I'm not 100% sure of the reason it was there, but it's been since before Core 18, so I was loathe to remove something that users might be relying upon. As to what the overlay actually does: it implements "fake" KMS (hence the fkms in the name) by having the ARM core request (via the mailbox) that the GPU carry out the required operations. This is in contrast to the "proper" KMS overlay (vc4-kms-v3d) which isn't currently recommended because it leaves the ARM in full control of the GPU registers, which breaks certain other bits of the GPU firmware (notably the camera module cannot operate with the latter overlay at this time). The FKMS overlay is likely used by several graphical applications (e.g. it's near impossible to run a desktop on the Pi without it ... not that that's something anyone would sensibly try on a 3A+) so I was left with a choice of "which thing do you want to break today?": 1) Leave the fkms overlay in, breaking boot for the 3A+ but with a relatively simple workaround. 2) Remove the fkms overlay, permitting boot on all models but likely breaking several existing graphical applications on Core, again with a relatively simple workaround (add the overlay line back in). My judgment was that the 3A+ is quite a rare beast with relatively esoteric use-cases (it's primarily used either where someone needs the reduced weight, e.g. drones, or where someone wants the absolute lowest cost possible although that niche is arguably better served by the compute modules which come with their own storage), so the former option would likely break less people's experiences out of the box. @pwlars - interesting observation on the pi2. I can't say I'd seriously tested Core on there. I wonder if the CMA allocation of the overlay can be adjusted and whether that would make a difference. I had previously tried removing the ",cma-256" parameter and noted it made no difference, but I don't recall testing alternatives (e.g. "cma-64"?) @xnox - minor correction to your query in comment 8: the fkms overlay is not included on classic. It was never included on there previously, so I couldn't justify breaking boot on the 3A+ just for the sake of bringing the two platforms into line (much as I might desire such harmony for ease of maintenance!). Hence, the only combination where one needed to fiddle with things to get it booting was Core 18 on the 3A+. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
Something that may be related - I tried booting the armhf image on an rpi2 and kept having a lot of problems with it. It was just extremely slow, but eventually booted to console-conf, but didn't see the ethernet adapter. I did notice a line early in the boot that it failed to allocate cma, so I removed the dtoverlay line for cma and it booted much faster + ethernet worked. This was on an rpi2b v1.1 with 1GB ram -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
When I filed this bug, I didn't recognize at first that it was the issue with that dtoverlay. I'm testing a lot of different devices to try to get a good picture of what works and doesn't work, and would rather err on the side of reporting stuff as soon as possible. I did go back later to see if removing the dtoverlay helped and confirmed that it did in comment #4. It's still not clear to me whether this dtoverlay config line is doing anything, or what the default will be, but I'll leave that to others to determine whether what the default should be. At the very least, this should be logged and release noted like we've done previously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
This issue is duplicate of the existing Bionic issue, and not a regression in UC20. https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes/#Raspberry_Pi """ For Ubuntu Core 18 on the Raspberry Pi, the vc4-fkms-v3d overlay is included in the default boot configuration. This is known to cause issues on the Raspberry Pi 3A+ on which the overlay allocates half the available memory, leaving insufficient memory for the system to operate correctly (1848247). The recommended workaround is to comment out the dtoverlay line in config.txt on the system-boot partition (the first partition on the card), like so: #dtoverlay=vc4-fkms-v3d """ also see https://bugs.launchpad.net/ubuntu/+source/linux-firmware- raspi2/+bug/1848247 config.txt allows per-model filters. https://www.raspberrypi.org/documentation/configuration/config-txt/conditional.md However there is no filter that will select the 3A+ model alone. because [pi3+] selects both the small 3A+ and big 3B+. We can fix one, by breaking the other. And we chose to have 3B+ to be working out of the box, whilst leaving 3A+ broken => requiring config.txt tweak. Ideally, we'd want to have config.txt filter for 3A+, but there isn't one. Hence the documentation. Without firmware fix, once we have multipartition boot, we will be able to boot to an initrd, detect things on runtime, adjust config.txt, soft reset and have the right dtb overlay loaded despite missing 3A+ filter selector. I'm not sure how to mark this bug. As it's a duplicate of a known issue, and is not currently fixable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
@ 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) Status: New => Invalid ** Changed in: snapd Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
** Changed in: snapd Status: New => Invalid ** Changed in: snapd Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
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 will allow it to boot at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
Earlier ## Warning: Input data exceeds 1048576 bytes - truncated sounds already scary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878432] Re: rpi3a+ does not boot with core20
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
