jammy/linux-mtk: 5.15.0-1032.37 -proposed tracker

Bug #2069247 reported by Jian Hui Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
In Progress
Medium
Unassigned
Abi-testing
Fix Released
Medium
Unassigned
Automated-testing
Invalid
Medium
Unassigned
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
New
Medium
Unassigned
New-review
Incomplete
Medium
Andy Whitcroft
Prepare-package
Fix Released
Medium
Jian Hui Lee
Prepare-package-generate
Fix Released
Medium
Jian Hui Lee
Prepare-package-meta
Fix Released
Medium
Jian Hui Lee
Prepare-package-signed
Fix Released
Medium
Jian Hui Lee
Promote-signing-to-proposed
New
Medium
Unassigned
Promote-to-proposed
Confirmed
Medium
Canonical Kernel Team
Promote-to-security
New
Medium
Unassigned
Promote-to-updates
New
Medium
Unassigned
Regression-testing
New
Medium
Canonical Kernel Team
Security-signoff
New
Medium
Unassigned
Sru-review
Fix Released
Medium
Andy Whitcroft
Verification-testing
New
Medium
Unassigned
linux-mtk (Ubuntu)
Jammy
New
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://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
built:
  from: aa55e6d9bbac7287
  route-entry: 1
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [main, meta, signed, generate]
flag:
  boot-testing-requested: true
packages:
  generate: linux-generate-mtk
  main: linux-mtk
  meta: linux-meta-mtk
  signed: linux-signed-mtk
phase: Ready for Promote to Proposed
phase-changed: Tuesday, 18. June 2024 12:54 UTC
reason:
  new-review: Stalled -- review FAILED
  promote-to-proposed: Stalled -- ready for review
trackers:
  jammy/linux-mtk/mediatek-genio-kernel: bug 2069246
variant: debs
versions:
  main: 5.15.0-1032.37
  meta: 5.15.0.1032.34
  signed: 5.15.0-1032.37
~~:
  announce:
    swm-transition-crankable: 2024-06-13 04:52:21.023436
  clamps:
    new-review: aa55e6d9bbac7287
    promote-to-proposed: aa55e6d9bbac7287
    self: 5.15.0-1032.37
    sru-review: aa55e6d9bbac7287
  tracker:
    last-message: '2024-06-17 12:28:53.049328+00:00'

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-d2024.05.27-1
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-mtk (Ubuntu Jammy):
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
description: updated
summary: - jammy/linux-mtk: <version to be filled> -proposed tracker
+ jammy/linux-mtk: 5.15.0-1032.37 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Ancillary Bot (ubuntu-kernel-ancillary-bot) wrote : ABI testing

arm64/mtk canonical-certs.pem unchanged
arm64/mtk canonical-revoked-certs.pem unchanged
arm64/mtk fwinfo unchanged
arm64/mtk modules differs
  @@ -5469,14 +5469,11 @@
   sch5627
   sch5636
   sch56xx-common
  -sch_atm (rejected)
   sch_cake
  -sch_cbq (rejected)
   sch_cbs
   sch_choke
   sch_codel
   sch_drr
  -sch_dsmark (rejected)
   sch_etf
   sch_ets
   sch_fq
arm64/mtk retpoline unchanged

description: updated
description: updated
Revision history for this message
Jian Hui Lee (jianhuilee) wrote :

the rejected items in comment #1 for abi-testing is coming from master kernel as following information:
net/sched: Retire dsmark qdisc commit bbe77c14ee61 upstream
net/sched: Retire ATM qdisc commit fb38306ceb9e upstream
net/sched: Retire CBQ qdisc commit 051d44209842 upstream
LP: #2060142

so set it to fix released as expected.

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Andy Whitcroft (apw) wrote :

This signing is currently routed via old keys but the code is compatible with the new keys only.

description: updated
description: updated
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.