[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

[Chris Halse Rogers]

So, looking at 2.1.14 in lunar-proposed -
This is not bugfix-only (or even bugfix and hardware-enablement only - it 
includes, at least, changes to colourise the output of some commands). Also, I 
think this will introduce bug #2046082 into lunar and jammy?

I see we've accepted some ZFS micro-releases in the past. I'm not
familiar with the circumstances surrounding those, but I'm uncomfortable
with this one. It seems clear that zfs upstream do not have the same
expectations of stable releases as we do, so I'm not confident that just
taking an upstream microrelease will be acceptable.

I'm not saying a hard “no”, but what investigation was done to determine
how much effort cherry-picks to jammy/lunar would be? What are the
actual set of changes between 2.1.9 (/2.1.5 for jammy) and 2.1.14, and
are any of those changes maybe unsuitable for an SRU?

We don't appear to have any special process documented for zfs - maybe
we should? Regressions have extremely high potential impact but at the
same time we *do* need to sometimes make significant updates for
hardware enablement, and, to the best of my knowledge, unlike the hwe
kernel the zfs changes are not opt-in.

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2047909] Re: Support standalone dkms source tree embedded in kernel source

[You-Sheng Yang]

Set linux/noble to OPINION as we don't currently need this for
linux/noble. Patch still sent to linux-unstable for further discussion
of its necessity.

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

Title:
  Support standalone dkms source tree embedded in kernel source

Status in linux package in Ubuntu:
  Opinion
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Opinion
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
  2041800 and a last minute fix bug 2047899), we're to embed usbio-
  drivers into oem-6.5 and remove it when all the bits are in position
  under formal process.

  While IPU6 drivers are still under development, all the related dkms
  packages were prebuilt  as linux-modules-{ipu6,ivsc}, and we're
  expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
  build` does not support this yet, so we are separating the mechanism
  part here, and the usbio dkms source import in bug 2041800.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+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 2047909] Re: Support standalone dkms source tree embedded in kernel source

[You-Sheng Yang]

* https://kernel.ubuntu.com/gitea/kernel/noble-linux-unstable/pulls/17
(linux-unstable)

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

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

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

Title:
  Support standalone dkms source tree embedded in kernel source

Status in linux package in Ubuntu:
  Opinion
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Opinion
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
  2041800 and a last minute fix bug 2047899), we're to embed usbio-
  drivers into oem-6.5 and remove it when all the bits are in position
  under formal process.

  While IPU6 drivers are still under development, all the related dkms
  packages were prebuilt  as linux-modules-{ipu6,ivsc}, and we're
  expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
  build` does not support this yet, so we are separating the mechanism
  part here, and the usbio dkms source import in bug 2041800.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+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 2048796] Re: post-installation script subprocess returned error exit status 1

[Juerg Haefliger]

1) What was the previous kernel version that you tried to upgrade from?
2) Can you post the full output of a failed kernel package installation?
3) Do you have any DKMS modules installed? Run 'dkms status' and post the 
output.

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

-- 
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/2048796

Title:
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi, I was updating my system, running sudo apt update then sudo apt
  upgrade and there were some errors in the installation. It seems to
  stem from some post-installation script for linux-
  image-6.6.0-14-generic and/or linux-headers-6.6.0-14-generic. After
  the upgrade apt told me that "errors were encountered while
  processing:" linux-generic, linux-headers-generic, linux-
  image-6.6.0-14-generic and linux-headers-6.6.0-14-generic. Running
  dpkg -a --configure does not solve the issue, nor does apt -f install.
  I've tried reconfiguring with the methods suggested in this thread:
  https://askubuntu.com/questions/949760/dpkg-warning-files-list-file-
  for-package-missing and I can manually reconfigure and reinstall
  linux-generic, linux-headers-generic and linux-image-6.6.0-14-generic,
  and I can reconfigure linux-headers-6.6.0-14-generic but then when I
  try to reinstall that package it gives the error "installed linux-
  headers-6.6.0-14-generic package post-installation script subprocess
  returned error exit status 1."

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixgoats   2427 F wireplumber
   /dev/snd/controlC0:  fixgoats   2408 F pipewire
    fixgoats   2427 F wireplumber
   /dev/snd/seq:fixgoats   2408 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  9 18:06:52 2024
  InstallationDate: Installed on 2023-03-30 (285 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=0fc69223-fb6f-45e4-9873-b76a5b689b0c ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2023-12-30 (10 days ago)
  dmi.bios.date: 03/29/2021
  dmi.bios.release: 2.3
  dmi.bios.vendor: Razer
  dmi.bios.version: 2.03
  dmi.board.name: LY350
  dmi.board.vendor: Razer
  dmi.board.version: 4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvnRazer:bvr2.03:bd03/29/2021:br2.3:efr1.0:svnRazer:pnBladeStealth13(Late2020)-RZ09-0327:pvr5.04:rvnRazer:rnLY350:rvr4:cvnRazer:ct10:cvr:skuRZ09-03272N12:
  dmi.product.family: 1A581006 Razer Blade Stealth
  dmi.product.name: Blade Stealth 13 (Late 2020) - RZ09-0327
  dmi.product.sku: RZ09-03272N12
  dmi.product.version: 5.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048796/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off

[Juerg Haefliger]

** Tags added: kern-8884

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

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2045722] Re: Ubuntu freeze randomly

[Fikrul Arif]

fyi,

- Probably this is related to KVM, QEMU, or Android emulator, because it 
usually happens when the computer is about to suspend, lock screen, or shut 
down in a session where Android emulator had ever disconnected/closed 
unexpectedly.
- I switched to nvidia-driver-525, so far the freeze has not happened.

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

Title:
  Ubuntu freeze randomly

Status in linux-hwe-6.2 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  Sometimes happens when I leave it (probably screen lock), sometimes
  happens when I about to shutdown, sometimes happens when running. The
  log shows it is related to xorg or nvidia.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 10:53:21 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 5.15.0-89-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed
   nvidia/535.129.03, 6.2.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company CometLake-H GT2 [UHD Graphics] 
[103c:878e]
   NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TU106M [GeForce RTX 2060 Max-Q] 
[103c:878e]
  InstallationDate: Installed on 2021-06-05 (913 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP ENVY Laptop 15-ep0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2021
  dmi.bios.release: 15.7
  dmi.bios.vendor: AMI
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878E
  dmi.board.vendor: HP
  dmi.board.version: 18.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 18.33
  dmi.modalias: 
dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6:
  dmi.product.family: 103C_5335KV HP ENVY
  dmi.product.name: HP ENVY Laptop 15-ep0xxx
  dmi.product.sku: 16P91PA#AR6
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2045722/+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/6.5.0.16.18)

[Ubuntu SRU Bot]

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

diffoscope/249 (armhf)
initramfs-tools/0.142ubuntu15.1 (arm64, armhf)
zfs-linux/2.2.0-0ubuntu1~23.10 (armhf)


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/mantic/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-azure 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 2040106] Autopkgtest regression report (linux-meta/6.5.0.16.18)

[Ubuntu SRU Bot]

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

diffoscope/249 (armhf)
initramfs-tools/0.142ubuntu15.1 (arm64, armhf)
zfs-linux/2.2.0-0ubuntu1~23.10 (armhf)


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/mantic/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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2040106

Title:
  firmware broken after upgrade to Ubuntu 23.10

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * Focal preinstalled systems with OEM kernel, if force upgraded to
  interim releases, before transitional packages have been made
  available resulted in systems having been stuck on focal oem kernel
  and not getting any kernel updates.

   * Reintroduce all focal oem kernel transitionals to trigger upgrade
  to hwe kernel in all stable releases for the oem-20.04* kernels

  [ Test Plan ]

   * Starting with focal, install linux-image-oem-20.04* 
linux-headers-oem-20.04* metapackages
   * Force upgrade to mantic
   * Observe that all oem-20.04 meta packages got upgraded and rolled to 
generic hwe kernel (of appropriate version for jammy & mantic)

  [ Where problems could occur ]

   * This may trigger dkms package recompilation, and nvidia driver missmatches
   * Likely users will have to rerun `ubuntu-drivers` or use additional drivers 
GUI to reinstall nvidia drivers
   * Users may experience jump from v5.10 kernel to v6.5 kernel

  [ Other Info ]

   * Original bug report

  After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and 
bluetooth did not work anymore.
  Looking at the dmesg output I saw this:
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
  ..
  Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
  no suitable firmware found!
  minimum version required: iwlwifi-QuZ-a0-hr-b0-39
  minimum version required: iwlwifi-QuZ-a0-hr-b0-59

  These files did seem to exist in /lib/firmware.
  I did sudo apt install linux-firmware/mantic --reinstall
  Which did not fix it.

  I manually overwrote the iwlwifi... files with the corresponding files from 
linux-firmware-20230804.tar.gz and this did fix the issue.
  I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.

  So my best guess is that something is wrong in the latest firmware
  package.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 20230919.git3672ccab-0ubuntu2.1
    Candidate: 20230919.git3672ccab-0ubuntu2.1
    Version table:
   *** 20230919.git3672ccab-0ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
  ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
  Uname: Linux 5.10.0-1053-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  joep   2545 F wireplumber
   /dev/snd/controlC0:  joep   2545 F wireplumber
   /dev/snd/seq:joep   2537 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:19:18 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  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
  InstallationDate: Installed on 2021-10-16 (736 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem 
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1053-oem N/A
   linux-backports-modules-5.10.0-1053-oem  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
  dmi.bios.date: 07/13/2023
  dmi.bios.release: 

[Kernel-packages] [Bug 2048078] Re: Add support of MTL audio of Lenovo

[AaronMa]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

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

Title:
  Add support of MTL audio of Lenovo

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  On Lenovo ThinkPad MTL platform, the audio and mic are not working.
  Error Logs:
  [   22.098899] sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back 
to default HDA path
  [   22.107925] sof-audio-pci-intel-mtl :00:1f.3: no matching blob for 
sample rate: 48000 sample width: 32 channels: 2
  [   22.107931] sof-audio-pci-intel-mtl :00:1f.3: failed to prepare widget 
dai-copier.DMIC.dmic01.capture
  [   22.107933] sof-audio-pci-intel-mtl :00:1f.3: Failed to prepare 
connected widgets
  [   22.107935] sof-audio-pci-intel-mtl :00:1f.3: error: failed widget 
list set up for pcm 6 dir 1
  [   22.107937] sof-audio-pci-intel-mtl :00:1f.3: ASoC: error at 
snd_soc_pcm_component_hw_params on :00:1f.3: -22

  [Fix]
  Commit:
  "ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format"
  Add support of both 24 bit and 32 bit of DMIC hardware.

  [Test]
  Tested on hardware, sound ouput and DMIC input work fine.

  [Where problems could occur]
  It may break sound driver.

  MTL is not supported by 5.15 and 6.2 kernel, SRU for oem-6.5, 6.5 and
  6.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048078/+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 2047518] Re: Fix BCM57416 lost after resume

[AaronMa]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

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

Title:
  Fix BCM57416 lost after resume

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  BCM57416 is lost after resume.
  Error log:
  [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
  [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
  [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure 
rc: fffb
  [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

  [Fix]
  Clear the reservations in driver after reset the ethernet card.

  [Test]
  Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works 
fine.

  [Where problems could occur]
  It may break broadcom bnxt driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH

[AaronMa]

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  RTL8111EPP: Fix the network lost after resume with DASH

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  On the system installed RTL8111EPP with DASH, unable to get the network back 
upon system resume

  [Fix]
  handle DASH during system suspend and resume.

  [Test]
  Vendor tested on hardware, the ethernet is OK after resume.

  [Where problems could occur]
  It may break r8169 driver.

  No SRU for Jammy 5.15 kernel due to too many commits are needed to
  backport to support DASH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2046105] Re: Sound: Add rtl quirk of M90-Gen5

[AaronMa]

** Tags removed: verification-needed-jammy-linux 
verification-needed-lunar-linux verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux verification-done-mantic-linux 
verification-needed-done-linux

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2047389] Re: Fix AMDGPU crash on 6.5 kernel

[AaronMa]

** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux

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

Title:
  Fix AMDGPU crash on 6.5 kernel

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  AMD GPU crash with a message: " cp queue preemption timeout".

  [Fix]
  Disable MCBP(mid command buffer preemption) by default as old Mesa
  hangs with it.

  [Test]
  Tested on hardware, play web video for more than 1 hour OK.

  [Where problems could occur]
  It may break AMD GPU.

  This issue is only reproduced on v6.5+ kernel versions and fixes in
  v6.6, so SRU for oem-6.5, mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047389/+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 2047861] Re: Merge crash 8.0.4-1 into Noble

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 8.0.4-1ubuntu1

---
crash (8.0.4-1ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes: (LP: #2047861)
- d/t/live: If the "live" autopkgtest fails with a recommendation to
  try /proc/kcore instead of the default, attempt that before
  failing the test. LP 1858958.
- d/t/live: Fix logic issue in "live" autopkgtest introduced in the
  last upload.
- d/t/live: Fix test, as if will return 0 when no cases were true.
- d/t/control: Add linux-libc-dev dependency for the autopkg test.
  This package gets usually broken with kernel upgrades, so let it
  already show in the autopkg test.
- d/t/control: Run autopkg test with allow-stderr.
  * Drop changes:
- d/p/0002-Fix-compilation-error-due-to-new-strlcpy-function.patch
  [ included upstream in 8.0.4 ]
- d/p/0003-Support-module-memory-layout-change-on-Linux-6.4.patch
  [ included upstream in 8.0.4 ]

 -- Mauricio Faria de Oliveira   Tue, 02 Jan 2024
19:09:28 -0300

** Changed in: crash (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
   Merge crash 8.0.4-1 into Noble

Status in crash package in Ubuntu:
  Fix Released

Bug description:
  $ rmadison -a source crash | grep noble
   crash | 8.0.3+ds1-3ubuntu1 | noble  | source

  $ rmadison -a source -u debian -s unstable crash
  crash  | 8.0.4-1   | unstable   | source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2047861/+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 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Kai-Heng Feng]

** Tags removed: verification-needed-lunar-linux 
verification-needed-mantic-linux
** Tags added: verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2048817] Re: Cheese app always has error maybe or maybe not.

[Norvel Roosevelt Miller IV]

(cheese:1289568): Gdk-WARNING **: 20:27:15.534: Native Windows taller than 
65535 pixels are not supported
norvel@norvel4-ThinkPad-T460:~$ Gtk-Message: 20:27:50.728: Not loading module 
"atk-bridge": The functionality is provided by GTK natively. Please try to not 
load it.

(cheese:1289568): Clutter-CRITICAL **: 20:40:00.103: Unable to create
dummy onscreen: No foreign surface, and wl_shell unsupported by the
compositor

norvel@norvel4-ThinkPad-T460:~$


That is from console of bug report. Exact error is "There was an error playing 
video from the webcam". Maybe it helps. All as per one might be maybe or might 
not be maybe, maybe or maybe not, maybe.

-- 
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/2048817

Title:
  Cheese app always has error maybe or maybe not.

Status in linux package in Ubuntu:
  New

Bug description:
  Light for camera comes on but always has an error with displaying from
  camera. Something like "There was an error...". I am sorry I can't
  show exact error now, it opened in debug mode and displays no such
  thing but with no camera image. All other apps can display and record
  camera on like my machine.

  norvel@norvel4-ThinkPad-T460:~$  cat /proc/version_signature 
  Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  norvel@norvel4-ThinkPad-T460:~$ sudo lspci -vnvn
  [sudo] password for norvel: 
  Sorry, try again.
  [sudo] password for norvel: 
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers [17aa:5053]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD 
Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee02004  Data: 0023
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec+ Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped-
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 
xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:5053]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
 

[Kernel-packages] [Bug 2048817] [NEW] Cheese app always has error maybe or maybe not.

[Norvel Roosevelt Miller IV]

Public bug reported:

Light for camera comes on but always has an error with displaying from
camera. Something like "There was an error...". I am sorry I can't show
exact error now, it opened in debug mode and displays no such thing but
with no camera image. All other apps can display and record camera on
like my machine.

norvel@norvel4-ThinkPad-T460:~$  cat /proc/version_signature 
Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
norvel@norvel4-ThinkPad-T460:~$ sudo lspci -vnvn
[sudo] password for norvel: 
Sorry, try again.
[sudo] password for norvel: 
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers [17aa:5053]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD 
Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5053]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee02004  Data: 0023
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec+ Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped-
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:5053]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 8GT/s, Width x1, ASPM L1, Exit Latency 
L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (downgraded), Width x1 (ok)
TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 

[Kernel-packages] [Bug 2048815] [NEW] Pull request to address TPM SPI devices

[Brad Figg]

Public bug reported:

TPM devices may insert wait state on last clock cycle of ADDR phase.
For SPI controllers that support full-duplex transfers, this can be
detected using software by reading the MISO line. For SPI controllers
that only support half-duplex transfers, such as the Tegra QSPI, it is
not possible to detect the wait signal from software.

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

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

Title:
  Pull request to address TPM SPI devices

Status in linux-nvidia-6.5 package in Ubuntu:
  New

Bug description:
  TPM devices may insert wait state on last clock cycle of ADDR phase.
  For SPI controllers that support full-duplex transfers, this can be
  detected using software by reading the MISO line. For SPI controllers
  that only support half-duplex transfers, such as the Tegra QSPI, it is
  not possible to detect the wait signal from software.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2048815/+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/6.2.0.41.41)

[Ubuntu SRU Bot]

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

apparmor/3.0.8-1ubuntu2.1 (armhf)
dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (armhf)
dm-writeboost/2.2.16-0.1ubuntu2 (armhf)
snapd/2.59.1+23.04ubuntu1.2 (s390x)
ubuntu-drivers-common/1:0.9.7.1.2 (ppc64el)


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/lunar/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-azure 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 1786013] Autopkgtest regression report (linux-restricted-modules/6.2.0-41.42)

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-525/525.147.05-0ubuntu0.23.04.1 (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/lunar/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-azure 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 2044592] Re: installed system + new install refuse to show GUI (Lubuntu, Xubuntu & Ubuntu Desktop noble)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2044592

** Tags added: iso-testing

-- 
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/2044592

Title:
  installed system + new install refuse to show GUI (Lubuntu, Xubuntu &
  Ubuntu Desktop noble)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please read comment #3, this issue maybe switched to INCOMPLETE

  A couple of days ago I suffered a brownout, causing my noble install to 
shutdown (uncleanly) on this box
  - hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel 
graphics 630)

  On power restore, the system would not allow GUI login, I noted an
  Xorg crash in the /var/crash/ directory; but I was unable to ubuntu-
  bug file it (out of date packages; though I `apt update; apt full-
  upgrade` and nothing changed).

  I've attempted a re-install today, and after install the system boots,
  I get to see the plymouth screen (xubuntu) then blank screen and
  cursor top left.

  If I switch to text terminal; I can login and see screen for a few
  seconds; before the flashing cursor returns (ie. I'm taken away from
  ctrl+alt+f4 terminal and to lightdm trying to restart I suspect).

  This is the same behavior I had before this install; ie. I believe the
  issue is related to a recent package upgrade (this box is only
  rebooted about fornightly; so the power outage was the first reboot in
  maybe ten days).

  My original install was Lubuntu noble (actually a mantic ISO; as noble
  ISOs hadn't started then, but using an updated calamares for noble
  installed that tsimonq2 requested I test, that upgraded calamares
  caused the installed system to use noble sources & become noble not
  mantic)

  I'm convinced this is a regression due to upgrade; but it also occurs
  on recent ISOs too; I also suspect it maybe related to graphic gpus
  (intel & nvidia)

  FYI:  There is a Xorg crash file in /var/crash/ on this box too, it
  likewise won't let me `ubuntu-bug` install it, again reporting out of
  date packages (libsepol2)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guiverc1015 F wireplumber
   /dev/snd/controlC1:  guiverc1015 F wireplumber
   /dev/snd/seq:guiverc1012 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Nov 25 18:05:14 2023
  InstallationDate: Installed on 2023-11-25 (0 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231125)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
   Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=1aef793d-b806-4b39-9b05-baea27c51b5e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.2
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.release: 2.15
  dmi.bios.vendor: HP
  dmi.bios.version: P07 Ver. 02.15
  dmi.board.name: 82B4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 06.21
  dmi.chassis.asset.tag: AUD8130DCW
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 6.33
  dmi.modalias: 
dmi:bvnHP:bvrP07Ver.02.15:bd01/30/2018:br2.15:efr6.33:svnHP:pnHPProDesk600G3SFF:pvr:rvnHP:rn82B4:rvrKBCVersion06.21:cvnHP:ct3:cvr:sku1MF39PA#ABG:
  dmi.product.family: 103C_53307F HP ProDesk
  dmi.product.name: HP ProDesk 600 G3 SFF
  dmi.product.sku: 1MF39PA#ABG
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

crash 8.0.4 accepted to noble-proposed, marking as Fix Committed
https://launchpad.net/ubuntu/+source/crash/8.0.4-1ubuntu1

** Also affects: crash (Ubuntu Noble)
   Importance: Medium
 Assignee: Mauricio Faria de Oliveira (mfo)
   Status: In Progress

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

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Fix Committed
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress
Status in crash source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free 

[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [needs-packaging] usbio-drivers

Status in Ubuntu:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in The Jammy Jellyfish:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in Noble:
  Fix Committed
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice 
AIC
   This package provides kernel drivers for MIPI cameras through the Intel IPU6
   on Intel MeteoLake platform with Lattice AIC.

  Upstream URL: https://github.com/intel/usbio-drivers
  Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms 
(to request usd-import after created)
  License: GPL v2

  PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2041800/+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 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing usb serial interface for FM101R-GL.

  [Fix]

  * commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem 
FM101R-GL"): in v6.6-rc7
  * commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in 
v6.7-rc3

  [Test Case]

  1. check lsusb & dmesg output
  ```
  $ lsusb
  Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
  ...
  $ sudo dmesg
  [8.460678] usbcore: registered new interface driver usbserial_generic
  [8.460690] usbserial: USB Serial support registered for generic
  [8.549734] usbcore: registered new interface driver option
  [8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
  [8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
  [8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
  [8.556445] usbcore: registered new interface driver cdc_ncm
  [8.601187] usbcore: registered new interface driver cdc_wdm
  [9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
  [9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
  [9.060338] wwan wwan0: port wwan0mbim0 attached
  ```

  2. make sure ModemManager has probed it:
  ```
  $ mmcli -L
  /org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom 
FM101-GL Module
  ```

  [Where problems could occur]

  New hardware, still under development. Maybe we'll have to
  enable/patch for its vendor specific interface or so.

  [Other Info]

  The first patch is available for v6.6, and the second for v6.7. While
  we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
  which is currently on v6.6, and linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038259/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  "spi-nor spi0.1:Software reset failed:-524" in shutdown screen

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  There is a spi error message on the screen when shutting down the machine.
  It won't hurt anything and all device work well in the next boot up.
  Intel SPI controller doesn't support reset command, but our customer feel bad 
about this message.

  [Fix]
  Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the 
warnning when it's op not supported.
  https://lkml.org/lkml/2023/11/29/62

  [Test case]
  1. boot up the system with intel SPI controller on it
  2. power off the system and check if there are spi software reset failed 
errors on the screen.

  [Where problems could occur]
  There is a minor risk of breaking user-space applications
  that rely on specific return codes for unsupported operations. However,
  this risk is considered low, as such use-cases are unlikely to be common
  or critical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045205/+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 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  New China SRRC compliance readiness check for Realtek WLAN

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2043964

  [Impact]

  SRRC (State Radio Regulation of China)  compliance readiness check for
  Realtek WLAN.

  [Fix]

  Capability for Realtek WiFi TX power tables load and report from RFE
  (RF front end) parameters is needed. Multiple commits from vanilla
  kernel.

  [Test Case]

  ```
  $ sudo iw reg set CN
  # manually connect to 5G ap : center channel 155 bw 80 M
  $ sudo cat /sys/kernel/debug/ieee80211/phy0/rtw89/txpwr_table | grep -E 
'MCS_2TX_80M_0|Regulatory' 
  ```
  The expected output s
  ```
  Regulatory: CN
  MCS_2TX_80M_0 - NON_BF BF | 10, 9, dbm
  ```
  And verification fail output:
  ```
  Regulatory: CN
  MCS_2TX_80M_0 - NON_BF BF | 15, 10, dbm
  ```

  [Where problems could occur]

  This updates the behaviors and constraints of radio device power
  transmission for rtw89 driver, and must be done for regulatory
  compliance.

  [Other Info]

  As needed for oem-6.5/jammy, nominate only for Noble and
  oem-6.5/jammy.

  == original bug report ==

  New China SRRC compliance readiness check

  Proposed Change:
   - China SRRC updates the testing requirement for 2.4/5GHz, the major changes 
are the in-band RSE limit, and EIRP limits.

   - The SRRC updates impact both WLAN modules and platforms. The WLAN
  modules need to complete the new SRRC testing then platform can start
  to apply / renew the new SRRC cert. If platform took several WLAN
  modules but not all of the modules have completed the new SRRC testing
  updates, platform cannot renew/apply the new SRRC cert.

   - The platforms which apply/renew SRRC new standards need to ensure
  the TX power can meet the new RSE/EIRP limits.

  IHV confirmed below driver version can support these requirements.

  Realtek:
  The upstream driver can support SRRC compliance.
  
https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340
 [lore.kernel.org]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043964/+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 2046225] Re: The eDP OLED panel has no output on MTL platform

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  The eDP OLED panel has no output on MTL platform

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  We got a blank screen when boot into the system with OLED panel.

  [Fix]
  Intel provides a patch to fix this
  https://patchwork.freedesktop.org/patch/570622/?series=127194=2

  Which is in drm-intel-next currently
  3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing

  [Test case]
  1. Install Ubuntu 22.04 on the system with 6.5+ kernel
  2. Check the screen display normally

  [Where problems could occur]
  The eDP panel support v1.4 and later may fail if it require the non-standard 
DP_LINK_BW_SET.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+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 2046105] Re: Sound: Add rtl quirk of M90-Gen5

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  drm/amd: Disable PSR-SU to fix the brightness issue

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Sometimes the brightness isn't changed on gnome menu.

  [Fix]
  The TCON is random hung by PSR-SU.
  Add a workaround to disable PSR-SU until the real fix.

  [Test]
  Tested on hardware, the brightness is changed as expected.

  [Where problems could occur]
  It may break AMD display.

  Note: This commit is replaced by commit: cd2e31a9ab93d13c4
  ("drm/amd/display: Set minimum requirement for using PSR-SU on
  Phoenix") in v6.5, but new commit failed to fix the original issue,
  disable PSR-SU again by this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046131/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  oem-6.5: disable psr2 for some panels according to edid

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-oem-6.5 source package in Noble:
  Invalid

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

  [Impact]
  On serveral Dell laptops, the screen often displays garbage or the screen is 
flicking

  This PR is just a workaround, the upstream bug is here:
  https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863

  After the upstream fix this bug with a real fix, I will revert the
  workaround and backport the real fix to Noble and Jammy oem-kernel.

  [Fix]
  There is no real fix so far, ODM recommends to use a workaround to disable 
PSR2, this is a temp solution, after we get the real fix, we could revert the 
temp workaround.

  [Test case]

  booting with the patched kernel, If the pannel's edid is in the qurik
  list, the PSR2 will be disabled (checking
  /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is
  not in the quirk list, the graphic driver will work as before.

  [Where problems could occur]
  It is possible that the temp solution couldn't work, then the screen will 
still show garbage and the screen is flicking, another possible regression is 
the screen has no problem before, but after running patched kernel, the PSR2 is 
disabled and the system cost more power, but this possibility is very low, I 
tested the patched on some dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  jammy-oem-6.5: one more panel needs to disable psr2

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Triaged
Status in linux-oem-6.5 source package in Noble:
  Invalid

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

  [Impact]
  The customer Dell provide the edid for one more panel, this panel also needs 
to disable the psr2, otherwise the display will not work correctly

  This PR is just a workaround, the upstream bug is here:
  https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863

  After the upstream fix this bug with a real fix, I will revert the
  workaround and backport the real fix to Noble and Jammy oem-kernel.

  [Fix]
  There is no real fix so far, ODM recommends to use a workaround to disable 
PSR2, this is a temp solution, after we get the real fix, we could revert the 
temp workaround.

  [Test case]

  booting with the patched kernel, If the pannel's edid is in the qurik
  list, the PSR2 will be disabled (checking
  /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is
  not in the quirk list, the graphic driver will work as before.

  [Where problems could occur]
  It is possible that the temp solution couldn't work, then the screen will 
still show garbage and the screen is flicking, another possible regression is 
the screen has no problem before, but after running patched kernel, the PSR2 is 
disabled and the system cost more power, but this possibility is very low, I 
tested the patched on some dell machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2047909] Re: Support standalone dkms source tree embedded in kernel source

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
- SAUCE: usbio-drivers: import intel-usbio-dkms source
- debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
- [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
- SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen   Wed, 03 Jan 2024
21:03:45 +0200

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Support standalone dkms source tree embedded in kernel source

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
  2041800 and a last minute fix bug 2047899), we're to embed usbio-
  drivers into oem-6.5 and remove it when all the bits are in position
  under formal process.

  While IPU6 drivers are still under development, all the related dkms
  packages were prebuilt  as linux-modules-{ipu6,ivsc}, and we're
  expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
  build` does not support this yet, so we are separating the mechanism
  part here, and the usbio dkms source import in bug 2041800.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+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 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1028.28

---
linux-oem-6.1 (6.1.0-1028.28) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1028.28 -proposed tracker (LP: #2046239)

  * drm/amd: Disable PSR-SU to fix the brightness issue (LP: #2046131)
- drm/amd: Disable PSR-SU on Parade 0803 TCON

  * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105)
- ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5

  * Avoid using damage rectangle under hardware rotation mode when PSR is
enabled (LP: #2045958)
- SAUCE: drm/amd/display: fix hw rotated modes when PSR-SU is enabled

  * CVE-2023-6111
- netfilter: nf_tables: remove catchall element in GC sync path

 -- Timo Aaltonen   Wed, 13 Dec 2023
14:41:09 +0200

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6111

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

Title:
  drm/amd: Disable PSR-SU to fix the brightness issue

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Sometimes the brightness isn't changed on gnome menu.

  [Fix]
  The TCON is random hung by PSR-SU.
  Add a workaround to disable PSR-SU until the real fix.

  [Test]
  Tested on hardware, the brightness is changed as expected.

  [Where problems could occur]
  It may break AMD display.

  Note: This commit is replaced by commit: cd2e31a9ab93d13c4
  ("drm/amd/display: Set minimum requirement for using PSR-SU on
  Phoenix") in v6.5, but new commit failed to fix the original issue,
  disable PSR-SU again by this commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046131/+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 2046105] Re: Sound: Add rtl quirk of M90-Gen5

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1028.28

---
linux-oem-6.1 (6.1.0-1028.28) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1028.28 -proposed tracker (LP: #2046239)

  * drm/amd: Disable PSR-SU to fix the brightness issue (LP: #2046131)
- drm/amd: Disable PSR-SU on Parade 0803 TCON

  * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105)
- ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5

  * Avoid using damage rectangle under hardware rotation mode when PSR is
enabled (LP: #2045958)
- SAUCE: drm/amd/display: fix hw rotated modes when PSR-SU is enabled

  * CVE-2023-6111
- netfilter: nf_tables: remove catchall element in GC sync path

 -- Timo Aaltonen   Wed, 13 Dec 2023
14:41:09 +0200

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6111

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1028.28

---
linux-oem-6.1 (6.1.0-1028.28) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1028.28 -proposed tracker (LP: #2046239)

  * drm/amd: Disable PSR-SU to fix the brightness issue (LP: #2046131)
- drm/amd: Disable PSR-SU on Parade 0803 TCON

  * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105)
- ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5

  * Avoid using damage rectangle under hardware rotation mode when PSR is
enabled (LP: #2045958)
- SAUCE: drm/amd/display: fix hw rotated modes when PSR-SU is enabled

  * CVE-2023-6111
- netfilter: nf_tables: remove catchall element in GC sync path

 -- Timo Aaltonen   Wed, 13 Dec 2023
14:41:09 +0200

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6111

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2036600] Re: Azure: Fix Azure vendor ID

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2036600

Title:
  Azure: Fix Azure vendor ID

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The linux-azure 6.2 kernel doesn't report a correct GUEST_ID

  There is a mistake in the commit
  (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
  :

  Before the commit, the good guest_id is 0x81860210.

  With the commit, the generated guest_id is incorrect:
  0x00860210, i.e. the 0x81 from bit 56~63 are dropped.

  See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
  * Bit(s)
  * 63 - Indicates if the OS is Open Source or not; 1 is Open Source

  * 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
  I'll post a patch to LKML to fix this typo.

  * 55:48 - Distro specific identification
  * 47:16 - Linux kernel version number
  * 15:0 - Distro specific identification

  See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
  windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)

  As a result, the host thinks that the VM is not an open-source OS, and
  it's not Linux. Consequently, the "VM Availability" fron Azure portal
  is 0 (unhealthy): some users rely on the info to manage their VMs,
  e.g. if the VM is erroneously reported "unhealthy", the VM may be
  killed and re-created, and the new VM is still "unhealthy", and the VM
  may be killed and re-created again...

  Please consider integrating the below fix ASAP. This affects regular
  VMs, and I think this affects CVMs as well.

  The fix should be:

  diff --git a/include/asm-generic/hyperv-tlfs.h 
b/include/asm-generic/hyperv-tlfs.h
  @@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
  *
  */

  -#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
  +#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  VMs could be misclassified.

  [Other Info]

  SF: #00368936

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2041495

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0
  kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  == original bug report ==

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2041613] Re: correct cephfs pull request for uidmap support

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2041613

Title:
  correct cephfs pull request for uidmap support

Status in linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  New

Bug description:
  [ Impact ]

   * During mantic dev cycle, we pulled all of cephfs testing patches, rather 
than uidmapshift patches alone
   * We also pulled in debug patches that generate a lot of dmesg and delays in 
the cephfs module

  [ Test Plan ]

   * run ceph fs and experience less dmesg at info level

  [ Where problems could occur ]

   * Hopefully the reverts were done correctly, and none of the messages
  reference non-existing things, in all the code paths.

  [ Other Info ]

   * Story time how we got here:

  The following pull requests

  BugLink: https://bugs.launchpad.net/bugs/2038522
  BugLink: https://bugs.launchpad.net/bugs/2032959

  generated the following commit list 1:

  eddf9ed788 UBUNTU: [Config] disable shiftfs
  72e8806959 UBUNTU: SAUCE: ceph: enable unsafe idmapped mounts by default
  80b85e5d76 UBUNTU: SAUCE: ceph: allow idmapped mounts
  9d341bb8aa UBUNTU: SAUCE: ceph/file: allow idmapped atomic_open inode op
  ddd1a8ee19 UBUNTU: SAUCE: ceph/acl: allow idmapped set_acl inode op
  1b12f12987 UBUNTU: SAUCE: ceph: allow idmapped setattr inode op
  b1f695f0d1 UBUNTU: SAUCE: ceph: pass idmap to __ceph_setattr
  8a9a3b9e88 UBUNTU: SAUCE: ceph: allow idmapped permission inode op
  e5471722b3 UBUNTU: SAUCE: ceph: allow idmapped getattr inode op
  f6b1d353fa UBUNTU: SAUCE: ceph: pass an idmapping to mknod/symlink/mkdir
  5ecfa6f659 UBUNTU: SAUCE: ceph: add enable_unsafe_idmap module parameter
  19724a984a UBUNTU: SAUCE: ceph: handle idmapped mounts in 
create_request_message()
  6ec4e53238 UBUNTU: SAUCE: ceph: stash idmapping in mdsc request
  8006617c5e UBUNTU: SAUCE: fs: export mnt_idmap_get/mnt_idmap_put
  55f4f0afc5 UBUNTU: SAUCE: ceph: make num_fwd and num_retry to __u32
  54e03068d6 UBUNTU: SAUCE: ceph: make the members in struct 
ceph_mds_request_args_ext an union
  f7ec09aaac UBUNTU: SAUCE: ceph: print the client global_id in all the debug 
logs
  b2831559c5 UBUNTU: SAUCE: ceph: add ceph_inode_to_client() helper support
  a0852434ee UBUNTU: SAUCE: ceph: move mdsmap.h to fs/ceph/
  cfda2c4b70 UBUNTU: SAUCE: ceph: rename _to_client() to _to_fs_client()
  42924fda3a UBUNTU: SAUCE: ceph: pass the mdsc to several helpers
  9f6e6f9ce9 UBUNTU: SAUCE: ceph: add the *_client debug macros support
  8f61639667 UBUNTU: SAUCE: ceph: BUG if MDS changed truncate_seq with client 
caps still outstanding
  a53dba9297 UBUNTU: SAUCE: ceph: make sure all the files successfully put 
before unmounting
  17fcf5d75d UBUNTU: SAUCE: mm: BUG if filemap_alloc_folio gives us a folio 
with a non-NULL ->private
  834ebb591f UBUNTU: SAUCE: ceph: dump info about cap flushes when we're 
waiting too long for them
  498d08b9bd UBUNTU: SAUCE: rbd: bump RBD_MAX_PARENT_CHAIN_LEN to 128
  3ae75e2438 UBUNTU: SAUCE: libceph: do not include crypto/algapi.h
  d984763988 UBUNTU: SAUCE: ceph: switch ceph_lookup/atomic_open() to use new 
fscrypt helper
  8e298c72fb UBUNTU: SAUCE: ceph: fix updating i_truncate_pagecache_size for 
fscrypt
  288f935219 UBUNTU: SAUCE: ceph: wait for OSD requests' callbacks to finish 
when unmounting
  435fc54954 UBUNTU: SAUCE: ceph: drop messages from MDS when unmounting
  862a1e3c2a UBUNTU: SAUCE: ceph: update documentation regarding snapshot 
naming limitations
  904f39f283 UBUNTU: SAUCE: ceph: prevent snapshot creation in encrypted locked 
directories
  a47bdc0f8a UBUNTU: SAUCE: ceph: add support for encrypted snapshot names
  e4202a1c3e UBUNTU: SAUCE: ceph: invalidate pages when doing direct/sync writes
  9f781cfb0d UBUNTU: SAUCE: ceph: plumb in decryption during reads
  e76383977f UBUNTU: SAUCE: ceph: add encryption support to writepage and 
writepages
  0b571b2ac0 UBUNTU: SAUCE: ceph: add read/modify/write to ceph_sync_write
  a81bd5f1c8 UBUNTU: SAUCE: ceph: align data in pages in ceph_sync_write
  edbe3d2a62 UBUNTU: SAUCE: ceph: don't use special DIO path for encrypted 
inodes
  efed7d1764 UBUNTU: SAUCE: 

[Kernel-packages] [Bug 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2042853

Title:
  [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * Today no s390x-specific vfio-pci devices (zPCI) can be passed
 from a KVM host to a KVM guest (incl. secure execution guests
 in the context of confidential computing).

   * s390x PCI passthrough needs various changes in the s390x kernel zPCI
 code (incl. the new s390x-specific Kernel config option
 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0
 and got backported to 22.04/jammy as part of LP: #1853306.

   * Lunar an newer Ubuntu releases have the code already included from
 upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the
 config option is not set, hence zPCI pass-through is still not possible.

  [Fix]

   * To be able to make use of VFIO zPCI pass-through on s390x running newer
 Ubuntu releases (especially needed in the context of secure execution)
 the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs
 to be enabled and set to 'y'.

  [Test Case]

   * Hardware used: z14 or greater LPAR, PCI-attached devices
 (RoCE VFs, ISM devices, NVMe drive)

   * Setup: Both the kernel and QEMU features are needed for the feature
 to function (an upstream QEMU can be used to verify the kernel early),
 and the facility is only available on z14 or newer.
 When any of those pieces is missing,
 the interpretation facility will not be used.
 When both the kernel and QEMU features are included in their respective
 packages, and running in an LPAR on a z14 or newer machine,
 this feature will be enabled automatically.
 Existing supported devices should behave as before with no changes
 required by an end-user (e.g. no changes to libvirt domain definitions)
 -- but will now make use of the interpretation facility.
 Additionally, ISM devices will now be eligible for vfio-pci passthrough
 (where before QEMU would exit on error if attempting to provide an ISM
 device for vfio-pci passthrough, preventing the guest from starting)

   * Testing will include the following scenarios, repeated each for RoCE,
 ISM and NVMe:

 1) Testing of basic device passthrough (create a VM with a vfio-pci
device as part of the libvirt domain definition, passing through
a RoCE VF, an ISM device, or an NVMe drive. Verify that the device
is available in the guest and functioning)
 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device,
virsh detach-device to remove the device from the running guest,
verify the device is removed from the guest, then virsh attach-device
to hotplug the device to the guest again, verify the device functions
in the guest)
 3) Host power off testing: Power off the device from the host, verify
that the device is unplugged from the guest as part of the poweroff
 4) Guest power off testing: Power off the device from within the guest,
verify that the device is unusable in the guest,
power the device back on within the guest and verify that the device
is once again usable.
 5) Guest reboot testing: (create a VM with a vfio-pci device,
verify the device is in working condition, reboot the guest,
verify that the device is still usable after reboot)

  [Regression Potential]

   * The regression potential is moderate, since the code is upstream
 for quite a while and already enabled in jammy.

   * The general way on using passthrough has not changed, with this
 change (config option) it's now just possible to passthrough
 zPCI on top.

   * CCW devices are not affected.

   * And this is s390x-specific anyway, so no other architectures are
  

[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Support speaker mute hotkey for Cirrus CS35L41 HDA codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Some systems use a special hotkey to mute speaker audio. On systems using 
CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI 
notifications to detect whether the hotkey is triggered to switch the mute 
state.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t.

  [Test Case]
  1. Power on the machine with CS35L41 HDA and the speaker mute hotkey.
  2. Verify the audio functions
  3. Verify if the speaker can be mute/unmute by the hotkey.

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey 
on keyboard. The impact is restricted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

  [Misc]
  Because the board_ahci_mobile is still not modified to board_ahci_low_power 
on Jammy,
  provide a single patch for Jammy.

  For generic J/M, passed the all arch compilations on cbd,
  Jammy,
  ~~~
  $ git push j_cbd
  Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ
  remote: * 0/1 workers busy, 0 builds queued
  remote: 2023-11-17 19:50:25  kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK
  remote: 2023-11-17 20:18:29  kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK
  remote: 2023-11-17 20:01:41  kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK
  remote: 2023-11-17 20:31:51  kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK
  remote: 2023-11-17 20:37:25  kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK
  remote: 

  To cbd.kernel:jammy.git
   * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next
  ~~~

  Lunar,
  $ git push l_cbd
  Enumerating objects: 9, done.
  Counting objects: 100% (9/9), done.
  Delta compression using up to 8 threads
  Compressing objects: 100% (5/5), done.
  Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done.
  Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-915de03d6ecf-V1nm
  remote: * 9/9 workers busy, 0 builds queued
  remote: 2023-11-20 16:00:11  kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK
  remote: 2023-11-20 15:59:57  

[Kernel-packages] [Bug 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook
  Fury 16 G9

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  
  [Impact]
  Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume 
from suspend. The audio play and capture functions are not working after resume 
from S3.

  [Fix]
  Backport the fix from Cirrus on linux-next 
https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/.

  [Test Case]
  1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA .
  2. Perform system suspend/resume at least 3 times.
  3. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Only affect specific laptops with the CS35L41 HDA. The impact is restricted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2035971

Title:
  linux tools packages for derived kernels refuse to install
  simultaneously due to libcpupower name collision

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * Multiple kernel flavours are conflicting with each on .deb / file
  level via their tools packages

   * Resolve the conflicting private libcpupower.so by statically
  linking it into the only C binary that uses said library in the linux-
  tools

  [ Test Plan ]

   * co-install tools packages from multiple kernel flavours of the same
  major version and abi, it should be successful

  [ Where problems could occur ]

   * If one tries really hard to find the private location of
  libcpupower.so and dlopen it by ever changing abi name, that will not
  be possible, until the separate bug report is fixed to introduce the
  public stable libcpupower.so.1 which so far ubuntu has never yet
  provided.

  [ Other Info ]
   
   * original bug report

  Taking linux-kvm and linux-gcp for example:

  $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103384 2023-07-25 20:00 
./usr/lib/libcpupower.so.6.2.0-1011
  $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | 
grep libcpupower
  -rw-r--r-- root/root103392 2023-08-16 15:08 
./usr/lib/libcpupower.so.6.2.0-1011

  linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
  a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
  utilities, and yet files of the same full path cannot be installed
  from two distinct debian packages, which follows we won't be able to
  install two linux-tools packages of two different derived kernels on
  the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
  Uname: Linux 6.5.0-9004-generic x86_64
  NonfreeKernelModules: zfs wl
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vicamo 6331 F wireplumber
   /dev/snd/controlC0:  vicamo 6331 F wireplumber
   /dev/snd/seq:vicamo 6315 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Sep 14 23:31:16 2023
  InstallationDate: Installed on 2022-04-10 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic 
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-generic N/A
   linux-backports-modules-6.5.0-9004-generic  N/A
   linux-firmware  20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 432.60.3.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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 removed: verification-done
** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Add SoF topology support on Intel RaptorLake DELL SKU 0C11

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in firmware-sof source package in Mantic:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  SRU Jusitification for firmware-sof

  [Impact]
  To support audio functions on RPL Dell SKU 0C11, it requires the topology 
file from sof-tplg-v2.2.7

  [Fix]
  Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from 
https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  [Test Case]
  Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the 
audio function.
  1. Install the firmware-sof on platform(RPL) Dell SKU 0C11
  2. Make sure the audio output/input devices are not dummy in audio settings.

  [Where problems could occur]
  New firmware is only for the RPL platforms which requires the specific 
topology file.

  [Misc]
  https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  

  [Impact]
  Audio play/capture are not functional on specific Dell machines of Intel RPL 
platforms

  [Fix]
  Backport the fix from Intel in https://github.com/thesofproject/linux

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy` shown on the Audio output/input option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  System hang after unplug/plug DP monitor with AMD W7500 card

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System hangs and no external output after unplug/plug DP monitor. (AMD Radeon 
Pro W7500)
  Observed a bunch of [Hardware Error] messages and finally amdgpu crashed.

  [Fix]
  AMD provides a patch to fix the issue
  https://www.spinics.net/lists/amd-gfx/msg99737.html

  which is included in v6.7-rc1
  7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code

  [Testcase]
  1. Connect the DUT to an external DP monitor via one of the ports on the AMD 
graphics card
  2. Boot into Ubuntu
  3. Unplug the DP cable from the DUT
  4. Wait for 30 seconds
  5. Replug in the DP cable
  6. Make sure the system doesn't hang and the external DP monitor works

  [Where probles could occur]
  The patch make sure MACO is supported only if BACO is supported. It creates a 
stricter rule for MACO to avoid MACO is enabled with BACO supports. It should 
be safe to apply stricter rules to enable features.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2043730] Re: Update io_uring to 6.6

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2043730

Title:
  Update io_uring to 6.6

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

Bug description:
  [Impact]
  io_uring is a fast-developed subsystem in the Linux kernel. In order to keep 
up with the latest changes such that applying further fixes are possible, it 
should be updated to a more recent version.

  [Test case]
  Given the general update, there are no specific test cases.

  [Potential regression]
  io_uring users only would be affected given most changes are restricted to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043730/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2043841

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 

[Kernel-packages] [Bug 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  RTL8111EPP: Fix the network lost after resume with DASH

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  On the system installed RTL8111EPP with DASH, unable to get the network back 
upon system resume

  [Fix]
  handle DASH during system suspend and resume.

  [Test]
  Vendor tested on hardware, the ethernet is OK after resume.

  [Where problems could occur]
  It may break r8169 driver.

  No SRU for Jammy 5.15 kernel due to too many commits are needed to
  backport to support DASH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2044512] Re: Build failure if run in a console

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2044512

Title:
  Build failure if run in a console

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [Impact]

  Build fails if run in a console:

  $ debian/rules binary
  ...
  # Compress kernel modules
  find debian/linux-unstable-tools-6.6.0-12 -name '*.ko' -print0 | xargs -0 -n1 
-P 8 zstd -19 --quiet --rm
  stdout is a console, aborting
  make: *** [debian/rules.d/2-binary-arch.mk:769: binary-perarch] Error 123

  [Test Case]

  See above.

  [Where Problems Could Occur]

  Build failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044512/+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 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  [Impact]
  Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops

  [Fix]
  Need to backport 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492
 to support dual speaker configuration on Dell Oasis series

  [Test Case]
  1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA.
  2. Verify the audio functions, including playback and capture

  [Where problems could occur]
  Add CS35L41 support on specific Dell laptops. Risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2044096/+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 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2045562

Title:
  [Debian] autoreconstruct - Do not generate chmod -x for deleted  files

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 Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Debian source format 1.0 cannot remove files, create symlinks and change
  permission in the .diff.gz tarball. Therefore any changes in these 3
  categories cannot be represented without any tricks. To solve this,
  the `reconstruct` script is used every time we build the source package.
  The script is generated by `gen-auto-reconstruct` script during `cranky
  close`. It checks if there has been any changes in the 3 categories
  mentioned above between the upstream version (i.e v6.5) and the current one.
  The problem with the script is that in case a file A was removed since the
  upstream version was released, the `reconstruct` script will contains
  these commands in this exact order:
  rm -f A
  chmod -x A
  The second command will fail because file A does not exist anymore.
  This is solved by generating the `chmod +/-x` commands before `rm`.
  Which results in:
  chmod -x A
  rm -f A
  But because the reconstruct script is used during `clean` rule which is
  triggered pretty much during every cranky step which is run in the
  source repo, the first command will always file because file A is not
  present anymore in the tree. To solved this, any `chmod` change is added
  only if the file has not been deleted. Therefore if file A has been
  deleted, the `reconstruct` script will contain only this:
  rm -f A

  [Fix]
  Generate chmod commands first.
  And when generating chmod -x command, first check if the file has been 
deleted. If yes, no need for a chmod command.

  [Test Plan]
  It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and 
it reconstruct script looked correct.

  [Other Info]
  An example of this is #lp2038611 where `script/is_rust_module.sh` was 
removed, but we keep seeing
  "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory"
  because `rm -f` and `chmod -x` command were generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2045796

Title:
  Update bnxt_en with bug fixes and support for Broadcom 5760X network
  adapters

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Confirmed

Bug description:
  [IMPACT]

  This is requested by one of our larger server hardware partners and
  Broadcom to to update the bnxt_en network driver code to add some bug
  fixes and support for the newer 5760X adapters into Mantic.  The goal
  is to have these land in 22.04.4 HWE and the installer environment via
  the HWE kernel.

  Missing these patches will mean customers running this hardware will
  not be able to use it with Ubuntu Server 22.04 LTS until the much
  later 22.04.5 point release, setting up a months-long gap in support
  for these adapters.

  [FIXES]

  These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and
  pick cleanly with the exception of the two noted at the end of this
  section.  For Mantic all are picked. For Noble, only the subset
  currently in linux-next will be picked, depending on what happens in
  our Noble tree during the cycle.

  d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc
  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new
  firmware interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion
  types for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions
  8243345bfaec bnxt_en: Refactor RSS capability fields
  d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism
  on P7 chips
  d3c16475dc06 bnxt_en: Consolidate DB offset calculation
  a432a45bdba4 bnxt_en: Define basic P7 macros
  397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15
  08b386b132c6 bnxt_en: Fix backing store V2 logic
  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2
  firmware calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always
  free bp->ctx
  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings
  required for TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field
  9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters
  5d4e1bf60664 bnxt_en: extend media types to supported and 

[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2046217] Re: Some machines can't pass the pm-graph test

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Some machines can't pass the pm-graph test

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux-hwe-6.5 source package in Jammy:
  New
Status in linux-signed-hwe-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-hwe-6.5 source package in Mantic:
  New
Status in linux-signed-hwe-6.5 source package in Mantic:
  New
Status in linux source package in Noble:
  Confirmed
Status in linux-hwe-6.5 source package in Noble:
  New
Status in linux-signed-hwe-6.5 source package in Noble:
  In Progress

Bug description:
  == SRU Justification ==
  [Impact]
  When iwlwifi firmware causes the WiFi NIC dropped off PCI bus on system
  resume, NULL pointer dereference occurs and the system stops working.

  [Fix]
  Rescan the bus in order to reprobe the device to avoid mac80211 layer
  gets messed up.

  [Test]
  With the fix in place, system keeps working after firmware issue occurs.
  Verified with thousand times of suspend.

  [Where problems could occur]
  If the firmware/hardware is really dead and beyond recoverable, the same
  process can be triggered again and again.

  == Original bug report ==
  During the jammy-hwe migration test, I found some machines failed to run the 
pm-graph. 
test(https://github.com/canonical/checkbox/blob/main/providers/base/units/stress/jobs.pxu#L604)

  One of machine when I rerun it locally, it passed, but others are
  still failed.

  Following are the machines failed to run pm-graph.
  https://certification.canonical.com/hardware/202005-27899/
  https://certification.canonical.com/hardware/201702-25401/
  https://certification.canonical.com/hardware/202002-27718/
  https://certification.canonical.com/hardware/201711-25989/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/)
  Date: Tue Dec 12 02:48:24 2023
  InstallationDate: Installed on 2023-02-22 (293 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046217/+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 2047389] Re: Fix AMDGPU crash on 6.5 kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix AMDGPU crash on 6.5 kernel

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  AMD GPU crash with a message: " cp queue preemption timeout".

  [Fix]
  Disable MCBP(mid command buffer preemption) by default as old Mesa
  hangs with it.

  [Test]
  Tested on hardware, play web video for more than 1 hour OK.

  [Where problems could occur]
  It may break AMD GPU.

  This issue is only reproduced on v6.5+ kernel versions and fixes in
  v6.6, so SRU for oem-6.5, mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047389/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2047382

Title:
  Hotplugging SCSI disk in QEMU VM fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest 
kernels >= 6.5 might be broken.
  The inconsistency suggests a potential race condition.

  [Fix]
  Reverting the two specified commits appears to restore reliability.
  ==
  cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only 
for non-root bus
  40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  Upstream has resolved the issue by reverting both commits through a commit 
placed below.
  ==
  5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  [Test Plan]
  1. Create a VM
  virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk 
path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio
  -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0
  2. Prepare two XMLs for adding two disk devices
  # cat disk_X.xml
  
    
    
    
  
  3. Hotplug disks and check for success
  virsh attach-device scsi_test disk_X.xml

  [Where problems could occur]
  The patch reverts two commits that previously addressed long-standing issues 
related to hotplugging devices with large BARs.
  While this reversion may reintroduce legacy issues, it does not introduce new 
problems.
  The associated risks are deemed low, making it worthwhile to address timing 
issues during the hotplugging of SCSI disks in QEMU VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2047398] Re: Add missing RPL P/U CPU IDs

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Add missing RPL P/U CPU IDs

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Without the correct GPU ID in the driver, the system will default to 
framebuffer mode, and some graphics functions may not work properly.

  [Fix]
  Below commit included in v6.7-rc1 adds the missing IDs
  5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U

  [Test case]
  1. check the system with GPU ID A7AC or A7AD
  2. boot the system into desktop and connecting a monior by HDMI cable with 
HDMI port or Type-C port
  3. make sure the external monitor works

  [Where problems could occur]
  Add only IDs; there is no potential for regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047398/+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 2047461] Re: drm: Update file owner during use

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-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/2047461

Title:
  drm: Update file owner during use

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Our testing tools need to check the app runs on which GPU, and now it only 
shows the processes as Xorg or XWayland

  $ cat /sys/kernel/debug/dri/0/clients
   command   pid dev master a   uid  magic
  Xorg  2344   0   yy 0  0
  Xorg  2344   0   ny 0  2
  Xorg  2344   0   ny 0  3
  Xorg  2344   0   ny 0  4

  [Fix]
  The commit from v6.7-rc1 fixes the issue

  $ cat /sys/kernel/debug/dri/0/clients
   command  tgid dev master a   uid  magic
  Xorg   830   0   yy 0  0
 xfce4-session   880   0   ny 0  1
 xfwm4   943   0   ny 0  2
 neverball  1095   0   ny 0  3

  
  [Test case]
  1. check processes by 'cat /sys/kernel/debug/dri/0/clients'
  2. runs glxgears(specify the GPU if needed)
  3. check the precesses again and there should be a 'glxgears' process 

  [Where problems could occur]
  This commit added some protections on read/write and only changes the 
process' pid, the worst case is that the process got the wrong pid as its owner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+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 2047518] Re: Fix BCM57416 lost after resume

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Fix BCM57416 lost after resume

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  BCM57416 is lost after resume.
  Error log:
  [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
  [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
  [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure 
rc: fffb
  [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

  [Fix]
  Clear the reservations in driver after reset the ethernet card.

  [Test]
  Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works 
fine.

  [Where problems could occur]
  It may break broadcom bnxt driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2048078] Re: Add support of MTL audio of Lenovo

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exists, change the tag 'verification-needed-mantic-
linux' to 'verification-failed-mantic-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-mantic-linux-v2 verification-needed-mantic-linux

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

Title:
  Add support of MTL audio of Lenovo

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  On Lenovo ThinkPad MTL platform, the audio and mic are not working.
  Error Logs:
  [   22.098899] sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back 
to default HDA path
  [   22.107925] sof-audio-pci-intel-mtl :00:1f.3: no matching blob for 
sample rate: 48000 sample width: 32 channels: 2
  [   22.107931] sof-audio-pci-intel-mtl :00:1f.3: failed to prepare widget 
dai-copier.DMIC.dmic01.capture
  [   22.107933] sof-audio-pci-intel-mtl :00:1f.3: Failed to prepare 
connected widgets
  [   22.107935] sof-audio-pci-intel-mtl :00:1f.3: error: failed widget 
list set up for pcm 6 dir 1
  [   22.107937] sof-audio-pci-intel-mtl :00:1f.3: ASoC: error at 
snd_soc_pcm_component_hw_params on :00:1f.3: -22

  [Fix]
  Commit:
  "ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format"
  Add support of both 24 bit and 32 bit of DMIC hardware.

  [Test]
  Tested on hardware, sound ouput and DMIC input work fine.

  [Where problems could occur]
  It may break sound driver.

  MTL is not supported by 5.15 and 6.2 kernel, SRU for oem-6.5, 6.5 and
  6.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048078/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Marc Dietrich]

seems to be fixed in linux-image-6.5.0-16-generic (frpm kernel ppa).

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Dan Clash]

The pre-patch discussion thread has a test program that I used to reproduce the 
issue.
The test program never completes if the bug is present.

I have not been through this process yet.  Is it appropriate for me to
do the testing?  If yes then is there a document or steps that describes
the appropriate way to test?

https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

The following is a copy of the test program:

Test program usage:

./io_uring_open_close_audit_hang --directory /tmp/deleteme --count 1

Test program source:

// Note: The test program is C++ but could be converted to C.
#include 
#include 
#include 
#include 
#include 
#include 

// open and close a file.  the file is created if it does not exist.

void
openClose(struct io_uring& ring, std::string fileName)
{
int ret;
struct io_uring_cqe* cqe {};
struct io_uring_sqe* sqe {};
int fd {};
int flags {O_RDWR | O_CREAT};
mode_t mode {0666};

// openat2

sqe = io_uring_get_sqe();
assert(sqe != nullptr);

io_uring_prep_openat(sqe, AT_FDCWD, fileName.data(), flags, mode);
io_uring_sqe_set_flags(sqe, IOSQE_ASYNC);

ret = io_uring_submit();
assert(ret == 1);

ret = io_uring_wait_cqe(, );
assert(ret == 0);

fd = cqe->res;
assert(fd > 0);

io_uring_cqe_seen(, cqe);

// close

sqe = io_uring_get_sqe();
assert(sqe != nullptr);

io_uring_prep_close(sqe, fd);
io_uring_sqe_set_flags(sqe, IOSQE_ASYNC);

ret = io_uring_submit();
assert(ret == 1);

// wait for the close to complete.
ret = io_uring_wait_cqe(, );
assert(ret == 0);

// verify that close succeeded.
assert(cqe->res == 0);

io_uring_cqe_seen(, cqe);
}

// create 100 files and then open each file twice.

void
openCloseHang(std::string filePath)
{
int ret;
struct io_uring ring;

ret = io_uring_queue_init(8, , 0);
assert(0 == ret);

int repeat {3};
int numFiles {100};

std::filesystem::create_directory(filePath);

// files of length 0 are created in the j==0 iteration below.
// those files are opened and closed during the j>0 iteraions.
// a repeat of 3 results in a fairly reliable reproduction.

for (int j = 0; j < repeat; j += 1) {
for (int i = 0; i < numFiles; i += 1) {
std::string fileName(filePath + "/file" + std::to_string(i));
openClose(ring, fileName);
}
}

std::filesystem::remove_all(filePath);

io_uring_queue_exit();
}

int
main(int argc, char** argv)
{
std::string filePath {};
int iterations {};

struct option options[]
{
{"help", no_argument, 0, 'h'}, {"directory", required_argument, 0, 'd'},
{"count", required_argument, 0, 'c'},
{
0, 0, 0, 0
}
};
bool printUsage {false};
int val {};

while ((val = getopt_long_only(argc, argv, "", options, nullptr)) != -1) {
if (val == 'h') {
printUsage = true;
} else if (val == 'd') {
filePath = optarg;
if (std::filesystem::exists(filePath)) {
printUsage = true;
std::cerr << "directory must not exist" << std::endl;
}
} else if (val == 'c') {
iterations = atoi(optarg);
if (0 == iterations) {
printUsage = true;
}
} else {
printUsage = true;
}
}

if ((0 == iterations) || (filePath.empty())) {
printUsage = true;
}

if (printUsage || (optind < argc)) {
std::cerr << "io_uring_open_close_audit_hang.cc --directory DIR --count 
COUNT" << std::endl;
exit(1);
}

for (int i = 0; i < iterations; i += 1) {
if (0 == (i % 100)) {
std::cout << "i=" << std::to_string(i) << std::endl;
}
openCloseHang(filePath);
}
return 0;
}

-- 
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/2043841

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  

[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  Fix ADL: System enabled AHCI can't get into s0ix when attached ODD

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  System can't enter suspend on AHCI mode,
  the CPU FAN and System FAN is running, PSU LED is on.
  When fail to enter suspend, remove ODD, the system can successfully enter 
suspend again.

  [Fix]
  Enable LPM on Alder Lake-P AHCI.

  [Test Cases]
  1. enabled AHCI on target machine.
  2. boot with kernel applied fix.
  3. suspend then check slp_s0_residency_usec_cstate_show
  ~~~
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  4951200
  Package C2 : 63571033
  Package C3 : 6212
  Package C6 : 5633477
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 5255561
  u@ubuntu:~$ sudo rtcwake -m mem -s 10
  rtcwake: assuming RTC uses UTC ...
  rtcwake: wakeup from "mem" using /dev/rtc0
  u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo 
cat /sys/kernel/debug/pmc_core/package_cstate_show
  12965280
  Package C2 : 75052691
  Package C3 : 46989
  Package C6 : 8108332
  Package C7 : 0
  Package C8 : 0
  Package C9 : 0
  Package C10 : 13628111
  ~~~

  [where the issue could happen]
  Medium, Intel promise there's no issue of ADL AHCI and
  they will take responsibility after regression.
  Intel also take LPM as POR so they will fix any issues.

  [Misc]
  Because the board_ahci_mobile is still not modified to board_ahci_low_power 
on Jammy,
  provide a single patch for Jammy.

  For generic J/M, passed the all arch compilations on cbd,
  Jammy,
  ~~~
  $ git push j_cbd
  Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ
  remote: * 0/1 workers busy, 0 builds queued
  remote: 2023-11-17 19:50:25  kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK
  remote: 2023-11-17 20:18:29  kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK
  remote: 2023-11-17 20:01:41  kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK
  remote: 2023-11-17 20:31:51  kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK
  remote: 2023-11-17 20:37:25  kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK
  remote: 

  To cbd.kernel:jammy.git
   * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next
  ~~~

  Lunar,
  $ git push l_cbd
  Enumerating objects: 9, done.
  Counting objects: 100% (9/9), done.
  Delta compression using up to 8 threads
  Compressing objects: 100% (5/5), done.
  Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done.
  Total 5 (delta 4), reused 0 (delta 0), pack-reused 0
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-915de03d6ecf-V1nm
  remote: * 9/9 workers busy, 0 builds queued
  remote: 2023-11-20 16:00:11  kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK
  remote: 2023-11-20 15:59:57  

[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0:
  Device not ready: aborting installation, CSTS=0x0

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

  BugLink: https://bugs.launchpad.net/bugs/2041495

  [Impact]

  NVME module left unready, therefore not recognized by the installation 
process, and/or after installation with following error messages:
  ```
  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0
  ```

  [Fix]

  Proposed fix in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5=6cc834ba62998c65c42d0c63499bdd35067151ec
  "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well
  as stable kernels v6.1.55 and v6.5.5.

  [Test Case]

  Apply to kernel and boot with the nvme module installed. Now the device 
should be probed with success.
  ```
  kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0
  kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI 
INT A
  kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff
  kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds
  kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer.
  kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues
  kernel: [2.136735]  nvme0n1: p1 p2 p3
  ```

  [Where problems could occur]

  This patch tries to set an appropriate CRTO (Controller Ready
  Timeouts) that may be reported incorrectly by some devices. There
  should be little (a bit longer CRTO) to no effect on devices
  performing normally before hands.

  [Other Info]

  While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1
  will be nominated.

  == original bug report ==

  NVME module left unready, therefore not recognized by the installation
  process, and/or after installation with following error messages:

  kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0
  kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A
  kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI
  kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, 
CSTS=0x0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2036600] Re: Azure: Fix Azure vendor ID

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2036600

Title:
  Azure: Fix Azure vendor ID

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The linux-azure 6.2 kernel doesn't report a correct GUEST_ID

  There is a mistake in the commit
  (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
  azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
  :

  Before the commit, the good guest_id is 0x81860210.

  With the commit, the generated guest_id is incorrect:
  0x00860210, i.e. the 0x81 from bit 56~63 are dropped.

  See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
  * Bit(s)
  * 63 - Indicates if the OS is Open Source or not; 1 is Open Source

  * 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
  I'll post a patch to LKML to fix this typo.

  * 55:48 - Distro specific identification
  * 47:16 - Linux kernel version number
  * 15:0 - Distro specific identification

  See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
  windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)

  As a result, the host thinks that the VM is not an open-source OS, and
  it's not Linux. Consequently, the "VM Availability" fron Azure portal
  is 0 (unhealthy): some users rely on the info to manage their VMs,
  e.g. if the VM is erroneously reported "unhealthy", the VM may be
  killed and re-created, and the new VM is still "unhealthy", and the VM
  may be killed and re-created again...

  Please consider integrating the below fix ASAP. This affects regular
  VMs, and I think this affects CVMs as well.

  The fix should be:

  diff --git a/include/asm-generic/hyperv-tlfs.h 
b/include/asm-generic/hyperv-tlfs.h
  @@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
  *
  */

  -#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
  +#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  VMs could be misclassified.

  [Other Info]

  SF: #00368936

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2020022

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...

  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.

  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.

  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.

  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?

  [Test Plan]

  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled

  2.Install OS

  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled

  4.Rebooting will reproduce this issue

  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS successfully).

  [ Other Info ]

  
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2042853

Title:
  [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * Today no s390x-specific vfio-pci devices (zPCI) can be passed
 from a KVM host to a KVM guest (incl. secure execution guests
 in the context of confidential computing).

   * s390x PCI passthrough needs various changes in the s390x kernel zPCI
 code (incl. the new s390x-specific Kernel config option
 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0
 and got backported to 22.04/jammy as part of LP: #1853306.

   * Lunar an newer Ubuntu releases have the code already included from
 upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the
 config option is not set, hence zPCI pass-through is still not possible.

  [Fix]

   * To be able to make use of VFIO zPCI pass-through on s390x running newer
 Ubuntu releases (especially needed in the context of secure execution)
 the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs
 to be enabled and set to 'y'.

  [Test Case]

   * Hardware used: z14 or greater LPAR, PCI-attached devices
 (RoCE VFs, ISM devices, NVMe drive)

   * Setup: Both the kernel and QEMU features are needed for the feature
 to function (an upstream QEMU can be used to verify the kernel early),
 and the facility is only available on z14 or newer.
 When any of those pieces is missing,
 the interpretation facility will not be used.
 When both the kernel and QEMU features are included in their respective
 packages, and running in an LPAR on a z14 or newer machine,
 this feature will be enabled automatically.
 Existing supported devices should behave as before with no changes
 required by an end-user (e.g. no changes to libvirt domain definitions)
 -- but will now make use of the interpretation facility.
 Additionally, ISM devices will now be eligible for vfio-pci passthrough
 (where before QEMU would exit on error if attempting to provide an ISM
 device for vfio-pci passthrough, preventing the guest from starting)

   * Testing will include the following scenarios, repeated each for RoCE,
 ISM and NVMe:

 1) Testing of basic device passthrough (create a VM with a vfio-pci
device as part of the libvirt domain definition, passing through
a RoCE VF, an ISM device, or an NVMe drive. Verify that the device
is available in the guest and functioning)
 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device,
virsh detach-device to remove the device from the running guest,
verify the device is removed from the guest, then virsh attach-device
to hotplug the device to the guest again, verify the device functions
in the guest)
 3) Host power off testing: Power off the device from the host, verify
that the device is unplugged from the guest as part of the poweroff
 4) Guest power off testing: Power off the device from within the guest,
verify that the device is unusable in the guest,
power the device back on within the guest and verify that the device
is once again usable.
 5) Guest reboot testing: (create a VM with a vfio-pci device,
verify the device is in working condition, reboot the guest,
verify that the device is still usable after reboot)

  [Regression Potential]

   * The regression potential is moderate, since the code is upstream
 for quite a while and already enabled in jammy.

   * The general way on using passthrough has not changed, with this
 change (config option) it's now just possible to passthrough
 zPCI on top.

   * CCW devices are not affected.

   * And this is s390x-specific anyway, so no other architectures are
  

[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2045562

Title:
  [Debian] autoreconstruct - Do not generate chmod -x for deleted  files

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 Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Debian source format 1.0 cannot remove files, create symlinks and change
  permission in the .diff.gz tarball. Therefore any changes in these 3
  categories cannot be represented without any tricks. To solve this,
  the `reconstruct` script is used every time we build the source package.
  The script is generated by `gen-auto-reconstruct` script during `cranky
  close`. It checks if there has been any changes in the 3 categories
  mentioned above between the upstream version (i.e v6.5) and the current one.
  The problem with the script is that in case a file A was removed since the
  upstream version was released, the `reconstruct` script will contains
  these commands in this exact order:
  rm -f A
  chmod -x A
  The second command will fail because file A does not exist anymore.
  This is solved by generating the `chmod +/-x` commands before `rm`.
  Which results in:
  chmod -x A
  rm -f A
  But because the reconstruct script is used during `clean` rule which is
  triggered pretty much during every cranky step which is run in the
  source repo, the first command will always file because file A is not
  present anymore in the tree. To solved this, any `chmod` change is added
  only if the file has not been deleted. Therefore if file A has been
  deleted, the `reconstruct` script will contain only this:
  rm -f A

  [Fix]
  Generate chmod commands first.
  And when generating chmod -x command, first check if the file has been 
deleted. If yes, no need for a chmod command.

  [Test Plan]
  It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and 
it reconstruct script looked correct.

  [Other Info]
  An example of this is #lp2038611 where `script/is_rust_module.sh` was 
removed, but we keep seeing
  "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory"
  because `rm -f` and `chmod -x` command were generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  RTL8111EPP: Fix the network lost after resume with DASH

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  On the system installed RTL8111EPP with DASH, unable to get the network back 
upon system resume

  [Fix]
  handle DASH during system suspend and resume.

  [Test]
  Vendor tested on hardware, the ethernet is OK after resume.

  [Where problems could occur]
  It may break r8169 driver.

  No SRU for Jammy 5.15 kernel due to too many commits are needed to
  backport to support DASH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2043841

Title:
  kernel BUG: io_uring openat triggers audit reference count underflow

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
  occurs during io_uring openat audit processing.  I have a kernel patch
  that was accepted into the upstream kernel as well as the v6.6,
  v6.5.9, and v6.1.60 releases.  The bug was first introduced in the
  upstream v5.16 kernel.

  I do not see the change yet in:

  * The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel 
repository.
  * The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.

  Can this upstream commit be cherry picked?

  The upstream commit is:

  03adc61edad49e1bbecfb53f7ea5d78f398fe368

  The upstream patch thread is:

  
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u

  The maintainer pull request thread is:

  https://lore.kernel.org/lkml/20231019-kampfsport-
  metapher-e5211d7be247@brauner

  The pre-patch discussion thread is:

  https://lore.kernel.org/io-
  
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u

  The commit log message is:

  commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
  Author: Dan Clash 
  Date:   Thu Oct 12 14:55:18 2023 -0700

  audit,io_uring: io_uring openat triggers audit reference count
  underflow

  An io_uring openat operation can update an audit reference count
  from multiple threads resulting in the call trace below.

  A call to io_uring_submit() with a single openat op with a flag of
  IOSQE_ASYNC results in the following reference count updates.

  These first part of the system call performs two increments that
  do not race.

  do_syscall_64()
__do_sys_io_uring_enter()
  io_submit_sqes()
io_openat_prep()
  __io_openat_prep()
getname()
  getname_flags()   /* update 1 (increment) */
__audit_getname()   /* update 2 (increment) */

  The openat op is queued to an io_uring worker thread which starts the
  opportunity for a race.  The system call exit performs one decrement.

  do_syscall_64()
syscall_exit_to_user_mode()
  syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
  audit_reset_context()
 putname()  /* update 3 (decrement) */

  The io_uring worker thread performs one increment and two decrements.
  These updates can race with the system call decrement.

  io_wqe_worker()
io_worker_handle_work()
  io_wq_submit_work()
io_issue_sqe()
  io_openat()
io_openat2()
  do_filp_open()
path_openat()
  __audit_inode()   /* update 4 (increment) */
  putname() /* update 5 (decrement) */
  __audit_uring_exit()
audit_reset_context()
  putname() /* update 6 (decrement) */

  The fix is to change the refcnt member of struct audit_names
  from int to atomic_t.

  kernel BUG at fs/namei.c:262!
  Call Trace:
  ...
   ? putname+0x68/0x70
   audit_reset_context.part.0.constprop.0+0xe1/0x300
   __audit_uring_exit+0xda/0x1c0
   io_issue_sqe+0x1f3/0x450
   ? lock_timer_base+0x3b/0xd0
   io_wq_submit_work+0x8d/0x2b0
   ? __try_to_del_timer_sync+0x67/0xa0
   io_worker_handle_work+0x17c/0x2b0
   io_wqe_worker+0x10a/0x350

  Cc: sta...@vger.kernel.org
  Link: 
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
  Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support 
to io_uring")
  Signed-off-by: Dan Clash 
  Link: 

[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  Avoid using damage rectangle under hardware rotation mode when PSR is
  enabled

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When hardware rotation feature is used by compositor, the clip damage on 
cursor plane causes screen glitches on AMD platforms with PSR panel.

  [Fix]
  Disable clip damage when hardware rotation is used.

  [Test]
  With the patch applied, the issue can't be observed when the screen is 
rotated 180 degree.
  90 and 270 degrees are unaffected since no compositor is using hardware 
rotation for those two angles.

  [Where problems could occur]
  The power consumption in theory will higher for 180 degree rotation because 
now the full screen may need to be redrawn when cursor moves.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045958/+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 2046105] Re: Sound: Add rtl quirk of M90-Gen5

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-linux

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

Title:
  Sound: Add rtl quirk of M90-Gen5

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  When plugin the headset jack, only speaker is identified.

  [Fix]
  Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.

  [Test]
  Vendor tested on hardware, headset mic works fine.

  [Where problems could occur]
  It may break audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046105/+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 2047382] Re: Hotplugging SCSI disk in QEMU VM fails

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still exists, change the tag 'verification-needed-lunar-
linux' to 'verification-failed-lunar-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-lunar-linux-v2 verification-needed-lunar-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/2047382

Title:
  Hotplugging SCSI disk in QEMU VM fails

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  In Progress

Bug description:
  [Impact]
  Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest 
kernels >= 6.5 might be broken.
  The inconsistency suggests a potential race condition.

  [Fix]
  Reverting the two specified commits appears to restore reliability.
  ==
  cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only 
for non-root bus
  40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  Upstream has resolved the issue by reverting both commits through a commit 
placed below.
  ==
  5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary
  ==

  [Test Plan]
  1. Create a VM
  virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk 
path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio
  -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0
  2. Prepare two XMLs for adding two disk devices
  # cat disk_X.xml
  
    
    
    
  
  3. Hotplug disks and check for success
  virsh attach-device scsi_test disk_X.xml

  [Where problems could occur]
  The patch reverts two commits that previously addressed long-standing issues 
related to hotplugging devices with large BARs.
  While this reversion may reintroduce legacy issues, it does not introduce new 
problems.
  The associated risks are deemed low, making it worthwhile to address timing 
issues during the hotplugging of SCSI disks in QEMU VM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+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 2048796] [NEW] post-installation script subprocess returned error exit status 1

[Valtýr Kári Daníelsson]

Public bug reported:

Hi, I was updating my system, running sudo apt update then sudo apt
upgrade and there were some errors in the installation. It seems to stem
from some post-installation script for linux-image-6.6.0-14-generic
and/or linux-headers-6.6.0-14-generic. After the upgrade apt told me
that "errors were encountered while processing:" linux-generic, linux-
headers-generic, linux-image-6.6.0-14-generic and linux-
headers-6.6.0-14-generic. Running dpkg -a --configure does not solve the
issue, nor does apt -f install. I've tried reconfiguring with the
methods suggested in this thread:
https://askubuntu.com/questions/949760/dpkg-warning-files-list-file-for-
package-missing and I can manually reconfigure and reinstall linux-
generic, linux-headers-generic and linux-image-6.6.0-14-generic, and I
can reconfigure linux-headers-6.6.0-14-generic but then when I try to
reinstall that package it gives the error "installed linux-
headers-6.6.0-14-generic package post-installation script subprocess
returned error exit status 1."

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fixgoats   2427 F wireplumber
 /dev/snd/controlC0:  fixgoats   2408 F pipewire
  fixgoats   2427 F wireplumber
 /dev/snd/seq:fixgoats   2408 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  9 18:06:52 2024
InstallationDate: Installed on 2023-03-30 (285 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=0fc69223-fb6f-45e4-9873-b76a5b689b0c ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-14-generic N/A
 linux-backports-modules-6.5.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2023-12-30 (10 days ago)
dmi.bios.date: 03/29/2021
dmi.bios.release: 2.3
dmi.bios.vendor: Razer
dmi.bios.version: 2.03
dmi.board.name: LY350
dmi.board.vendor: Razer
dmi.board.version: 4
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvnRazer:bvr2.03:bd03/29/2021:br2.3:efr1.0:svnRazer:pnBladeStealth13(Late2020)-RZ09-0327:pvr5.04:rvnRazer:rnLY350:rvr4:cvnRazer:ct10:cvr:skuRZ09-03272N12:
dmi.product.family: 1A581006 Razer Blade Stealth
dmi.product.name: Blade Stealth 13 (Late 2020) - RZ09-0327
dmi.product.sku: RZ09-03272N12
dmi.product.version: 5.04
dmi.sys.vendor: Razer

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


** Tags: amd64 apport-bug noble

** Description changed:

  Hi, I was updating my system, running `sudo apt update` then `sudo apt
  upgrade` and there were some errors in the installation. It seems to
  stem from some post-installation script for linux-image-6.6.0-14-generic
  and/or linux-headers-6.6.0-14-generic. After the upgrade apt told me
  that "errors were encountered while processing:" linux-generic, linux-
  headers-generic, linux-image-6.6.0-14-generic and linux-
  headers-6.6.0-14-generic. Running `dpkg -a --configure` does not solve
- the issue. I've tried reconfiguring with the methods suggested in [this
- thread](https://askubuntu.com/questions/949760/dpkg-warning-files-list-
- file-for-package-missing) and I can manually reconfigure and reinstall
+ the issue. I've tried reconfiguring with the methods suggested in this
+ thread: https://askubuntu.com/questions/949760/dpkg-warning-files-list-
+ file-for-package-missing and I can manually reconfigure and reinstall
  linux-generic, linux-headers-generic and linux-image-6.6.0-14-generic,
  and I can reconfigure linux-headers-6.6.0-14-generic but then when I try
  to reinstall that package it gives the error "installed linux-
  headers-6.6.0-14-generic package post-installation script subprocess
  returned error exit status 1."
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.6.0-14-generic 6.6.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  fixgoats   2427 F wireplumber
-  /dev/snd/controlC0:  fixgoats   2408 F pipewire
-   fixgoats   2427 F wireplumber
-  /dev/snd/seq:fixgoats   2408 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  fixgoats   2427 F 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-5.15/5.15.0-1048.56~20.04.1+1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15 
(5.15.0-1048.56~20.04.1+1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf)


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/focal/update_excuses.html#linux-restricted-modules-gcp-5.15

[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-azure 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 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

[Mauricio Faria de Oliveira]

The crash 8.0.4 merge in bug 2047861 looks good, it passed
autopkgtests/manual tests, and is now waiting on review/sponsoring for
Noble.

Once accepted/released to Noble, this should unblock the SRUs (which have 
patches from 8.0.4).
I'll continue the SRU debdiff reviews for now.

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  In Progress
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.3++ (8.0.4 development)
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show 

[Kernel-packages] [Bug 2047861] Re: Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Tested in dump file form in s390x; working.

s390x
-

vm

SERIES=noble
ARCH=s390x
DISK=${SERIES}_${ARCH}.qcow2

wget 
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f 
qcow2 $DISK 8G

sudo apt install -y qemu-system-s390x

qemu-system-s390x \
  -machine s390-ccw-virtio -cpu qemu \
\
-smp cpus=2 -m 2048 \
-nodefaults -no-user-config \
-nographic -serial stdio \
\
-drive file=$DISK,if=none,id=drive0 \
-device virtio-blk,drive=drive0 \
\
-drive file=test-cidata.iso,media=cdrom \
\
-netdev user,hostfwd=::4-:22,id=net0 \
-device virtio-net,netdev=net0

$ ssh ubuntu@127.0.0.1 -p 4

$ lsb_release -cs
No LSB modules are available.
noble

$ uname -m
s390x

$ uname -rv
6.6.0-14-generic #14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023

kdump-tools

sudo apt update && sudo apt install -y linux-crashdump # No, Yes
sudo sed '/^parameters =/ s/$/ crashkernel=512M/' -i /etc/zipl.conf
sudo zipl && sudo reboot

$ sudo dmesg | grep 'crashkernel.*RAM'
[1.176382] setup: Reserving 512MB of memory at 1509MB for 
crashkernel (System RAM: 1536MB)

$ sudo kdump-config status
current state   : ready to kdump

crashdump

$ echo c | sudo tee /proc/sysrq-trigger

$ find /var/crash
/var/crash
/var/crash/kexec_cmd
/var/crash/kdump_lock
/var/crash/linux-image-6.6.0-14-generic-202401091639.crash
/var/crash/202401091639
/var/crash/202401091639/dmesg.202401091639
/var/crash/202401091639/dump.202401091639

debug symbols

dpkg -l | awk '$2 ~ /linux-image-[0-9.-]+-generic/ { print $2, $3}' \
  | while read pkg version; do \
  dbgpkg="linux-image-${pkg#linux-image-}-dbgsym"; \
  arch=$(dpkg --print-architecture); \
  wget 
"https://launchpad.net/ubuntu/+archive/primary/+files/${dbgpkg}_${version}_${arch}.ddeb;;
 \
done

ar p linux-image-*-dbgsym_*.ddeb data.tar.xz | tar xJ
--wildcards './usr/lib/debug/boot/vmlinux-*-generic'

crash

sudo add-apt-repository -y ppa:mfo/lp2047861-noble-crash && sudo
apt install -y crash

# dpkg -s crash | grep Version:
Version: 8.0.4-1ubuntu1

# crash ./usr/lib/debug/boot/vmlinux-*-generic /var/crash/*/dump.*
...

  KERNEL: ./usr/lib/debug/boot/vmlinux-6.6.0-14-generic
DUMPFILE: /var/crash/202401091639/dump.202401091639  [PARTIAL DUMP]
CPUS: 2
DATE: Tue Jan  9 16:36:47 UTC 2024
  UPTIME: 00:06:08
LOAD AVERAGE: 2.56, 2.20, 1.11
   TASKS: 148
NODENAME: test
 RELEASE: 6.6.0-14-generic
 VERSION: #14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023
 MACHINE: s390x  (unknown Mhz)
  MEMORY: 2 GB
   PANIC: "Kernel panic - not syncing: sysrq triggered crash"
 PID: 1615
 COMMAND: "tee"
TASK: 4bd2400  [THREAD_INFO: 4bd2400]
 CPU: 0
   STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1615 TASK: 4bd2400   CPU: 0COMMAND: "tee"
 LOWCORE INFO:
  -psw  : 0x0400c0018000 0x00126220
  -function : __do_machine_kdump at 126220
  -prefix   : 0x026e8000
  -cpu timer: 0x7ea07b16f64d
  -clock cmp: 0x796343ea7b0db800
  -general registers:
 0x026bd400 0x026bd400
 0x00126220 0x7f239800
 00 00
 0x7f239800 0x01743958
 0x7f239800 00
 0x01743c90 0x0002
 0x03ff960d9c80 0x00fa24d0
 0x001263ee 0x026b7db8
  -access registers:
 0x03ff 0x962fa760 00 00
 00 00 00 00
 00 00 00 00
 00 00 00 00
  -control registers:
 0x14166a10 0x020ec007
 0x000ff140 00
 0x 0x000ff140
 0x3000 0x0474c1c7
 0x8000 00
 00 00
 00 0x020ec007
 0xdb00 0x000ff000
  -floating point registers:
 0x02aa1fe4e383 0x5554462d38004c43
 0x03ff960db4c3 

[Kernel-packages] [Bug 2047861] Re: Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Autopkgtests (live system form) PASS in amd64, arm64, ppc64el, s390x (armhf 
skipped) [comment #3]
Manual tests (dump file form) PASS in amd64, arm64, ppc64el, s390x [comments 
#4, #5, #6, #7]

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

Title:
   Merge crash 8.0.4-1 into Noble

Status in crash package in Ubuntu:
  In Progress

Bug description:
  $ rmadison -a source crash | grep noble
   crash | 8.0.3+ds1-3ubuntu1 | noble  | source

  $ rmadison -a source -u debian -s unstable crash
  crash  | 8.0.4-1   | unstable   | source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2047861/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Tim Gardner]

** Changed in: linux-aws (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Changed in: linux-aws (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2048758] Re: nvidia-dkms-535-server-open FTBS with the latest 6.7 kernel in noble

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.129.03-0ubuntu2

---
nvidia-graphics-drivers-535-server (535.129.03-0ubuntu2) noble; urgency=medium

  * Support linux 6.7 ABI (LP: #2048758):
- debian/open-kernel/patches/re-add-crypto_tfm_ctx_aligned.patch

 -- Andrea Righi   Tue, 09 Jan 2024 09:06:46
+

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  nvidia-dkms-535-server-open FTBS with the latest 6.7 kernel in noble

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: error: 
implicit declaration of function ‘crypto_tfm_ctx_aligned’; did you mean 
‘crypto_tfm_ctx_align’? [-Werror=implicit-function-declaration]
 90 | char *src_ipad = crypto_tfm_ctx_aligned(_tfm->base);
|  ^~
|  crypto_tfm_ctx_align
  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:91:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
 91 | char *dst_ipad = crypto_tfm_ctx_aligned(_tfm->base);
|  ^~
  cc1: some warnings being treated as errors

  [Test case]

   $ sudo apt install nvidia-dkms-535-server-open

  [Fix]

  Upstream commit acd7799574e5 ("crypto: shash - remove
  crypto_shash_ctx_aligned()") removed crypto_tfm_ctx_aligned() that is
  used by the open variant of the driver.

  Re-introduce this function (as a static inline) directly in the driver
  (like the original one):

  static inline void *crypto_tfm_ctx_aligned(struct crypto_tfm *tfm)
  {
 return crypto_tfm_ctx_align(tfm, crypto_tfm_alg_alignmask(tfm) + 1);
  }

  This should fix the build error, since crypto_tfm_ctx_align() is still
  available in the kernel ABI.

  [Regression potential]

  We may experience graphics regressions in systems that are using the
  open variant of the 535-server nvidia driver, especially with any 6.7
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: nvidia-dkms-535-server-open 535.129.03-0ubuntu1
  ProcVersionSignature: User Name 6.7.0-5.5-generic 6.7.0-rc8
  Uname: Linux 6.7.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20240101
  CloudSubPlatform: config-disk (/dev/vdb)
  Date: Tue Jan  9 08:54:19 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nvidia-graphics-drivers-535-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2048758/+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 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel

[Andrew Cloke]

Work is still ongoing on reproducing this issue in a more predictable
environment.

-- 
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/2042564

Title:
  Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4
  Ubuntu 20.04 kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  We in the Canonical Public Cloud team have received report from our
  colleagues in Google regarding a potential performance regression with
  the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were
  performed using the linux-gkeop and linux-gkeop-5.15 kernels.

  I have verified with the generic Ubuntu 20.04 5.4 linux-generic and
  the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels.

  The tests were run using `fio`

  fio commands:

  * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`
  * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write 
--filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting 
--numjobs=8 --name=fiojob1 --filename=/dev/sdc`

  
  My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the 
results are below:

  Using 5.4 kernel

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.4.0-164-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] 
  fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov  2 09:15:22 2023
write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets
  slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61
  clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38
   lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80
  clat percentiles (usec):
   |  1.00th=[  775],  5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024],
   | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261],
   | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932],
   | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676],
   | 99.99th=[32113]
 bw (  MiB/s): min=  524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, 
samples=4232
 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, 
samples=4232
lat (nsec)   : 500=0.01%, 750=0.01%, 1000=0.01%
lat (usec)   : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01%
lat (usec)   : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93%
lat (msec)   : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07%
lat (msec)   : 100=0.01%
cpu  : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103
IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
   submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.0%
   complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
>=64=0.1%
   issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0
   latency   : target=0, window=0, percentile=100.00%, depth=128

  Run status group 0 (all jobs):
WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), 
io=320GiB (344GB), run=264837-264837msec

  Disk stats (read/write):
sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, 
util=100.00%
  ```

  
  After upgrading to linux-generic-hwe-20.04 kernel and rebooting

  ```
  ubuntu@cloudimg:~$ uname --kernel-release
  5.15.0-88-generic

  ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k 
--readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 
--group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda
  fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  ...
  fio-3.16
  Starting 8 processes
  Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s]
  fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov  2 09:46:49 2023
write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets
  slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50
  clat (nsec): min=1100, max=782743k, avg=6595008.67, stdev=6290570.04
   lat (usec): min=86, max=782748, avg=6606.08, stdev=6294.03
  clat percentiles (usec):
   |  1.00th=[   914],  5.00th=[  2180], 10.00th=[  2802], 20.00th=[  3556],
   | 30.00th=[  4178], 40.00th=[  4817], 50.00th=[  5538], 60.00th=[  6259],
   | 

[Kernel-packages] [Bug 2048782] [NEW] RM obsolete auxiliary packages for removed nvidia server ERD drivers

[Dimitri John Ledkov]

Public bug reported:

RM obsolete auxiliary packages for removed nvidia server ERD drivers.

libnvidia-nscq & fabric-manager are userspace packages related to the
ERD drivers.

Once ERD drivers are removed from the archive so should these packages
too

** Affects: fabric-manager-450 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: fabric-manager-460 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: fabric-manager-510 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: fabric-manager-515 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: libnvidia-nscq-450 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: libnvidia-nscq-460 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: libnvidia-nscq-510 (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: libnvidia-nscq-515 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Also affects: libnvidia-nscq-510 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fabric-manager-510 (Ubuntu)
   Status: New => Triaged

** Changed in: libnvidia-nscq-510 (Ubuntu)
   Status: New => Triaged

** Also affects: fabric-manager-515 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fabric-manager-515 (Ubuntu)
   Status: New => Incomplete

** Also affects: libnvidia-nscq-515 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libnvidia-nscq-515 (Ubuntu)
   Status: New => Incomplete

** Also affects: fabric-manager-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fabric-manager-460 (Ubuntu)
   Status: New => Triaged

** Also affects: libnvidia-nscq-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libnvidia-nscq-460 (Ubuntu)
   Status: New => Triaged

** Also affects: libnvidia-nscq-450 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libnvidia-nscq-450 (Ubuntu)
   Status: New => Triaged

** Also affects: fabric-manager-450 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fabric-manager-450 (Ubuntu)
   Status: New => Triaged

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

Title:
  RM obsolete auxiliary packages for removed nvidia server ERD drivers

Status in fabric-manager-450 package in Ubuntu:
  Triaged
Status in fabric-manager-460 package in Ubuntu:
  Triaged
Status in fabric-manager-510 package in Ubuntu:
  Triaged
Status in fabric-manager-515 package in Ubuntu:
  Incomplete
Status in libnvidia-nscq-450 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-460 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-510 package in Ubuntu:
  Triaged
Status in libnvidia-nscq-515 package in Ubuntu:
  Incomplete

Bug description:
  RM obsolete auxiliary packages for removed nvidia server ERD drivers.

  libnvidia-nscq & fabric-manager are userspace packages related to the
  ERD drivers.

  Once ERD drivers are removed from the archive so should these packages
  too

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+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 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

[Stefan Bader]

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

-- 
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/2028158

Title:
  [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  Description of problem:

  Observed device_dax related probe errors in dmesg when HBM CPU is set
  to flat mode.  Duplicate device_dax ids were created and hence probing
  is failing.

  How reproducible:
  Frequently

  Version-Release
  Release:22.04.2, 22.10

  [Test Case]

  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.

  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.

  Expected results:
  Dummy/duplicate devices should not create.

  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/

  
  [Where problems could occur]

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2

  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].

  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16

  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"system-ram",---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    },
    {
  "chardev":"dax5.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  

[Kernel-packages] [Bug 2047154] Re: [amdgpu][drm] *ERROR* flip_done timed out

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [amdgpu][drm] *ERROR* flip_done timed out

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out
  gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CRTC:84:crtc-0] commit wait timed out
  gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
  gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[CONNECTOR:119:HDMI-A-1] commit wait timed out
  gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=2>
  gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
flip_done timed out
  gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* 
[PLANE:67:plane-5] commit wait timed out
  gru 21 16:32:46 karol.home.prv kernel: [ cut here ]
  gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at 
/var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di>
  gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls 
xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i>
  gru 21 16:32:46 karol.home.prv kernel:  reed_solomon pstore_zone efi_pstore 
sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp>
  gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: 
PW  OE  6.2.0-26-generic #26~22.04.1-Ubuntu
  gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. 
To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29>
  gru 21 16:32:46 karol.home.prv kernel: RIP: 
0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu]
  gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 
00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5>
  gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 
00010002
  gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 
00013195 RCX: 
  gru 21 16:32:46 karol.home.prv kernel: RDX:  RSI: 
 RDI: 
  gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: 
 R09: 
  gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: 
 R12: 0246
  gru 21 16:32:46 karol.home.prv kernel: R13:  R14: 
9710a5d8d118 R15: 9710a5d8d000
  gru 21 16:32:46 karol.home.prv kernel: FS:  7f3267b4ea80() 
GS:97179eac() knlGS:
  gru 21 16:32:46 karol.home.prv kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 
000250f4e000 CR4: 003506e0
  gru 21 16:32:46 karol.home.prv kernel: Call Trace:
  gru 21 16:32:46 karol.home.prv kernel:  
  gru 21 16:32:46 karol.home.prv kernel:  commit_tail+0xc5/0x1a0 
[drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_helper_commit+0x137/0x160 
[drm_kms_helper]
  gru 21 16:32:46 karol.home.prv kernel:  drm_atomic_commit+0x99/0xd0 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? __pfx___drm_printfn_info+0x10/0x10 
[drm]
  gru 21 16:32:46 karol.home.prv kernel:  
drm_mode_obj_set_property_ioctl+0x179/0x430 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
drm_mode_createblob_ioctl+0xff/0x130 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl_kernel+0xc3/0x160 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  drm_ioctl+0x27b/0x4c0 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? 
__pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm]
  gru 21 16:32:46 karol.home.prv kernel:  ? __pm_runtime_suspend+0x7b/0x110
  gru 21 16:32:46 karol.home.prv kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
  gru 21 16:32:46 karol.home.prv kernel:  __x64_sys_ioctl+0x9d/0xe0
  gru 21 16:32:46 karol.home.prv kernel:  do_syscall_64+0x5c/0x90
  gru 21 16:32:46 karol.home.prv kernel:  ? do_syscall_64+0x69/0x90
  gru 21 16:32:46 karol.home.prv kernel:  ? exit_to_user_mode_prepare+0x3b/0xd0
  gru 21 16:32:46 karol.home.prv kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
  ? do_syscall_64+0x69/0x90
  gru 21 16:32:46 karol.home.prv kernel:  
entry_SYSCALL_64_after_hwframe+0x72/0xdc
  gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f
  gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 
24 60 c7 04 24 

[Kernel-packages] [Bug 2047861] Re: Merge crash 8.0.4-1 into Noble

[Mauricio Faria de Oliveira]

Tested in dump file form in ppc64el; working.

ppc64el
---

vm

SERIES=noble
ARCH=ppc64el
DISK=${SERIES}_${ARCH}.qcow2

wget 
https://cloud-images.ubuntu.com/$SERIES/current/${SERIES}-server-cloudimg-${ARCH}.img
qemu-img create -F qcow2 -b ${SERIES}-server-cloudimg-${ARCH}.img -f 
qcow2 $DISK 8G

sudo apt install -y qemu-system-ppc

qemu-system-ppc64 \
  -machine pseries -cpu POWER10 \
\
-smp cpus=2 -m 2048 \
-nodefaults -no-user-config \
-nographic -serial stdio \
\
-drive file=$DISK,if=none,id=drive0 \
-device virtio-blk,drive=drive0 \
\
-drive file=test-cidata.iso,media=cdrom \
\
-netdev user,hostfwd=::3-:22,id=net0 \
-device virtio-net,netdev=net0

$ ssh ubuntu@127.0.0.1 -p 3

$ lsb_release -cs
No LSB modules are available.
noble

$ uname -m
ppc64le

$ uname -rv
6.5.0-9-generic #9-Ubuntu SMP Fri Oct  6 20:21:54 UTC 2023

kdump-tools

sudo apt update && sudo apt install -y linux-crashdump # No, Yes
sudo sed 's/crashkernel=[^" ]\+/crashkernel=512M/' -i 
/etc/default/grub.d/kdump-tools.cfg
sudo update-grub && sudo reboot

...

$ sudo dmesg | grep 'crashkernel.*RAM'
[0.00] Reserving 512MB of memory at 512MB for crashkernel 
(System RAM: 2048MB)


$ sudo kdump-config status
current state   : ready to kdump

crashdump

$ echo c | sudo tee /proc/sysrq-trigger

$ find /var/crash
/var/crash
/var/crash/202401082101
/var/crash/202401082101/dmesg.202401082101
/var/crash/202401082101/dump.202401082101
/var/crash/kexec_cmd
/var/crash/kdump_lock


debug symbols

dpkg -l | awk '$2 ~ /linux-image-[0-9.-]+-generic/ { print $2, $3}' \
  | while read pkg version; do \
  dbgpkg="${pkg}-dbgsym"; \
  arch=$(dpkg --print-architecture); \
  wget 
"https://launchpad.net/ubuntu/+archive/primary/+files/${dbgpkg}_${version}_${arch}.ddeb;;
 \
done

ar p linux-image-*-dbgsym_*.ddeb data.tar.xz | tar xJ
--wildcards './usr/lib/debug/boot/vmlinux-*-generic'

crash

sudo add-apt-repository -y ppa:mfo/lp2047861-noble-crash && sudo
apt install -y crash

$ dpkg -s crash | grep Version:
Version: 8.0.4-1ubuntu1

$ crash ./usr/lib/debug/boot/vmlinux-*-generic /var/crash/*/dump.*
...
  KERNEL: ./usr/lib/debug/boot/vmlinux-6.6.0-14-generic
DUMPFILE: /var/crash/202401082101/dump.202401082101  [PARTIAL DUMP]
CPUS: 2
DATE: Mon Jan  8 21:00:05 UTC 2024
  UPTIME: 00:20:30
LOAD AVERAGE: 0.12, 0.15, 0.39
   TASKS: 140
NODENAME: test
 RELEASE: 6.6.0-14-generic
 VERSION: #14-Ubuntu SMP Thu Nov 30 10:29:25 UTC 2023
 MACHINE: ppc64le  (1000 Mhz)
  MEMORY: 2 GB
   PANIC: "Kernel panic - not syncing: sysrq triggered crash"
 PID: 1174
 COMMAND: "tee"
TASK: c00047f89900  [THREAD_INFO: c00047f89900]
 CPU: 1
   STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1174 TASK: c00047f89900  CPU: 1COMMAND: "tee"
 R0:  c0305af8R1:  c00047df7890R2:  c2162b00
 R3:  c00047df78a8R4:  R5:  
 R6:  c00047df7a58R7:  R8:  0001
 R9:  cec87000R10: R11: 
 R12: R13: c0007fffee80R14: 
 R15: dfc4R16: 182cb62e2458R17: 0080
 R18: 0081R19: 7fffe1a2c5d8R20: 7fffe1a2c5a0
 R21: R22: 0002R23: 0001
 R24: c3aa0390R25: R26: 0004
 R27: c38a4a20R28: c3cbace0R29: c3cbad20
 R30: c3d12b00R31: 
 NIP: c0303904MSR: 80009033OR3: 
 CTR: LR:  c0305af8XER: 20040004
 CCR: 24048200MQ:  0001DAR: 
 DSISR:  Syscall Result: 
 [NIP  : crash_setup_regs+84]
 [LR   : __crash_kexec+152]
 #0 [c00047df7890] crash_setup_regs at c0303904
crash> quit

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

Title:
   Merge crash 8.0.4-1 into Noble

[Kernel-packages] [Bug 2045387] Re: Add ODM driver f81604 usb-can

[Stefan Bader]

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

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

-- 
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/2045387

Title:
  Add ODM driver f81604 usb-can

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  From 68b4664246d9f4d44409f344a6b67890ab88156b Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:46:08 +0100
  Subject: [PATCH 3/3] Add f81604 usb-can kernel driver

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045387

  [ Impact ]
  f81604  driver needed for ODM partner

  [ Test Plan ]

  Install can-utils

  apt install can-utils

  insert the driver:
  modprobe f81604

  two socket can interfaces will be created, can0 and can1

  connect the DB9 cable and termination provided.
  Set up the two interfaces:
  ip link set can1 up type can bitrate 50
  ip link set can1 up type can bitrate 50
  candump can0

  In another shell run:
  cansend can1 123#DEADBEEF

  The first shell should report the received frame. Switch the
  interfaces in the last commands to test the frame flow in the other
  way around.

  [ Where problems could occur ]
  USB bus miss-behavior could cause issues to the driver.

  [ Other Info ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045387/+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 2045385] Re: Add ODM driver rtc-pcf85263

[Stefan Bader]

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

-- 
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/2045385

Title:
  Add ODM driver rtc-pcf85263

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:43:41 +0100
  Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385

  
  [ Impact ]
  rtc-pcf85263 driver needed for ODM partner

  [ Test Plan ]

  Load the driver setting the timestamp level to 0 (default to 1) :
  modprobe rtc-pcf85263 tsl=0

  export the rtc device:
  echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device

  RTC device should act as a standard RTC,
  hwclock -r -f /dev/rtc1 #for reading
  hwclock -w -f /dev/rtc1 #for writing

  This driver has anti-tampering function.
  Get the current tamper timestamp:
  cat /sys/class/rtc/rtc1/device/timestamp1

  unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the 
anti-tampering goes in open state.
  The timestamp should be updated to the current time.

  [ Where problems could occur ]

  Events could occur on the I2C bus communication.

  [ Other Info ]

  X-HWE-Bug: Bug #2046985

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 2045386] Re: Add ODM driver gpio-m058ssan

[Stefan Bader]

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

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

-- 
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/2045386

Title:
  Add ODM driver gpio-m058ssan

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  From ab1655aff54bdbd7a6d5867b9c176d577ea4 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:45:07 +0100
  Subject: [PATCH 2/3] Add gpio-m058ssan kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045386

  [ Impact ]
  gpio-m058ssan driver needed for ODM partner

  [ Test Plan ]

  Connect the loopback GPIO connector to the ReliaCOR-40-13 system and
  connect the power supply of the GPIO connector.

  insert the "m058ssan" module:
  modprobe m058ssan

  create GPIOchip:
  echo "m058ssan 0x40" > /sys/bus/i2c/devices/i2c-0/new_device

  get the GPIO chip base and export 16 GPIOs. The former 8 are GPOs ,
  the latter 8 are GPIs.

  Set and reset all of the GPOs one at a time and check that the
  corresponding GPI is set and reset accordingly.

  [ Where problems could occur ]

  Make sure that the power supply of the GPIO connector is correctly connected, 
otherwise the GPI will always report 0.
  Events could occur on the i2c bus communication that may cause miss-behavior 
of the driver.

  [ Other Info ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045386/+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 2045385] Re: Add ODM driver rtc-pcf85263

[Stefan Bader]

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => 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/2045385

Title:
  Add ODM driver rtc-pcf85263

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  In Progress

Bug description:
  From de5bc92c48fefb23e570a97d12738a39927edb72 Mon Sep 17 00:00:00 2001
  From: Filippo Copetti 
  Date: Mon, 4 Dec 2023 14:43:41 +0100
  Subject: [PATCH 1/3] Add rtc-pcf85263 kernel driver

  BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045385

  
  [ Impact ]
  rtc-pcf85263 driver needed for ODM partner

  [ Test Plan ]

  Load the driver setting the timestamp level to 0 (default to 1) :
  modprobe rtc-pcf85263 tsl=0

  export the rtc device:
  echo "pcf85263 0x51" > /sys/bus/i2c/devices/i2c-1/new_device

  RTC device should act as a standard RTC,
  hwclock -r -f /dev/rtc1 #for reading
  hwclock -w -f /dev/rtc1 #for writing

  This driver has anti-tampering function.
  Get the current tamper timestamp:
  cat /sys/class/rtc/rtc1/device/timestamp1

  unmount the bottom metal panel, unscrewing the 6x T-10 screws and let the 
anti-tampering goes in open state.
  The timestamp should be updated to the current time.

  [ Where problems could occur ]

  Events could occur on the I2C bus communication.

  [ Other Info ]

  X-HWE-Bug: Bug #2046985

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2045385/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

[Heitor Alves de Siqueira]

I've successfully confirmed that the mount issues seem to be fixed using
systemd from focal-proposed. Using the 'rep-tmpfs.sh' script, all
variants ran without any issues for multiple rounds. Basic testing on a
VM also looks good. Below are the versions used for this test:

$ dpkg -l systemd
...
||/ Name   Version   Architecture Description
+++-==-=--=
ii  systemd245.4-4ubuntu3.23 amd64system and service manager

$ uname -rv
5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023

I'll look into the reported regressions next, to confirm none of them
are caused by this LP.

** Tags removed: se-sponsor-halves verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
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/1837227

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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 2046608] Re: The fan of VisionFive2 still works after I power it off.

[Emil Renner Berthing]

If you look at page 2 of the schematic:

https://doc-en.rvspace.org/VisionFive2/PDF/SCH_RV002_V1.2A_20221216.pdf

you'll see that the fan is connected directly to the 5V power supply.
There is no way to turn it off but to cut the power to the whole board.

Marking as invalid.

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

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

Title:
  The fan of VisionFive2 still works after I power it off.

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  The fan of VisionFive2 still works after I power it off.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.4
  ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Sat Dec 16 10:23:41 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.2
  InstallationDate: Installed on 2023-09-19 (88 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
  Lspci-vt:
   -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI USB 
3.0 Controller
   -[0001:00]---00.0-[01]00.0  Silicon Motion, Inc. SM2263EN/SM2263XT 
(DRAM-less) NVMe SSD Controllers
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, 
Driver=rtl8xxxu, 480M
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046608/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/147983.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/147984.html (lunar)

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

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: Triaged => Fix Committed

-- 
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/2045384

Title:
  AppArmor patch for mq-posix interface is missing in jammy

Status in linux package in Ubuntu:
  Triaged
Status in livecd-rootfs package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Jammy:
  New

Bug description:
  [ Impact ]

  mq-posix snapd interface does not work on Ubuntu Core 22. It results
  in permission denied even all interfaces are connected.

  Our brandstore customer is using posix message queue for IPC between
  snaps. They added mq-posix interface and connected them properly but
  getting permission denied error.

  The AppArmor patch for posix message queue created for other customer
  did not land in the standard jammy kernel.

  Userspace support for AppArmor message queue handling is already
  present in Ubuntu Core 22, it is just missing from the kernel.

  [ Test Plan ]

   * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or 
Classic 22.04 with the standard kernel.
   * Example snaps for testing: 
https://code.launchpad.net/~itrue/+git/mqtest-provider and 
https://code.launchpad.net/~itrue/+git/mqtest-client

  [ Where problems could occur ]

   * The patches already exist for 5.15 and have been used on other
  private customer kernels and all kernels released after 22.04, so
  there is already a good track record for this patchset and it
  shouldn't create any issues.

  [ Other Info ]
   
   * This is a time-sensitive issue for a paying customer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off

[You-Sheng Yang]

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ Dell dock station WD22TB4 loses ether dev after reboot/power off.
+ 
+ [Fix]
+ 
+ Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
+ devices").
+ 
+ [Test Case]
+ 
+ 1. Connect WD22TB4 with ethernet cable
+ 2. Boot into OS
+ 3. power off (or just reboot)
+ 4. power on and check if ethernet connection is still available.
+ 
+ [Where problems could occur]
+ 
+ Opaque firmware update. No known issue found yet after the update.
+ 
+ [Other Info]
+ 
+ The proposed fix has been included in Mantic and Noble, so nominate only for
+ Lunar and Jammy (for oem-6.5).
+ 
+ == original bug report ==
+ 
  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron
  
  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

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

Title:
  Dell dock station WD22TB4 loses ether dev after reboot/power off

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-firmware source package in Lunar:
  In Progress
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  Dell dock station WD22TB4 loses ether dev after reboot/power off.

  [Fix]

  Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
  devices").

  [Test Case]

  1. Connect WD22TB4 with ethernet cable
  2. Boot into OS
  3. power off (or just reboot)
  4. power on and check if ethernet connection is still available.

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  The proposed fix has been included in Mantic and Noble, so nominate only for
  Lunar and Jammy (for oem-6.5).

  == original bug report ==

  [Steps to reproduce]
  1. Connect WD22TB4 with ethernet
  2. Boot into OS
  3. poweroff (or just reboot)
  4. poweron

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2048758] [NEW] nvidia-dkms-535-server-open FTBS with the latest 6.7 kernel in noble

[Andrea Righi]

Public bug reported:

[Impact]

/var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: error: 
implicit declaration of function ‘crypto_tfm_ctx_aligned’; did you mean 
‘crypto_tfm_ctx_align’? [-Werror=implicit-function-declaration]
   90 | char *src_ipad = crypto_tfm_ctx_aligned(_tfm->base);
  |  ^~
  |  crypto_tfm_ctx_align
/var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
/var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:91:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
   91 | char *dst_ipad = crypto_tfm_ctx_aligned(_tfm->base);
  |  ^~
cc1: some warnings being treated as errors

[Test case]

 $ sudo apt install nvidia-dkms-535-server-open

[Fix]

Upstream commit acd7799574e5 ("crypto: shash - remove
crypto_shash_ctx_aligned()") removed crypto_tfm_ctx_aligned() that is
used by the open variant of the driver.

Re-introduce this function (as a static inline) directly in the driver
(like the original one):

static inline void *crypto_tfm_ctx_aligned(struct crypto_tfm *tfm)
{
   return crypto_tfm_ctx_align(tfm, crypto_tfm_alg_alignmask(tfm) + 1);
}

This should fix the build error, since crypto_tfm_ctx_align() is still
available in the kernel ABI.

[Regression potential]

We may experience graphics regressions in systems that are using the
open variant of the 535-server nvidia driver, especially with any 6.7
kernel.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nvidia-dkms-535-server-open 535.129.03-0ubuntu1
ProcVersionSignature: User Name 6.7.0-5.5-generic 6.7.0-rc8
Uname: Linux 6.7.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20240101
CloudSubPlatform: config-disk (/dev/vdb)
Date: Tue Jan  9 08:54:19 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: nvidia-graphics-drivers-535-server
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-535-server (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-535-server (Ubuntu Noble)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cloud-image noble

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-dkms-535-server-open FTBS with the latest 6.7 kernel in noble

Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server source package in Noble:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: error: 
implicit declaration of function ‘crypto_tfm_ctx_aligned’; did you mean 
‘crypto_tfm_ctx_align’? [-Werror=implicit-function-declaration]
 90 | char *src_ipad = crypto_tfm_ctx_aligned(_tfm->base);
|  ^~
|  crypto_tfm_ctx_align
  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
  /var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:91:26: warning: 
initialization of ‘char *’ from ‘int’ makes pointer from integer without a cast 
[-Wint-conversion]
 91 | char *dst_ipad = crypto_tfm_ctx_aligned(_tfm->base);
|  ^~
  cc1: some warnings being treated as errors

  [Test case]

   $ sudo apt install nvidia-dkms-535-server-open

  [Fix]

  Upstream commit acd7799574e5 ("crypto: shash - remove
  crypto_shash_ctx_aligned()") removed crypto_tfm_ctx_aligned() that is
  used by the open variant of the driver.

  Re-introduce this function (as a static inline) directly in the driver
  (like the original one):

  static inline void *crypto_tfm_ctx_aligned(struct crypto_tfm *tfm)
  {
 return crypto_tfm_ctx_align(tfm, crypto_tfm_alg_alignmask(tfm) + 1);
  }

  This should fix the build error, since crypto_tfm_ctx_align() is still
  available in the kernel ABI.

  [Regression potential]

  We may experience graphics regressions in systems that are using the
  open variant of the 535-server nvidia driver, especially with any 6.7
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
 

[Kernel-packages] [Bug 2046534] Re: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration

[Chengen Du]

The verification of jammy (5.4.0-171.189) was conducted using a custom approach 
due to the absence of an InfiniBand environment for testing the patch.
The patch specifically altered the count of mm->mm_users within a function.
To ensure that this modification did not impact the original logic, a kernel 
module was developed.
The module replicated the content of ib_umem_odp_alloc_child but substituted 
InfiniBand-related functions with other unaffected custom functions for testing 
purposes.
===
#include 
#include 
#include 
#include 

MODULE_DESCRIPTION("Test");
MODULE_LICENSE("GPL");

int inner_test(void) {
return 0;
}

int test(void) {
int ret;
char *odp_data = kzalloc(8, GFP_KERNEL);
if (!odp_data)
return -ENOMEM;
if (!mmget_not_zero(current->mm)) {
ret = -EFAULT;
goto out_free;
}

ret = inner_test();
if (ret)
goto out_mmput;
mmput(current->mm);
return 0;

out_mmput:
mmput(current->mm);
out_free:
kfree(odp_data);
return ret;
}

static int test_init(void) { return test(); }

static void test_exit(void) {}

module_init(test_init);
module_exit(test_exit);
===

Executing this kernel module allows us to verify that the count of
mm_users aligns with expectations, validated through the use of the
atomic_read function.

** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-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/2046534

Title:
  Page fault in RDMA ODP triggers BUG_ON during MMU notifier
  registration

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  When a page fault is triggered in RDMA ODP, it registers an MMU notifier 
during the process.
  Unfortunately, an error arises due to a race condition where the mm is 
released while attempting to register a notifier.
  ==
  Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at 
mm/mmu_notifier.c:255!
  Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 
EFLAGS: 00010246
  Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: 
a0f913ba5800 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: 
c0b601c7 RDI: a0f913ba5850
  Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX:  RBX: 
c0b5a060 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: 
a1152ed3c400 RDI: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: 
a1163f4f50e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: 
 R12: a1152c923b80
  Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: 
a1163f7350e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: 
 R12: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: 
a1152c923bf8 R15: a114f8127800
  Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS:  () 
GS:a1163f4c() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: 
a1152ed3c478 R15: a1101cbfbc00
  Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS:  () 
GS:a1163f70() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 
001722472004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 
001f9f1fc004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace:
  Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.923112]  
mmu_notifier_get_locked+0x5f/0xe0
  Oct 14 23:38:32 bnode001 kernel: