[Kernel-packages] [Bug 2077260] Re: freeze after updating to newest kernel on log in sreen or just after log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

[Denis Kuniß]

Hi.
Anyone of the affected users got rid of this issue? If so, how?
I still facing the issue...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077260

Title:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to restero to 6.5.0-45

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  freeze after updating to newest kernel on log in sreen or just after
  log in (6.8.0-45 ?). Had to use Grub to rester to 6.5.0-45

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-45-generic 6.5.0-45.45~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 18 15:53:56 2024
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michal 2670 F wireplumber
   /dev/snd/seq:michal 2665 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  MachineType: Hewlett-Packard HP G62 Notebook PC
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-45-generic 
root=UUID=62689215-60a8-4e0a-8e4e-fb3115fd7b88 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-45-generic N/A
   linux-backports-modules-6.5.0-45-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.2
  Tags: noble wayland-session
  Uname: Linux 6.5.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/29/2010
  dmi.bios.release: 15.37
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1439
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 60.3F
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 60.63
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd10/29/2010:br15.37:efr60.63:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn1439:rvr60.3F:cvnHewlett-Packard:ct10:cvrChassisVersion:skuLD667EA#AKD:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP G62 Notebook PC
  dmi.product.sku: LD667EA#AKD
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.init.d.apport: 2024-07-22T14:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077260/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra-igx/5.15.0.1020.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-nvidia-tegra-igx 
(5.15.0.1020.22) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

evdi/1.12.0+dfsg-0ubuntu2~22.04.4 (arm64)
glibc/2.35-0ubuntu3.8 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-tegra-igx

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095199] [NEW] Focal update: v5.4.288 upstream stable release

[Noah Wager]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.288 upstream stable release
   from git://git.kernel.org/

usb: host: max3421-hcd: Correctly abort a USB request.
ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
usb: ehci-hcd: fix call balance of clocks handling routines
usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing 
null pointer
xfs: don't drop errno values when we fail to ficlone the entire range
bpf, sockmap: Fix update element with same
batman-adv: Do not send uninitialized TT changes
batman-adv: Remove uninitialized data in full table TT response
batman-adv: Do not let TT changes list grows indefinitely
tipc: fix NULL deref in cleanup_bearer()
net: lapb: increase LAPB_HEADER_LEN
ACPI: resource: Fix memory resource type union access
qca_spi: Fix clock speed for multiple QCA7000
qca_spi: Make driver probing reliable
net/sched: netem: account for backlog updates from child qdisc
ACPICA: events/evxfregn: don't release the ContextMutex that was never acquired
blk-iocost: clamp inuse and skip noops in __propagate_weights()
blk-iocost: fix weight updates of inner active iocgs
blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
tracing/kprobes: Skip symbol counting logic for module symbols in 
create_local_trace_kprobe()
xen/netfront: fix crash when removing device
ALSA: usb-audio: Fix a DMA to stack memory bug
Linux 5.4.288
UBUNTU: Upstream stable to v5.4.288

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Noah Wager (nwager)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Noah Wager (nwager)

** Description changed:

  
  SRU Justification
  
  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:
  
 v5.4.288 upstream stable release
 from git://git.kernel.org/
  
- 
+ usb: host: max3421-hcd: Correctly abort a USB request.
+ ata: sata_highbank: fix OF node reference leak in highbank_initialize_phys()
+ usb: dwc2: hcd: Fix GetPortStatus & SetPortFeature
+ usb: ehci-hcd: fix call balance of clocks handling routines
+ usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to 
accessing null pointer
+ xfs: don't drop errno values when we fail to ficlone the entire range
+ bpf, sockmap: Fix update element with same
+ batman-adv: Do not send uninitialized TT changes
+ batman-adv: Remove uninitialized data in full table TT response
+ batman-adv: Do not let TT changes list grows indefinitely
+ tipc: fix NULL deref in cleanup_bearer()
+ net: lapb: increase LAPB_HEADER_LEN
+ ACPI: resource: Fix memory resource type union access
+ qca_spi: Fix clock speed for multiple QCA7000
+ qca_spi: Make driver probing reliable
+ net/sched: netem: account for backlog updates from child qdisc
+ ACPICA: events/evxfregn: don't release the ContextMutex that was never 
acquired
+ blk-iocost: clamp inuse and skip noops in __propagate_weights()
+ blk-iocost: fix weight updates of inner active iocgs
+ blk-iocost: Avoid using clamp() on inuse in __propagate_weights()
+ KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
+ tracing/kprobes: Skip symbol counting logic for module symbols in 
create_local_trace_kprobe()
+ xen/netfront: fix crash when removing device
+ ALSA: usb-audio: Fix a DMA to stack memory bug
  Linux 5.4.288
- ALSA: usb-audio: Fix a DMA to stack memory bug
- xen/netfront: fix crash when removing device
- tracing/kprobes: Skip symbol counting logic for module symbols in 
create_local_

[Kernel-packages] [Bug 2095028] Re: Pull request to enable GPU passthrough for CUDA

[Jacob Martin]

** Also affects: linux-nvidia-6.11 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-nvidia-6.11 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2095028

Title:
  Pull request to enable GPU passthrough for CUDA

Status in linux-nvidia-6.11 package in Ubuntu:
  Invalid
Status in linux-nvidia-6.11 source package in Noble:
  Fix Committed

Bug description:
  [Test plan]

  boot up host
  boot up VMs in host with 1 GPU, 2 GPUs, 3 GPUs and 4 GPUs.
  Run the following to do the basic checks

  //
  // Get CPU device
  //
  $ lspci | grep 3D
  //
  // Show GPU info
  //
  $ nvidia-smi
  //
  // Result must be passed
  //
  $ /root/r570/tests/runtime/gflops/gflops
  $ /root/r570/tests/runtime/uvmConformance/uvmConformance -t texture_simple
  $ /root/r570/tests/runtime/uvmConformance/uvmConformance -t ats_malloc_host

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2095028/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2094048] Re: Pick up patches that were missed in the work to create a new linux-nvidia-6.11 kernel

[Jacob Martin]

** Also affects: linux-nvidia-6.11 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-nvidia-6.11 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2094048

Title:
  Pick up patches that were missed in the work to create a new linux-
  nvidia-6.11 kernel

Status in linux-nvidia-6.11 package in Ubuntu:
  Invalid
Status in linux-nvidia-6.11 source package in Noble:
  Fix Committed

Bug description:
  a number of patches were not carried forward. The following collection of 
patches should be cherry-picked:
  Commit Summary

  6adf616 cppc_cpufreq: Use desired perf if feedback ctrs are 0 or unchanged
  cd955fc cppc_cpufreq: Remove HiSilicon CPPC workaround
  ae2224f NVIDIA: SAUCE: ACPI/HMAT: Move HMAT messages to pr_debug()
  404b06a perf cs-etm: Create decoders after both AUX and HW_ID search passes
  6dc551f perf: cs-etm: Allocate queues for all CPUs
  0695b8e perf: cs-etm: Move traceid_list to each queue
  4cb2195 perf: cs-etm: Create decoders based on the trace ID mappings
  7abe526 perf: cs-etm: Only save valid trace IDs into files
  6a74057 perf: cs-etm: Support version 0.1 of HW_ID packets
  a82a4c6 perf: cs-etm: Print queue number in raw trace dump
  f1fbb5b coresight: Remove unused ETM Perf stubs
  aefc384 coresight: Clarify comments around the PID of the sink owner
  1676c55 coresight: Move struct coresight_trace_id_map to common header
  975a565 coresight: Expose map arguments in trace ID API
  11b2f11 coresight: Make CPU id map a property of a trace ID map
  6455295 coresight: Use per-sink trace ID maps for Perf sessions
  f273c8e coresight: Remove pending trace ID release mechanism
  09e8442 coresight: Emit sink ID in the HW_ID packets
  9418582 coresight: Make trace ID map spinlock local to the map

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2094048/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2092703] Re: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50

[WDW]

The same bug affects me. I use a Lenovo ThinkPad T14 Gen 2 AMD laptop,
with Ryzen 5 PRO 5650U processor.

Ubuntu 22.04 fails to boot after the update (by the Software Updater 
application) on Friday 2024-12-20 to kernel Linux 6.8.0-50-generic on my laptop.
A black screen with blinking cursor appears after booting. Ctrl-Alt-Delete 
changes this to a Lenovo and Ubuntu logo, and triggers a restart. The same 
happens during each new boot to the now default kernel.
Selecting the old Linux 6.8.0-49-generic kernel during boot results in a 
successful boot and fully functional system, but any attempt with 
6.8.0-50-generic fails.

When booting with with 6.8.0-50-generic, the following error message
appears in the log files: " org.gnome.Shell.desktop[1547]: Failed to
setup: No GPUs found ".

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2092703

Title:
  Ubuntu 22.04 fails to start after kernel update to 6.8.0-50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu
  22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still
  successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2
  with AMD Ryzen 5850U.

  As far as I noticed in boot logs from previous boot (journalctl -b
  -1), there is some problem with X.org:

  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) modesetting: Driver for Modesetting Kernel Drivers: kms
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) FBDEV: driver for framebuffer: fbdev
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) VESA: driver for VESA chipsets: vesa
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
xf86EnableIO: failed to enable I/O ports -03ff (Operation not permitted)
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) open /dev/dri/card0: No such file or directory
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(WW) Falling back to old probe method for modesetting
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) open /dev/dri/card0: No such file or directory
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Loading sub module "fbdevhw"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) LoadModule: "fbdevhw"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Module fbdevhw: vendor="X.Org Foundation"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]:  
   compiled for 1.21.1.4, module version = 0.0.2
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]:  
   ABI class: X.Org Video Driver, version 25.2
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) Unable to find a valid framebuffer device
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(WW) Falling back to old probe method for fbdev
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Loading sub module "fbdevhw"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) LoadModule: "fbdevhw"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) Module fbdevhw: vendor="X.Org Foundation"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]:  
   compiled for 1.21.1.4, module version = 0.0.2
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]:  
   ABI class: X.Org Video Driver, version 25.2
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) open /dev/fb0: No such file or directory
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
vesa: Ignoring device with a bound kernel driver
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) Screen 0 deleted because of no matching config section.
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) UnloadModule: "modesetting"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(EE) Screen 0 deleted because of no matching config section.
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) UnloadModule: "fbdev"
  gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: 
(II) UnloadSubModule: "fbdevhw"
  gru 30 0

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.15.0.132.131)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta (5.15.0.132.131) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

backport-iwlwifi-dkms/11510-0ubuntu1~22.04.1 (amd64, arm64, armhf, ppc64el)
ddcci-driver-linux/unknown (amd64)
glibc/unknown (ppc64el)
lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64, armhf, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2094270] Re: Bring in some 6.8 CONFIG annotations that were missed

[Jacob Martin]

** Also affects: linux-nvidia-6.11 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
   Status: New => Fix Committed

** Changed in: linux-nvidia-6.11 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2094270

Title:
  Bring in some 6.8 CONFIG annotations that were missed

Status in linux-nvidia-6.11 package in Ubuntu:
  Invalid
Status in linux-nvidia-6.11 source package in Noble:
  Fix Committed

Bug description:
   CONFIG_CORESIGHT_TRBE   policy<{'arm64': 'm'}>
   CONFIG_CORESIGHT_TRBE   note<'Required for Grace 
enablement'>

  +CONFIG_PREEMPT_NONE policy<{'amd64': 'n', 
'arm64': 'y'}>
  +CONFIG_PREEMPT_NONE note<'Required for NVIDIA 
workloads'>
  +
  +CONFIG_PREEMPT_VOLUNTARYpolicy<{'amd64': 'y', 
'arm64': 'n'}>
  +CONFIG_PREEMPT_VOLUNTARYnote<'Required for NVIDIA 
workloads'>
  +
  +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDpolicy<{'arm64': 'n'}>
  +CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDnote<'Required for NVIDIA 
workloads'>
  +
  +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE policy<{'amd64': 'n', 
'arm64': 'y'}>
  +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE note<'Required for NVIDIA 
workloads'>
  +
   CONFIG_DRM_NOUVEAU  policy<{'amd64': 'n', 
'arm64': 'n'}>
   CONFIG_DRM_NOUVEAU  note<'Disable nouveau for 
NVIDIA kernels'>

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2094270/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2094821] Re: PCI resources unassigned with Bluefield3 switch

[Jacob Martin]

** Also affects: linux-nvidia-6.11 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-nvidia (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: linux-nvidia-6.11 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-nvidia (Ubuntu)
   Status: New => Invalid

** Changed in: linux-nvidia-6.11 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-nvidia (Ubuntu Noble)
   Status: New => Fix Committed

** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2094821

Title:
  PCI resources unassigned with Bluefield3 switch

Status in linux-nvidia package in Ubuntu:
  Invalid
Status in linux-nvidia-6.11 package in Ubuntu:
  Invalid
Status in linux-nvidia source package in Noble:
  Fix Committed
Status in linux-nvidia-6.11 source package in Noble:
  Fix Committed

Bug description:
  System with Mellanox Bluefield3 with a Bluefield3 card and 4 NVME when 
probing will see at dmesg some pci resources unassigned. 
  Will see these messages at dmesg:
  [8.670754] pci 0006:03:00.0: BAR 0: assigned [mem 
0x6300c000-0x6300c1ff 64bit pref]
  [8.679447] pci 0006:03:00.1: BAR 0: assigned [mem 
0x6300c200-0x6300c3ff 64bit pref]
  [8.688134] pci 0006:03:00.2: BAR 0: no space for [mem size 0x0080 
64bit pref]
  [8.695876] pci 0006:03:00.2: BAR 0: failed to assign [mem size 0x0080 
64bit pref]
  [8.703974] pci 0006:03:00.0: BAR 7: no space for [mem size 0x0200 
64bit pref]
  [8.711714] pci 0006:03:00.0: BAR 7: failed to assign [mem size 0x0200 
64bit pref]
  [8.719811] pci 0006:03:00.1: BAR 7: no space for [mem size 0x0200 
64bit pref]
  [8.727553] pci 0006:03:00.1: BAR 7: failed to assign [mem size 0x0200 
64bit pref]
  [8.735650] pci 0006:03:00.0: BAR 6: assigned [mem 
0x63004000-0x6300400f pref]
  [8.743748] pci 0006:03:00.1: BAR 6: assigned [mem 
0x63004010-0x6300401f pref]
  [8.751845] pci 0006:03:00.0: BAR 0: assigned [mem 
0x6300c000-0x6300c1ff 64bit pref]
  [8.760531] pci 0006:03:00.1: BAR 0: assigned [mem 
0x6300c200-0x6300c3ff 64bit pref]
  [8.769217] pci 0006:03:00.2: BAR 0: no space for [mem size 0x0080 
64bit pref]
  [8.776956] pci 0006:03:00.2: BAR 0: failed to assign [mem size 0x0080 
64bit pref]
  [8.785052] pci 0006:03:00.0: BAR 6: assigned [mem 
0x63004000-0x6300400f pref]
  [8.793150] pci 0006:03:00.1: BAR 6: assigned [mem 
0x63004010-0x6300401f pref]
  [8.801247] pci 0006:03:00.1: BAR 7: no space for [mem size 0x0200 
64bit pref]
  [8.808987] pci 0006:03:00.1: BAR 7: failed to assign [mem size 0x0200 
64bit pref]
  [8.817086] pci 0006:03:00.0: BAR 7: no space for [mem size 0x0200 
64bit pref]
  [8.824828] pci 0006:03:00.0: BAR 7: failed to assign [mem size 0x0200 
64bit pref]

  ...
  [9.180489] pci_bus 0006:00: Some PCI device resources are unassigned, try 
booting with pci=realloc

  We were using the kernel parameter pci=realloc to avoid the failure but patch 
in this lore discussion 
  https://lore.kernel.org/all/20241204022457.51322-1-kaihe...@nvidia.com/
  fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2094821/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-132.143)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules 
(5.15.0-132.143) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525/unknown (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2064176] Re: LXD fan bridge causes blocked tasks

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2064176

Title:
  LXD fan bridge causes blocked tasks

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  User can trigger a host crash on Jammy/Noble by launching
  a container which uses Ubuntu FAN network in LXD.

  [Fix]

  A first proposed patch fixes RCU locking by releasing rcu_read_lock
  on the skb discard codepath.

  Second patch just use a proper way (dev_core_stats_tx_dropped_inc() function)
  to increase netdev's tx_dropped statistic value.

  [Test Plan]

  As provided by Max Asnaashari:

  # Install LXD from channel latest/stable
  snap install lxd --channel latest/stable

  # Configure LXD
  lxd init --auto

  # Create a FAN network
  lxc network create lxdfan0 bridge.mode=fan ipv4.nat=true

  # Launch a container using the FAN network
  lxc launch ubuntu-minimal:22.04 c1 --network lxdfan0

  # Try to interact with LXD
  lxc ls

  [Where problems could occur]

  Change is local and only related to Ubuntu FAN code. I would not expect
  any problems with this patchset.

  Hi, cross posting this from
  https://github.com/canonical/lxd/issues/12161

  I've got a lxd cluster running across 3 VMs using the fan bridge. I'm
  using a dev revision of LXD based on 6413a948. Creating a container
  causes the trace in the attached syslog snippet; this causes the
  container creation process to hang indefinitely. ssh logins, `lxc
  shell cluster1`, and `ps -aux` also hang.

  Apr 29 17:15:01 cluster1 kernel: [  161.250951] [ cut here 
]
  Apr 29 17:15:01 cluster1 kernel: [  161.250957] Voluntary context switch 
within RCU read-side critical section!
  Apr 29 17:15:01 cluster1 kernel: [  161.250990] WARNING: CPU: 2 PID: 510 at 
kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251003] Modules linked in: nft_masq 
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vxlan 
ip6_udp_tunnel udp_tunnel dummy br
  idge stp llc zfs(PO) spl(O) nf_tables libcrc32c nfnetlink vhost_vsock vhost 
vhost_iotlb binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common 
kvm_intel kvm irqbypass crct10dif
  _pclmul crc32_pclmul virtio_gpu polyval_clmulni polyval_generic 
ghash_clmulni_intel sha256_ssse3 sha1_ssse3 virtio_dma_buf aesni_intel 
vmw_vsock_virtio_transport 9pnet_virtio xhci_
  pci drm_shmem_helper i2c_i801 ahci 9pnet vmw_vsock_virtio_transport_common 
xhci_pci_renesas drm_kms_helper libahci crypto_simd joydev virtio_input cryptd 
lpc_ich virtiofs i2c_smbus
   vsock psmouse input_leds mac_hid serio_raw rapl qemu_fw_cfg vmgenid nfsd 
dm_multipath auth_rpcgss scsi_dh_rdac nfs_acl lockd scsi_dh_emc scsi_dh_alua 
grace sch_fq_codel drm sunrpc
   efi_pstore virtio_rng ip_tables x_tables autofs4
  Apr 29 17:15:01 cluster1 kernel: [  161.251085] CPU: 2 PID: 510 Comm: nmbd 
Tainted: P   O   6.5.0-28-generic #29~22.04.1-Ubuntu
  Apr 29 17:15:01 cluster1 kernel: [  161.251089] Hardware name: QEMU Standard 
PC (Q35 + ICH9, 2009)/LXD, BIOS unknown 2/2/2022
  Apr 29 17:15:01 cluster1 kernel: [  161.251091] RIP: 
0010:rcu_note_context_switch+0x2a7/0x2f0
  Apr 29 17:15:01 cluster1 kernel: [  161.251095] Code: 08 f0 83 44 24 fc 00 48 
89 de 4c 89 f7 e8 d1 af ff ff e9 1e fe ff ff 48 c7 c7 d0 60 56 88 c6 05 e6 27 
40 02 01 e8 79 b2 f2 ff
  <0f> 0b e9 bd fd ff ff a9 ff ff ff 7f 0f 84 75 fe ff ff 65 48 8b 3c
  Apr 29 17:15:01 cluster1 kernel: [  161.251098] RSP: 0018:b9cbc11dbbc8 
EFLAGS: 00010046
  Apr 29 17:15:01 cluster1 kernel: [  161.251101] RAX:  RBX: 
941ef7cb3f80 RCX: 
  Apr 29 17:15:01 cluster1 kernel: [  161.251103] RDX:  RSI: 
 RDI: 
  Apr 29 17:15:01 cluster1 kernel: [  161.251104] RBP: b9cbc11dbbe8 R08: 
 R09: 0

[Kernel-packages] [Bug 2080378] Re: IOMMU warnings on AMD systems after booting into kdump kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080378

Title:
  IOMMU warnings on AMD systems after booting into kdump kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [impact]
  On some AMD systems, loading into a kdump kernel will show a few warnings 
IOMMU warnings during early boot. These warnings have not been observed yet to 
cause any issues but there is a fix upstream for them. Currently only focal-HWE 
and jammy 5.15 are affected. Newer kernel releases already have the fix. The 
stack traces look like the following:

  [9.125703] WARNING: CPU: 0 PID: 1 at drivers/iommu/amd/init.c:829 
iommu_init_irq+0x2f2/0x3c0
  [9.134223] Modules linked in:
  [9.137283] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
5.15.0-107-generic #117~20.04.1-Ubuntu
  [9.145716] Hardware name: 
  [9.153111] RIP: 0010:iommu_init_irq+0x2f2/0x3c0
  [9.157729] Code: 90 ff 85 c0 0f 84 e8 fd ff ff be 01 00 00 00 44 89 
ef 89 45 94 e8 2e dc 90 ff 4c 89 e7 e8 b6 cf 90 ff 8b 45 94 e9 6c fd ff ff <0f> 
0b 31 c0 e9 63 fd ff ff 0f 0b 31 c0 e9 5a fd ff ff 31 c9 48 c7
  [9.176475] RSP: 0018:a005000fbd00 EFLAGS: 00010202
  [9.181703] RAX: 0198 RBX: 9335af44a000 RCX: 
a0050010
  [9.188838] RDX: a0050010 RSI: 9335c05b9140 RDI: 
9335c05b95c8
  [9.195970] RBP: a005000fbd70 R08:  R09: 

  [9.203101] R10: ffe0 R11: 0025 R12: 
9335c0468cc0
  [9.210231] R13: 001a R14: 9335b0151600 R15: 
0006
  [9.217362] FS:  () GS:9336aec0() 
knlGS:
  [9.225446] CS:  0010 DS:  ES:  CR0: 80050033
  [9.231185] CR2:  CR3: 02006c81 CR4: 
00350ef0
  [9.238318] Call Trace:
  [9.240763]  
  [9.242869]  ? show_regs.cold+0x1a/0x1f
  [9.246710]  ? iommu_init_irq+0x2f2/0x3c0
  [9.250722]  ? __warn+0x8b/0xe0
  [9.253868]  ? iommu_init_irq+0x2f2/0x3c0
  [9.257883]  ? report_bug+0xd5/0x110
  [9.261461]  ? handle_bug+0x39/0x90
  [9.264956]  ? exc_invalid_op+0x19/0x70
  [9.268794]  ? asm_exc_invalid_op+0x1b/0x20
  [9.272980]  ? iommu_init_irq+0x2f2/0x3c0
  [9.276993]  ? e820__memblock_setup+0x89/0x89
  [9.281353]  state_next+0x3f5/0x6ba
  [9.284847]  ? e820__memblock_setup+0x89/0x89
  [9.289206]  iommu_go_to_state+0x28/0x31
  [9.293131]  amd_iommu_init+0x15/0x4f
  [9.296797]  ? e820__memblock_setup+0x89/0x89
  [9.301150]  pci_iommu_init+0x1a/0x48
  [9.304817]  do_one_initcall+0x48/0x1e0
  [9.308655]  kernel_init_freeable+0x284/0x2f1
  [9.313016]  ? rest_init+0x100/0x100
  [9.316593]  kernel_init+0x1b/0x150
  [9.320078]  ? rest_init+0x100/0x100
  [9.323658]  ret_from_fork+0x22/0x30
  [9.327238]  
  [9.329431] ---[ end trace 6113ebe8cb8ce54f ]---

  The commit that fixes the issue is:

  * c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC
  (AVIC) Enablement")

  However another commit was also created that fixed compiler warnings
  introduced by the above commit:

  * be280ea763f7 ("iommu/amd: Fix compile warning in init code")

  [Test Plan]

  1- On a machine using an AMD CPU and running the focal-hwe or jammy
  5.15 kernel, make sure kdump is configured following these steps:
  https://ubuntu.com/server/docs/kernel-crash-dump

  2- Trigger a kernel panic. This can be done using the command:

  $ echo c > /proc/sysrq-trigger

  3- When the machine reboots, you will notice IOMMU warnings during the
  early phases of the boot process in dmesg.

  4- After applying the two commits and repeating step 2. No IOMMU
  warnings should show up anymore in dmesg.

  [Fix]
  Only the first commit of the below list 

[Kernel-packages] [Bug 2074380] Re: [UBUNTU 22.04] s390/cpum_cf: make crypto counters upward compatible

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2074380

Title:
  [UBUNTU 22.04] s390/cpum_cf: make crypto counters upward compatible

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  SRU Justification:

  [ Impact ]

   * The CPU Measurement Facility (CPU MF) crypto counter set
     is not listed in the device sysfs tree - it's not exported
     in the sysfs directory /sys/devices/cpum_cf/events.

   * The attribute files for each CPU-MF counter defined
     in the crypto counter set is missing.

   * This is caused by the counter second version number of CPU MF
     hardware being incremented on new machines.

   * This causes a sanity check to fail,
     but the counters are supported by hardware.

   * The solution is to remove the upper limit in counter second
     version number check.

  [ Fix ]

   * f10933cbd2df f10933cbd2dfddf6273698a45f76db9bafd8150f
 "s390/cpum_cf: make crypto counters upward compatible across machine types"

   * The fix was upstream accepted with kernel v6.10(-rc1).

   * Upstream commit applies cleanly on noble master-next, 
 but needed to be backported to jammy master-next due to different code
 and context in kernel 5.15.

  [ Test Plan ]

   * Run the following commands on a new machine generation:
     (hence only doable by IBM)
     # ls -l /sys/devices/cpum_cf/events/ | grep AES

   * If the output is empty than this patch is required.

   * With a patched kernel the output should be like:
     # ls /sys/devices/cpum_cf/events/ | grep AES
     AES_BLOCKED_CYCLES
     AES_BLOCKED_FUNCTIONS
     AES_CYCLES
     AES_FUNCTIONS

  [ Where problems could occur ]

   * This affects s390x only - CPU MF is s390-specific,
     and only s390 specific code is modified.

   * And it furthermore is limited to the crypto counter set
     of CPU MF.

   * So any impact is likely limited to hardware crypto counters
     on s390x only.

   * In s390/kernel/perf_cpum_cf.c the else if case got changed from
     explicitly checking for 6 or 7 to >= 6 which seems to require
     attention for future 8 and more cases.

   * In s390/kernel/perf_cpum_cf_events.c the switch (ci.csvn) statement
     was changed to an if / else if with similar logic.
     Again attentioin for any potential future cases >= 8.

   * It does not look like currently used cases (1..5 and 6..7)
     are affected by the modification, just >7.

   * Test build of patched jammy and noble s390x kernels were build
     and are avaiable here:
     https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380

  [ Other Info ]

   * Since the code/fix was upstream accepted with kernel v6.10(-rc1)
     it does not affect the current development release oracular.

   * This SRU can also be seen under the umbrella of new
  hardware enablement.

   * Since it requires special hw, the verification needs to be
     done by IBM.

  __

  Description:   kernel: s390/cpum_cf: make crypto counters upward
  compatible

  Symptom:   The CPU Measurement facility crypto counter set is not
     listed in the device sysfs tree.

  Problem:   The CPU Measurement facility crypto counter set is not
     exported in the sysfs directory
     /sys/devices/cpum_cf/events.
     The attribute files for each CPU-MF counter defined
     in the crypto counter set is missing. This is caused
     by the counter second version number of the CPU
     Measurement Facility hardware being incremented on
     new machines.  This causes a sanity check to fail,
     but the counters are supported by hardware.

  Solution:  Remove upper limit in counter second version number
     check.

  Reproduction:  Run command on a new machine generation:
  # ls -l /sys/devices/cpum_cf/events/ | 

[Kernel-packages] [Bug 2069961] Re: turbostat fails with too many open files on large systems

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2069961

Title:
  turbostat fails with too many open files on large systems

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in linux source package in Noble:
  Fix Released

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2069961

  [Impact]

  On large systems, e.g. with 512 cpus or more, turbostat fails to run
  due to exceeding the rlimit for number of files. 512 cpus requires
  1028 file descriptors, but the current limit is 999.

  $ lscpu
  ...
  CPU(s):  512
    On-line CPU(s) list:   0-511
  ...

  $ sudo turbostat
  ...
  turbostat: /sys/devices/system/cpu/cpu477/cpuidle/state0/usage: open failed: 
Too many open files

  There is no workaround, apart from maybe using powerstat instead.

  [Fix]

  The fix is to increase the rlimit to increase the amount of file
  descriptors that turbostat can open to 2^15, which should be plenty
  for some time to come.

  commit 3ac1d14d0583a2de75d49a5234d767e2590384dd
  Author: Wyes Karny 
  Date:   Tue Oct 3 05:07:51 2023 +
  Subject: tools/power turbostat: Increase the limit for fd opened
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3ac1d14d0583a2de75d49a5234d767e2590384dd

  This landed in 6.9-rc4, and requires a backport for minor context
  adjustment in the first hunk for jammy. Noble got fixed already
  through upstream stable.

  [Testcase]

  Deploy a bare metal system with 512 or more cpus.

  Install linux-tools:

  $ sudo apt install linux-tools-$(uname -r)

  Run turbostat:

  $ sudo turbostat
  ...
  turbostat: /sys/devices/system/cpu/cpu477/cpuidle/state0/usage: open failed: 
Too many open files

  There are test kernels available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf388491-test

  If you install them, you should be able to see normal turbostat output
  for all cpus installed in the system.

  [Where problems can occur]

  We are simply increasing the rlimit for file descriptors that
  turbostat can open. This should have no impact on any existing
  systems.

  If a regression should occur, then turbostat functionality might not
  work. Users could use powerstat instead as a workaround while things
  are fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069961/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2093263] Re: apply NVIDIA patches Jan 8, 2025

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2093263

Title:
  apply NVIDIA patches Jan 8, 2025

Status in linux-nvidia-tegra package in Ubuntu:
  New
Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  apply NVIDIA patches Jan 8, 2025

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2093263/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2091990] Re: ovs/linuxbridge jobs running on ubuntu jammy broken with latest kernel 5.15.0-127.137

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2091990

Title:
  ovs/linuxbridge jobs running on ubuntu jammy broken with latest kernel
  5.15.0-127.137

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Oracular:
  Fix Committed

Bug description:
  A commit[1] got backported to ubuntu jammy kernel[2] which had an
  issue, Fix is already available[3] but not got released with latest
  kernel so all our ovs/linuxbridge/fullstack/functional jobs running on
  ubuntu jammy are impacted. Master also impacted as we have grenade
  jobs running on ubuntu and 1 dedicated job that we run on ubuntu
  jammy.

  Errors like below can be seen in these jobs
  (4, ('', 'ip6tables-restore v1.8.7 (nf_tables): unknown option 
"--set-xmark"\nError occurred at line: 26\nTry `ip6tables-restore -h\' or 
\'ip6tables-restore --help\' for more information.\n', 2)) {{(pid=56448)

  # Completed by iptables_manager
  ; Stdout: ; Stderr: ip6tables-restore v1.8.7 (nf_tables): unknown option 
"--set-xmark"
  Error occurred at line: 26
  Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.

  example failures:-
  
https://b711d185688da3b864bc-5593d50c131879f6a486eeedbad80e3c.ssl.cf2.rackcdn.com/937879/1/check/neutron-functional-with-uwsgi/91e08a5/testr_results.html
  
https://2d070bf6c45f6c37d47e-4e5a5ec72a48e33cae1713c394f26e02.ssl.cf1.rackcdn.com/937879/1/check/neutron-fullstack-with-uwsgi/4b33689/testr_results.html
  
https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_720/937879/1/check/neutron-ovs-grenade-dvr-multinode/720442a/controller/logs/grenade.sh_log.txt
  
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_0be/937603/2/check/neutron-tempest-plugin-openvswitch-ubuntu-jammy/0be23a8/testr_results.html
  
https://7c5dce2b8628b0a2e78b-f88cc2e228aea8b2c74f92ce7ecb609d.ssl.cf1.rackcdn.com/periodic/opendev.org/openstack/neutron/stable/2024.2/neutron-tempest-plugin-linuxbridge-2024-2/1d99042/testr_results.html


  [1] 
https://github.com/torvalds/linux/commit/0bfcb7b71e735560077a42847f69597ec7dcc326
  [2] https://launchpad.net/ubuntu/+source/linux/5.15.0-127.137
  [3] 
https://github.com/torvalds/linux/commit/306ed1728e8438caed30332e1ab46b28c25fe3d8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091990/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2085479] Re: apply NVIDIA patches Oct 4-23, 2024

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2085479

Title:
  apply NVIDIA patches Oct 4-23, 2024

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released
Status in linux-nvidia-tegra-igx package in Ubuntu:
  Fix Released

Bug description:
  apply NVIDIA patches Oct 4-23, 2024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2085479/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959940

Title:
  [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer
  keys - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [ Impact ]

   * Hypervisor-initiated dumps for Secure Execution
 (aka confidential computing) guests are not helpful,
 because memory and CPU state is encrypted by a
 transient key only available to the Ultravisor (uv).

   * Workload owners can still configure kdump in order to obtain kernel
 crash information, but there are situation where kdump doesn't work.

   * In such situations problem determination is severely impeded.

   * This patch set solves this by implementing dumps created in a way
 that can only be decrypted by the owner of the guest image
 and be used for problem determination.

  [ Test Plan ]

   * The setup of a Secure Execution environment is not trivial
 and requires a certain set of hardware (IBM z15 or higher)
 with FC 115).

   * On top of the modification of qemu that are handled in this
 LP bug, modifications of the Kernel (LP#1959940) and
 the s390-tools (LP#1959965) are required on top.

   * So at least a modified kernel and qemu test builds are needed
 or both should be in -proposed at the same time (which might
 be difficult).
 A modified s390-tools is not urgently needed, since for the
 verification of the kernel and qemu part a newer version
 can be used (but a modified s390-tools is also available in PPA).

   * A detailed description (using Ubuntu as example) on how to setup
 secure execution is available here:
 Introducing IBM Secure Execution for Linux, April 2024 update
 https://www.ibm.com/docs/en/linuxonibm/pdf/lx24se04.pdf

   * And information on 'Working with dumps of KVM guests in
 IBM Secure Execution mode' is available here:
 
https://www.ibm.com/docs/en/linux-on-systems?topic=commands-zgetdump#czgetdump__se_dump_examples

  [ Where problems could occur ]

   * Ultravisor (uv) return codes are introduced, which is
 generally appreciated. Just the right return codes need to be set
 (and reacted upon).

   * Protected virtual machine dumps are newly introduced on top of
 dump of 'normal' KVM VMs.
 Since code is shared, it could have an unforeseen impact.

   * The doc renaming could lead to confusion,
 if people rely on old doc structure.

   * The new capability case (217) could cause issues,
 for example is case of issues during initialization..
   
   * CPU dump functionality was added (mainly as new s390x specific code
 under s390/kvm), but CPU dump is only one part,
 if not working correctly, it may lead to partially useless dump data.

   * Configuration dump functionality was also added
 (again mainly as new s390x specific code under s390/kvm),
 similar to CPU dump.
 And moving from dumping inside of a VM to dumping from outside
 (due to potential failures if done inside), might lead to a more
 complex flow (now involving the uv), hence could be more error prone.

   * Adding query dump information, requires user space buffers.
 Here it's crucial that buffer size is big enough.

   * The newly added constants and structure definitions that are
 needed for dump support could become problematic in case wrong
 data types were used (applies to all header modifications).

   * IOCTL for PV information retrieval got introduced
 (kvm_s390_handle_pv_info, kvm_s390_handle_pv).
 There are potential side effect (see man ioctl),
 hence all potential failure cases should be covered.

   * New dump feature requires to know how much memory is needed, but if
 this call for this is incorrect, it could break the dump process.

   * uv_cb_header struct changed to offset representation,
 but using wrong offsets will lead to a

[Kernel-packages] [Bug 2085082] Re: Cannot detect audio sinks and sources in proposed kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2085082

Title:
  Cannot detect audio sinks and sources in proposed kernel

Status in linux package in Ubuntu:
  New
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  [Impact]

  Failed to detect audio sinks/sources.

  [Test Case]

  1. run "pactl list sinks short | grep -v -E "monitor|auto_null" to check if 
any sinks was found
  2. run "pactl list sources short | grep -v -E "monitor|auto_null" to check if 
any sources was found

  
  [Verify]

  1. reverse the kernel to 5.15.0.124
  2. run the same tests
  3. confirmed audio is activate

  
  [Fail rate]

  3/3

  
  [Expected result]

  0 
alsa_output.pci-_00_1f.3-platform-sof_sdw.HiFi__hw_sofsoundwire_7__sink 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED
  1 
alsa_output.pci-_00_1f.3-platform-sof_sdw.HiFi__hw_sofsoundwire_6__sink 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED
  2 
alsa_output.pci-_00_1f.3-platform-sof_sdw.HiFi__hw_sofsoundwire_5__sink 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED
  3 
alsa_output.pci-_00_1f.3-platform-sof_sdw.HiFi__hw_sofsoundwire__sink   
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED
  4 
alsa_output.pci-_00_1f.3-platform-sof_sdw.HiFi__hw_sofsoundwire_2__sink 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED


  
  [Actual result]

  No available sources found.

  
  [Additional information]
  https://certification.canonical.com/hardware/202111-29676/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-125-generic 5.15.0-125.135~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-125.135~20.04.1-generic 5.15.167
  Uname: Linux 5.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
  Date: Mon Oct 21 14:02:46 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-starmie-adl+X173
  InstallationDate: Installed on 2024-10-16 (4 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085082/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2077321] Re: Please backport the more restrictive XSAVES deactivation for Zen1/2 arch

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1020.20 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to 'verification-done-jammy-linux-nvidia-tegra-igx'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-nvidia-
tegra-igx' to 'verification-failed-jammy-linux-nvidia-tegra-igx'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-igx-v2 
verification-needed-jammy-linux-nvidia-tegra-igx

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077321

Title:
  Please backport the more restrictive XSAVES deactivation for  Zen1/2
  arch

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Confirmed

Bug description:
  On recent kernels, commit https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/jammy/commit/?id=b0563468eeac88ebc70559d52a0b66efc37e4e9d
  deactivate the XSAVES instruction for Zen 1/2 architectures.

  This means that for a QEMU vm using cpu=host running on older kernels
  where XSAVES is activated, it will not be possible to migrate that VM
  to newer kernels which have the XSAVES disabled.

  The more recent commit
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29ba89f1895285f06c333546882e0c5ae9a6df23
  only deactivates XSAVES on kernel where the fixed microcode is not
  present.

  This will prevent the QEMU migration problem to occur on AMD system
  where the microcode has been correctly updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077321/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095100] Re: kernel panic when setting application in fullscreen

[AaronMa]

https://kernel.ubuntu.com/mainline/v6.13-rc1/

please try 6.13-rc1.

Yes, need to confirm it's already fixed by latest kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095100

Title:
  kernel panic when setting application in fullscreen

Status in linux package in Ubuntu:
  New

Bug description:
  Since 24.10, on amdgpu device (AMD Ryzen 7 PRO 5850U), anytime I set
  an application in fullscreen mode (video player, firefox, signal etc.)
  I end up with this crash.

  It seems to only reproduce when I have my two 4K screens connected to
  the USB-C ThinkPad Thunderbolt station. Laptop screen is disabled in
  that setup. I dont reproduce when only on the laptop screen.

  [92840.827857] [ cut here ]
  [92840.827861] atomic remove_fb failed with -28
  [92840.827874] WARNING: CPU: 11 PID: 1219167 at 
drivers/gpu/drm/drm_framebuffer.c:1146 drm_framebuffer_remove+0x233/0x240
  [92840.827884] Modules linked in: wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel ipmi_devintf ipmi_msghandler uas 
usb_storage nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
ccm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc overlay qrtr uhid rfcomm 
cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_acp_legacy_mach 
snd_acp_mach snd_soc_nau8821 intel_rapl_msr amd_atl intel_rapl_common 
nls_iso8859_1 snd_acp3x_rn snd_soc_dmic ee1004 snd_acp3x_pdm_dma 
snd_sof_amd_acp63 edac_mce_amd snd_sof_amd_vangogh amdgpu snd_sof_amd_rembrandt 
snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp kvm_amd 
snd_sof snd_sof_utils kvm snd_pci_ps snd_amd_sdw_ac
 pi btusb soundwire_amd btrtl uvcvideo
  [92840.828004]  soundwire_generic_allocation btintel rapl btbcm 
videobuf2_vmalloc amdxcp uvc btmtk drm_exec soundwire_bus gpu_sched 
videobuf2_memops snd_hda_codec_realtek snd_soc_core drm_buddy iwlmvm 
videobuf2_v4l2 drm_suballoc_helper snd_hda_codec_generic snd_compress 
drm_ttm_helper snd_hda_scodec_component ttm videodev snd_hda_codec_hdmi 
ac97_bus snd_usb_audio bluetooth drm_display_helper mac80211 videobuf2_common 
snd_pcm_dmaengine snd_seq_midi snd_usbmidi_lib think_lmi snd_hda_intel 
snd_seq_midi_event snd_rpl_pci_acp6x firmware_attributes_class libarc4 snd_ump 
snd_acp_pci snd_seq snd_intel_dspcfg cec snd_acp_legacy_common wmi_bmof 
snd_intel_sdw_acpi snd_pci_acp6x snd_rawmidi snd_hda_codec snd_pci_acp5x 
snd_seq_device snd_hda_core mc snd_hwdep snd_rn_pci_acp3x iwlwifi 
snd_acp_config snd_pcm snd_soc_acpi mhi_wwan_ctrl i2c_piix4 mhi_wwan_mbim 
rc_core k10temp snd_pci_acp3x i2c_smbus snd_ctl_led wwan ccp i2c_algo_bit 
snd_timer cfg80211 thinkpad_acpi nvram i2c_scmi joydev input_leds 
 mac_hid serio_raw sch_fq_codel msr
  [92840.828125]  parport_pc ppdev lp parport nvme_fabrics efi_pstore nfnetlink 
dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c hid_logitech_hidpp hid_logitech_dj dm_crypt hid_generic usbhid hid 
cdc_ether usbnet r8152 mii crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel snd nvme rtsx_pci_sdmmc sha256_ssse3 
ucsi_acpi soundcore mhi_pci_generic r8169 xhci_pci sha1_ssse3 nvme_core psmouse 
typec_ucsi video sparse_keymap mhi xhci_pci_renesas rtsx_pci realtek nvme_auth 
typec platform_profile wmi aesni_intel crypto_simd cryptd
  [92840.828214] CPU: 11 UID: 0 PID: 1219167 Comm: kworker/11:0 Tainted: G  
  W  6.11.0-13-generic #14-Ubuntu
  [92840.828219] Tainted: [W]=WARN
  [92840.828221] Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET59W 
(1.29 ) 09/18/2024
  [92840.828224] Workqueue: events drm_mode_rmfb_work_fn
  [92840.828230] RIP: 0010:drm_framebuffer_remove+0x233/0x240
  [92840.828235] Code: ea 48 c7 c7 c1 2b c7 8c 48 89 c6 e8 37 60 45 ff 0f 0b e9 
16 fe ff ff 4c 8b 2f eb d6 89 c6 48 c7 c7 b8 47 d4 8c e8 1d 60 45 ff <0f> 0b e9 
3c fe ff ff 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90
  [92840.828238] RSP: 0018:a9e5103a7df0 EFLAGS: 00010246
  [92840.828242] RAX:  RBX: 915a297ec200 RCX: 

  [92840.828245] RDX:  RSI:  RDI: 

  [92840.828247] RBP: a9e5103a7e10 R08:  R09: 

  [92840.828250] R10:  R11:  R12: 
915a55d80010
  [92840.828252] R13: a9e5115dfd80 R14: a9e5115dfd60 R15: 

  [92840.828255] FS:  () GS:916011d8() 
knlGS:
  [92840.828257] CS:  0010 DS:  ES:  CR0: 80050033
  [92840.828260] CR2: 728564a66bbc CR3:

[Kernel-packages] [Bug 988799]

[james09cameroon]

It appears that the Bugzilla link you provided
(https://bugzilla.kernel.org/show_bug.cgi?id=12309) is related to a
specific bug report for the Linux kernel. However, I do not have the
capability to access external websites, including Bugzilla, and cannot
retrieve the specific details of the bug or its context. If you could
provide some details on the bug or the issue you’re experiencing, I
would be happy to help write a response or answer with relevant
information and references based on the context you provide.

In general, when responding to kernel bug reports, the steps include:

Reproducing the issue: Make sure the issue can be replicated using the provided 
steps or under similar conditions.
System Information: Provide details about your hardware (CPU, GPU, storage like 
NVMe SSD https://serverorbit.com/solid-state-drives-ssd/nvme-ssd/6-4tb-2-5inch, 
etc.) and software environment (kernel version, distro, etc.).
Log Files: Attach relevant log files, such as dmesg logs, kernel logs, and 
syslogs, to help diagnose the issue.
Potential Fixes or Workarounds: If possible, suggest a workaround or solution 
based on existing patches or configuration changes.
References: Cite official kernel documentation or other resources that may help 
clarify or resolve the issue.
If you want to draft a response, please provide more context or details, and I 
can assist you in formulating an answer accordingly.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/988799

Title:
  Precise freezes under heavy i/o

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Whilst creating a VM with 20 GB persistent HD and my system froze
  until the disk was created.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-23-generic 3.2.0-23.36
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gema   2526 F pulseaudio
   /dev/snd/controlC0:  gema   2526 F pulseaudio
   /dev/snd/controlC1:  gema   2526 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,104383c4,0010'
 Controls  : 45
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:081d'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 16
 Mono: Capture 12 [75%] [24.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Thu Apr 26 11:59:11 2012
  HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   virbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0401
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:c

[Kernel-packages] [Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04

[Gerald Krottendorfer]

I could resolve my problem, credits to:
https://askubuntu.com/questions/1511648/audio-not-working-ubuntu-24-04

I copy pasted the answer from user
https://askubuntu.com/users/123433/linjunhalida

-START-
I had the same issue on my old XPS 15 9560 (Intel audio driver). For me the 
audio worked fine when trying out the Ubuntu (prior to installation) but not 
after installation.Seems snd_soc_avs is the issue so blacklisting that solves 
it for me

Add the below at end of /etc/modprobe.d/alsa-base.conf and restart alsa:
sudo alsa force-reload

options snd-hda-intel model=auto
blacklist snd_soc_avs

--END-

This bugfix worked for me, audio is running stable, detects plug in/out
of my headphones and keeps running after rebooting / hybernating.

Since I made no chages to my former bugfix attempt, "snd_soc_avs" is now
blacklisted twice in alsa-base.conf as well as in in blacklist.conf.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound, stutters and clicks after upgrade to 24.04

Status in linux package in Ubuntu:
  Expired
Status in pipewire package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04, it does not work on the
  computer.

  Work with:
  1) Bluetooth
  2) Jack 3.5

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pipewire 1.0.5-1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:52:58 2024
  InstallationDate: Installed on 2024-03-25 (28 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095100] Re: kernel panic when setting application in fullscreen

[Pirouette Cacahuète]

Before rebooting, I was trying to reproduce again and now I dont
reproduce. Error -28 is -ENOSPC. I'm wondering if the problem requires
more time to present **or** if it depends on more applications / windows
running.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095100

Title:
  kernel panic when setting application in fullscreen

Status in linux package in Ubuntu:
  New

Bug description:
  Since 24.10, on amdgpu device (AMD Ryzen 7 PRO 5850U), anytime I set
  an application in fullscreen mode (video player, firefox, signal etc.)
  I end up with this crash.

  It seems to only reproduce when I have my two 4K screens connected to
  the USB-C ThinkPad Thunderbolt station. Laptop screen is disabled in
  that setup. I dont reproduce when only on the laptop screen.

  [92840.827857] [ cut here ]
  [92840.827861] atomic remove_fb failed with -28
  [92840.827874] WARNING: CPU: 11 PID: 1219167 at 
drivers/gpu/drm/drm_framebuffer.c:1146 drm_framebuffer_remove+0x233/0x240
  [92840.827884] Modules linked in: wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel ipmi_devintf ipmi_msghandler uas 
usb_storage nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
ccm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc overlay qrtr uhid rfcomm 
cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_acp_legacy_mach 
snd_acp_mach snd_soc_nau8821 intel_rapl_msr amd_atl intel_rapl_common 
nls_iso8859_1 snd_acp3x_rn snd_soc_dmic ee1004 snd_acp3x_pdm_dma 
snd_sof_amd_acp63 edac_mce_amd snd_sof_amd_vangogh amdgpu snd_sof_amd_rembrandt 
snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp kvm_amd 
snd_sof snd_sof_utils kvm snd_pci_ps snd_amd_sdw_ac
 pi btusb soundwire_amd btrtl uvcvideo
  [92840.828004]  soundwire_generic_allocation btintel rapl btbcm 
videobuf2_vmalloc amdxcp uvc btmtk drm_exec soundwire_bus gpu_sched 
videobuf2_memops snd_hda_codec_realtek snd_soc_core drm_buddy iwlmvm 
videobuf2_v4l2 drm_suballoc_helper snd_hda_codec_generic snd_compress 
drm_ttm_helper snd_hda_scodec_component ttm videodev snd_hda_codec_hdmi 
ac97_bus snd_usb_audio bluetooth drm_display_helper mac80211 videobuf2_common 
snd_pcm_dmaengine snd_seq_midi snd_usbmidi_lib think_lmi snd_hda_intel 
snd_seq_midi_event snd_rpl_pci_acp6x firmware_attributes_class libarc4 snd_ump 
snd_acp_pci snd_seq snd_intel_dspcfg cec snd_acp_legacy_common wmi_bmof 
snd_intel_sdw_acpi snd_pci_acp6x snd_rawmidi snd_hda_codec snd_pci_acp5x 
snd_seq_device snd_hda_core mc snd_hwdep snd_rn_pci_acp3x iwlwifi 
snd_acp_config snd_pcm snd_soc_acpi mhi_wwan_ctrl i2c_piix4 mhi_wwan_mbim 
rc_core k10temp snd_pci_acp3x i2c_smbus snd_ctl_led wwan ccp i2c_algo_bit 
snd_timer cfg80211 thinkpad_acpi nvram i2c_scmi joydev input_leds 
 mac_hid serio_raw sch_fq_codel msr
  [92840.828125]  parport_pc ppdev lp parport nvme_fabrics efi_pstore nfnetlink 
dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c hid_logitech_hidpp hid_logitech_dj dm_crypt hid_generic usbhid hid 
cdc_ether usbnet r8152 mii crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel snd nvme rtsx_pci_sdmmc sha256_ssse3 
ucsi_acpi soundcore mhi_pci_generic r8169 xhci_pci sha1_ssse3 nvme_core psmouse 
typec_ucsi video sparse_keymap mhi xhci_pci_renesas rtsx_pci realtek nvme_auth 
typec platform_profile wmi aesni_intel crypto_simd cryptd
  [92840.828214] CPU: 11 UID: 0 PID: 1219167 Comm: kworker/11:0 Tainted: G  
  W  6.11.0-13-generic #14-Ubuntu
  [92840.828219] Tainted: [W]=WARN
  [92840.828221] Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET59W 
(1.29 ) 09/18/2024
  [92840.828224] Workqueue: events drm_mode_rmfb_work_fn
  [92840.828230] RIP: 0010:drm_framebuffer_remove+0x233/0x240
  [92840.828235] Code: ea 48 c7 c7 c1 2b c7 8c 48 89 c6 e8 37 60 45 ff 0f 0b e9 
16 fe ff ff 4c 8b 2f eb d6 89 c6 48 c7 c7 b8 47 d4 8c e8 1d 60 45 ff <0f> 0b e9 
3c fe ff ff 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90
  [92840.828238] RSP: 0018:a9e5103a7df0 EFLAGS: 00010246
  [92840.828242] RAX:  RBX: 915a297ec200 RCX: 

  [92840.828245] RDX:  RSI:  RDI: 

  [92840.828247] RBP: a9e5103a7e10 R08:  R09: 

  [92840.828250] R10:  R11:  R12: 
915a55d80010
  [92840.828252] R13: a9e5115dfd80 R14: a9e5115dfd60 R15: 

  [92840.828255] FS:  () GS:916011d8() 
knlGS:
  [92840.828257] CS

[Kernel-packages] [Bug 2095151] [NEW] n:linux-meta-xilinx: migrate linux-xilinx-zynqmp package to linux-xilinx

[LEE KUAN-YING]

Public bug reported:

We want to do-release-upgrade on jammy:linux-xilinx-zynqmp.

But we don't have linux-xilinx-zynqmp package on noble and we only have
noble:linux-xilinx.

We have to make a transitional package for linux-xilinx-zynqmp to
migrate.

** Affects: linux-meta-xilinx (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-xilinx (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-meta-xilinx (Ubuntu Noble)
 Importance: Undecided
 Assignee: LEE KUAN-YING (kyyc0426)
 Status: New

** Also affects: linux-xilinx (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-xilinx (Ubuntu Noble)
 Assignee: (unassigned) => LEE KUAN-YING (kyyc0426)

** Also affects: linux-meta-xilinx (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-meta-xilinx (Ubuntu Noble)
 Assignee: (unassigned) => LEE KUAN-YING (kyyc0426)

** Changed in: linux-xilinx (Ubuntu Noble)
   Status: New => Invalid

** No longer affects: linux-xilinx (Ubuntu Noble)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx in Ubuntu.
https://bugs.launchpad.net/bugs/2095151

Title:
  n:linux-meta-xilinx: migrate linux-xilinx-zynqmp package to linux-
  xilinx

Status in linux-meta-xilinx package in Ubuntu:
  New
Status in linux-xilinx package in Ubuntu:
  New
Status in linux-meta-xilinx source package in Noble:
  New

Bug description:
  We want to do-release-upgrade on jammy:linux-xilinx-zynqmp.

  But we don't have linux-xilinx-zynqmp package on noble and we only
  have noble:linux-xilinx.

  We have to make a transitional package for linux-xilinx-zynqmp to
  migrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx/+bug/2095151/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2089711] Re: Request to backport mseal syscall to LTS 24.04 LTS GA kernel

[Juerg Haefliger]

** Description changed:

  Hello,
  
  My name is Jeff Xu, I work with Stephen Röttger on hardening the chrome
  browser.  I'm reaching out to explore the possibility of backporting
- memory sealing into the 22.04 LTS kernel.
+ memory sealing into the 24.04 LTS kernel.
  
  For context, it is worth noting that the Kernel introduces mseal support
  in version 6.10 [1].  The Chrome V8 engine will utilize the memory
  sealing function to protect its JIT compiler from memory corruption
  vulnerabilities. The change is merged in Chrome, and we believe that
  Ubuntu users would benefit from using this safer version of Chrome.
  
  In addition, glibc’s dynamic linker is adding mseal to seal RO mapping
  such as  .text, .rodata, .relco [2], the integration test is completed.
  
  The backport work includes 4 commits [3] [4] [5] [6].  ChromeOS and
  Android GKI both have the mseal backported to the 6.6 kernel.  I will
  send out patches for LTS 22.04 to kernel-t...@lists.ubuntu.com
  
  Thank you for your time and consideration.
  Best regards,
  Jeff
  
  [1] https://docs.kernel.org/userspace-api/mseal.html
  [2] https://sourceware.org/pipermail/libc-alpha/2024-September/160291.html
  [3] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595211/4
  [4] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595853/4
  [5] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5742931
  [6] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5802772

** Description changed:

  Hello,
  
  My name is Jeff Xu, I work with Stephen Röttger on hardening the chrome
  browser.  I'm reaching out to explore the possibility of backporting
  memory sealing into the 24.04 LTS kernel.
  
  For context, it is worth noting that the Kernel introduces mseal support
  in version 6.10 [1].  The Chrome V8 engine will utilize the memory
  sealing function to protect its JIT compiler from memory corruption
  vulnerabilities. The change is merged in Chrome, and we believe that
  Ubuntu users would benefit from using this safer version of Chrome.
  
  In addition, glibc’s dynamic linker is adding mseal to seal RO mapping
  such as  .text, .rodata, .relco [2], the integration test is completed.
  
  The backport work includes 4 commits [3] [4] [5] [6].  ChromeOS and
  Android GKI both have the mseal backported to the 6.6 kernel.  I will
- send out patches for LTS 22.04 to kernel-t...@lists.ubuntu.com
+ send out patches for LTS 24.04 to kernel-t...@lists.ubuntu.com
  
  Thank you for your time and consideration.
  Best regards,
  Jeff
  
  [1] https://docs.kernel.org/userspace-api/mseal.html
  [2] https://sourceware.org/pipermail/libc-alpha/2024-September/160291.html
  [3] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595211/4
  [4] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595853/4
  [5] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5742931
  [6] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5802772

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2089711

Title:
  Request to backport mseal syscall to LTS 24.04 LTS GA kernel

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Triaged

Bug description:
  Hello,

  My name is Jeff Xu, I work with Stephen Röttger on hardening the
  chrome browser.  I'm reaching out to explore the possibility of
  backporting memory sealing into the 24.04 LTS kernel.

  For context, it is worth noting that the Kernel introduces mseal
  support in version 6.10 [1].  The Chrome V8 engine will utilize the
  memory sealing function to protect its JIT compiler from memory
  corruption vulnerabilities. The change is merged in Chrome, and we
  believe that Ubuntu users would benefit from using this safer version
  of Chrome.

  In addition, glibc’s dynamic linker is adding mseal to seal RO mapping
  such as  .text, .rodata, .relco [2], the integration test is
  completed.

  The backport work includes 4 commits [3] [4] [5] [6].  ChromeOS and
  Android GKI both have the mseal backported to the 6.6 kernel.  I will
  send out patches for LTS 24.04 to kernel-t...@lists.ubuntu.com

  Thank you for your time and consideration.
  Best regards,
  Jeff

  [1] https://docs.kernel.org/userspace-api/mseal.html
  [2] https://sourceware.org/pipermail/libc-alpha/2024-September/160291.html
  [3] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595211/4
  [4] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5595853/4
  [5] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5742931
  [6] 
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5802772

To manage notifications abou

[Kernel-packages] [Bug 2095099] Re: T14s G4 AMD/T16 Gen 2 AMD not booting after update with 22.04

[Ammar Sheikh]

Hi Bin,

I can't access the tty console when it hangs at "Lenovo" post screen.
However, I have attached the logs from the previous boot. And the issue
only occurs on the touch panel system.

Thanks,

** Attachment added: "freeze.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095099/+attachment/5852452/+files/freeze.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095099

Title:
  T14s G4 AMD/T16 Gen 2 AMD  not booting after update with 22.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have tested this issue on the T14s Gen 4 AMD and T16 Gen 2 AMD SVT1
  with Kernel versions 6.8.0-49-generic and 6.8.0-51-generic. If I
  restart my system, it occasionally hangs at the Lenovo boot screen or
  just shows a black screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2095099/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04

[Davias]

OK, the new card from Aliexpress, an CMI8738 based PCIexp, has arrived. Could 
not plug it in my PCIx4 slot (a chip in the middle) so I had to use a PCI full 
slot...ok, nothing else needed inside my PC...
Ubuntu 24.04 started, recognized the card and use it as a primary: we have 
SOUND. So end of the story...for me. Still the problem with a perfectly working 
(on up to 18.04) SB on the MB remain...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound, stutters and clicks after upgrade to 24.04

Status in linux package in Ubuntu:
  Expired
Status in pipewire package in Ubuntu:
  Invalid

Bug description:
  After upgrading from Ubuntu 23.10 to 24.04, it does not work on the
  computer.

  Work with:
  1) Bluetooth
  2) Jack 3.5

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pipewire 1.0.5-1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:52:58 2024
  InstallationDate: Installed on 2024-03-25 (28 days ago)
  InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028933] Re: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

[Lars-Leon Meffjanky]

I came across a peculiar issue and wanted to share my thoughts in case
someone more knowledgeable can analyze it further.

My suspicion is that this might be related to a UEFI rootkit,
potentially injected through Unicode normalization. Specifically, I
believe the æ character is being used during the injection process. The
idea is that this character, æ, gets embedded deep within the ACPI
tables, possibly as part of malicious firmware modifications.

Here’s where it gets strange: When attempting to access these tables
from Linux, it seems the æ character is normalized to AE (Unicode
normalization), which could explain why direct access to the altered
ACPI data fails or behaves unexpectedly.

I can somewhat prove this behavior because when I use a SPI flasher to
erase the BIOS chip completely and then re-flash the UEFI BIOS from the
manufacturer’s original image, something different happens on the first
boot. Initially, I get error messages about misplaced GPT partitions
with invalid sector addresses, but the ACPI error involving AE does not
appear yet.

Then, upon the first boot, it seems like some malicious code is somehow
loaded from the storage drives (which, in my case, are all infected!).
After this happens, the system freezes completely. When I restart the
machine, the ACPI error involving AE reappears, even if I’m booting
directly from an installation media. This suggests that the malicious
code persists on the drives and re-infects the system at a very low
level.

Additionally, I can further support this suspicion because I was hacked
a little over a year ago, during which I communicated with the hackers
through a chatbox running on the UEFI level. Since then, these issues
have been happening consistently.

I’m no expert on this, but this behavior caught my attention, and I’m
wondering if there’s anyone here with expertise in firmware security,
ACPI handling, or UEFI rootkits who could take a closer look. Could this
be a vector for persisting malicious code in UEFI firmware or storage
devices?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2028933

Title:
  ACPI BIOS Error (bug): Failure creating named object
  [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)

Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed

Bug description:
  At boot up after the GRUB selection, these ACPI BIOS Error (bug)
  appear.

  These errors were taken from dmesg but they report the similar error at boot 
up
  [0.320650] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320680] fbcon: Taking over console
  [0.320694] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320700] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320705] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320712] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320717] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320720] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320727] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320731] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320734] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320741] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320745] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.320793] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)
  [0.320801] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  [0.320806] ACPI: Skipping parse of AML opcode: Method (0x0014)

  
  Then at runtime random Multiple Corrected error appear at this PCIe port
  1c.0-[01]00.0  Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 
M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]1c.0-[01]00.0  
Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]

  Not exactly connected but similar reports of ACPI error above is
  related to NVIDIA. Not sure if it helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-78-generic 5.15.0-78.85~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99
  Uname: Linux 5.15.0-78-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GN

[Kernel-packages] [Bug 2086606] Re: Add list of source files to linux-buildinfo

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-206.226 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still exists, change the tag 'verification-needed-focal-
linux' to 'verification-failed-focal-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2086606

Title:
  Add list of source files to linux-buildinfo

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Fix Committed
Status in linux source package in Plucky:
  Fix Committed

Bug description:
  [Impact]

  For CVE triaging, it's helpful to have an exact list of the source
  files used for a build. Add that information to the linux-buildinfo
  packages.

  [Test Case]

  Check content of linux-buildinfo packages of the individual kernels.

  Test packages for Noble, Jammy and Focal:
  https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages

  [Where Problems Could Occur]

  Build failures. This does not change the functionality of any of the
  kernel packages but just adds another text file to the linux-buildinfo
  packages so should not cause any user visible issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2089699] Re: kernel:nft "Could not process rule: Device or resource busy" on unreferenced chain

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-206.226 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still exists, change the tag 'verification-needed-focal-
linux' to 'verification-failed-focal-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2089699

Title:
  kernel:nft "Could not process rule: Device or resource busy" on
  unreferenced chain

Status in linux package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gke source package in Jammy:
  In Progress

Bug description:
  We see some nftables/netfilter problems after kernel upgrade from 
5.15.0-1061-gke to 5.15.0-1067-gke.
  Correct transaction with nft fails with "Error: Could not process rule: 
Device or resource busy"
  which usually means a deleted chain is referenced, but you can see it's not.
  Full nft table dump + transaction + error is in the attached file.
  This is logs from kubernetes CI, which started failing immediately after 
mentioned kernel update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089699/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2078011] Re: nouveau keeps showing `disp: ctrl 00000080` and crippling the system

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.4.0-206.226 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal-linux' to 'verification-done-focal-linux'. If
the problem still exists, change the tag 'verification-needed-focal-
linux' to 'verification-failed-focal-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2078011

Title:
  nouveau keeps showing `disp: ctrl 0080` and crippling the system

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in xserver-xorg-video-nouveau source package in Focal:
  Invalid

Bug description:
  During the kerenl SRU testing, I found that the DGX A100 station kept
  showing error messages from nouveau in dmesg as follows. These
  numerous kernel error messages crippled the system and made it
  unresponsive.

  [ 2265.721452] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721457] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721463] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721474] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721480] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721485] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721491] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721496] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721507] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721514] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721519] nouveau :07:00.0: disp: ctrl 0080
  [ 2265.721525] nouveau :07:00.0: disp: ctrl 0080

  When the system reaches the idle delay, I guess the system will try to turn 
off the monitor then something went wrong.
  I can quickly reproduce this by setting idle-delay to 1 sec after the system 
boot into desktop.
  `gsettings set org.gnome.desktop.session idle-delay 0`

  The impacted system is https://ubuntu.com/certified/201711-25989

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.4.0-193.213-generic 5.4.278
  Uname: Linux 5.4.0-193-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Aug 27 20:31:20 2024
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  InstallationDate: Installed on 2020-08-03 (1485 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-193-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078011/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095145] Re: Focal update: v5.4.287 upstream stable release

[TSOHost]

The latest Focal update, v5.4.287, is the upstream stable release,
providing crucial improvements and bug fixes. This update enhances the
system's overall performance and stability, ensuring smoother operation
for users. For those looking to host their tech-related websites,
https://tsohost.net/ offers excellent hosting options with reliability
and speed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095145

Title:
  Focal update: v5.4.287 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.4.287 upstream stable release
 from git://git.kernel.org/

  netlink: terminate outstanding dump on socket close
  net/mlx5: fs, lock FTE when checking if active
  net/mlx5e: kTLS, Fix incorrect page refcounting
  ocfs2: uncache inode which has failed entering the group
  KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN
  nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint
  ocfs2: fix UBSAN warning in ocfs2_verify_volume()
  nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint
  Revert "mmc: dw_mmc: Fix IDMAC operation with pages bigger than 4K"
  media: dvbdev: fix the logic when DVB_DYNAMIC_MINORS is not set
  kbuild: Use uname for LINUX_COMPILE_HOST detection
  mm: revert "mm: shmem: fix data-race in shmem_getattr()"
  ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet
  mac80211: fix user-power when emulating chanctx
  selftests/watchdog-test: Fix system accidentally reset after watchdog-test
  ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13
  x86/amd_nb: Fix compile-testing without CONFIG_AMD_NB
  net: usb: qmi_wwan: add Quectel RG650V
  soc: qcom: Add check devm_kasprintf() returned value
  regulator: rk808: Add apply_bit for BUCK3 on RK809
  ASoC: stm: Prevent potential division by zero in stm32_sai_mclk_round_rate()
  ASoC: stm: Prevent potential division by zero in stm32_sai_get_clk_div()
  proc/softirqs: replace seq_printf with seq_put_decimal_ull_width
  ipmr: Fix access to mfc_cache_list without lock held
  cifs: Fix buffer overflow when parsing NFS reparse points
  NFSD: Force all NFSv4.2 COPY requests to be synchronous
  nvme: fix metadata handling in nvme-passthrough
  mips: asm: fix warning when disabling MIPS_FP_SUPPORT
  initramfs: avoid filename buffer overrun
  nvme-pci: fix freeing of the HMB descriptor table
  m68k: mvme147: Fix SCSI controller IRQ numbers
  m68k: mvme16x: Add and use "mvme16x.h"
  m68k: mvme147: Reinstate early console
  acpi/arm64: Adjust error handling procedure in gtdt_parse_timer_block()
  s390/syscalls: Avoid creation of arch/arch/ directory
  hfsplus: don't query the device logical block size multiple times
  firmware: google: Unregister driver_info on failure and exit in gsmi
  firmware: google: Unregister driver_info on failure
  EDAC/bluefield: Fix potential integer overflow
  EDAC/fsl_ddr: Fix bad bit shift operations
  crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return 
-EBUSY
  crypto: cavium - Fix the if condition to exit loop after timeout
  crypto: bcm - add error check in the ahash_hmac_init function
  crypto: cavium - Fix an error handling path in cpt_ucode_load_fw()
  time: Fix references to _msecs_to_jiffies() handling of values
  soc: ti: smartreflex: Use IRQF_NO_AUTOEN flag in request_irq()
  soc: qcom: geni-se: fix array underflow in geni_se_clk_tbl_get()
  mmc: mmc_spi: drop buggy snprintf()
  efi/tpm: Pass correct address to memblock_reserve
  tpm: fix signed/unsigned bug when checking event logs
  ARM: dts: cubieboard4: Fix DCDC5 regulator constraints
  regmap: irq: Set lockdep class for hierarchical IRQ domains
  firmware: arm_scpi: Check the DVFS OPP count returned by the firmware
  drm/mm: Mark drm_mm_interval_tree*() functions with __maybe_unused
  wifi: ath9k: add range check for conn_rsp_epid in htc_connect_service()
  drm/omap: Fix locking in omap_gem_new_dmabuf()
  wifi: p54: Use IRQF_NO_AUTOEN flag in request_irq()
  wifi: mwifiex: Use IRQF_NO_AUTOEN flag in request_irq()
  drm/imx/ipuv3: Use IRQF_NO_AUTOEN flag in request_irq()
  dt-bindings: vendor-prefixes: Add NeoFidelity, Inc
  ASoC: fsl_micfil: Drop unnecessary register read
  ASoC: fsl_micfil: do not define SHIFT/MASK for single bits
  ASoC: fsl_micfil: use GENMASK to define register bit fields
  ASoC: fsl_

[Kernel-packages] [Bug 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

[Koichiro Den]

** Changed in: linux (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Noble)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2070339

Title:
  [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed
  with error -95"

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Noble:
  Fix Committed

Bug description:
  Fresh install Ubuntu 24.04 on Lenovo systems with Birch Stream SFR and
  check kernel boot log "dmesg", there is an error of spi-nor show up as
  follows:

  spi-nor: probe of spi0.0 failed with error -95

  while open kernel dynamic debugging of spi-nor, kernel log show as:

  [7.143574] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 1714
  [7.145046] calling  iaa_crypto_init_module+0x0/0xff0 [iaa_crypto] @ 1611
  [7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [7.146135] spi-nor: probe of spi0.0 failed with error -95

  Since upstream 6.7.0 has more details info output, I applied it and it
  was:

  [   15.425497] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 2944
  [   15.426707] spi-nor spi0.0: w25q512nwq (65536 Kbytes)
  [   15.426714] [2944] spi-nor spi0.0: mtd .name = :00:1f.5, .size = 
0x400 (64MiB), .erasesize = 0x1000 (4KiB) .numeraseregions = 0
  [   15.426735] [2944] spi-nor spi0.0: error -524 reading CR
  [   15.426738] spi-nor: probe of spi0.0 failed with error -524
  [   15.426780] probe of spi0.0 returned 524 after 1247 usecs
  [   15.426797] initcall spi_nor_module_init+0x0/0xff0 [spi_nor] returned 0 
after 1282 usecs

  
  SRU Justification:
  ==
  [Impact]
  During bootup, the error is shown in dmesg:
  [ 7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [ 7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [ 7.146135] spi-nor: probe of spi0.0 failed with error -95

  [Fix]
  Handle the failed case of -EOPNOTSUPP,
  and correct the condition of error report.
  upstream commit in 6.10:
  fe0b8213c0129 mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported
  5043e55536015 mtd: core: Align comment with an action in mtd_otp_nvmem_add()

  [Test]
  Vendor tested on hardware, there is no error on the testing built
  kernel.

  [Where problems could occur]
  It may break spi-nor flash support.

  Both 2 commits are in 6.10 kernel, so SRU for noble-6.8 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070339/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095153] [NEW] Broken since the upgrade to Ubuntu 24.10

[Linux Admin]

Public bug reported:

Example that worked with 24.04 and broke after the upgrade:

> curlftpfs ftp://ftp.gnu.org/ /mnt/test
Error setting curl:

** Affects: curlftpfs (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: linux (Ubuntu) => curlftpfs (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095153

Title:
  Broken since the upgrade to Ubuntu 24.10

Status in curlftpfs package in Ubuntu:
  New

Bug description:
  Example that worked with 24.04 and broke after the upgrade:

  > curlftpfs ftp://ftp.gnu.org/ /mnt/test
  Error setting curl:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curlftpfs/+bug/2095153/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2093146] Re: KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-Exit

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2093146

Title:
  KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter
  and VM-Exit

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/2093146

  [Impact]

  The CPUID instruction is particularly slow on newer generation processors,
  with Intel's Emerald Rapids processor taking significantly longer to execute
  CPUID than Skylake or Icelake.

  This introduces significant latency into the KVM subsystem, as it frequently
  calls CPUID when recomputing XSTATE offsets, and especially XSAVE values, as
  they need to call CPUID twice for each XSAVE call.

  CPUID.0xD.[1..n] are constant and do not change during runtime, as they don't
  depend on XCR0 or XSS values, and can be saved and cached for future usage.

  By caching CPUID.0xD.[1..n] at kvm.ko module load, latency decreases by up to
  400%.

  For a round trip transition between VM-Enter and VM-Exit figures from the
  commit log are:

  Skylake 11650
  Icelake 22350
  Emerald 28850

  When you add the caching in:

  Skylake 6850
  Icelake 9000
  Emerald 7900

  That's a saving of 170% for Skylake, 248% for Icelake and 365% for
  Emerald Rapids.

  [Fix]

  The fix is part of a 5 patch series. We will only SRU patch 1 for the moment, 
as
  it is the only one in mainline, and provides a 400% latency improvement, doing
  the brunt of the work. Patches 2-5 are refactors and smaller performance
  improvements, not yet mainlined due to needing rework, and only account for
  about 2.5% latency improvement, quite small, compared to what patch 1 does.

  The fix is:

  commit 1201f226c863b7da739f7420ddba818cedf372fc
  Author: Sean Christopherson 
  Date:   Tue Dec 10 17:32:58 2024 -0800
  Subject: KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1201f226c863b7da739f7420ddba818cedf372fc

  This landed in 6.13-rc3, and is currently queued up for upstream -stable 6.12,
  6.6 and 6.1.

  This applies cleanly to noble, oracular. For jammy, it requires the below
  dependency, and a small backport to fix some minor context mismatches.

  commit cc04b6a21d431359eceeec0d812b492088b04af5
  Author: Jing Liu 
  Date:   Wed Jan 5 04:35:14 2022 -0800
  Subject: kvm: x86: Fix xstate_required_size() to follow XSTATE alignment rule
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc04b6a21d431359eceeec0d812b492088b04af5

  1) Install KVM Stack on Baremetal host
  $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients 
bridge-utils
  2) Enable nested virt
  $ vim /etc/modprobe.d/kvm.conf
  options kvm-intel nested=1
  $ sudo reboot
  3) Start a VM.
  4) In guest, run:
  $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients 
bridge-utils
  5) In host and the guest, run:
  $ sudo apt install build-essential
  6) Install kvm-unit-tests and run x86/vmexit/cpuid testcase.
  https://gitlab.com/kvm-unit-tests/kvm-unit-tests
  $ git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git
  $ ./configure
  $ make standalone
  $ cd tests
  $ sudo -s
  # ACCEL=kvm ./vmexit_cpuid
  BUILD_HEAD=0ed2cdf3
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot 
-nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 
-vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel 
/tmp/tmp.GMVjItBglu -smp 1 -append cpuid # -initrd /tmp/tmp.uaD4VVyIqc
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  smp: waiting for 0 APs
  paging enabled
  cr0 = 80010011
  cr3 = 1007000
  cr4 = 20
  pci-testdev at 0x10 membar febff000 iobar c000
  cpuid 66485
  PASS vmexit_cpuid 

  The numbers next to cpuid, is the (t2 = rdtsc) - (t1 = rdtsc) count. Smaller 
is
  better.

  A test kernel is available in the follo

[Kernel-packages] [Bug 2089699] Re: kernel:nft "Could not process rule: Device or resource busy" on unreferenced chain

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2089699

Title:
  kernel:nft "Could not process rule: Device or resource busy" on
  unreferenced chain

Status in linux package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gke source package in Jammy:
  In Progress

Bug description:
  We see some nftables/netfilter problems after kernel upgrade from 
5.15.0-1061-gke to 5.15.0-1067-gke.
  Correct transaction with nft fails with "Error: Could not process rule: 
Device or resource busy"
  which usually means a deleted chain is referenced, but you can see it's not.
  Full nft table dump + transaction + error is in the attached file.
  This is logs from kubernetes CI, which started failing immediately after 
mentioned kernel update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089699/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2089373] Re: WARN in trc_wait_for_one_reader about failed IPIs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2089373

Title:
  WARN in trc_wait_for_one_reader about failed IPIs

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  When ending bpf tracing, 5.15 kernels now report a warning in
  trc_wait_for_one_reader() on platforms that support hot-plugging CPUs,
  but that do not have all of their hotplug slots populated.  In this
  submitter's environment, it reproduces on Xen EC2 instances, but not
  Nitro ones.

  The warning looks like this:

  kernel: [ 6416.920266] [ cut here ]
  kernel: [ 6416.920272] trc_wait_for_one_reader(): smp_call_function_single() 
failed for CPU: 64
  kernel: [ 6416.920289] WARNING: CPU: 0 PID: 13 at kernel/rcu/tasks.h:1044 
trc_wait_for_one_reader+0x2b8/0x300
  kernel: [ 6416.920299] Modules linked in: xt_state xt_connmark 
nf_conntrack_netlink nfnetlink xt_addrtype xt_statistic xt_nat xt_tcpudp 
ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nvidia_uvm(POE) nvidia_drm(POE) 
drm_kms_helper cec rc_core fb_sys_fops syscopyarea sysfillrect sysimgblt 
nvidia_modeset(POE) nvidia(POE) iptable_mangle ip6table_mangle ip6table_filter 
ip6table_nat ip6_tables xt_MASQUERADE xt_conntrack xt_comment iptable_filter 
xt_mark iptable_nat nf_nat bpfilter aufs overlay udp_diag tcp_diag inet_diag 
binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel sha256_ssse3 sha1_ssse3 
aesni_intel input_leds psmouse crypto_simd cryptd serio_raw floppy sch_fq_codel 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ena drm efi_pstore 
ip_tables x_tables autofs4
  kernel: [ 6416.920368] CPU: 0 PID: 13 Comm: rcu_tasks_trace Tainted: P OE 
5.15.0-1071-aws #77~20.04.1-Ubuntu
  kernel: [ 6416.920372] Hardware name: Xen HVM domU, BIOS 4.11.amazon 
08/24/2006
  kernel: [ 6416.920374] RIP: 0010:trc_wait_for_one_reader+0x2b8/0x300
  kernel: [ 6416.920376] Code: 00 00 00 4c 89 ef e8 37 ac 4e 00 eb 9f 44 89 fa 
48 c7 c6 00 63 e2 b8 48 c7 c7 a0 9a 1e b9 c6 05 2f 2e 09 02 01 e8 15 2e b9 00 
<0f> 0b e9 31 ff ff ff 4c 89 ee 48 c7 c7 20 df b7 b9 e8 a2 99 52 00
  kernel: [ 6416.920380] RSP: 0018:9e048c4efe00 EFLAGS: 00010286
  kernel: [ 6416.920382] RAX:  RBX:  RCX: 
0027
  kernel: [ 6416.920384] RDX: 0027 RSI: 0003 RDI: 
93074ae20588
  kernel: [ 6416.920385] RBP: 9e048c4efe28 R08: 93074ae20580 R09: 
0001
  kernel: [ 6416.920387] R10: 000a R11: 93463feb2c7f R12: 
92cbc6a1e600
  kernel: [ 6416.920389] R13: 0040 R14: 000205a4 R15: 
0040
  kernel: [ 6416.920390] FS: () GS:93074ae0() 
knlGS:
  kernel: [ 6416.920393] CS: 0010 DS:  ES:  CR0: 80050033
  kernel: [ 6416.920394] CR2: 7f4a72b04098 CR3: 0046c8964001 CR4: 
001706f0
  kernel: [ 6416.920399] Call Trace:
  kernel: [ 6416.920401] 
  kernel: [ 6416.920404] ? show_regs.cold+0x1a/0x1f
  kernel: [ 6416.920410] ? trc_wait_for_one_reader+0x2b8/0x300
  kernel: [ 6416.920412] ? __warn+0x8b/0xe0
  kernel: [ 6416.920418] ? trc_wait_for_one_reader+0x2b8/0x300
  kernel: [ 6416.920421] ? report_bug+0xd5/0x110
  kernel: [ 6416.920427] ? handle_bug+0x39/0x90
  kernel: [ 6416.920431] ? exc_invalid_op+0x19/0x70
  kernel: [ 6416.920434] ? asm_exc_invalid_op+0x1b/0x20
  kernel: [ 6416.920442] ? trc_wait_for_one_reader+0x2b8/0x300
  kernel: [ 6416.920446] rcu_tasks_trace_postscan+0x47/0x80
  kernel: [ 6416.920449] rcu_tasks_wait_gp+0x108/0x210
  kernel: [ 6416.920453] rcu_tasks_kthread+0x10f/0x1c0
  kernel: [ 6416.920456] ? wait_woken+0x60/0x60
  kernel: [ 6416.920462] ? show_rcu_tasks_trace_gp_kthread+0x80/0x80
  kernel: [ 6416.920464] kthread+0x12a/0x150
  kernel: [ 6416.920471] ? set_kthread_struct+0x50/0x50
  kernel: [ 6416.920476] ret_from_fork+0x22/0x30
  kernel: [ 6416.920485] 
  kernel: [ 6416.920486] ---[ end trace 0500611ddaff33a7 ]---

  The problem appears when:

  - The system is performing a rcu_tasks_trace grace period wait
  - T

[Kernel-packages] [Bug 2087853] Re: UFS: uspi->s_3apb UBSAN: shift-out-of-bounds

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2087853

Title:
  UFS: uspi->s_3apb UBSAN: shift-out-of-bounds

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Fix Committed

Bug description:
  [ Impact ]

  UBSAN shift-out-of-bounds warning appears on system when some UFS
  filesystems are mounted.

  [ Test Plan ]

  Mount the UFS partition with the proposed kernel and verify that the warning
  is gone.

  [ Where problems could occur ]

  Should have zero impact, removes dead code.

  [ Original Bug Report ]

  Hello!

  I have mounted UFS partition (ufstype=ufs2).
  Ubuntu allows only read only mounts for UFS by default, so it is mounted with 
ro option.

  I see those messages in the log:

  kernel: [ cut here ]
  kernel: UBSAN: shift-out-of-bounds in 
/build/linux-21sZ5Q/linux-6.8.0/fs/ufs/super.c:1247:19
  kernel: shift exponent 36 is too large for 32-bit type 'int'
  kernel: CPU: 3 PID: 2212 Comm: mount Not tainted 6.8.0-48-generic #48-Ubuntu
  kernel: Hardware name: SOYO SY-YL B550M/SY-YL B550M, BIOS 5.17 05/19/2023
  kernel: Call Trace:
  kernel:  
  kernel:  dump_stack_lvl+0x76/0xa0
  kernel:  dump_stack+0x10/0x20
  kernel:  __ubsan_handle_shift_out_of_bounds+0x199/0x370
  kernel:  ufs_fill_super.cold+0x16/0x1b7 [ufs]
  kernel:  ? sb_set_blocksize+0x1d/0x70
  kernel:  ? __pfx_ufs_fill_super+0x10/0x10 [ufs]
  kernel:  mount_bdev+0xf6/0x140
  kernel:  ufs_mount+0x15/0x30 [ufs]
  kernel:  legacy_get_tree+0x2b/0x60
  kernel:  vfs_get_tree+0x2a/0x100
  kernel:  do_new_mount+0x1a0/0x340
  kernel:  path_mount+0x1e0/0x830
  kernel:  ? putname+0x5b/0x80
  kernel:  __x64_sys_mount+0x127/0x160
  kernel:  x64_sys_call+0x1df5/0x25c0
  kernel:  do_syscall_64+0x7f/0x180
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? mntput+0x24/0x50
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? path_put+0x1e/0x30
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? do_faccessat+0x1c2/0x2f0
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? syscall_exit_to_user_mode+0x86/0x260
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? do_syscall_64+0x8c/0x180
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? syscall_exit_to_user_mode+0x86/0x260
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? do_syscall_64+0x8c/0x180
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? __do_sys_newfstatat+0x53/0x90
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? syscall_exit_to_user_mode+0x86/0x260
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? do_syscall_64+0x8c/0x180
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? irqentry_exit+0x43/0x50
  kernel:  ? srso_return_thunk+0x5/0x5f
  kernel:  ? exc_page_fault+0x94/0x1b0
  kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
  kernel: RIP: 0033:0x7417b2d2af0e
  kernel: Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 
84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff 
ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
  kernel: RSP: 002b:7fff1145f4d8 EFLAGS: 0246 ORIG_RAX: 00a5
  kernel: RAX: ffda RBX: 59b6f92e7b00 RCX: 7417b2d2af0e
  kernel: RDX: 59b6f92e7f10 RSI: 59b6f92e81b0 RDI: 59b6f92e83f0
  kernel: RBP: 7fff1145f540 R08: 59b6f92e8150 R09: 7fff1145f5b0
  kernel: R10: 0401 R11: 0246 R12: 59b6f92e83f0
  kernel: R13: 59b6f92e81b0 R14: 59b6f92e7f10 R15: 59b6f92e7c60
  kernel:  
  kernel: ---[ end trace ]---

  kernel: [ cut here ]
  kernel: UBSAN: shift-out-of-bounds in 
/build/linux-21sZ5Q/linux-6.8.0/fs/ufs/super.c:1247:19
  kernel: shift exponent 36 is too large for 32-bit type 'int'
  kernel: CPU: 6 PID: 2113 Comm: mount Not tainted 6.8.0-48-generic #48-Ubuntu
  kernel: Hardware name: SOYO SY-YL B550M/SY-YL B550M, BIOS 5.17 05/19/2023
  kernel: Call Trace:
  kernel:  
  kernel:  dump_stack_lvl+0x76/0xa0
  kernel:  dump_stack+0x10/0x20
  kernel:  __ubs

[Kernel-packages] [Bug 2086606] Re: Add list of source files to linux-buildinfo

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2086606

Title:
  Add list of source files to linux-buildinfo

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Fix Committed
Status in linux source package in Plucky:
  Fix Committed

Bug description:
  [Impact]

  For CVE triaging, it's helpful to have an exact list of the source
  files used for a build. Add that information to the linux-buildinfo
  packages.

  [Test Case]

  Check content of linux-buildinfo packages of the individual kernels.

  Test packages for Noble, Jammy and Focal:
  https://launchpad.net/~juergh/+archive/ubuntu/linux/+packages

  [Where Problems Could Occur]

  Build failures. This does not change the functionality of any of the
  kernel packages but just adds another text file to the linux-buildinfo
  packages so should not cause any user visible issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086606/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2095100] Re: kernel panic when setting application in fullscreen

[Pirouette Cacahuète]

Unfortunately, those wont work with SecureBoot enabled. Is there some
post 24.10 signed kernel I can test ?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2095100

Title:
  kernel panic when setting application in fullscreen

Status in linux package in Ubuntu:
  New

Bug description:
  Since 24.10, on amdgpu device (AMD Ryzen 7 PRO 5850U), anytime I set
  an application in fullscreen mode (video player, firefox, signal etc.)
  I end up with this crash.

  It seems to only reproduce when I have my two 4K screens connected to
  the USB-C ThinkPad Thunderbolt station. Laptop screen is disabled in
  that setup. I dont reproduce when only on the laptop screen.

  [92840.827857] [ cut here ]
  [92840.827861] atomic remove_fb failed with -28
  [92840.827874] WARNING: CPU: 11 PID: 1219167 at 
drivers/gpu/drm/drm_framebuffer.c:1146 drm_framebuffer_remove+0x233/0x240
  [92840.827884] Modules linked in: wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel ipmi_devintf ipmi_msghandler uas 
usb_storage nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
ccm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc overlay qrtr uhid rfcomm 
cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_acp_legacy_mach 
snd_acp_mach snd_soc_nau8821 intel_rapl_msr amd_atl intel_rapl_common 
nls_iso8859_1 snd_acp3x_rn snd_soc_dmic ee1004 snd_acp3x_pdm_dma 
snd_sof_amd_acp63 edac_mce_amd snd_sof_amd_vangogh amdgpu snd_sof_amd_rembrandt 
snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp kvm_amd 
snd_sof snd_sof_utils kvm snd_pci_ps snd_amd_sdw_ac
 pi btusb soundwire_amd btrtl uvcvideo
  [92840.828004]  soundwire_generic_allocation btintel rapl btbcm 
videobuf2_vmalloc amdxcp uvc btmtk drm_exec soundwire_bus gpu_sched 
videobuf2_memops snd_hda_codec_realtek snd_soc_core drm_buddy iwlmvm 
videobuf2_v4l2 drm_suballoc_helper snd_hda_codec_generic snd_compress 
drm_ttm_helper snd_hda_scodec_component ttm videodev snd_hda_codec_hdmi 
ac97_bus snd_usb_audio bluetooth drm_display_helper mac80211 videobuf2_common 
snd_pcm_dmaengine snd_seq_midi snd_usbmidi_lib think_lmi snd_hda_intel 
snd_seq_midi_event snd_rpl_pci_acp6x firmware_attributes_class libarc4 snd_ump 
snd_acp_pci snd_seq snd_intel_dspcfg cec snd_acp_legacy_common wmi_bmof 
snd_intel_sdw_acpi snd_pci_acp6x snd_rawmidi snd_hda_codec snd_pci_acp5x 
snd_seq_device snd_hda_core mc snd_hwdep snd_rn_pci_acp3x iwlwifi 
snd_acp_config snd_pcm snd_soc_acpi mhi_wwan_ctrl i2c_piix4 mhi_wwan_mbim 
rc_core k10temp snd_pci_acp3x i2c_smbus snd_ctl_led wwan ccp i2c_algo_bit 
snd_timer cfg80211 thinkpad_acpi nvram i2c_scmi joydev input_leds 
 mac_hid serio_raw sch_fq_codel msr
  [92840.828125]  parport_pc ppdev lp parport nvme_fabrics efi_pstore nfnetlink 
dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c hid_logitech_hidpp hid_logitech_dj dm_crypt hid_generic usbhid hid 
cdc_ether usbnet r8152 mii crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel snd nvme rtsx_pci_sdmmc sha256_ssse3 
ucsi_acpi soundcore mhi_pci_generic r8169 xhci_pci sha1_ssse3 nvme_core psmouse 
typec_ucsi video sparse_keymap mhi xhci_pci_renesas rtsx_pci realtek nvme_auth 
typec platform_profile wmi aesni_intel crypto_simd cryptd
  [92840.828214] CPU: 11 UID: 0 PID: 1219167 Comm: kworker/11:0 Tainted: G  
  W  6.11.0-13-generic #14-Ubuntu
  [92840.828219] Tainted: [W]=WARN
  [92840.828221] Hardware name: LENOVO 21A0CTO1WW/21A0CTO1WW, BIOS R1MET59W 
(1.29 ) 09/18/2024
  [92840.828224] Workqueue: events drm_mode_rmfb_work_fn
  [92840.828230] RIP: 0010:drm_framebuffer_remove+0x233/0x240
  [92840.828235] Code: ea 48 c7 c7 c1 2b c7 8c 48 89 c6 e8 37 60 45 ff 0f 0b e9 
16 fe ff ff 4c 8b 2f eb d6 89 c6 48 c7 c7 b8 47 d4 8c e8 1d 60 45 ff <0f> 0b e9 
3c fe ff ff 66 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90
  [92840.828238] RSP: 0018:a9e5103a7df0 EFLAGS: 00010246
  [92840.828242] RAX:  RBX: 915a297ec200 RCX: 

  [92840.828245] RDX:  RSI:  RDI: 

  [92840.828247] RBP: a9e5103a7e10 R08:  R09: 

  [92840.828250] R10:  R11:  R12: 
915a55d80010
  [92840.828252] R13: a9e5115dfd80 R14: a9e5115dfd60 R15: 

  [92840.828255] FS:  () GS:916011d8() 
knlGS:
  [92840.828257] CS:  0010 DS:  ES:  CR0: 80050033
  [92840.828260] CR2: 728564a66bbc CR3: 0001e0f36000 C

[Kernel-packages] [Bug 2050083] Re: generate and ship vmlinux.h to allow packages to build BPF CO-RE

[Mehmet Basaran]

** Changed in: linux (Ubuntu Noble)
 Assignee: Mehmet Basaran (mehmetbasaran) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2050083

Title:
  generate and ship vmlinux.h to allow packages to build BPF CO-RE

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Committed

Bug description:
  A vmlinux.h header generated from a kernel build with bpftool is needed to 
build and ship BPF CO-RE programs. We are looking to ship these in the next 
version of systemd.
  vmlinux.h being generated depends on the kernel version, architecture and 
kconfig. There are some vague promises of backward compatibility, but it is 
hard to gauge.

  We definitely do not want this file to be generated from the kernel
  running the build machine when building a package though, as very
  often these are very old and stable kernels building packages for the
  bleeding edge.

  In Fedora and now Debian we generate vmlinux.h at kernel package build
  time, and ship it with the other kernel headers (_not_ UAPI, the
  internal headers): https://salsa.debian.org/kernel-
  team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e

  Please consider doing the same in Ubuntu's linux-headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp