jammy/linux-aws: 5.15.0-1001.3 -proposed tracker

Bug #1959689 reported by Tim Gardner
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Invalid
Medium
Unassigned
Automated-testing
Incomplete
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Prepare-package
Fix Released
Medium
Tim Gardner
Prepare-package-lrg
Fix Released
Medium
Tim Gardner
Prepare-package-lrm
Fix Released
Medium
Tim Gardner
Prepare-package-lrs
Fix Released
Medium
Tim Gardner
Prepare-package-meta
Fix Released
Medium
Tim Gardner
Prepare-package-signed
Fix Released
Medium
Tim Gardner
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Andy Whitcroft
Promote-to-release
New
Medium
Ubuntu Package Archive Administrators
Regression-testing
Triaged
Medium
Canonical Kernel Team
Sru-review
Fix Released
Medium
Andy Whitcroft
linux-aws (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://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
boot-testing-requested: true
built:
  route-entry: 1
delta:
  promote-to-proposed:
  - lrm
  - signed
  - lrs
  - lrg
  - main
  - meta
  sru-review:
  - main
  - signed
  - lrg
  - meta
  - lrm
  - lrs
kernel-stable-master-bug: 1958638
packages:
  lrg: linux-restricted-generate-aws
  lrm: linux-restricted-modules-aws
  lrs: linux-restricted-signatures-aws
  main: linux-aws
  meta: linux-meta-aws
  signed: linux-signed-aws
phase: Testing
phase-changed: Monday, 07. February 2022 12:01 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  automated-testing: Stalled -- testing FAILED
  regression-testing: Ongoing -- testing in progress
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 5.15.0-1001.3
  main: 5.15.0-1001.3
  meta: 5.15.0.1001.3
  signed: 5.15.0-1001.3
  source: 5.15.0-1001.3

Tim Gardner (timg-tpi)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-d2022.01.21-2
description: updated
description: updated
tags: added: kernel-sru-derivative-of-1958638
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-aws (Ubuntu Jammy):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
Tim Gardner (timg-tpi)
summary: - jammy/linux-aws: <version to be filled> -proposed tracker
+ jammy/linux-aws: 5.15.0-1001.3 -proposed tracker
description: updated
description: updated
description: updated
Tim Gardner (timg-tpi)
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
description: updated
description: updated
description: updated
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Packages outside of proper component

The following packages ended up in the wrong component in the Proposed pocket:

linux-signed-aws 5.15.0-1001.3 - is in universe instead of main
linux-image-5.15.0-1001-aws 5.15.0-1001.3 - is in universe instead of main
linux-image-5.15.0-1001-aws 5.15.0-1001.3 - is in universe instead of main
linux-image-5.15.0-1001-aws-dbgsym 5.15.0-1001.3 - is in universe instead of main
linux-image-5.15.0-1001-aws-dbgsym 5.15.0-1001.3 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

description: updated
description: updated
description: updated
Tim Gardner (timg-tpi)
Changed in kernel-sru-workflow:
status: In Progress → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (83.1 KiB)

This bug was fixed in the package linux-aws - 5.15.0-1002.4

---------------
linux-aws (5.15.0-1002.4) jammy; urgency=medium

  * jammy/linux-aws: 5.15.0-1002.4 -proposed tracker (LP: #1960330)

  * Miscellaneous Ubuntu changes
    - [Config] aws: toolchain version update
    - [Config] aws: CONFIG_SYSFB_SIMPLEFB=y

  [ Ubuntu: 5.15.0-22.22 ]

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

  [ Ubuntu: 5.15.0-21.21 ]

  * jammy/linux: 5.15.0-21.21 -proposed tracker (LP: #1960211)
  * Miscellaneous Ubuntu changes
    - [packaging] unhook lowlatency flavours from the build

  [ Ubuntu: 5.15.0-20.20 ]

  * jammy/linux: 5.15.0-20.20 -proposed tracker (LP: #1959881)
  * Jammy update: v5.15.19 upstream stable release (LP: #1959879)
    - can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if
      length is 0
    - net: sfp: ignore disabled SFP node
    - net: stmmac: configure PTP clock source prior to PTP initialization
    - net: stmmac: skip only stmmac_ptp_register when resume from suspend
    - ARM: 9179/1: uaccess: avoid alignment faults in
      copy_[from|to]_kernel_nofault
    - ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
    - KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
    - s390/hypfs: include z/VM guests with access control group set
    - s390/nmi: handle guarded storage validity failures for KVM guests
    - s390/nmi: handle vector validity failures for KVM guests
    - bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
    - powerpc32/bpf: Fix codegen for bpf-to-bpf calls
    - powerpc/bpf: Update ldimm64 instructions during extra pass
    - scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
      devices
    - udf: Restore i_lenAlloc when inode expansion fails
    - udf: Fix NULL ptr deref when converting from inline format
    - efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
    - PM: wakeup: simplify the output logic of pm_show_wakelocks()
    - tracing/histogram: Fix a potential memory leak for kstrdup()
    - tracing: Don't inc err_log entry count if entry allocation fails
    - ceph: properly put ceph_string reference after async create attempt
    - ceph: set pool_ns in new inode layout for async creates
    - fsnotify: fix fsnotify hooks in pseudo filesystems
    - Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
    - psi: Fix uaf issue when psi trigger is destroyed while being polled
    - powerpc/audit: Fix syscall_get_arch()
    - perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
    - perf/x86/intel: Add a quirk for the calculation of the number of counters on
      Alder Lake
    - drm/etnaviv: relax submit size limits
    - drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
    - drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
    - KVM: LAPIC: Also cancel preemption timer during SET_LAPIC
    - KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests
    - KVM: SVM: Don't intercept #GP for SEV guests
    - KVM: x86: nSVM: skip eax alignment check for non-SVM instructions
    - KVM: x86: Forcibly leave nested virt when ...

Changed in linux-aws (Ubuntu Jammy):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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