raspi-nolpae flavor is pointless nowadays
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
linux-raspi (Ubuntu) | Status tracked in Mantic | |||||
Focal |
Invalid
|
Undecided
|
Unassigned | |||
Jammy |
Fix Released
|
Undecided
|
Unassigned | |||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | |||
Lunar |
Fix Released
|
Undecided
|
Unassigned | |||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
linux-raspi 5.4 in Focal was the first kernel to support Pi 4B, which requires LPAE to be enabled for armhf. Since we currently don't support board-specific kernels but follow a one-kernel-fits-all strategy, the LPAE kernel is also used on Pi 3 and 2 boards. Back then, running an armhf LPAE kernel on a Pi 3/2 resulted in additional kernel memory consumption of ~70MB compared to arm64 and non-LPAE kernels. For that reason I decided to introduce a raspi-nolpae flavor which can be used on Pi 3 and 2 (only). That flavor was never officially announced nor installed automatically anywhere. A user has to install it manually. We never had any complaints about armhf kernel memory consumption so never directed anybody at installing this flavor. Therefore I'm assuming it's not being used...
Turns out that the early 5.4 kernels were broken and incorrectly initialized a 64MB SWIOTLB buffer which is the reason for the above additional memory consumption. This was fixed here: https:/
With this commit, the memory consumption of both the armhf raspi and raspi-nolpae flavor are pretty much on par [1] and there is really no reason anymore to keep the raspi-nolpae flavor around. So let's get rid of it and introduce a transitional package that replaces installed raspi-nolpae packages with raspi packages.
[Test Case]
Install raspi-nolpae flavor and upgrade to the new kernel and verify that the raspi flavor is installed instead.
[Where Problems Could Occur]
Only users that have the raspi-nolpae flavor installed are affected. Upgrades, i.e., transitions from raspi-nolpae to raspi could go wrong. It's not expected that there is a user visible difference between running a current raspi-nolpae and raspi kernel flavor.
[1]
arm64 raspi -- Memory: 815528K/970752K available (13376K kernel code, 2472K rwdata, 4296K rodata, 5504K init, 850K bss, 89688K reserved, 65536K cma-reserved)
armhf raspi -- Memory: 835732K/970752K available (12288K kernel code, 1643K rwdata, 3692K rodata, 2048K init, 533K bss, 69484K reserved, 65536K cma-reserved, 118784K highmem)
armhf raspi-nolpae -- Memory: 836620K/970752K available (12288K kernel code, 1633K rwdata, 3676K rodata, 1024K init, 511K bss, 68596K reserved, 65536K cma-reserved)
Changed in linux-raspi (Ubuntu Kinetic): | |
status: | New → Won't Fix |
status: | Won't Fix → New |
summary: |
- -nolpae flavor is pointless nowadays + raspi-nolpae flavor is pointless nowadays |
Changed in linux-raspi (Ubuntu Focal): | |
status: | New → Invalid |
tags: | added: kern-7041 |
description: | updated |
description: | updated |
Changed in linux-raspi (Ubuntu Lunar): | |
status: | New → Fix Committed |
Changed in linux-raspi (Ubuntu Kinetic): | |
status: | New → Fix Committed |
Changed in linux-raspi (Ubuntu Jammy): | |
status: | New → Fix Committed |
All autopkgtests for the newly accepted linux-meta-raspi (6.2.0.1008.11) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:
bbswitch/ 0.8-14ubuntu1 (arm64) rw/unknown (arm64) 2.1.9-2ubuntu1. 1 (arm64)
dpdk-kmods/unknown (arm64)
linux-apfs-
zfs-linux/
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp dates policy regarding autopkgtest regressions [1].
https:/ /people. canonical. com/~ubuntu- archive/ proposed- migration/ lunar/update_ excuses. html#linux- meta-raspi
[1] https:/ /wiki.ubuntu. com/StableRelea seUpdates# Autopkgtest_ Regressions
Thank you!