[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

[Hui Wang]

About the enable proposed ppa:
It was the actual official proposed pocket for mantic and jammy. sth like this: 
deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-proposed main 
restricted

About the two additional steps:
I did run them in mantic and jammy in my verification (#3 and #4).

Thx.

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

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

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

  [Impact]

  We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
  and booting up, the bluetooth couldn't work at all. Checking the dmesg,
  the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
  but there is no this firmware in the linux-firmware of Jammy, and I
  also checked the Mantic and Noble, Mandic doesn't have this firmware too,
  Noble already has the firmware since the upstream linux-firmware integrated
  the intel/ibt-0180-4150.sfi last year.

  
  [Fix]

  Backport 4 commits from upstream linux-firmware, these 4 commits are all
  on intel/ibt-0180-4150.sfi|ddc

  
  [Test Case]

  Put the firmware into the /lib/firmware/intel/, reboot the machine,
  check dmesg, the bluetooth driver loads the firmware successfully,

  run hciconfig, the hci0 shows up.

  run checkbox testcase, it could pass.
  [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

  
  [Where problems could occur]

  Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
  is very low, we tested the firmware on different lenovo machines with the BT 
adapter
  AX201, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics

[Chris Chiu]

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

** Tags added: oem-priority originate-from-2048051 somerville

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

  
=

  SRU Jusitification for linux-firmware

  [Impact]
  The system will randomly hang due to page fault while suspending.

  [Fix]
  Add release FW binary from AMD to linux-firmware
  dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
  dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Test with latest linux kernel and linux-firmware
  3. Running fwts s3 stress test to check if system hangs

  [Where problems could occur]
  The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063417/+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 2063529] [NEW] Add support for Quectel RM520N-GL modem

[Atlas Yu]

Public bug reported:

[Impact]

* Add support for Quectel RM520N-GL modem, so the device could be
properly probed.

[Test Plan]

* Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
use` is mht-pci-generic.

[Where problems could occur]

* These commits only introduces a PID, it won't impact devices which are
supported originally.

[Other Info]

* Upstream commits:
  
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
  
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
* Lenovo with this device will be enabled by linux-oem-6.5.

** Affects: hwe-next
 Importance: Undecided
 Assignee: Atlas Yu (pseudoc)
 Status: In Progress

** Affects: oem-priority
 Importance: Critical
 Assignee: Atlas Yu (pseudoc)
 Status: Confirmed

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

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


** Tags: oem-priority originate-from-2045276 sutton

** Also affects: hwe-next
   Importance: Undecided
   Status: New

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

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

Title:
  Add support for Quectel RM520N-GL modem

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New

Bug description:
  [Impact]

  * Add support for Quectel RM520N-GL modem, so the device could be
  properly probed.

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * These commits only introduces a PID, it won't impact devices which
  are supported originally.

  [Other Info]

  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2063399] Re: Add support for Quectel EM160R-GL modem

[Atlas Yu]

** Changed in: hwe-next
   Status: New => Fix Committed

** Changed in: hwe-next
   Status: Fix Committed => In Progress

** Tags added: oem-priority originate-from-2045276 sutton

** Changed in: oem-priority
 Assignee: (unassigned) => Atlas Yu (pseudoc)

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Add support for Quectel EM160R-GL modem

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  In Progress

Bug description:
  [Impact]

  * Add support for Quectel EM160R-GL modem, so the device could be
  properly probed.

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * The commit only introduces a PID, it won't impact devices which are
  supported originally.

  [Other Info]

  * Upstream commit: 
https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063399/+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 2063503] [NEW] NVidia drivers won't install completely

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

ll versions of the nvidia driver fail to install no matter what.
Including the one downloaded from Nvidia. It doesn't matter the version.

:~$ sudo apt install nvidia-driver-550
[sudo] password for jim: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  nvidia-firmware-545-545.29.06
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
  libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
  libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
  libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
  libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
  nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550
  nvidia-utils-550 xserver-xorg-video-nvidia-550
The following packages will be REMOVED:
  libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545
  libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386
  libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545
  libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545
  libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545
  nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545
  nvidia-utils-545 xserver-xorg-video-nvidia-545
The following NEW packages will be installed:
  libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
  libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
  libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
  libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
  libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
  nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550
  nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550
0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded.
2 not fully installed or removed.
Need to get 360 MB of archives.
After this operation, 14.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 
amd64 550.67-0ubuntu3 [35.8 kB]
Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB]
Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB]
Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB]
Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB]
Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB]
Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB]
Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB]
Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB]
Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB]
Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB]
Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB]
Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB]
Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB]
Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB]
Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB]
Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB]
Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-common-550 amd64 550.67-0ubuntu3 [120 kB]
Get:19 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-utils-550 amd64 550.67-0ubuntu3 [521 kB]
Get:20 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
xserver-xorg-video-nvidia-550 amd64 550.67-0ubuntu3 [1,616 kB]
Get:21 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-driver-550 amd64 550.67-0ubuntu3 [486 kB]
Fetched 360 MB in 30s (11.8 MB/s)  
(Reading database ... 339762 files and directories currently installed.)
Removing nvidia-driver-545 (545.29.06-0ubuntu0~gpu24.04.1) ...
Removing 

[Kernel-packages] [Bug 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop

[Sebastian Podjasek]

That previous comment was false-positive, I was probably still booted to
6.5.0-26 and on 6.5.0-28 this bug is still present. After resume from
suspend in 6.5.0-28 keyboard is not-responsive.

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

Title:
  Keyboard not working after resume from suspend on Dell XPS 13 laptop

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes 
back to life after suspend.
  When booted with 6.5.0-26-generic everything is fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2063512] [NEW] on reboot with linux-image-6.5.0-34 system hangs at loading initial ramdisk

[James Hill]

Public bug reported:

loading initial ramdisk hangs only with linux-image-6.5.0-34

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-550 550.67-0ubuntu1.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 16:36:07 2024
InstallationDate: Installed on 2021-01-20 (1191 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: nvidia-graphics-drivers-550
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-550 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  on reboot with linux-image-6.5.0-34 system hangs at loading initial
  ramdisk

Status in nvidia-graphics-drivers-550 package in Ubuntu:
  New

Bug description:
  loading initial ramdisk hangs only with linux-image-6.5.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-550 550.67-0ubuntu1.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 16:36:07 2024
  InstallationDate: Installed on 2021-01-20 (1191 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nvidia-graphics-drivers-550
  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-550/+bug/2063512/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Aaron Honeycutt]

For the record 6.8.0-31-generic also does not boot on the hardware.

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

@Roxana,

Checkout tag Ubuntu-6.5.0-34.34 and revert two patches below, it can
boot up without problem.

thermal: core: Store trip pointer in struct thermal_instance
thermal: trip: Drop lockdep assertion from thermal_zone_trip_id()

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2063529] Re: Add support for Quectel RM520N-GL modem

[Atlas Yu]

** Description changed:

  [Impact]
  
  * Add support for Quectel RM520N-GL modem, so the device could be
  properly probed.
  
  [Test Plan]
  
  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.
  
  [Where problems could occur]
  
- * The commit only introduces a PID, it won't impact devices which are
+ * These commits only introduces a PID, it won't impact devices which are
  supported originally.
  
  [Other Info]
  
- * Upstream commits: 
-   
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
-   
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
+ * Upstream commits:
+   
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
+   
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

** Tags added: oem-priority originate-from-2045276 sutton

** Changed in: oem-priority
 Assignee: (unassigned) => Atlas Yu (pseudoc)

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: hwe-next
 Assignee: (unassigned) => Atlas Yu (pseudoc)

** Changed in: hwe-next
   Status: New => In Progress

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

Title:
  Add support for Quectel RM520N-GL modem

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New

Bug description:
  [Impact]

  * Add support for Quectel RM520N-GL modem, so the device could be
  properly probed.

  [Test Plan]

  * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in
  use` is mht-pci-generic.

  [Where problems could occur]

  * These commits only introduces a PID, it won't impact devices which
  are supported originally.

  [Other Info]

  * Upstream commits:
    
https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e
    
https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081
  * Lenovo with this device will be enabled by linux-oem-6.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2063497] Re: MIPI camera on Lenovo Carbon X1 will not work

[Martin D. Weinberg]

I moved the driver file up a directory from /lib/firmware/intel/ipu to
/lib/firmware/intel and now the firmware appears to be loaded.  But
something else is still wrong here:

[   19.220279] intel-ipu6 :00:05.0: Device 0xa75d (rev: 0x0)
[   19.220291] intel-ipu6 :00:05.0: physical base address 0x603c00
[   19.220292] intel-ipu6 :00:05.0: mapped as: 0x9d0decc9
[   19.220340] intel-ipu6 :00:05.0: IPU in secure mode
[   19.220341] intel-ipu6 :00:05.0: IPU secure touch = 0x0
[   19.220342] intel-ipu6 :00:05.0: IPU camera mask = 0xff
[   19.222151] intel-ipu6 :00:05.0: IPC reset done
[   19.222152] intel-ipu6 :00:05.0: cpd file name: intel/ipu6ep_fw.bin
[   19.223266] intel-ipu6 :00:05.0: FW version: 20230925
[   19.226903] int3472-discrete INT3472:05: cannot find GPIO chip INTC1096:00, 
deferring

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

Title:
  MIPI  camera on Lenovo Carbon X1 will not work

Status in linux package in Ubuntu:
  New

Bug description:
  I followed the suggestions here for handling the Intel MIPI camera
  replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo

  Perhaps I should have installed 22.04?  Anyway, this is a new laptop
  so I went with the new release.

  I tried both the generic and oem kernel.  Same.  The pertinent message
  seems to be:

  [   18.420012] intel-ipu6 :00:05.0: Direct firmware load for 
intel/ipu6ep_fw.bin failed with error -2
  [   18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed
  [   18.420023] intel-ipu6: probe of :00:05.0 failed with error -2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+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 2063308] Re: lenovo p1g5 suspend issues with docking stations

[AaronMa]

The ethernet on Dock should be this one;
usb-:57:00.0-1.4, ASIX AX88179 USB 3.0 Gigabit Ethernet

My TBT 4 Dock is I225, which is enabled by 12900H vPro CPU.

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

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+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 2063503] Re: NVidia drivers won't install completely

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550
(Ubuntu)

** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  NVidia drivers won't install completely

Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  New

Bug description:
  ll versions of the nvidia driver fail to install no matter what.
  Including the one downloaded from Nvidia. It doesn't matter the
  version.

  :~$ sudo apt install nvidia-driver-550
  [sudo] password for jim: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following package was automatically installed and is no longer required:
nvidia-firmware-545-545.29.06
  Use 'sudo apt autoremove' to remove it.
  The following additional packages will be installed:
libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550
nvidia-utils-550 xserver-xorg-video-nvidia-550
  The following packages will be REMOVED:
libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545
libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386
libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545
libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545
libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545
nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545
nvidia-utils-545 xserver-xorg-video-nvidia-545
  The following NEW packages will be installed:
libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550
libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386
libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550
libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550
libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550
nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550
nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550
  0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded.
  2 not fully installed or removed.
  Need to get 360 MB of archives.
  After this operation, 14.7 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 
amd64 550.67-0ubuntu3 [35.8 kB]
  Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB]
  Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB]
  Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB]
  Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB]
  Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB]
  Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB]
  Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB]
  Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB]
  Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB]
  Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB]
  Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB]
  Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB]
  Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 
libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB]
  Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB]
  Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB]
  Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB]
  Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 
nvidia-kernel-common-550 

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

[Atlas Yu]

I tested linux-image-6.5.0-1021-oem on ThinkPad L15 Gen4 with 10 boots(20 
suspends/resumes for each boot).
Cannot reproduce this bug anyway, considered fixed.

---
To: Aussems J.a.c. (ramcsir)
To: Ganton (ganton)

The SKU we hold here, rarely reproduces this issue on the previous
kernels, we would be much appreciated if you can help to verify the fix
as well according to #20 and #22.


** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5

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

Title:
  The keyboard does not work after latest kernel update

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

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card

[Jess Ferments]

I just went ahead last night and updated to Ubuntu 24.04 with `do-
release-upgrade -d` and it seems that this most of the iwlwifi errors
are no longer popping up with the 6.8 kernel. Specifically, I am no
longer getting the "Microcode SW error detected." and "api flags index 2
larger than supported by driver"

The only error I'm still getting for iwlwifi with 6.8 kernel is "WRT:
Invalid buffer destination"

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

Title:
  iwlwifi error popping up every few minutes in Kubuntu 23.10 using
  Intel AX210 card

Status in linux package in Ubuntu:
  New

Bug description:
  I just installed Kubuntu 23.10 (using latest default kernel) on a new
  desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth
  card. Here is output from lspci -v:

  e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15
Memory at ba30 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  

  Wifi error popping up every few minutes in Kubuntu
  I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an 
AX210NGW DTK M.2 wifi card:

  Code:

  e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 
160MHz (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15
Memory at ba30 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  The internet seems to be somewhat working, but at least once a minute
  I have two "Network Management" error notifications that pop up in KDE
  that say "Connection Wired Connection 3 deactivated" and "Wired
  Interface e2x52e8ae7d39d1: IP configuration was unavailable".

  I checked the logs in /var/log/dmesg and saw that there were a ton of
  iwlwifi error messages in there that look like this:

  [   44.926474] kernel: Intel(R) Wireless WiFi driver for Linux
  [   44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002)
  [   44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 
0x400410 wfpm id 0x8000
  [   44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, 
rfid=0x10d000
  [   44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than 
supported by driver
  [   44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.2.41
  [   44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 
83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm
  [   44.955070] kernel: Bluetooth: Core ver 2.22
  [   44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family
  [   44.955090] kernel: Bluetooth: HCI device and connection manager 
initialized
  [   44.955095] kernel: Bluetooth: HCI socket layer initialized
  [   44.955097] kernel: Bluetooth: L2CAP socket layer initialized
  [   44.955101] kernel: Bluetooth: SCO socket layer initialized
  [   45.275827] kernel: Bluetooth: hci0: Device revision is 0
  [   45.275833] kernel: Bluetooth: hci0: Secure boot is enabled
  [   45.275836] kernel: Bluetooth: hci0: OTP lock is enabled
  [   45.275838] kernel: Bluetooth: hci0: API lock is enabled
  [   45.275840] kernel: Bluetooth: hci0: Debug lock is disabled
  [   45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 
buildtype 1 build 38
  [   45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  [   45.278400] kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-0041-0041.sfi
  [   45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800
  [   45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23
  [   47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
  [   47.405936] kernel: iwlwifi :e4:00.0: 

[Kernel-packages] [Bug 2063532] [NEW] missing uic

[Michael Bridak]

Public bug reported:

Package python3-pyqt6 does not provide uic.

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

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

Title:
  missing uic

Status in linux package in Ubuntu:
  New

Bug description:
  Package python3-pyqt6 does not provide uic.

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


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

[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04

[Fred Vkigg]

Problem lies in the Intel kernel driver 'snd_soc_avs' which is becoming
active but fail to support the HDA sound hardware correctly.

Workaround is to blacklist 'snd_soc_avs'.

Problem is well know and seems to be already in Kernel 6.7. See for
example https://bbs.archlinux.org/viewtopic.php?id=294655

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

Title:
  No sound after upgrade to 24.04

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  Confirmed

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

  Work with:
  1) Bluetooth
  2) Jack 3.5

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

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


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

[Kernel-packages] [Bug 2063376] Re: linux-source-6.5.0 will install kernel 6.5.13

[Juerg Haefliger]

That's correct albeit confusing behavior. The source package name is
always linux-source-x.y.0 regardless of the actual (upstream) kernel
version that it provides. If you really need upstream version 6.5.0 you
need to install a specific/old version (6.5.0-5.5 in this case) of
linux-source-6.5.0. But those early versions are pretty much development
versions and prone to have issues...

If you care about upstream kernel versions you should use the git repo
[1] rather than the linux-source-x.y.0 packages.

[1] https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic


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

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

Title:
  linux-source-6.5.0 will install kernel 6.5.13

Status in linux-hwe-6.5 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  As the summary suggests, when I install linux-source-6.5.0 it will
  actually install the 6.5.13 kernel sources. Querying

apt show linux-source-6.5.0

  reports:

[...]
Description: Linux kernel source for version 6.5.0 with Ubuntu patches
 This package provides the source code for the Linux kernel version
 6.5.0.
[...]

  So providing 6.5.13 seems like a bug to me. But it's my first time
  trying to build a kernel module for Debian myself, so I'm quite unsure
  what's happening here. Any pointers welcome.

  Here's what I did:

sudo su
apt install linux-source-6.5.0
cd /usr/src
tar xjf linux-source-6.5.0.tar.bz2
head linux-source-6.5.0/Makefile

  which shows:

# SPDX-License-Identifier: GPL-2.0
VERSION = 6
PATCHLEVEL = 5
SUBLEVEL = 13
EXTRAVERSION =
NAME = Hurr durr I'ma ninja sloth

# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
# More info can be located in ./README

  I don't know how or why this happens, but I found the following in
  dmesg

$ dmesg | grep 6.5.13
[0.00] Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
14:39:20 UTC 2 (Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13)

  If I'm decyphering this correctly my running 6.5.0 kernel was build on
  a machine running 6.5.13. Is it possible that this machine by accident
  uploaded it's own kernel source tree rather than the built kernel's?

$ lsb_release -rd
Description:Linux Mint 21.3
Release:21.3

$ apt-cache policy linux-source-6.5.0
linux-source-6.5.0:
  Installed: 6.5.0-28.29~22.04.1
  Candidate: 6.5.0-28.29~22.04.1
  Version table:
 *** 6.5.0-28.29~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
100 /var/lib/dpkg/status
 6.5.0-27.28~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-26.26~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-25.25~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-21.21~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main i386 
Packages
 6.5.0-18.18~22.04.1 500
500 http://mirror.ipb.de/ubuntu jammy-updates/main amd64 Packages
500 http://mirror.ipb.de/ubuntu jammy-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main 

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

[Ubuntu SRU Bot]

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

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (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/jammy/update_excuses.html#linux-restricted-modules

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

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04

[shangsong]

root@ll:~# modprobe -v ib_ipoib
insmod 
/lib/modules/6.8.0-31-generic/kernel/drivers/infiniband/core/ib_cm.ko.zst 
insmod 
/lib/modules/6.8.0-31-generic/kernel/drivers/infiniband/ulp/ipoib/ib_ipoib.ko.zst
 
root@ll:~# 

After probe the module manually, the port can be shown with the command 'ip a'
7: ibs2f0:  mtu 4092 qdisc noop state DOWN group default 
qlen 256
link/infiniband 00:00:10:69:fe:80:00:00:00:00:00:00:b8:3f:d2:03:00:3c:55:1c 
brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
altname ibp216s0f0
8: ibs2f1:  mtu 4092 qdisc noop state DOWN group default 
qlen 256
link/infiniband 00:00:11:69:fe:80:00:00:00:00:00:00:b8:3f:d2:03:00:3c:55:1d 
brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
altname ibp216s0f1


** Attachment added: "sosreport and lsmod log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060437/+attachment/5770182/+files/ipoib_log.zip

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

Title:
  The module ib_ipoib does not load automatically on ubuntu server 24.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Fresh install Ubuntu server 24.04 on a server with mellanox card and 
infiniband mode
  2. As the module "ib_ipoib" does not load automatically, it fail to display 
the port via the command "ip a". The port can display after load manually.

  Please help to fix it, thanks.

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


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

[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04

[Fred Vkigg]

alsa-info from a Dell Precision 5520

** Attachment added: "alsa-info.txt.1IMNEYShPL"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+attachment/5770168/+files/alsa-info.txt.1IMNEYShPL

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

Title:
  No sound after upgrade to 24.04

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  Confirmed

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

  Work with:
  1) Bluetooth
  2) Jack 3.5

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

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


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

[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No sound after upgrade to 24.04

Status in linux package in Ubuntu:
  Incomplete
Status in pipewire package in Ubuntu:
  Confirmed

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

  Work with:
  1) Bluetooth
  2) Jack 3.5

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

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


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

[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Ivan Hu]

Test latest master-next of mantic with below two patches,

thermal: trip: Drop redundant trips check from for_each_thermal_trip()
thermal: core: Rework and rename __for_each_thermal_trip()

still failed.

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2063417] [NEW] Fix system hang while entering suspend with AMD Navi3x graphics

[Chris Chiu]

Public bug reported:

SRU Jusitification for Kernel

[Impact]
The system with AMD W7500/W7600/W7700 graphics will randomly hang when entering 
suspend. The page fault would keep happening and the system can't handle other 
tasks.
BUG: unable to handle page fault for address: 0a980148 

[Fix]
Backport the fix from upstream 
drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · GitHub
https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

[Test Case]
1. Install AMD W7500/W7600/W7700 graphics
2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
3. Running fwts s3 stress test to check if system hangs

[Where problems could occur]
Improve the error handling when suspend and add the fallback mechanism in MES 
engine. Only observed on particular AMD models. Need to test w/ more 
combinations

=

SRU Jusitification for linux-firmware

[Impact]
The system will randomly hang due to page fault while suspending.

[Fix]
Add release FW binary from AMD to linux-firmware
dcn_3_2_0_dmcub.bin for Navi31 and 32: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47
 [git.kernel.org]
dcn_3_2_1_dmcub.bin for Navi33: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a
 [git.kernel.org]

[Test Case]
1. Install AMD W7500/W7600/W7700 graphics
2. Test with latest linux kernel and linux-firmware
3. Running fwts s3 stress test to check if system hangs

[Where problems could occur]
The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The 
impact are restricted to particular series.

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

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

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: linux-oem-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-firmware (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  Fix system hang while entering suspend with AMD Navi3x graphics

Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.5 source package in Noble:
  New

Bug description:
  SRU Jusitification for Kernel

  [Impact]
  The system with AMD W7500/W7600/W7700 graphics will randomly hang when 
entering suspend. The page fault would keep happening and the system can't 
handle other tasks.
  BUG: unable to handle page fault for address: 0a980148 

  [Fix]
  Backport the fix from upstream 
  drm/amdgpu: skip to program GFXDEC registers for suspend abort · 
torvalds/linux@0326de4 · GitHub
  drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · 
GitHub
  https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org]

  [Test Case]
  1. Install AMD W7500/W7600/W7700 graphics
  2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and 
dcn_3_2_1_dmcub.bin for Navi33. 
  3. Running fwts s3 stress test to check if system hangs

  [Where 

[Kernel-packages] [Bug 2063150] Re: No sound after upgrade to 24.04

[Sebastien Bacher]

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

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

Title:
  No sound after upgrade to 24.04

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

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

  Work with:
  1) Bluetooth
  2) Jack 3.5

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

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


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

[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

[You-Sheng Yang]

verified linux-firmware/mantic-proposed version
20230919.git3672ccab-0ubuntu2.10, linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.30.

** Tags added: verification-done-jammy verification-done-mantic

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

Title:
  add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Devices hang up at its desktop (Intel based platform + AMD Navi3.x
  dGPU) during warm boot stress test.

  [Fix]

  AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The
  affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the
  first revision since Jammy is ever released. However, the related
  commits from the upgrade path have also included blob updates to all
  kinds of different, unrelated hardware models.

  This pull request bumps only the affected binary to the target commit
  per online discussion with AMD.

  [Test Case]

  Perform checkbox warmboot stress test:

  $ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  While DCN blob maybe shared with several hardware models, with
  confirmation from IHV, there should be little risk to upgrade it.

  [Other Info]

  Affects both Jammy and Mantic.

  == original bug report ==

  Dell reported sporadically hang up at its desktop (Intel based
  platform + AMD Navi3.x dGPU) during warm boot stress test.

  After updating DMCUB firmware version to 0x07002600, they observed a
  significant improvement in passing rate. And Dell wants to add the
  updated DMCUB firmware (ver 0x7002600) to its OEM image.

  DMCUB firmware (ver 0x7002600) is at
  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  
firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker

[Ubuntu Kernel Bot]

*** This bug is a duplicate of bug 2060233 ***
https://bugs.launchpad.net/bugs/2060233

** Changed in: kernel-sru-workflow
   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.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2058357

Title:
  noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Fix Released
Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow abi-testing series:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Triaged
Status in Kernel SRU Workflow boot-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrg series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrs series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in linux-oem-6.8 package in Ubuntu:
  New
Status in linux-oem-6.8 source package in Noble:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  built:
from: 5938de740722141b
route-entry: 2
  delta:
promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate]
  flag:
boot-testing-requested: true
proposed-testing-requested: true
  kernel-stable-master-bug: 2058221
  packages:
generate: linux-generate-oem-6.8
lrg: linux-restricted-generate-oem-6.8
lrm: linux-restricted-modules-oem-6.8
lrs: linux-restricted-signatures-oem-6.8
main: linux-oem-6.8
meta: linux-meta-oem-6.8
signed: linux-signed-oem-6.8
  phase: Promote to Proposed
  phase-changed: Monday, 25. March 2024 15:37 UTC
  reason:
automated-testing: Ongoing -s testing in progress
promote-to-proposed: Stalled -- copy FAILED
regression-testing: Stalled -s testing FAILED
  synthetic:
:promote-to-as-proposed: Fix Released
  variant: debs
  versions:
lrm: 6.8.0-1001.1
main: 6.8.0-1001.1
meta: 6.8.0-1001.1
signed: 6.8.0-1001.1
  ~~:
clamps:
  new-review: 5938de740722141b
  promote-to-proposed: 5938de740722141b
  self: 6.8.0-1001.1
  sru-review: 5938de740722141b
tracker:
  last-message: '2024-03-25 17:56:19.962040+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2058357/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024

[Ubuntu Kernel Bot]

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


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


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


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

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

Title:
  apply NVIDIA patches April 6-16, 2024

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

Bug description:
  Apply NVIDIA patches April 6-16, 2024:

  
  NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016

  NVIDIA: SAUCE: enable handling of macronix block protection
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006

  PCI: dwc: Restore MSI Receiver mask during resume
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2060337] Re: apply NVIDIA patches Mar 22 - April 5, 2024

[Ubuntu Kernel Bot]

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


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


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


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

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

Title:
  apply NVIDIA patches Mar 22 - April 5, 2024

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

Bug description:
  NVIDIA patches Mar 22 - April 5, 2024.

  NVIDIA tracking details

  soc/tegra: fuse: Remove security_mode fuse from keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228

  soc/tegra: fuse: Update Tegra234 nvmem keepout list
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227

  arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255

  arm64: defconfig: Enable DMATEST
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125

  PCI: tegra194: Fix probe path for Endpoint mode
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622

  arm64: configs: enable hidraw
  https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2063449] [NEW] WARNING: CPU: 5 PID: 464 at drivers/net/wireless/realtek/rtw88/pci.c:1277 rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]

[El jinete sin cabeza]

Public bug reported:

[  102.836810] [ cut here ]
[  102.836817] failed to read DBI register, addr=0x0719
[  102.836916] WARNING: CPU: 5 PID: 464 at 
drivers/net/wireless/realtek/rtw88/pci.c:1277 
rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
[  102.836963] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer qrtr cmac 
algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi snd_sof_pci_intel_skl 
snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_avs 
snd_soc_hda_codec snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc 
snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core 
snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus 
snd_pcm_dmaengine snd_hda_intel binfmt_misc snd_intel_dspcfg snd_intel_sdw_acpi 
snd_hda_codec intel_uncore_frequency intel_uncore_frequency_common snd_hda_core 
rtw88_8821ce snd_hwdep rtw88_8821c rtw88_pci snd_pcm intel_tcc_cooling 
x86_pkg_temp_thermal rtw88_core intel_powerclamp snd_seq_midi crct10dif_pclmul 
polyval_clmulni snd_seq_midi_event polyval_generic ghash_clmulni_intel 
sha256_ssse3 snd_rawmidi uvcvideo sha1_
 ssse3 mac80211 aesni_intel
[  102.837296]  videobuf2_vmalloc crypto_simd uvc cryptd snd_seq 
videobuf2_memops btusb processor_thermal_device_pci_legacy videobuf2_v4l2 btrtl 
snd_seq_device processor_thermal_device rapl nls_iso8859_1 mei_hdcp mei_pxp 
intel_rapl_msr snd_timer processor_thermal_wt_hint videodev cfg80211 btintel 
hid_sensor_magn_3d processor_thermal_rfim hid_sensor_accel_3d 
hid_sensor_custom_intel_hinge snd hid_sensor_gyro_3d i2c_i801 
processor_thermal_rapl btbcm hp_wmi videobuf2_common hid_sensor_rotation 
hid_sensor_incl_3d btmtk intel_cstate hid_sensor_trigger 
industrialio_triggered_buffer platform_profile i915 wmi_bmof 
intel_wmi_thunderbolt soundcore i2c_smbus libarc4 mc bluetooth kfifo_buf mei_me 
intel_rapl_common drm_buddy mei hid_sensor_iio_common ttm ecdh_generic 
processor_thermal_wt_req ecc processor_thermal_power_floor drm_display_helper 
processor_thermal_mbox industrialio cec intel_pch_thermal rc_core 
intel_soc_dts_iosf i2c_algo_bit intel_xhci_usb_role_switch int3403_thermal 
int340x_thermal
 _zone soc_button_array intel_vbtn
[  102.837570]  sparse_keymap intel_pmc_core intel_vsec int3400_thermal 
pmt_telemetry hp_accel pmt_class acpi_thermal_rel wireless_hotkey acpi_pad 
lis3lv02d input_leds joydev serio_raw mac_hid coretemp msr parport_pc ppdev lp 
parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 ax88179_178a 
usbnet usbhid mii hid_sensor_custom hid_sensor_hub intel_ishtp_hid 
hid_multitouch hid_generic spi_pxa2xx_platform dw_dmac dw_dmac_core 8250_dw 
sdhci_pci nvme intel_lpss_pci video intel_lpss i2c_hid_acpi crc32_pclmul cqhci 
intel_ish_ipc nvme_core i2c_hid psmouse ahci xhci_pci nvme_auth libahci sdhci 
intel_ishtp hid xhci_pci_renesas idma64 wmi pinctrl_sunrisepoint
[  102.837807] CPU: 5 PID: 464 Comm: kworker/u16:10 Not tainted 
6.8.0-31-generic #31-Ubuntu
[  102.837822] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, 
BIOS F.41 11/16/2022
[  102.837831] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
[  102.838215] RIP: 0010:rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
[  102.838253] Code: 1f 00 41 88 45 00 31 c0 5b 41 5c 41 5d 5d 31 d2 31 f6 31 
ff c3 cc cc cc cc be 19 07 00 00 48 c7 c7 60 f4 c8 c0 e8 4c 1c c7 e5 <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d 31 d2 31 f6 31 ff c3 cc cc
[  102.838266] RSP: :b08005e2fc60 EFLAGS: 00010246
[  102.838279] RAX:  RBX:  RCX: 
[  102.838288] RDX:  RSI:  RDI: 
[  102.838295] RBP: b08005e2fc78 R08:  R09: 
[  102.838304] R10:  R11:  R12: 8f5c04fd1fc0
[  102.838313] R13: b08005e2fc8f R14: 8f5c04fd71f8 R15: 8f5c021a7e00
[  102.838322] FS:  () GS:8f5f61e8() 
knlGS:
[  102.838333] CS:  0010 DS:  ES:  CR0: 80050033
[  102.838341] CR2: 78baf9e03020 CR3: 1423c003 CR4: 003706f0
[  102.838350] Call Trace:
[  102.838358]  
[  102.838396]  ? show_regs+0x6d/0x80
[  102.838416]  ? __warn+0x89/0x160
[  102.838435]  ? rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
[  102.838468]  ? report_bug+0x17e/0x1b0
[  102.838488]  ? handle_bug+0x51/0xa0
[  102.838500]  ? exc_invalid_op+0x18/0x80
[  102.838512]  ? asm_exc_invalid_op+0x1b/0x20
[  102.838533]  ? rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
[  102.838565]  rtw_pci_link_ps.part.0+0xa8/0x100 [rtw88_pci]
[  102.838595]  rtw_pci_link_ps+0x1b/0x30 [rtw88_pci]
[  102.838623]  rtw_enter_ips+0x47/0x60 [rtw88_core]
[  102.838733]  rtw_ops_config+0xb2/0xe0 [rtw88_core]
[  102.838836]  ieee80211_hw_config+0x8e/0x130 [mac80211]
[  

[Kernel-packages] [Bug 2063435] [NEW] Radeon stacktrace during boot

[Piotr Parczewski]

Public bug reported:

Noble beta:

[Thu Apr 25 11:13:28 2024] [drm] radeon kernel modesetting enabled.
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: vgaarb: deactivate vga console
[Thu Apr 25 11:13:28 2024] [drm] initializing kernel modesetting (PALM 
0x1002:0x9802 0x1849:0x9802 0x00).
[Thu Apr 25 11:13:28 2024] ATOM BIOS: AMD
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: VRAM: 32M 0x - 
0x01FF (32M used)
[Thu Apr 25 11:13:28 2024] radeon :00:01.0: GTT: 1024M 0x0200 - 
0x41FF
[Thu Apr 25 11:13:28 2024] [drm] Detected VRAM RAM=32M, BAR=32M
[Thu Apr 25 11:13:28 2024] [drm] RAM width 32bits DDR
[Thu Apr 25 11:13:28 2024] [drm] radeon: 32M of VRAM memory ready
[Thu Apr 25 11:13:28 2024] [drm] radeon: 1024M of GTT memory ready.
[Thu Apr 25 11:13:28 2024] [drm] Loading PALM Microcode
[Thu Apr 25 11:13:29 2024] [drm] Internal thermal controller without fan control
[Thu Apr 25 11:13:29 2024] [ cut here ]
[Thu Apr 25 11:13:29 2024] UBSAN: array-index-out-of-bounds in 
/build/linux-OjsR9e/linux-6.8.0/drivers/gpu/drm/radeon/radeon_atombios.c:2718:34
[Thu Apr 25 11:13:29 2024] index 16 is out of range for type 'UCHAR [1]'
[Thu Apr 25 11:13:29 2024] CPU: 1 PID: 366 Comm: (udev-worker) Not tainted 
6.8.0-11-generic #11-Ubuntu
[Thu Apr 25 11:13:29 2024] Hardware name: To Be Filled By O.E.M. To Be Filled 
By O.E.M./E350M1, BIOS P2.10 03/06/2014
[Thu Apr 25 11:13:29 2024] Call Trace:
[Thu Apr 25 11:13:29 2024]  
[Thu Apr 25 11:13:29 2024]  dump_stack_lvl+0x48/0x70
[Thu Apr 25 11:13:29 2024]  dump_stack+0x10/0x20
[Thu Apr 25 11:13:29 2024]  __ubsan_handle_out_of_bounds+0xc6/0x110
[Thu Apr 25 11:13:29 2024]  radeon_atombios_parse_power_table_6+0x3ba/0x3e0 
[radeon]
[Thu Apr 25 11:13:29 2024]  radeon_atombios_get_power_modes+0x247/0x270 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_pm_init+0xd0/0x100 [radeon]
[Thu Apr 25 11:13:29 2024]  evergreen_init+0x158/0x400 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_device_init+0x540/0xa90 [radeon]
[Thu Apr 25 11:13:29 2024]  radeon_driver_load_kms+0xcc/0x2f0 [radeon]
[Thu Apr 25 11:13:29 2024]  drm_dev_register+0x12b/0x2a0
[Thu Apr 25 11:13:29 2024]  radeon_pci_probe+0xec/0x180 [radeon]
[Thu Apr 25 11:13:29 2024]  local_pci_probe+0x47/0xb0
[Thu Apr 25 11:13:29 2024]  pci_call_probe+0x55/0x1a0
[Thu Apr 25 11:13:29 2024]  pci_device_probe+0x84/0x120
[Thu Apr 25 11:13:29 2024]  really_probe+0x1c7/0x410
[Thu Apr 25 11:13:29 2024]  __driver_probe_device+0x8c/0x180
[Thu Apr 25 11:13:29 2024]  driver_probe_device+0x24/0xd0
[Thu Apr 25 11:13:29 2024]  __driver_attach+0x10b/0x210
[Thu Apr 25 11:13:29 2024]  ? __pfx___driver_attach+0x10/0x10
[Thu Apr 25 11:13:29 2024]  bus_for_each_dev+0x8d/0xf0
[Thu Apr 25 11:13:29 2024]  driver_attach+0x1e/0x30
[Thu Apr 25 11:13:29 2024]  bus_add_driver+0x156/0x260
[Thu Apr 25 11:13:29 2024]  driver_register+0x5e/0x130
[Thu Apr 25 11:13:29 2024]  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
[Thu Apr 25 11:13:29 2024]  __pci_register_driver+0x5e/0x70
[Thu Apr 25 11:13:29 2024]  radeon_module_init+0x4c/0xff0 [radeon]
[Thu Apr 25 11:13:29 2024]  do_one_initcall+0x5e/0x340
[Thu Apr 25 11:13:29 2024]  do_init_module+0xc0/0x2c0
[Thu Apr 25 11:13:29 2024]  load_module+0xba1/0xcf0
[Thu Apr 25 11:13:29 2024]  init_module_from_file+0x96/0x100
[Thu Apr 25 11:13:29 2024]  ? init_module_from_file+0x96/0x100
[Thu Apr 25 11:13:29 2024]  idempotent_init_module+0x11c/0x2b0
[Thu Apr 25 11:13:29 2024]  __x64_sys_finit_module+0x64/0xd0
[Thu Apr 25 11:13:29 2024]  do_syscall_64+0x77/0x140
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? switch_fpu_return+0x55/0xf0
[Thu Apr 25 11:13:29 2024]  ? syscall_exit_to_user_mode+0x97/0x1e0
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? switch_fpu_return+0x55/0xf0
[Thu Apr 25 11:13:29 2024]  ? syscall_exit_to_user_mode+0x97/0x1e0
[Thu Apr 25 11:13:29 2024]  ? do_syscall_64+0x83/0x140
[Thu Apr 25 11:13:29 2024]  ? sysvec_apic_timer_interrupt+0x4b/0xd0
[Thu Apr 25 11:13:29 2024]  entry_SYSCALL_64_after_hwframe+0x6e/0x76
[Thu Apr 25 11:13:29 2024] RIP: 0033:0x717ba4f2725d
[Thu Apr 25 11:13:29 2024] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 
1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 
05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b bb 0d 00 f7 d8 64 89 01 48
[Thu Apr 25 11:13:29 2024] RSP: 002b:7ffd5fa93148 EFLAGS: 0246 
ORIG_RAX: 0139
[Thu Apr 25 11:13:29 2024] RAX: ffda RBX: 5fbbfc5b3710 RCX: 
717ba4f2725d
[Thu Apr 25 11:13:29 2024] RDX: 0004 RSI: 717ba50fa07d RDI: 
001f
[Thu Apr 25 11:13:29 2024] RBP: 7ffd5fa93200 R08: 0040 R09: 
7ffd5fa93190
[Thu Apr 25 11:13:29 2024] R10: 717ba5003b20 R11: 0246 R12: 
717ba50fa07d
[Thu Apr 25 11:13:29 2024] R13: 0002 R14: 

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

[Aussems J.a.c.]

I tryed yesterday to setup my system to receive the -proposed kernel
update using the link, https://wiki.ubuntu.com/Testing/EnableProposed.
The system got some developers updates, but not the kernel update jammy-
linux-oem-6.5. So I am indoubt, did I do something wrong or did I forget
something settingup before I could test the new kernel solotion? A
response from your side would be appreciated.

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

Title:
  The keyboard does not work after latest kernel update

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

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2059380] Re: [Ubuntu 24.04-server]- installation failed on FHF-R platform with kernel trace

[Kleber Sacilotto de Souza]

Hello Quanxian,

Could you please also try with the latest Ubuntu 24.04 server image?

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

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

Title:
  [Ubuntu 24.04-server]- installation failed on FHF-R platform with
  kernel trace

Status in intel:
  New
Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in Noble:
  New
Status in linux source package in Noble:
  Incomplete

Bug description:
  Description:
  we try Ubuntu 24.04 server version from 
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/

  installed failed with usb disk and BMC.

  [HW/SW Information]

  Platform: FHF-R workstation (SPR-R CPU)

  [Software Information]
Target Version:
  24.04
Target Kernel:
  TBD
Commit IDs:
  TBD
External Links:

  [Business Justification]
  Installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2059380/+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 2063439] [NEW] Overwriting existing binding of keysym 31 with keysym 31 (keycode a

[Deepak]

Public bug reported:


/var/log/syslog: 

Window manager warning: Overwriting existing binding of keysym 31 with keysym 
31 (keycode a).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 16:01:11 2024
InstallationDate: Installed on 2021-09-13 (954 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Overwriting existing binding of keysym 31 with keysym 31 (keycode a

Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  
  /var/log/syslog: 

  Window manager warning: Overwriting existing binding of keysym 31 with keysym 
31 (keycode a).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Apr 25 15:55:39 deep-lenovo gnome-shell[2156]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-28-generic 6.5.0-28.29~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 16:01:11 2024
  InstallationDate: Installed on 2021-09-13 (954 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  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-signed-hwe-6.5/+bug/2063439/+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 2042363] Re: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 ser

[GuoqingJiang]

Per comment#23, the ip from AIX 7.2 client are:

9.20.120.127 name = adia.v6.hursley.ibm.com -- Primary
9.20.121.46 name = amberjack.v6.hursley.ibm.com ? Partner


And I searched the trace again with above ips, looks socket cc6f0db2 is 
created between 9.20.120.127 and nfs server, however it can also return EAGAIN.

duckseason kernel: [13254.724411] svc: socket cc6f0db2 
sendto([8485f39d 72... ], 72) = 72 (addr 9.20.120.127, port=1022)
...
duckseason kernel: [13254.724734] svc: socket cc6f0db2(inet 
c831762e), busy=0
duckseason kernel: [13254.724759] svc: server 728e82a2, pool 0, 
transport cc6f0db2, inuse=2
duckseason kernel: [13254.724761] svc: tcp_recv cc6f0db2 data 1 conn 0 
close 0
duckseason kernel: [13254.724765] svc: socket cc6f0db2 
recvfrom(b6708704, 4) = 4
duckseason kernel: [13254.724766] svc: TCP record, 168 bytes
duckseason kernel: [13254.724769] svc: socket cc6f0db2 
recvfrom(57dbced3, 4096) = 168
duckseason kernel: [13254.724771] svc: TCP final record (168 bytes)
duckseason kernel: [13254.724775] svc: svc_authenticate (1)
duckseason kernel: [13254.724779] svc: server ee62a401, pool 0, 
transport cc6f0db2, inuse=3
duckseason kernel: [13254.724780] svc: tcp_recv cc6f0db2 data 1 conn 0 
close 0
duckseason kernel: [13254.724783] svc: socket cc6f0db2 
recvfrom(b6708704, 4) = -11

And it is same for socket 3497acd5 which is used between
9.20.121.46 and nfs server.

duckseason kernel: [13254.802249] svc: socket 3497acd5 
sendto([86e5a045 72... ], 72) = 72 (addr 9.20.121.46, port=1020)
...
duckseason kernel: [13254.802533] svc: socket 3497acd5(inet 
72c9551d), busy=0
duckseason kernel: [13254.802571] svc: server 728e82a2, pool 0, 
transport 3497acd5, inuse=2
duckseason kernel: [13254.802573] svc: tcp_recv 3497acd5 data 1 conn 0 
close 0
duckseason kernel: [13254.802578] svc: socket 3497acd5 
recvfrom(77f9cf7c, 4) = 4
duckseason kernel: [13254.802579] svc: TCP record, 164 bytes
duckseason kernel: [13254.802583] svc: socket 3497acd5 
recvfrom(57dbced3, 4096) = 164
duckseason kernel: [13254.802585] svc: TCP final record (164 bytes)
duckseason kernel: [13254.802590] svc: svc_authenticate (1)
duckseason kernel: [13254.802596] svc: server ee62a401, pool 0, 
transport 3497acd5, inuse=3
duckseason kernel: [13254.802597] svc: tcp_recv 3497acd5 data 1 conn 0 
close 0
duckseason kernel: [13254.802599] svc: socket 3497acd5 
recvfrom(77f9cf7c, 4) = -11 

But since aix 7.2 client can work with the same server according to bug
description, I am curious why 7.2 client also return EAGAIN which is
same as 7.3 client, what am I missing?

Some questions/suggestion:

1. Did aix 7.3 nfs client work with previous kernel? If so, run "git bisect" to 
find which commit caused the issue.
2. Is it possible to try with latest 5.4 stable kernel as suggested in 
comment#1? Also try latest upstream kernel (6.9-rc5 at this time) as well.
3. Does increase lease time make difference?

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

Title:
  AIX 7.3 NFS client frequently returns an EIO error to an application
  when reading or writing to a file that has been locked with fcntl() on
  a Ubuntu 20.04 NFSV4 server

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  AIX 7.3 NFS client frequently returns an EIO error to an application when 
reading or writing to a file that has been locked with fcntl(). NFS server is 
Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not 
appear to affect other combinations of NFS client (including AIX 7.2) with this 
NFS server.

  The AIX team have indicated that the cause of the EIO is triggered by the NFS 
server returning a BAD_SEQID error which leads to the AIX NFS client 
incorrectly zeroing the stateid, which then leads to the NFS server returning a 
BAD_STATEID error and the NFS client then returns the EIO error. The AIX team 
would like to understand why the BAD_SEQID has been returned.
   
  ---uname output---
  Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
   
  Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 
2.30GHz  

  ---Steps to Reproduce---
   We cannot offer a simple way to recreate the problem as it involves IBM MQ 
running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 
storage.

  However, we can provide any requested trace or dumps from any or all
  of the involved machines.

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


-- 
Mailing list: 

[Kernel-packages] [Bug 2063013] Re: Facing display issue (Display distortion and shows distorted lines) on booting after upgrading to new kernel.

[Jac]

6.5.0-28 also works fine.

But error messages on the screen during boot like : "(UBSAN: 
array-index-out-of-bounds in 
/build/linux-hwe-6.5-5nKPnc/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1249:61
Apr 25 11:10:36 Vero-hp kernel: [   13.379380] index 1 is out of range for type 
'ATOM_PPLIB_VCE_Clock_Voltage_Limit_Record [1]'
Apr 25 11:10:36 Vero-hp kernel: [   13.379388] CPU: 1 PID: 96 Comm: 
systemd-udevd Not tainted 6.5.0-28-generic #29~22.04.1-Ubuntu
Apr 25 11:10:36 Vero-hp kernel: [   13.379393] Hardware name: HP HP Laptop 
17-ak0xx/8345, BIOS F.02 04/14/2017"
Etc.

Attached is a kernel log with boots with different kernels.


** Attachment added: "Kern-log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063013/+attachment/5770222/+files/Kern-log

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

Title:
  Facing display issue (Display distortion and shows distorted lines) on
  booting after upgrading to new kernel.

Status in linux package in Ubuntu:
  New

Bug description:
  Facing display issue (Display distortion and shows distorted lines) on
  booting after upgrading to new kernel. It is working good till version
  linux-image-5.15.0-84-generic (currently using). after this version
  able to boot system only in recovery mode. (currently installed:
  linux-image-5.15.0-105)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148
  Uname: Linux 5.15.0-105-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 10:11:19 2024
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2021-10-10 (923 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063013/+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 2060727] Re: The keyboard does not work after latest kernel update

[AaronMa]

@ramcsir,

Your Ubuntu is 23.10.
Would you mind try to add the following line to "/etc/apt/sources.list":
deb http://archive.ubuntu.com/ubuntu/ jammy-proposed main

$ sudo apt update
$ sudo apt install  linux-image-6.5.0-1021-oem linux-modules-6.5.0-1021-oem

After you test, the line and packages can be removed.

Thanks.

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

Title:
  The keyboard does not work after latest kernel update

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

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2063449] Re: No WIFI after upgrade to 24.04

[El jinete sin cabeza]

** Summary changed:

- WARNING: CPU: 5 PID: 464 at drivers/net/wireless/realtek/rtw88/pci.c:1277 
rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
+ No WIFI after upgrade to 24.04

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

Title:
  No WIFI after upgrade to 24.04

Status in linux package in Ubuntu:
  New

Bug description:
  [  102.836810] [ cut here ]
  [  102.836817] failed to read DBI register, addr=0x0719
  [  102.836916] WARNING: CPU: 5 PID: 464 at 
drivers/net/wireless/realtek/rtw88/pci.c:1277 
rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
  [  102.836963] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer qrtr cmac 
algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi snd_sof_pci_intel_skl 
snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_avs 
snd_soc_hda_codec snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc 
snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core 
snd_hda_codec_realtek snd_compress snd_hda_codec_generic ac97_bus 
snd_pcm_dmaengine snd_hda_intel binfmt_misc snd_intel_dspcfg snd_intel_sdw_acpi 
snd_hda_codec intel_uncore_frequency intel_uncore_frequency_common snd_hda_core 
rtw88_8821ce snd_hwdep rtw88_8821c rtw88_pci snd_pcm intel_tcc_cooling 
x86_pkg_temp_thermal rtw88_core intel_powerclamp snd_seq_midi crct10dif_pclmul 
polyval_clmulni snd_seq_midi_event polyval_generic ghash_clmulni_intel 
sha256_ssse3 snd_rawmidi uvcvideo sha
 1_ssse3 mac80211 aesni_intel
  [  102.837296]  videobuf2_vmalloc crypto_simd uvc cryptd snd_seq 
videobuf2_memops btusb processor_thermal_device_pci_legacy videobuf2_v4l2 btrtl 
snd_seq_device processor_thermal_device rapl nls_iso8859_1 mei_hdcp mei_pxp 
intel_rapl_msr snd_timer processor_thermal_wt_hint videodev cfg80211 btintel 
hid_sensor_magn_3d processor_thermal_rfim hid_sensor_accel_3d 
hid_sensor_custom_intel_hinge snd hid_sensor_gyro_3d i2c_i801 
processor_thermal_rapl btbcm hp_wmi videobuf2_common hid_sensor_rotation 
hid_sensor_incl_3d btmtk intel_cstate hid_sensor_trigger 
industrialio_triggered_buffer platform_profile i915 wmi_bmof 
intel_wmi_thunderbolt soundcore i2c_smbus libarc4 mc bluetooth kfifo_buf mei_me 
intel_rapl_common drm_buddy mei hid_sensor_iio_common ttm ecdh_generic 
processor_thermal_wt_req ecc processor_thermal_power_floor drm_display_helper 
processor_thermal_mbox industrialio cec intel_pch_thermal rc_core 
intel_soc_dts_iosf i2c_algo_bit intel_xhci_usb_role_switch int3403_thermal 
int340x_therm
 al_zone soc_button_array intel_vbtn
  [  102.837570]  sparse_keymap intel_pmc_core intel_vsec int3400_thermal 
pmt_telemetry hp_accel pmt_class acpi_thermal_rel wireless_hotkey acpi_pad 
lis3lv02d input_leds joydev serio_raw mac_hid coretemp msr parport_pc ppdev lp 
parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 ax88179_178a 
usbnet usbhid mii hid_sensor_custom hid_sensor_hub intel_ishtp_hid 
hid_multitouch hid_generic spi_pxa2xx_platform dw_dmac dw_dmac_core 8250_dw 
sdhci_pci nvme intel_lpss_pci video intel_lpss i2c_hid_acpi crc32_pclmul cqhci 
intel_ish_ipc nvme_core i2c_hid psmouse ahci xhci_pci nvme_auth libahci sdhci 
intel_ishtp hid xhci_pci_renesas idma64 wmi pinctrl_sunrisepoint
  [  102.837807] CPU: 5 PID: 464 Comm: kworker/u16:10 Not tainted 
6.8.0-31-generic #31-Ubuntu
  [  102.837822] Hardware name: HP HP Pavilion x360 Convertible 14-cd0xxx/8486, 
BIOS F.41 11/16/2022
  [  102.837831] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
  [  102.838215] RIP: 0010:rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
  [  102.838253] Code: 1f 00 41 88 45 00 31 c0 5b 41 5c 41 5d 5d 31 d2 31 f6 31 
ff c3 cc cc cc cc be 19 07 00 00 48 c7 c7 60 f4 c8 c0 e8 4c 1c c7 e5 <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d 31 d2 31 f6 31 ff c3 cc cc
  [  102.838266] RSP: :b08005e2fc60 EFLAGS: 00010246
  [  102.838279] RAX:  RBX:  RCX: 

  [  102.838288] RDX:  RSI:  RDI: 

  [  102.838295] RBP: b08005e2fc78 R08:  R09: 

  [  102.838304] R10:  R11:  R12: 
8f5c04fd1fc0
  [  102.838313] R13: b08005e2fc8f R14: 8f5c04fd71f8 R15: 
8f5c021a7e00
  [  102.838322] FS:  () GS:8f5f61e8() 
knlGS:
  [  102.838333] CS:  0010 DS:  ES:  CR0: 80050033
  [  102.838341] CR2: 78baf9e03020 CR3: 1423c003 CR4: 
003706f0
  [  102.838350] Call Trace:
  [  102.838358]  
  [  102.838396]  ? show_regs+0x6d/0x80
  [  102.838416]  ? __warn+0x89/0x160
  [  102.838435]  ? rtw_dbi_read8.constprop.0+0xb4/0xd0 [rtw88_pci]
  [  102.838468]  ? report_bug+0x17e/0x1b0

[Kernel-packages] [Bug 2016881] Re: Building for Focal fails on riscv64

[Heitor Alves de Siqueira]

Bionic is EoL, if RISC-V support is needed there we'll need to target
Pro 18.04.

** Tags removed: patch se-sponsor-halves

** Description changed:

- Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
- patch missing:
- https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80
+ [Impact]
+  * riscv64 builds fail completely, so users on that architecture can't use 
ZFS.
+ 
+ [Test Plan]
+  * Build zfs-linux on target architecture. No test failure is expected.
+ 
+ [Where problems could occur]
+  * Test failures and bugs that are exclusive to RISCV64 might show up
+ 
+ [Other Info]
+  * Upstream introduced support riscv64 with 4254e407294b
+  * Builds succeed on Jammy and newer, Focal is missing the enablement patch
+ 
+ --
+ [Original Description]
+ Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch 
missing: 
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: Invalid => Won't Fix

** Summary changed:

- Building for Focal fails on riscv64
+ zfs-linux FTBFS for riscv64 on Focal

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

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

Title:
  zfs-linux FTBFS for riscv64 on Focal

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in zfs-linux source package in Focal:
  In Progress

Bug description:
  [Impact]
   * riscv64 builds fail completely, so users on that architecture can't use 
ZFS.

  [Test Plan]
   * Build zfs-linux on target architecture. No test failure is expected.

  [Where problems could occur]
   * Test failures and bugs that are exclusive to RISCV64 might show up

  [Other Info]
   * Upstream introduced support riscv64 with 4254e407294b
   * Builds succeed on Jammy and newer, Focal is missing the enablement patch

  --
  [Original Description]
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch 
missing: 
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic

[Roxana Nicolescu]

@ivan.hu Can you please test if dropping these 2 patches work? This is a
temporary solution to start the next cycle, we'll need to find a proper
one though.

thermal: core: Store trip pointer in struct thermal_instance
thermal: trip: Drop lockdep assertion from thermal_zone_trip_id()

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

Title:
  Some DUTs can't boot up after installing the proposed kernel on Mantic

Status in linux package in Ubuntu:
  In Progress

Bug description:
  During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at 
very early stage of booting process.
  The last messages displayed on the screen are:
  EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
  EFI stub: Measured initrd data into PCR 9

  There are no journal logs existed when it boot with the 6.5.0-33
  kernel.

  Here is the list of the impacted machines that I found so far
  https://certification.canonical.com/hardware/202106-29206/
  https://certification.canonical.com/hardware/202106-29207/
  https://certification.canonical.com/hardware/201912-27623/
  https://certification.canonical.com/hardware/202007-28059/
  https://certification.canonical.com/hardware/202103-28762/
  https://certification.canonical.com/hardware/202012-28510/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2063461] [NEW] Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA Grace system

[Brad Figg]

Public bug reported:

PROBLEM:

While trying to monitor the ipc group for using perf-stat tool, despite it 
being supported, I get the following errors:
$ sudo perf list | grep ipc
  ipc
  ipc_rate
  retired_ipc
  spec_ipc


$ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0  -t 10s
Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event 
(instructions).
/bin/dmesg | grep -i perf may provide additional information.
$ sudo -S perf stat -a -M ipc_rate -- sudo -S stress-ng --cpu 0  -t 10s
Error:
The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event 
(instructions).
/bin/dmesg | grep -i perf may provide additional information.


However, I can get the groups retired_ipc and spec_ipc to work: 
$ sudo -S perf stat -a -M retired_ipc  -- sudo -S stress-ng --cpu 0  -t 10s
Value 0  contains non-numeric: ' '

 Performance counter stats for 'system wide':

96,818,964  INST_RETIRED # 0.58 retired_ipc 
  
   166,601,455  CPU_CYCLES  
  

   0.013516186 seconds time elapsed


$ sudo -S perf stat -a -M spec_ipc  -- sudo -S stress-ng --cpu 0  -t 10s
Value 0  contains non-numeric: ' '

 Performance counter stats for 'system wide':

91,053,297  INST_SPEC# 0.58 spec_ipc
  
   156,558,810  CPU_CYCLES  
  

   0.009877355 seconds time elapsed

SOLUTION:
Please accept the pull request which cherry-picks the following two upstream 
commits:

d43f5491210197196458c1454f2be0eb66d3e4d1 perf vendor events arm64: Update 
stall_slot workaround
 for N2 r0p3
4473949074c35072f598bd525ae51d5455f05745 perf vendor events arm64: Update N2 
and V2 metrics and
 events using Arm telemetry repo

** 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/2063461

Title:
  Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA
  Grace system

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

Bug description:
  PROBLEM:

  While trying to monitor the ipc group for using perf-stat tool, despite it 
being supported, I get the following errors:
  $ sudo perf list | grep ipc
ipc
ipc_rate
retired_ipc
spec_ipc

  
  $ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0  -t 10s
  Error:
  The sys_perf_event_open() syscall returned with 22 (Invalid argument) for 
event (instructions).
  /bin/dmesg | grep -i perf may provide additional information.
  $ sudo -S perf stat -a -M ipc_rate -- sudo -S stress-ng --cpu 0  -t 10s
  Error:
  The sys_perf_event_open() syscall returned with 22 (Invalid argument) for 
event (instructions).
  /bin/dmesg | grep -i perf may provide additional information.


  However, I can get the groups retired_ipc and spec_ipc to work: 
  $ sudo -S perf stat -a -M retired_ipc  -- sudo -S stress-ng --cpu 0  -t 10s
  Value 0  contains non-numeric: ' '

   Performance counter stats for 'system wide':

  96,818,964  INST_RETIRED # 0.58 
retired_ipc   
 166,601,455  CPU_CYCLES


 0.013516186 seconds time elapsed

  
  $ sudo -S perf stat -a -M spec_ipc  -- sudo -S stress-ng --cpu 0  -t 10s
  Value 0  contains non-numeric: ' '

   Performance counter stats for 'system wide':

  91,053,297  INST_SPEC# 0.58 spec_ipc  

 156,558,810  CPU_CYCLES


 0.009877355 seconds time elapsed

  SOLUTION:
  Please accept the pull request which cherry-picks the following two upstream 
commits:

  d43f5491210197196458c1454f2be0eb66d3e4d1 perf vendor events arm64: Update 
stall_slot workaround
   for N2 r0p3
  4473949074c35072f598bd525ae51d5455f05745 perf vendor events arm64: Update N2 
and V2 metrics and
   events using Arm telemetry repo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2063461/+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 2063308] Re: lenovo p1g5 suspend issues with docking stations

[Mark Pearson]

Can we get the system config details please - CPU, GPU in particular. Also 
confirm if WWAN is enabled
Which dock is being used?

Can you confirm if AMT is enabled or not in the BIOS?
We've seen issues with AMT enabled with the TBT dock, especially with 
networking.

Will look to reproduce the issue with high power numbers after the ME FW
update - agreed that looks like a FW issue.

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

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+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 2063470] [NEW] 6.8.0-1004-raspi "The futex facility returned an unexpected error code."

[Luke-Jr]

Public bug reported:

Upgrading my Raspberry Pi 5 to 6.8.0-1004-raspi broke the CI that runs
on it.

https://cirrus-ci.com/task/6254679959535616

All the attempts were after upgrading, except the very last re-run that
succeeded after downgrading to 6.8.0-1001-raspi.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-1004-raspi 6.8.0-1004.4
ProcVersionSignature: Ubuntu 6.8.0-1001.1-raspi 6.8.0-rc4
Uname: Linux 6.8.0-1001-raspi aarch64
ApportVersion: 2.28.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 25 18:54:42 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 noble

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

Title:
  6.8.0-1004-raspi "The futex facility returned an unexpected error
  code."

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Upgrading my Raspberry Pi 5 to 6.8.0-1004-raspi broke the CI that runs
  on it.

  https://cirrus-ci.com/task/6254679959535616

  All the attempts were after upgrading, except the very last re-run
  that succeeded after downgrading to 6.8.0-1001-raspi.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-1004-raspi 6.8.0-1004.4
  ProcVersionSignature: Ubuntu 6.8.0-1001.1-raspi 6.8.0-rc4
  Uname: Linux 6.8.0-1001-raspi aarch64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Apr 25 18:54:42 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063470/+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 2016881] Re: zfs-linux FTBFS for riscv64 on Focal

[Heinrich Schuchardt]

I would suggest not to invest in enabling a new feature in Focal now
that we have two newer LTS releases. Setting to won't fix.

** Changed in: zfs-linux (Ubuntu Focal)
   Status: In Progress => Won't Fix

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

Title:
  zfs-linux FTBFS for riscv64 on Focal

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Won't Fix
Status in zfs-linux source package in Focal:
  Won't Fix

Bug description:
  [Impact]
   * riscv64 builds fail completely, so users on that architecture can't use 
ZFS.

  [Test Plan]
   * Build zfs-linux on target architecture. No test failure is expected.

  [Where problems could occur]
   * Test failures and bugs that are exclusive to RISCV64 might show up

  [Other Info]
   * Upstream introduced support riscv64 with 4254e407294b
   * Builds succeed on Jammy and newer, Focal is missing the enablement patch

  --
  [Original Description]
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single patch 
missing: 
https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2062412] Re: No input through internal microphone (Ryzen 6000)

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 2061254 ***
https://bugs.launchpad.net/bugs/2061254

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No input through internal microphone (Ryzen 6000)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
  updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
  is a known problem and a patch may be included in kernel 6.8.3.

  Is it possible to backport this patch? Or is the plan to wait for a
  kernel update? It would be good use the microphone in 24.04.

  The symptoms are exactly as described in
  https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297

  Reportedly the patch is included in
  
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2063308] Re: lenovo p1g5 suspend issues with docking stations

[Dariusz Gadomski]

Sure Mark. I have some information handy:

grep "model name" /proc/cpuinfo | head -n 1 
model name  : 12th Gen Intel(R) Core(TM) i9-12900H

GPU:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2438] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:22f8]


The dock is:
ThinkPad Thunderbolt 4 Dock:
│ │   Device ID:  c0170efdf195b859fa21474253c0d97e7335
│ │   Current version:10.11
│ │   Vendor: Lenovo (USB:0x17EF)


No WWAN seems to be in use according to the logs.

I'm checking with the user about the AMT status.

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

Title:
  lenovo p1g5 suspend issues with docking stations

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lenovo Docking Station Issue with Ubuntu 22.04 Sleep mode Recovery

  Hello,
  We are having trouble with our lenovo p1 laptops docking stations. When 
waking from suspend on Ubuntu with a docking station is an issue for some users 
even with Intel AMT disabled in BIOS.
  The exact steps to reproduce are as follows:
  1) Suspend/sleep the laptop
  2) Plug the docking station into the laptop
  3) Wake the laptop

  The sleep settings in BIOS are set to Linux S3. Docking station
  issues, such as Ethernet not working after waking, do not occur with
  Windows/Linux sleep settings, but the laptop doesn't properly suspend
  processes in Windows/Linux sleep mode and will overheat the laptop
  when in an enclosed space such as a bag. Linux S3 is the only way
  we've found laptops to not overheat after suspending, but we that
  makes the dock inoperable after waking from suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063308/+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 2060919] Re: cifs: Copying file to same directory results in page fault

[Roxana Nicolescu]

Hi all,

This fix should be released in ~2 weeks.

** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/2060919

Title:
  cifs: Copying file to same directory results in page fault

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

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

  [Impact]

  Copying or modifying a file to the same directory within a cifs mount
  results in a page fault, and the process that initiated the copy being
  killed. This could be cp, nautilus, etc.

  This results in the following oops:

  BUG: unable to handle page fault for address: fffe
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0
  Oops:  [#1] PREEMPT SMP NOPTI
  CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic 
#28-Ubuntu
  RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 
89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 
f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  RAX:  RBX: fffe RCX: 
  RDX:  RSI:  RDI: 
  RBP: aab6865ffc28 R08: 0001 R09: 
  R10: 00023854 R11:  R12: 
  R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70
  FS: 7bd4d594b6c0() GS:90753f80() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: fffe CR3: 00017022a000 CR4: 00750ef0
  PKRU: 5554
  Call Trace:
  
  ? show_regs+0x6d/0x80
  ? __die+0x24/0x80
  ? page_fault_oops+0x99/0x1b0
  ? kernelmode_fixup_or_oops+0xb2/0x140
  ? __bad_area_nosemaphore+0x1a5/0x2c0
  ? bad_area_nosemaphore+0x16/0x30
  ? do_kern_addr_fault+0x7b/0xa0
  ? exc_page_fault+0x1a4/0x1b0
  ? asm_exc_page_fault+0x27/0x30
  ? cifs_flush_folio+0x41/0xf0 [cifs]
  ? cifs_flush_folio+0x37/0xf0 [cifs]
  cifs_remap_file_range+0x172/0x660 [cifs]
  do_clone_file_range+0x101/0x2d0
  vfs_clone_file_range+0x3f/0x150
  ioctl_file_clone+0x52/0xc0
  do_vfs_ioctl+0x68f/0x910
  ? __fget_light+0xa5/0x120
  __x64_sys_ioctl+0x7d/0xf0
  do_syscall_64+0x59/0x90
  ? kmem_cache_free+0x22/0x3e0
  ? putname+0x5b/0x80
  ? exit_to_user_mode_prepare+0x30/0xb0
  ? syscall_exit_to_user_mode+0x37/0x60
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90

  There is no known workaround.

  [Fix]

  The stacktrace is very similar to a regression reported to upstream
  6.1.y:

  https://lore.kernel.org/linux-
  mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/

  The thread mentions that:

  commit 7b2404a886f8b91250c31855d287e632123e1746
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746

  introduced the issue to Debian's 6.1 kernel.

  This got backported to Ubuntu in:

  commit 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()

  $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Ubuntu-6.5.0-20.20~107

  Which we have been using for some time now, and is not the culprit.

  Reading the regression mailing list thread, they mention that things
  work differently in 6.1:

  > Yeah.  __filemap_get_folio() works differently in v6.1.y. There it returns a
  > folio or NULL.  In 6.7 it returns a folio or a negative error code.  The 
error
  > check in cifs_flush_folio() needs to change to something like:
  >
  > folio = filemap_get_folio(inode->i_mapping, index);
  > if (!folio)
  > return -ENOMEM;
  >
  > David 

  6.1.y then got a specific patch to fix the issue in 6.1, which is:

  commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Author: Steve French 
  Date: Fri Jan 12 23:08:51 2024 -0600
  Subject: cifs: fix flushing folio regression for 6.1 backport
  Link: 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1

  $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Ubuntu-6.5.0-27.28~162

  Since the Ubuntu mantic kernel consumes both 6.1.y and 6.7.y / 6.8.y
  stable patches, this patch was applied to mantic's 6.5 kernel by
  mistake, and contains the wrong logic for how __filemap_get_folio()
  works in 6.5.

  The fix 

[Kernel-packages] [Bug 2040948] Re: USB stick can't be detected

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   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/2040948

Title:
  USB stick can't be detected

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Focal:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Focal:
  New
Status in linux-signed-oem-6.1 source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Jammy:
  New
Status in linux-signed-oem-6.1 source package in Jammy:
  New
Status in linux source package in Mantic:
  Fix Committed
Status in linux-signed-hwe-5.15 source package in Mantic:
  New
Status in linux-signed-oem-6.1 source package in Mantic:
  New
Status in linux source package in Noble:
  Triaged
Status in linux-signed-hwe-5.15 source package in Noble:
  Won't Fix
Status in linux-signed-oem-6.1 source package in Noble:
  Won't Fix

Bug description:
  [Summary]

  During SRU testing, I found some of devices failed to run the usb
  test, when I re-plugged the usb stick, it can be detected, but after
  rebooting, usb stick is gone again.

  I did some further checks and found that If I power cycle the device,
  it can be detected again.

  It seems to happen on the device plugged with a Sandisk usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.1.0-1025-oem 6.1.0-1025.25
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Thu Oct 26 10:37:58 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-lapras+X64
  InstallationDate: Installed on 2023-09-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040948/+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 2061986] Re: Mount CIFS fails with Permission denied

[Roxana Nicolescu]

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

** 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/2061986

Title:
  Mount CIFS fails with Permission denied

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * Mounting SMB share from server without Key Exchange capability is
  failing with Access Denied error

   * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE 
message does not advertise
 Key Exchange capabilities SMB client < 5.16 will forcefully use it leading 
to error response during
 TCON requests.

   * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction 
on 6.5 Kernel
   
   * This scenario was fixed in upstream commit 
9de0737d5ba0425c3154d5d83da12a8fa8595c0f
   
   * An example of server without Key Exchange capability is Oracle Solaris 
11.4 SMB zfs, meaning
 mounting share from that server will result in ACCESS_DENIED error.
   
  [ Test Plan ]

   * So far issue was reported only with Oracle Solaris 11.04 smb server
  and Ubuntu with Kernel <= 5.15

   * To reproduce, setup Oracle Solaris SMB server and try to mount share on 
22.04/20.04 (5.15/5.04)
 Steps to configure SMB server:
  1. Download the ISO for Oracle Solaris Common Build Edition [1]
  2. Create a VM with at least 16 GB of memory - I have experienced 
installation issues with less memory
  3. Install Oracle Solaris using the downloaded ISO
  a. Make sure to create a test user
  4. Log into the VM as the root user
  5. Create a test directory for the share:
  a. mkdir /smbshare && chmod 777 /smbshare 
  6. Disable the normal Samba daemon: [2]
  a. svcadm disable svc:/network/samba
  b. svcadm disable svc:/network/wins
  7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3]
  a. svcadm enable -r smb/server
  b. smbadm join -w workgroup
  8 Update the /etc/pam.d/other file to require authentication by adding the 
following line:
  a. password requiredpam_smb_passwd.so.1nowarn
  9. Reset the password for the test user so that it is updated in the SMB 
password database
  10. Create the pool and share it using Samba: [4]
  a. zfs create -o mountpoint=/smbshare/ rpool/smbshare
  b. zfs share -o share.smb=on rpool/smbshare%share

  [1] 

  [2] 

  [3] 

  [4] 


   * With server configured, mount share using ubuntu SMB client
 Expected result: mount operation should succeed
 Actual result: mount returns following error:
  root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare 
test
  Password for rmalz@//192.168.50.217/smbshare:  
  mount error(13): Permission denied
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log 
messages (dmesg) 

  [ Where problems could occur ]

   * Upstream patch is changing smb client behavior based on server 
NTLMSSP_CHALLENGE Negotiate Flags,
 if server does not advertise Key Exchange Capability but requires it from 
client communication might
 be broken. It is unknown if such servers are used, such instance should be 
treated as a server bug.

   * Patch is available in upstream kernel since 5.16, any issues associated 
with it should be already
 detected.

   * Patch adds additional requirement checks on server NTLM flags, although it 
is possible to hit
 these checks, I was not able to find any instances of that occurring.

   * To lower regression potential, upstream patch backported to Ubuntu 5.15 
and 5.04 Kernels have been
 tested in following environments:
 smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE
 smb client: Ubuntu 22.04, Ubuntu 20.04
 During testing no issues have been detected.

  [ Other Info ]
   
   * Error message coming from SMB client is the same as providing incorrect 
credentials, which might
 confuse users. 
   * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and 
without patch.

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


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

[Kernel-packages] [Bug 2063067] Re: Fix bluetooth connections with 3.0 device

[Roxana Nicolescu]

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

** 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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2063067

Title:
  Fix bluetooth connections with 3.0 device

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
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

Bug description:
  [Impact]
  Bluetooth keyboard cannot be connected to Realtek BT controller.

  [Fix]
  It's a regression from Ubuntu-6.5.0-20.20 and Ubuntu-oem-6.5-6.5.0-1016.17
  The bad commit:
  c7f59461f5a78 ("Bluetooth: Fix a refcnt underflow problem for hci_conn")
  Fix:
  7e74aa53a68bf ("Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST")

  [Test]
  Tested on hardware, the bt3.0 keyboard connects to host well.

  [Where problems could occur]
  It may break bluetooth.

  The commit is already in v6.8-rc7,
  SRU Jammy, oem-6.5 and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063067/+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 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle

[Roxana Nicolescu]

** Changed in: linux (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Mantic)
   Status: New => Fix Committed

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

Title:
  RTL8852BE fw security fail then lost WIFI function during
  suspend/resume cycle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  New
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:
  New
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]

  On a Dell laptop, When we do suspend/resume test, we found the
  realtek wifi couldn't work after resume, from the dmesg, we found
  the error log as below:
  Log:
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security 
fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download 
firmware fail
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x1E0 = 0x62
  三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 
0x83F2 = 0x8

  [Fix]

  Backport a commit from mainline kernel (linux-next), this will retry firmware
  loading for 5 times.

  [Test Case]

  run suspend/resume test case for over 100 times, the wifi still
  works.

  [Where problems could occur]

  This commit comes from mailine kernel, and it doesn't change existing
  driver except loading firmware a couple of more times if there is an error.
  In theory this will not introduce regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2063096/+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 2051922] Re: Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all

[Ferenc Jozsef Stefan]

** Description changed:

- Dear Members!
- 
- No wifi adapter detected on ubuntu, on win11 it works fine
- 
- lsb_release -rd
- Description:  Ubuntu 22.04.3 LTS
- Release:  22.04
- But wifi failed to manifest on previous versions and on the upcoming 24.04 as 
well
- ---
- 
- 
- tethering works
- bluetooth works fine
- no soft block / no hard block
- 
- "Additional drivers" empty
- "ethernet interface" never tried but it is detected
- "lspci" doesnt show wifi
- "lshw -C network" doesnt show wifi
- 
- did a woodoo with iwlwifi-7265-ucode-25.30.14.0 file, copied files to 
firmware folder, it must have failed since still no wifi. 
- I have done a couple other things in vain, glad to repeat for the sake of 
practice and result.
- 
-
- inxi -Abd
- System:
-   Kernel: 6.5.0-14-generic x86_64 bits: 64
- Desktop: GNOME 42.9 Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
- Machine:
-   Type: Mini-pc Mobo: N/A model: N/A v: V00 serial: 
- UEFI: American Megatrends v: 1.11_P4C4M43_EC_0_0_59_AMI date: 11/05/2022
- Network:
-   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
- driver: r8169
-   Device-2: Intel Bluetooth wireless interface type: USB driver: btusb
- 
- 
- Is there a way to give life to that piece of wifi technology?
- 
- 
- Thank you all in advance!
+ empty input is unacceptable
+ yeah, right

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

Title:
  Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected
  at all

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

Bug description:
  empty input is unacceptable
  yeah, right

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051922/+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 2063229] Re: SATA devices on Alder-Lake S not recognized

[Eduardo Siemann]

Same problem here, after upgrading from Ubuntu 23.10 to
24.04(6.8.0-31-generic) it stopped working.

Using kernel 6.8.0-31-generic and 6.8.7-x64v3-xanmod2 the same error
occurs. I'm using 6.6.28-x64v3-xanmod2 to temporarily solve this
problem.

Using: 6.8.0-31-generic

dmesg:
[0.788961] kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit
[0.789154] kernel: ahci :00:17.0: AHCI 0001.0301 32 slots 4 ports 6 
Gbps 0xf0 impl SATA mode
[0.789158] kernel: ahci :00:17.0: flags: 64bit ncq sntf led clo only 
pio slum part ems deso sadm sds 
[0.798278] kernel: nvme nvme0: allocated 32 MiB host memory buffer.
[0.799063] kernel: scsi host0: ahci
[0.799144] kernel: scsi host1: ahci
[0.799187] kernel: scsi host2: ahci
[0.799229] kernel: scsi host3: ahci
[0.799278] kernel: scsi host4: ahci
[0.799326] kernel: scsi host5: ahci
[0.799373] kernel: scsi host6: ahci
[0.799418] kernel: scsi host7: ahci
[0.799439] kernel: ata1: DUMMY
[0.799440] kernel: ata2: DUMMY
[0.799440] kernel: ata3: DUMMY
[0.799441] kernel: ata4: DUMMY
[0.799450] kernel: ata5: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522300 irq 131 lpm-pol 0
[0.799453] kernel: ata6: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522380 irq 131 lpm-pol 0
[0.799454] kernel: ata7: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522400 irq 131 lpm-pol 0
[0.799456] kernel: ata8: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522480 irq 131 lpm-pol 0
[0.799767] kernel: nvme nvme0: 12/0/0 default/read/poll queues
[0.802618] kernel:  nvme0n1: p1 p2
[0.808595] kernel: intel-lpss :00:15.1: enabling device (0004 -> 0006)
[0.809052] kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit
[1.020755] kernel: e1000e :00:1f.6 :00:1f.6 (uninitialized): 
registered PHC clock
[1.029682] kernel: usb 1-7: new high-speed USB device number 2 using 
xhci_hcd
[1.085033] kernel: e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 
f4:b5:20:47:67:44
[1.085045] kernel: e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network 
Connection
[1.085121] kernel: e1000e :00:1f.6 eth0: MAC: 15, PHY: 12, PBA No: 
FF-0FF
[1.106605] kernel: ata8: SATA link down (SStatus 4 SControl 300)
[1.106840] kernel: ata5: SATA link down (SStatus 4 SControl 300)
[1.107020] kernel: ata7: SATA link down (SStatus 4 SControl 300)
[1.107059] kernel: ata6: SATA link down (SStatus 4 SControl 300)


lspci | grep -i -e raid -e sata
00:17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller 
[AHCI Mode] (rev 11)

lshw
description: SATA controller
product: Alder Lake-S PCH SATA Controller [AHCI Mode]
vendor: Intel Corporation
physical id: 17
bus info: pci@:00:17.0
version: 11
width: 32 bits
clock: 66MHz
capabilities: sata ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:123 memory:8052-80521fff memory:80523000-805230ff 
ioport:3090(size=8) ioport:3080(size=4) ioport:3060(size=32) 


lsb_release -rd
Description:Ubuntu 24.04 LTS
Release:24.04

apt-cache policy linux-image-6.8.0-31-generic   
 
linux-image-6.8.0-31-generic:
Installed: 6.8.0-31.31

---

Using kernel 6.6.28-x64v3-xanmod2 which is working:

dmesg
[0.706843] kernel: idma64 idma64.0: Found Intel integrated DMA 64-bit
[0.708855] kernel: ahci :00:17.0: AHCI 0001.0301 32 slots 4 ports 6 
Gbps 0xf0 impl SATA mode
[0.708859] kernel: ahci :00:17.0: flags: 64bit ncq sntf led clo only 
pio slum part ems deso sadm sds 
[0.713211] kernel: nvme nvme0: allocated 32 MiB host memory buffer.
[0.714590] kernel: nvme nvme0: 12/0/0 default/read/poll queues
[0.717412] kernel:  nvme0n1: p1 p2
[0.726589] kernel: intel-lpss :00:15.1: enabling device (0004 -> 0006)
[0.726830] kernel: idma64 idma64.1: Found Intel integrated DMA 64-bit
[0.751112] kernel: scsi host0: ahci
[0.751461] kernel: scsi host1: ahci
[0.751697] kernel: scsi host2: ahci
[0.751886] kernel: scsi host3: ahci
[0.751942] kernel: scsi host4: ahci
[0.752023] kernel: scsi host5: ahci
[0.752070] kernel: scsi host6: ahci
[0.752118] kernel: scsi host7: ahci
[0.752140] kernel: ata1: DUMMY
[0.752141] kernel: ata2: DUMMY
[0.752141] kernel: ata3: DUMMY
[0.752142] kernel: ata4: DUMMY
[0.752147] kernel: ata5: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522300 irq 125
[0.752149] kernel: ata6: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522380 irq 125
[0.752151] kernel: ata7: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522400 irq 125
[0.752153] kernel: ata8: SATA max UDMA/133 abar m2048@0x80522000 port 
0x80522480 irq 125
[0.950924] kernel: e1000e :00:1f.6 :00:1f.6 (uninitialized): 
registered PHC clock
[0.958644] kernel: usb 1-7: new high-speed USB device number 2 using 

[Kernel-packages] [Bug 2051922] Re: Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected at all

[Ferenc Jozsef Stefan]

no solution

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

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

Title:
  Intel(R) Dual Band Wireless-AC 7265, wireless adapter is not detected
  at all

Status in linux-hwe-6.5 package in Ubuntu:
  Invalid

Bug description:
  empty input is unacceptable
  yeah, right

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051922/+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 2063229] Re: SATA devices on Alder-Lake S not recognized

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  SATA devices on Alder-Lake S not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Jammy (kernel 5.15.0-94) and Ubuntu Noble (kernel 6.8.0-22)
  installations and Ubuntu Mantic installed hard drive (kernel
  6.5.0-28-generic) are unable to find SATA devices on Alder-Lake S
  Intel SATA controller.

  Ubuntu Focal and Bionic works just fine. Debian 12 (kernel 6.1.0-18)
  and other debian based distros (Mint, Kali, OpenMediaVault, Proxmox)
  works just fine.

  relevant dmesg logs:
  2024-04-19T17:18:50.668222+00:00 ubuntu-server kernel: ahci :00:17.0: 
version 3.0
  2024-04-19T17:18:50.668356+00:00 ubuntu-server kernel: ahci :00:17.0: 
AHCI 0001.0301 32 slots 4 ports 6 Gbps 0xf0 impl SATA mode
  2024-04-19T17:18:50.668358+00:00 ubuntu-server kernel: ahci :00:17.0: 
flags: 64bit ncq sntf led clo only pio slum part ems deso sadm sds
  2024-04-19T17:18:50.668361+00:00 ubuntu-server kernel: intel-lpss 
:00:15.0: enabling device (0004 -> 0006)
  2024-04-19T17:18:50.668362+00:00 ubuntu-server kernel: idma64 idma64.0: Found 
Intel integrated DMA 64-bit
  2024-04-19T17:18:50.668363+00:00 ubuntu-server kernel: scsi host0: ahci
  2024-04-19T17:18:50.668364+00:00 ubuntu-server kernel: scsi host1: ahci
  2024-04-19T17:18:50.668370+00:00 ubuntu-server kernel: scsi host2: ahci
  2024-04-19T17:18:50.668371+00:00 ubuntu-server kernel: scsi host3: ahci
  2024-04-19T17:18:50.668372+00:00 ubuntu-server kernel: scsi host4: ahci
  2024-04-19T17:18:50.668373+00:00 ubuntu-server kernel: scsi host5: ahci
  2024-04-19T17:18:50.668374+00:00 ubuntu-server kernel: scsi host6: ahci
  2024-04-19T17:18:50.668380+00:00 ubuntu-server kernel: scsi host7: ahci
  2024-04-19T17:18:50.668383+00:00 ubuntu-server kernel: ata1: DUMMY
  2024-04-19T17:18:50.668385+00:00 ubuntu-server kernel: ata2: DUMMY
  2024-04-19T17:18:50.668386+00:00 ubuntu-server kernel: ata3: DUMMY
  2024-04-19T17:18:50.668387+00:00 ubuntu-server kernel: ata4: DUMMY
  2024-04-19T17:18:50.668388+00:00 ubuntu-server kernel: ata5: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8300 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668389+00:00 ubuntu-server kernel: ata6: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8380 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668390+00:00 ubuntu-server kernel: ata7: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8400 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668391+00:00 ubuntu-server kernel: ata8: SATA max 
UDMA/133 abar m2048@0x8000 port 0x8480 irq 123 lpm-pol 3
  2024-04-19T17:18:50.668392+00:00 ubuntu-server kernel: ahci :02:00.0: 
enabling device ( -> 0003)
  2024-04-19T17:18:50.668393+00:00 ubuntu-server kernel: ahci :02:00.0: SSS 
flag set, parallel bus scan disabled
  2024-04-19T17:18:50.668394+00:00 ubuntu-server kernel: ahci :02:00.0: 
AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
  2024-04-19T17:18:50.668395+00:00 ubuntu-server kernel: ahci :02:00.0: 
flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
  2024-04-19T17:18:50.668396+00:00 ubuntu-server kernel: scsi host8: ahci
  2024-04-19T17:18:50.668397+00:00 ubuntu-server kernel: scsi host9: ahci
  2024-04-19T17:18:50.668398+00:00 ubuntu-server kernel: ata9: SATA max 
UDMA/133 abar m512@0x8211 port 0x82110100 irq 130 lpm-pol 0
  2024-04-19T17:18:50.668399+00:00 ubuntu-server kernel: ata10: SATA max 
UDMA/133 abar m512@0x8211 port 0x82110180 irq 130 lpm-pol 0
  2024-04-19T17:18:50.668400+00:00 ubuntu-server kernel: intel-lpss 
:00:15.1: enabling device (0004 -> 0006)
  2024-04-19T17:18:50.668401+00:00 ubuntu-server kernel: idma64 idma64.1: Found 
Intel integrated DMA 64-bit
  2024-04-19T17:18:50.668407+00:00 ubuntu-server kernel: ata7: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668408+00:00 ubuntu-server kernel: ata9: SATA link down 
(SStatus 0 SControl 300)
  2024-04-19T17:18:50.668409+00:00 ubuntu-server kernel: ata5: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668410+00:00 ubuntu-server kernel: ata6: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668411+00:00 ubuntu-server kernel: ata8: SATA link down 
(SStatus 4 SControl 300)
  2024-04-19T17:18:50.668435+00:00 ubuntu-server kernel: ata10: SATA link down 
(SStatus 0 SControl 300)
  2024-04-19T17:18:50.668466+00:00 ubuntu-server kernel: raid6: avx2x4   gen() 
37283 MB/s
  2024-04-19T17:18:50.668467+00:00 ubuntu-server kernel: raid6: avx2x2   gen() 
39645 MB/s
  2024-04-19T17:18:50.668468+00:00 ubuntu-server kernel: raid6: avx2x1   gen() 
35756 MB/s
  2024-04-19T17:18:50.668469+00:00 ubuntu-server kernel: raid6: using algorithm 
avx2x2 gen() 39645 MB/s
  

[Kernel-packages] [Bug 2063290] Re: Jammy update: v5.15.153 upstream stable release

[Roxana Nicolescu]

** 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/2063290

Title:
  Jammy update: v5.15.153 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  io_uring/unix: drop usage of io_uring socket
  io_uring: drop any code related to SCM_RIGHTS
  rcu-tasks: Provide rcu_trace_implies_rcu_gp()
  bpf: Defer the free of inner map when necessary
  selftests: tls: use exact comparison in recv_partial
  ASoC: rt5645: Make LattePanda board DMI match more precise
  x86/xen: Add some null pointer checking to smp.c
  MIPS: Clear Cause.BD in instruction_pointer_set
  HID: multitouch: Add required quirk for Synaptics 0xcddc device
  gen_compile_commands: fix invalid escape sequence warning
  RDMA/mlx5: Fix fortify source warning while accessing Eth segment
  RDMA/mlx5: Relax DEVX access upon modify commands
  riscv: dts: sifive: add missing #interrupt-cells to pmic
  x86/mm: Move is_vsyscall_vaddr() into asm/vsyscall.h
  x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault()
  net/iucv: fix the allocation size of iucv_path_table array
  parisc/ftrace: add missing CONFIG_DYNAMIC_FTRACE check
  block: sed-opal: handle empty atoms when parsing response
  dm-verity, dm-crypt: align "struct bvec_iter" correctly
  scsi: mpt3sas: Prevent sending diag_reset when the controller is ready
  ALSA: hda/realtek - ALC285 reduce pop noise from Headphone port
  drm/amdgpu: Enable gpu reset for S3 abort cases on Raven series
  Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security
  firewire: core: use long bus reset on gap count error
  ASoC: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet
  Input: gpio_keys_polled - suppress deferred probe error for gpio
  ASoC: wm8962: Enable oscillator if selecting WM8962_FLL_OSC
  ASoC: wm8962: Enable both SPKOUTR_ENA and SPKOUTL_ENA in mono mode
  ASoC: wm8962: Fix up incorrect error message in wm8962_set_fll
  do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak
  s390/dasd: put block allocation in separate function
  s390/dasd: add query PPRC function
  s390/dasd: add copy pair setup
  s390/dasd: add autoquiesce feature
  s390/dasd: Use dev_*() for device log messages
  s390/dasd: fix double module refcount decrement
  fs/select: rework stack allocation hack for clang
  md: Don't clear MD_CLOSING when the raid is about to stop
  lib/cmdline: Fix an invalid format specifier in an assertion msg
  time: test: Fix incorrect format specifier
  rtc: test: Fix invalid format specifier.
  aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
  timekeeping: Fix cross-timestamp interpolation on counter wrap
  timekeeping: Fix cross-timestamp interpolation corner case decision
  timekeeping: Fix cross-timestamp interpolation for non-x86
  sched/fair: Take the scheduling domain into account in select_idle_core()
  wifi: ath10k: fix NULL pointer dereference in 
ath10k_wmi_tlv_op_pull_mgmt_tx_compl_ev()
  wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled
  wifi: b43: Stop/wake correct queue in PIO Tx path when QoS is disabled
  wifi: b43: Stop correct queue in DMA worker when QoS is disabled
  wifi: b43: Disable QoS for bcm4331
  wifi: wilc1000: fix declarations ordering
  wifi: wilc1000: fix RCU usage in connect path
  wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work
  wifi: wilc1000: fix multi-vif management when deleting a vif
  wifi: mwifiex: debugfs: Drop unnecessary error check for debugfs_create_dir()
  cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value
  cpufreq: Explicitly include correct DT includes
  cpufreq: mediatek-hw: Wait for CPU supplies before probing
  sock_diag: annotate data-races around sock_diag_handlers[family]
  inet_diag: annotate data-races around inet_diag_table[]
  bpftool: Silence build warning about calloc()
  af_unix: Annotate data-race of gc_in_progress in wait_for_unix_gc().
  cpufreq: mediatek-hw: Don't error out if supply is not found
  arm64: dts: imx8mm-kontron: Disable pullups for I2C signals on SL/BL i.MX8MM
  arm64: dts: imx8mm-kontron: Disable pullups for onboard UART signals on BL 
board
  arm64: dts: imx8mm-kontron: Add support for ultra high speed 

[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

[Andreas Hasenack]

Hi,

the test plan calls out for two additional steps which I don't see in
your verification:

> run hciconfig, the hci0 shows up.

> run checkbox testcase, it could pass.
> [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

Could you please clarify if you have performed these steps in mantic and
jammy?

Also, you said:
> enable proposed ppa

Could you please clarify if this was a PPA, or if it was the actual
official proposed pocket for mantic and jammy?

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

Title:
  Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

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

  [Impact]

  We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image
  and booting up, the bluetooth couldn't work at all. Checking the dmesg,
  the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi,
  but there is no this firmware in the linux-firmware of Jammy, and I
  also checked the Mantic and Noble, Mandic doesn't have this firmware too,
  Noble already has the firmware since the upstream linux-firmware integrated
  the intel/ibt-0180-4150.sfi last year.

  
  [Fix]

  Backport 4 commits from upstream linux-firmware, these 4 commits are all
  on intel/ibt-0180-4150.sfi|ddc

  
  [Test Case]

  Put the firmware into the /lib/firmware/intel/, reboot the machine,
  check dmesg, the bluetooth driver loads the firmware successfully,

  run hciconfig, the hci0 shows up.

  run checkbox testcase, it could pass.
  [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]

  
  [Where problems could occur]

  Probably could make the Intel AX201 BT adapter couldn't work, but the 
possibility
  is very low, we tested the firmware on different lenovo machines with the BT 
adapter
  AX201, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2063276] Re: Jammy update: v5.15.152 upstream stable release

[Roxana Nicolescu]

** 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/2063276

Title:
  Jammy update: v5.15.152 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  mmc: mmci: stm32: use a buffer for unaligned DMA requests
  mmc: mmci: stm32: fix DMA API overlapping mappings warning
  net: lan78xx: fix runtime PM count underflow on link stop
  ixgbe: {dis, en}able irqs in ixgbe_txrx_ring_{dis, en}able
  i40e: disable NAPI right after disabling irqs when handling xsk_pool
  tracing/net_sched: Fix tracepoints that save qdisc_dev() as a string
  geneve: make sure to pull inner header in geneve_rx()
  net: sparx5: Fix use after free inside sparx5_del_mact_entry
  net: ice: Fix potential NULL pointer dereference in ice_bridge_setlink()
  net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
  cpumap: Zero-initialise xdp_rxq_info struct before running XDP program
  net/rds: fix WARNING in rds_conn_connect_if_down
  netfilter: nft_ct: fix l3num expectations with inet pseudo family
  netfilter: nf_conntrack_h323: Add protection for bmp length out of range
  erofs: apply proper VMA alignment for memory mapped files on THP
  netrom: Fix a data-race around sysctl_netrom_default_path_quality
  netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser
  netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
  netrom: Fix a data-race around sysctl_netrom_transport_timeout
  netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
  netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay
  netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
  netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size
  netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout
  netrom: Fix a data-race around sysctl_netrom_routing_control
  netrom: Fix a data-race around sysctl_netrom_link_fails_count
  netrom: Fix data-races around sysctl_net_busy_read
  ALSA: usb-audio: Refcount multiple accesses on the single clock
  ALSA: usb-audio: Clear fixed clock rate at closing EP
  ALSA: usb-audio: Split endpoint setups for hw_params and prepare (take#2)
  ALSA: usb-audio: Properly refcounting clock rate
  ALSA: usb-audio: Apply mutex around snd_usb_endpoint_set_params()
  ALSA: usb-audio: Correct the return code from snd_usb_endpoint_set_params()
  ALSA: usb-audio: Avoid superfluous endpoint setup
  ALSA: usb-audio: Add quirk for Tascam Model 12
  ALSA: usb-audio: Add new quirk FIXED_RATE for JBL Quantum810 Wireless
  ALSA: usb-audio: Fix microphone sound on Nexigo webcam.
  ALSA: usb-audio: add quirk for RODE NT-USB+
  drm/amd/display: Fix uninitialized variable usage in core_link_ 'read_dpcd() 
& write_dpcd()' functions
  nfp: flower: add goto_chain_index for ct entry
  nfp: flower: add hardware offload check for post ct entry
  selftests/mm: switch to bash from sh
  selftests: mm: fix map_hugetlb failure on 64K page size systems
  xhci: process isoc TD properly when there was a transaction error mid TD.
  xhci: handle isoc Babble and Buffer Overrun events properly
  serial: max310x: use regmap methods for SPI batch operations
  serial: max310x: use a separate regmap for each port
  serial: max310x: prevent infinite while() loop in port startup
  drm/amd/pm: do not expose the API used internally only in kv_dpm.c
  drm/amdgpu: Reset IH OVERFLOW_CLEAR bit
  selftests: mptcp: decrease BW in simult flows
  hv_netvsc: use netif_is_bond_master() instead of open code
  hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed
  drm/amd/display: Re-arrange FPU code structure for dcn2x
  drm/amd/display: move calcs folder into DML
  drm/amd/display: remove DML Makefile duplicate lines
  drm/amd/display: Increase frame-larger-than for all display_mode_vba files
  getrusage: add the "signal_struct *sig" local variable
  getrusage: move thread_group_cputime_adjusted() outside of lock_task_sighand()
  getrusage: use __for_each_thread()
  getrusage: use sig->stats_lock rather than lock_task_sighand()
  proc: Use task_is_running() for wchan in /proc/$pid/stat
  fs/proc: do_task_stat: move thread_group_cputime_adjusted() outside of 

[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms

[Roxana Nicolescu]

** Changed in: linux (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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2054487

Title:
  There is sound from the speakers and headphones at the same time on
  Oasis 14 and 16 platforms

Status in HWE Next:
  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 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:
  Fix Released
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]
  While playing audio with headset plugged, the sound play from both headset 
and internal speaker.

  [Fix]
  The commit from v6.8-rc5 fixes the issue
  fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform

  To avoid conflict pull in one more quirk from v6.8-rc3
  fcfc9f711d1e ALSA: hda/realtek - Add speaker pin verbtable for Dell dual 
speaker platform

  [Test Case]
  1. play an audio file.
  2. plug 3.5mm headset.
  3. select "headset".
  4. sound will play only from headset

  [Where problems could occur]
  It simply added 2 IDs to the table, should have no impact to the existing 
machines.
  The other commit add one more ID to the table and disable speaker passthrough.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2060919] Re: cifs: Copying file to same directory results in page fault

[windracer]

If I upgrade to 24.04 which just came out today with the 6.8 kernel,
would that also fix this?

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

Title:
  cifs: Copying file to same directory results in page fault

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

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

  [Impact]

  Copying or modifying a file to the same directory within a cifs mount
  results in a page fault, and the process that initiated the copy being
  killed. This could be cp, nautilus, etc.

  This results in the following oops:

  BUG: unable to handle page fault for address: fffe
  #PF: supervisor read access in kernel mode
  #PF: error_code(0x) - not-present page
  PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0
  Oops:  [#1] PREEMPT SMP NOPTI
  CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic 
#28-Ubuntu
  RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 
89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 
f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  RAX:  RBX: fffe RCX: 
  RDX:  RSI:  RDI: 
  RBP: aab6865ffc28 R08: 0001 R09: 
  R10: 00023854 R11:  R12: 
  R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70
  FS: 7bd4d594b6c0() GS:90753f80() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: fffe CR3: 00017022a000 CR4: 00750ef0
  PKRU: 5554
  Call Trace:
  
  ? show_regs+0x6d/0x80
  ? __die+0x24/0x80
  ? page_fault_oops+0x99/0x1b0
  ? kernelmode_fixup_or_oops+0xb2/0x140
  ? __bad_area_nosemaphore+0x1a5/0x2c0
  ? bad_area_nosemaphore+0x16/0x30
  ? do_kern_addr_fault+0x7b/0xa0
  ? exc_page_fault+0x1a4/0x1b0
  ? asm_exc_page_fault+0x27/0x30
  ? cifs_flush_folio+0x41/0xf0 [cifs]
  ? cifs_flush_folio+0x37/0xf0 [cifs]
  cifs_remap_file_range+0x172/0x660 [cifs]
  do_clone_file_range+0x101/0x2d0
  vfs_clone_file_range+0x3f/0x150
  ioctl_file_clone+0x52/0xc0
  do_vfs_ioctl+0x68f/0x910
  ? __fget_light+0xa5/0x120
  __x64_sys_ioctl+0x7d/0xf0
  do_syscall_64+0x59/0x90
  ? kmem_cache_free+0x22/0x3e0
  ? putname+0x5b/0x80
  ? exit_to_user_mode_prepare+0x30/0xb0
  ? syscall_exit_to_user_mode+0x37/0x60
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90
  ? do_syscall_64+0x68/0x90

  There is no known workaround.

  [Fix]

  The stacktrace is very similar to a regression reported to upstream
  6.1.y:

  https://lore.kernel.org/linux-
  mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/

  The thread mentions that:

  commit 7b2404a886f8b91250c31855d287e632123e1746
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746

  introduced the issue to Debian's 6.1 kernel.

  This got backported to Ubuntu in:

  commit 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Author: David Howells 
  Date: Fri Dec 1 00:22:00 2023 +
  Subject: cifs: Fix flushing, invalidation and file size with copy_file_range()

  $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288
  Ubuntu-6.5.0-20.20~107

  Which we have been using for some time now, and is not the culprit.

  Reading the regression mailing list thread, they mention that things
  work differently in 6.1:

  > Yeah.  __filemap_get_folio() works differently in v6.1.y. There it returns a
  > folio or NULL.  In 6.7 it returns a folio or a negative error code.  The 
error
  > check in cifs_flush_folio() needs to change to something like:
  >
  > folio = filemap_get_folio(inode->i_mapping, index);
  > if (!folio)
  > return -ENOMEM;
  >
  > David 

  6.1.y then got a specific patch to fix the issue in 6.1, which is:

  commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Author: Steve French 
  Date: Fri Jan 12 23:08:51 2024 -0600
  Subject: cifs: fix flushing folio regression for 6.1 backport
  Link: 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1

  $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1
  Ubuntu-6.5.0-27.28~162

  Since the Ubuntu mantic kernel consumes both 6.1.y and 6.7.y / 6.8.y
  stable patches, this patch was applied to mantic's 6.5 kernel by
  mistake, and contains the wrong logic for how __filemap_get_folio()
  works in 6.5.

  The fix is to revert "cifs: fix flushing 

[Kernel-packages] [Bug 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)

[Richard van der Hoff]

Oddly, I don't seem to be able to reproduce this problem on an upstream
6.8 kernel. I'll try with a rebuild of 6.5.0-27-generic instead.

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

Title:
  Freezing user space processes failed after 20.008 seconds (1 tasks
  refusing to freeze, wq_busy=0)

Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Sometimes, when trying to shut down or suspend my laptop, it gets
  stuck on the console screen. If I was suspending, it eventually gives
  up and goes back to the X session. During a shutdown it hangs forever
  and the only solution seems to be to force a reboot with Magic-SysRq.

  The following appears in `kern.log`:

  ```
  Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes 
failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
  Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D 
stack:0 pid:2408  ppid:2398   flags:0x0006
  Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace:
  Apr 12 08:59:54 xps9320 kernel: [173172.521755]  
  Apr 12 08:59:54 xps9320 kernel: [173172.524099]  __schedule+0x2cb/0x750
  Apr 12 08:59:54 xps9320 kernel: [173172.526333]  schedule+0x63/0x110
  Apr 12 08:59:54 xps9320 kernel: [173172.528585]  
snd_power_ref_and_wait+0xe5/0x140 [snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.530825]  ? 
__pfx_autoremove_wake_function+0x10/0x10
  Apr 12 08:59:54 xps9320 kernel: [173172.533103]  snd_ctl_elem_info+0x4f/0x1b0 
[snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.535354]  
snd_ctl_elem_info_user+0x59/0xc0 [snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.537598]  snd_ctl_ioctl+0x1d4/0x650 
[snd]
  Apr 12 08:59:54 xps9320 kernel: [173172.539846]  ? __fget_light+0xa5/0x120
  Apr 12 08:59:54 xps9320 kernel: [173172.542082]  __x64_sys_ioctl+0xa0/0xf0
  Apr 12 08:59:54 xps9320 kernel: [173172.544334]  do_syscall_64+0x58/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.546566]  ? 
syscall_exit_to_user_mode+0x37/0x60
  Apr 12 08:59:54 xps9320 kernel: [173172.548838]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.551085]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.553342]  ? 
syscall_exit_to_user_mode+0x37/0x60
  Apr 12 08:59:54 xps9320 kernel: [173172.96]  ? do_syscall_64+0x67/0x90
  Apr 12 08:59:54 xps9320 kernel: [173172.557828]  ? common_interrupt+0x54/0xb0
  Apr 12 08:59:54 xps9320 kernel: [173172.560075]  
entry_SYSCALL_64_after_hwframe+0x6e/0xd8
  Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f
  Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 
EFLAGS: 0246 ORIG_RAX: 0010
  Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 
7ffef20729b0 RCX: 70f3adb1a94f
  Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: 
c1105511 RDI: 0022
  Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 
65107d2b6070 R09: 0004
  Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 
0246 R12: 65107d2ee100
  Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 
7ffef2072b30 R15: 7ffef2072ad0
  Apr 12 08:59:54 xps9320 kernel: [173172.578308]  
  ```

  
  Another point of interest is that, when in this situation:
   * `lsusb` hangs after printing out a few lines
   * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent 
appears to be trying to check for smartcards.

  So I guess there is some sort of deadlock in the USB subsystem which
  is causing all the other problems?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 09:42:52 2024
  InstallationDate: Installed on 2022-06-28 (653 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  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-signed-hwe-6.5/+bug/2061091/+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 2063495] [NEW] Kernel soft lockup occures in `fib6_select_path` function

[Omid]

Public bug reported:

We operate a Linux-based cluster of edge routers within a highly dynamic
setting where BGP-advertised routes constantly evolve due to new next
hop destinations frequently appearing and disappearing. In areas
experiencing significant IPv6 traffic, we periodically face kernel soft
lockups. Upon investigation, these lockups seem to occur during the
traversal of the multipath circular linked-list, for finding the optimal
path, in the fib6_select_path function, specifically while iterating
through the siblings in the multipath linked-list. The problem typically
arises when the linked list is unexpectedly deleted (its reference count
reaches zero), leading to an infinite loop. This results in a soft
lockup that, if not resolved, triggers a system panic due to the
watchdog timer.

It's worth noting that this is a longstanding issue we've been dealing
with for about a year. Despite switching between different kernel
versions, the problem persists.

Attached please find the `.crash` report generated by `apport-cli`.


Thanks,
Omid

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Apr 23 00:00:14 2024
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy uec-images

** Attachment added: "report extracted from the core dump by `apport-cli`"
   
https://bugs.launchpad.net/bugs/2063495/+attachment/5770523/+files/linux-image-6.5.0-27-generic-202404231849.crash

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

Title:
  Kernel soft lockup occures in `fib6_select_path` function

Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  We operate a Linux-based cluster of edge routers within a highly
  dynamic setting where BGP-advertised routes constantly evolve due to
  new next hop destinations frequently appearing and disappearing. In
  areas experiencing significant IPv6 traffic, we periodically face
  kernel soft lockups. Upon investigation, these lockups seem to occur
  during the traversal of the multipath circular linked-list, for
  finding the optimal path, in the fib6_select_path function,
  specifically while iterating through the siblings in the multipath
  linked-list. The problem typically arises when the linked list is
  unexpectedly deleted (its reference count reaches zero), leading to an
  infinite loop. This results in a soft lockup that, if not resolved,
  triggers a system panic due to the watchdog timer.

  It's worth noting that this is a longstanding issue we've been dealing
  with for about a year. Despite switching between different kernel
  versions, the problem persists.

  Attached please find the `.crash` report generated by `apport-cli`.

  
  Thanks,
  Omid

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 23 00:00:14 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.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-signed-hwe-6.5/+bug/2063495/+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 2063497] [NEW] MIPI camera on Lenovo Carbon X1 will not work

[Martin D. Weinberg]

Public bug reported:

I followed the suggestions here for handling the Intel MIPI camera
replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo

Perhaps I should have installed 22.04?  Anyway, this is a new laptop so
I went with the new release.

I tried both the generic and oem kernel.  Same.  The pertinent message
seems to be:

[   18.420012] intel-ipu6 :00:05.0: Direct firmware load for 
intel/ipu6ep_fw.bin failed with error -2
[   18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed
[   18.420023] intel-ipu6: probe of :00:05.0 failed with error -2

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

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

Title:
  MIPI  camera on Lenovo Carbon X1 will not work

Status in linux package in Ubuntu:
  New

Bug description:
  I followed the suggestions here for handling the Intel MIPI camera
  replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo

  Perhaps I should have installed 22.04?  Anyway, this is a new laptop
  so I went with the new release.

  I tried both the generic and oem kernel.  Same.  The pertinent message
  seems to be:

  [   18.420012] intel-ipu6 :00:05.0: Direct firmware load for 
intel/ipu6ep_fw.bin failed with error -2
  [   18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed
  [   18.420023] intel-ipu6: probe of :00:05.0 failed with error -2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+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 2063495] Re: Kernel soft lockup occures in `fib6_select_path` function

[Omid]

** Description changed:

  We operate a Linux-based cluster of edge routers within a highly dynamic
  setting where BGP-advertised routes constantly evolve due to new next
  hop destinations frequently appearing and disappearing. In areas
  experiencing significant IPv6 traffic, we periodically face kernel soft
  lockups. Upon investigation, these lockups seem to occur during the
  traversal of the multipath circular linked-list, for finding the optimal
  path, in the fib6_select_path function, specifically while iterating
  through the siblings in the multipath linked-list. The problem typically
- arises when the linked list is unexpectedly deleted (its reference count
- reaches zero), leading to an infinite loop. This results in a soft
- lockup that, if not resolved, triggers a system panic due to the
- watchdog timer.
+ arises when the linked list is unexpectedly deleted (its head eference
+ count equals zero), leading to an infinite loop. This results in a soft
+ lockup that triggers a system panic due to the watchdog timer.
  
  It's worth noting that this is a longstanding issue we've been dealing
  with for about a year. Despite switching between different kernel
  versions, the problem persists.
  
  Attached please find the `.crash` report generated by `apport-cli`.
- 
  
  Thanks,
  Omid
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 23 00:00:14 2024
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  We operate a Linux-based cluster of edge routers within a highly dynamic
  setting where BGP-advertised routes constantly evolve due to new next
  hop destinations frequently appearing and disappearing. In areas
  experiencing significant IPv6 traffic, we periodically face kernel soft
  lockups. Upon investigation, these lockups seem to occur during the
  traversal of the multipath circular linked-list, for finding the optimal
  path, in the fib6_select_path function, specifically while iterating
  through the siblings in the multipath linked-list. The problem typically
- arises when the linked list is unexpectedly deleted (its head eference
- count equals zero), leading to an infinite loop. This results in a soft
- lockup that triggers a system panic due to the watchdog timer.
+ arises when the linked list is unexpectedly deleted (its list-head
+ reference count equals zero), leading to an infinite loop. This results
+ in a soft lockup that triggers a system panic due to the watchdog timer.
  
  It's worth noting that this is a longstanding issue we've been dealing
  with for about a year. Despite switching between different kernel
  versions, the problem persists.
  
  Attached please find the `.crash` report generated by `apport-cli`.
  
  Thanks,
  Omid
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr 23 00:00:14 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Kernel soft lockup occures in `fib6_select_path` function

Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  We operate a Linux-based cluster of edge routers within a highly
  dynamic setting where BGP-advertised routes constantly evolve due to
  new next hop destinations frequently appearing and disappearing. In
  areas experiencing significant IPv6 traffic, we periodically face
  kernel soft lockups. Upon investigation, these lockups seem to occur
  during the traversal of the multipath circular linked-list, for
  finding the optimal path, in the fib6_select_path function,
  specifically while iterating through the siblings in the multipath
  linked-list. The problem typically arises when the linked list is
  unexpectedly deleted (its list-head reference count equals zero),
  leading to an infinite loop. This results in a soft lockup that
  triggers a system panic due to the watchdog timer.

  It's worth noting that this is a longstanding issue we've been dealing
  with 

[Kernel-packages] [Bug 2054391] Re: Fix CPU thermal sensors enumeration

[Lucas Kanashiro]

Thanks for the patch @Kai-Heng! I took a look and in general it looks
good, but I'd like to ask you to add some DEP-3 headers [1] to your
patch, that will give us (packagers) more context when revisiting this
package for whatever reason.

Now a personal opinion, I like when the patch file name is listed in the
changelog entry ("* d/p/0016-Fixed-enumeration-of-cpu-thermal-
sensors.patch: "). It makes a direct link between
the change listed there and the file actually fixing it.

Once you address my first comment at least (the second one is not
mandatory), please subscribe ~ubuntu-sponsors again (I am unsubscribing
it now).

[1] https://dep-team.pages.debian.net/deps/dep3/

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

Title:
  Fix  CPU thermal sensors enumeration

Status in HWE Next:
  New
Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  Some CPU sensors are not enumerated, this can make thermald deviates from the 
correct behavior of the CPU TDP.

  [Fix]
  Traverse all sensors under hwmon sysfs directory to make sure everything is 
enumerated.

  [Test]
  Check the output of thermald. Once the fix is in place, thermal zones that 
are previously omitted now shows up:
  [INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1

  [Where problems could occur]
  Since the new logic traverse the whole hwmon sysfs, the startup time can take 
slightly longer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+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