jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | |||
Automated-testing |
Fix Released
|
Medium
|
Canonical Kernel Team | |||
Boot-testing |
Fix Released
|
Medium
|
Unassigned | |||
Prepare-package |
Fix Released
|
Medium
|
Juerg Haefliger | |||
Prepare-package-meta |
Fix Released
|
Medium
|
Juerg Haefliger | |||
Promote-signing-to-proposed |
Invalid
|
Medium
|
Unassigned | |||
Promote-to-proposed |
Fix Released
|
Medium
|
Dimitri John Ledkov | |||
Promote-to-release |
Fix Released
|
Medium
|
Ubuntu Package Archive Administrators | |||
Regression-testing |
Fix Released
|
Medium
|
Canonical Kernel Team | |||
Sru-review |
Fix Released
|
Medium
|
Dimitri John Ledkov | |||
linux-raspi (Ubuntu) | ||||||
Jammy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This bug will contain status and test results related to a kernel source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https:/
-- swm properties --
boot-testing-
built:
route-entry: 2
delta:
promote-
- main
- meta
promote-
- meta
- main
sru-review:
- main
- meta
kernel-
packages:
main: linux-raspi
meta: linux-meta-raspi
phase: Complete
phase-changed: Wednesday, 02. February 2022 18:45 UTC
proposed-
proposed-
reason: {}
synthetic:
:promote-
variant: debs
versions:
main: 5.15.0-1002.2
meta: 5.15.0.1002.2
source: 5.15.0-1002.2
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-d2022.01.21-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1958638 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux-raspi (Ubuntu Jammy): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
description: | updated |
summary: |
- jammy/linux-raspi: <version to be filled> -proposed tracker + jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
We could enable more "uefi-ish" features on this kernel to keep it closer to generic configs, but they are of little to no value for most of our users. I.e. PLATFORM_KERYING, LOCK_DOWN_ IN_SECURE_ BOOT.
CONFIG_ RESET_RASPBERRY PI is not set on raspi-nolpae flavour, and I don't know for sure why not. (edit: nolpae is for rpi23 only thus no need for rpi4-only driver)
Some raspi patchseries are reverted, maybe we should ask them to drop them.
Some raspi patches should be upstreamd - for example poweroff_halt & zswap patches are cute and generally useful everywhere.
Somehow src:linux-raspi .deb compression is xz instead of the expected zstd. Which is inherited from master kernel, will follow up on that.
somewhat expect virtio drivers to be promoted from modules-extra to modules. It would be nice, if one could boot stock rpi image in qemu locally (albeit not using regular boot methods). But i guess need to evaluate if carrying virtio drivers in our default initrd is worth it. Maybe not.
rpi-5.13 dropped rpi-fan module, yet we still carry it in impish.
Otherwise, packaging looks sane; rebase looks sane; diffs look sane.