hirsute/linux: 5.11.0-41.45 -proposed tracker
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-
bugs-spammed: true
built:
route-entry: 1
delta:
promote-
- lrs
- lrg
- lrm
promote-
promote-
- lrs
- main
- lrm
- meta
- signed
sru-review:
- lrg
- lrm
- lrs
issue: KSRU-325
packages:
lrg: linux-restricte
lrm: linux-restricte
lrs: linux-restricte
main: linux
meta: linux-meta
signed: linux-signed
phase: Complete
phase-changed: Monday, 29. November 2021 21:47 UTC
proposed-
proposed-
reason: {}
synthetic:
:promote-
trackers:
focal/
hirsute/
hirsute/
hirsute/
hirsute/
hirsute/
hirsute/
hirsute/
variant: debs
versions:
lrm: 5.11.0-41.45+2
main: 5.11.0-41.45
meta: 5.11.0.41.42
signed: 5.11.0-41.45
source: 5.11.0-41.45
| tags: | added: kernel-release-tracking-bug-live |
| description: | updated |
| tags: | added: kernel-sru-cycle-2021.11.08-1 |
| Changed in kernel-sru-workflow: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Hirsute): | |
| importance: | Undecided → Medium |
| tags: | added: kernel-block-derivatives |
| Changed in kernel-sru-workflow: | |
| status: | Confirmed → Triaged |
| description: | updated |
| Changed in kernel-sru-workflow: | |
| status: | Triaged → In Progress |
| tags: | added: kernel-jira-preparation-blocked |
| description: | updated |
| tags: | removed: kernel-jira-preparation-blocked |
| description: | updated |
| summary: |
- hirsute/linux: <version to be filled> -proposed tracker + hirsute/linux: 5.11.0-41.45 -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 |
| tags: | added: boot-testing-passed |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: |
added: kernel-unblock-derivatives removed: kernel-block-derivatives |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: | added: kernel-signing-bot |
| 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 |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: | added: kernel-unblock-ppa |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: | added: regression-testing-passed |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| tags: | added: kernel-jira-issue-ksru-325 |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
| description: | updated |
There is one odd issue (bug #1951289) where one CPU seems unable to schedule across all possible CPUs. However this could not be seen on other arm64 hardware. For that I am tempted to say this is either a hardware issue or race. However this happening on a CPU #32 when 128 are available sounds a little suspicious.
The remaining missing results are deploy or setup issues on nodes which are extremely slow/busy (spitfire/michael).