Public bug reported:
Came across something bizarre when investigating the audio situation
with server on the Pi 5 (LP: #2038924). Moving the server images to use
the KMS overlay solves the situation, and would be preferable as it
would eliminate another difference between server and desktop images.
However, it also renders the 512MB 3A+ unbootable with an out-of-memory
error. The reason this is strange is that the 512MB Zero 2W continues to
boot quite happily. I'm attaching the serial output from the kernel up
to the point of the crash (screenlog.0).
The only changes made to the stock server config.txt were the addition
of these lines under the final "[all]" section:
[all]
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1
This setup booted happily on all other boards. A trivial workaround is
to manually specify a smaller CMA on the 3A+ with:
dtoverlay=vc4-kms-v3d,cma-128
With this alteration, it boots happily (and I'll be using this in an
appropriate [section] to work around the issue), but it might be nice to
understand why this is required on this board specifically (and why the
512MB Zero 2W doesn't exhibit the same issue).
** Affects: linux-raspi (Ubuntu)
Importance: Low
Status: New
** Attachment added: "screenlog.0"
https://bugs.launchpad.net/bugs/2060300/+attachment/5761694/+files/screenlog.0
** Changed in: linux-raspi (Ubuntu)
Importance: Undecided => Low
--
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/2060300
Title:
KMS overlay causes OOM oops on 3A+
Status in linux-raspi package in Ubuntu:
New
Bug description:
Came across something bizarre when investigating the audio situation
with server on the Pi 5 (LP: #2038924). Moving the server images to
use the KMS overlay solves the situation, and would be preferable as
it would eliminate another difference between server and desktop
images. However, it also renders the 512MB 3A+ unbootable with an out-
of-memory error. The reason this is strange is that the 512MB Zero 2W
continues to boot quite happily. I'm attaching the serial output from
the kernel up to the point of the crash (screenlog.0).
The only changes made to the stock server config.txt were the addition
of these lines under the final "[all]" section:
[all]
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1
This setup booted happily on all other boards. A trivial workaround is
to manually specify a smaller CMA on the 3A+ with:
dtoverlay=vc4-kms-v3d,cma-128
With this alteration, it boots happily (and I'll be using this in an
appropriate [section] to work around the issue), but it might be nice
to understand why this is required on this board specifically (and why
the 512MB Zero 2W doesn't exhibit the same issue).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
