Have now also observed this on the Zero 2W with the current noble daily server image. Interestingly, it *didn't* occur directly on the image at first. This booted happily on the Zero 2W. However, this same card was then used to test a 3A+. On the 3A+ I regenerated the initramfs (testing a reported issue on low-memory boards), then moved the card back to the Zero 2W and observed the same OOM issue on boot as the 3A+ does without the CMA-128 workaround.
I also tried re-generating the initrd on the Zero 2W, but it still booted happily after that without the workaround. This implies there's something about the initrd, which is triggering the issue (sizing, position in memory, I'm not sure?) but that the Zero 2W may coincidentally run into the issue in normal operation. Placing the CMA-128 workaround on the KMS overlay worked around the issue, so I'll now add a [pi02] section in the config.txt applying the same workaround for this board too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060300 Title: KMS overlay causes OOM oops on 3A+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
