Activity log for bug #2023359

Date Who What changed Old value New value Message
2023-06-09 06:42:01 Juerg Haefliger bug added bug
2023-06-09 06:42:25 Juerg Haefliger nominated for series Ubuntu Lunar
2023-06-09 06:42:25 Juerg Haefliger bug task added linux-raspi (Ubuntu Lunar)
2023-06-09 06:42:25 Juerg Haefliger nominated for series Ubuntu Jammy
2023-06-09 06:42:25 Juerg Haefliger bug task added linux-raspi (Ubuntu Jammy)
2023-06-09 06:42:25 Juerg Haefliger nominated for series Ubuntu Focal
2023-06-09 06:42:25 Juerg Haefliger bug task added linux-raspi (Ubuntu Focal)
2023-06-09 06:42:25 Juerg Haefliger nominated for series Ubuntu Kinetic
2023-06-09 06:42:25 Juerg Haefliger bug task added linux-raspi (Ubuntu Kinetic)
2023-06-09 06:42:25 Juerg Haefliger nominated for series Ubuntu Mantic
2023-06-09 06:42:25 Juerg Haefliger bug task added linux-raspi (Ubuntu Mantic)
2023-06-09 06:42:35 Juerg Haefliger linux-raspi (Ubuntu Kinetic): status New Won't Fix
2023-06-09 06:42:56 Juerg Haefliger linux-raspi (Ubuntu Kinetic): status Won't Fix New
2023-06-09 06:43:29 Juerg Haefliger summary -nolpae flavor is pointless nowadays raspi-nolpae flavor is pointless nowadays
2023-06-09 06:47:43 Juerg Haefliger linux-raspi (Ubuntu Focal): status New Invalid
2023-06-12 07:12:41 Juerg Haefliger tags kern-7041
2023-06-13 07:54:06 Juerg Haefliger description linux-raspi 5.4 in Focal is the first kernel that supports 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 in manually. We never had any complaints about 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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 With this commit, the memory consumption of both the armhf raspi and raspi-nolpae flavor are pretty much on par 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. [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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 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)
2023-06-13 07:58:20 Juerg Haefliger 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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 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) [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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 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)
2023-06-28 14:30:19 Juerg Haefliger linux-raspi (Ubuntu Lunar): status New Fix Committed
2023-06-28 14:30:22 Juerg Haefliger linux-raspi (Ubuntu Kinetic): status New Fix Committed
2023-06-28 14:30:25 Juerg Haefliger linux-raspi (Ubuntu Jammy): status New Fix Committed
2023-07-08 03:15:54 Ubuntu Kernel Bot tags kern-7041 kern-7041 kernel-spammed-lunar-linux-raspi verification-needed-lunar
2023-07-11 15:21:48 Manuel Diewald tags kern-7041 kernel-spammed-lunar-linux-raspi verification-needed-lunar kern-7041 kernel-spammed-lunar-linux-raspi verification-done-lunar
2023-07-11 22:24:53 Launchpad Janitor linux-raspi (Ubuntu Lunar): status Fix Committed Fix Released
2023-07-11 22:24:53 Launchpad Janitor cve linked 2023-2124
2023-07-11 22:24:53 Launchpad Janitor cve linked 2023-2176
2023-07-19 06:46:34 Ubuntu Kernel Bot tags kern-7041 kernel-spammed-lunar-linux-raspi verification-done-lunar kern-7041 kernel-spammed-jammy-linux-raspi kernel-spammed-lunar-linux-raspi verification-done-lunar verification-needed-jammy
2023-08-04 05:27:31 Juerg Haefliger tags kern-7041 kernel-spammed-jammy-linux-raspi kernel-spammed-lunar-linux-raspi verification-done-lunar verification-needed-jammy kern-7041 kernel-spammed-jammy-linux-raspi kernel-spammed-lunar-linux-raspi verification-done-jammy verification-done-lunar
2023-08-14 06:51:33 Launchpad Janitor linux-raspi (Ubuntu Jammy): status Fix Committed Fix Released
2023-08-14 06:51:33 Launchpad Janitor cve linked 2022-48502
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-0597
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-3090
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-31248
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-3141
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-3389
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-3390
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-3439
2023-08-14 06:51:33 Launchpad Janitor cve linked 2023-35001
2023-08-14 07:57:20 Juerg Haefliger linux-raspi (Ubuntu Kinetic): status Fix Committed Won't Fix
2023-09-18 16:17:15 Launchpad Janitor linux-raspi (Ubuntu Mantic): status New Fix Released