[Kernel-packages] [Bug 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62

[Salem Yaslim]

Somehow it boot now from third time in same PC Case

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

Title:
  Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block  failed
  -62

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello, I'm facing this issue before few months after software upgrade,

  Distro: Kubuntu 23.10
  Kernel: Linux kernel 6.5.0-17-generic
  Linux Firmware: 20230919.git3672ccab-0ubuntu2.5

  My Specs:
  CPU: Ryzen 9 7950X
  RAM: 64GB = 16GB × 4 5200/MT DDR5
  GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire)
  Motherboard: Gigabyte B650M GAMING X AX

  NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at
  all

  there other users faced same issue (look like because linux-firmware):
  https://ubuntuforums.org/showthread.php?t=2489556

  My dmesg logs attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62

[Salem Yaslim]

Today I tried to unplug everything and start the PC in workbench (lay
motherboard down and connected the GPU, CPU and CPU Cooling AIO without
case and fans except AIO Fans)

the PC work fine two times in row and boot without issue then I plug
everything back to the case and the system failed to boot

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

Title:
  Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block  failed
  -62

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello, I'm facing this issue before few months after software upgrade,

  Distro: Kubuntu 23.10
  Kernel: Linux kernel 6.5.0-17-generic
  Linux Firmware: 20230919.git3672ccab-0ubuntu2.5

  My Specs:
  CPU: Ryzen 9 7950X
  RAM: 64GB = 16GB × 4 5200/MT DDR5
  GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire)
  Motherboard: Gigabyte B650M GAMING X AX

  NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at
  all

  there other users faced same issue (look like because linux-firmware):
  https://ubuntuforums.org/showthread.php?t=2489556

  My dmesg logs attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

[Brett Grandbois]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

Status in linux package in Ubuntu:
  New

Bug description:
  Since I've upgraded my server's to Ubuntu 22.04.4  I'm facing problems to 
make my fcoe setup to work correctly.
  Firstly, some context. We have a HPE Synergy appliance with a bunch of 
Synergy 480 Gen10 servers still running Ubuntu 20.04. 
  Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi Function 
network adapters with two of them dedicated to storage communication through 
FCoE.

  Recently, I've upgraded one of them to Ubuntu 22.04 and realized that after 
the upgrade, all the Fibre Channel LUNs have disappeared. During the diagnostic 
process I noticed that both network (bnx2x) and fcoe (fcoe, bnx2fc) kernel 
drivers have been loaded properly, FCoE vlans were correctly detected by 
fcoe-utils, but there was no connection between the server and the storage and 
the server could not detect any LUN.
  I also noticed that fcoeadm was reporting the following status:

  # fcoeadm -i
  Description:  BCM57840 NetXtreme II Ethernet Multi Function
  Revision: 11
  Manufacturer: Broadcom Inc. and subsidiaries
  Serial Number:9440C953B7F0

  Driver:   bnx2x Unknown
  Number of Ports:  1

  Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f2.4093-fco
  OS Device Name:host2
  Node Name: 0x1a3d2725
  Port Name: 0x1a3d2724
  Fabric Name:   0x0
  Speed: 20 Gbit
  Supported Speed:   1 Gbit, 10 Gbit
  MaxFrameSize:  2048 bytes
  FC-ID (Port ID):   0x
  State: Offline
  Description:  BCM57840 NetXtreme II Ethernet Multi Function
  Revision: 11
  Manufacturer: Broadcom Inc. and subsidiaries
  Serial Number:9440C953B7F0

  Driver:   bnx2x Unknown
  Number of Ports:  1

  Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f3.4094-fco
  OS Device Name:host3
  Node Name: 0x1a3d2727
  Port Name: 0x1a3d2726
  Fabric Name:   0x0
  Speed: 20 Gbit
  Supported Speed:   1 Gbit, 10 Gbit
  MaxFrameSize:  2048 bytes
  FC-ID (Port ID):   0x
  State: Offline

  Although most of information displayed was correct, the port state was
  always offline (what explains no storage connectivity) and the FC-ID
  reported was 0x for both interfaces.

  Supposing that something went wrong during the upgrade process, I decided to 
make a fresh install of the server and, for my surprise, the fcoe ports went 
online and all luns were detected correctly.
  Unfortunately, the ports went offline again after a dist-upgrade.
  Trying to understand what was happening I performed another fresh install of 
the Ubuntu 22.04, but this time collecting some information about kernel and 
packages versions from before and after dist-upgrade.
  What I discovered was that all packages related (fcoe-utils, lldpad) had the 
same versions before and after, the only exception was the kernel itself. 
Before the dist-upgrade the kernel in use was 5.15.0-25-generic and after 
dist-upgrade the kernel was 5.15.0-100-generic.
  Suspecting a kernel problem I installed and booted different kernel versions 
from 5.15.0-25 and 5.15.0-100 and discovered that the problem probably was 
introduced with kernel 5.15.0-94, since it is the first version showing the 
describe behavior.
  Looking at the changelog of linux-modules package, I noticed some changes on 
fcoe and other scsi modules, right after the 5.15.0-91 version. 
  Could those changes be the cause of the behavior observed on my server or 
just a coincidence? Is there any fix to it?

  Thanks in advance.

  Anderson

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-94-generic 5.15.0-94.104
  ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136
  Uname: Linux 5.15.0-94-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 14 11:03 seq
   crw-rw 1 root audio 116, 33 Mar 14 11:03 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Thu Mar 14 14:57:14 2024
  HibernationDevice: 

[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64

[Seth Arnold]

I added llvm and gcc toolchains to the affected packages list here based
on some internet reports, not my own testing:

https://stackoverflow.com/questions/77894856/possible-bug-in-gcc-sanitizers
https://stackoverflow.com/questions/77826203/addresssanitizer-randomly-throws-sigsegv-with-no-explanation?noredirect=1=1
https://github.com/llvm/llvm-project/commit/fb77ca05ffb4f8e666878f2f6718a9fb4d686839
https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/commit/15cbe5ecc28cc4f52a38bad5a5cecaaa8a66a020
https://github.com/actions/runner-images/issues/9491#issuecomment-1996621369

This looks like the most useful comment from the github runners issue:
https://github.com/actions/runner-
images/issues/9491#issuecomment-1989718917 -- I strongly suggest
starting here.

And thanks to Daniel Stenberg for bringing this to our attention:
https://mastodon.social/@bagder/112093452688780674
https://answers.launchpad.net/ubuntu/+source/llvm-toolchain-14/+question/709571

Thanks

** Bug watch added: github.com/actions/runner-images/issues #9491
   https://github.com/actions/runner-images/issues/9491

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

Title:
  Autopkgtest failures on amd64

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in gcc-12 package in Ubuntu:
  New
Status in gcc-13 package in Ubuntu:
  New
Status in gcc-14 package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in Ubuntu:
  New
Status in llvm-toolchain-16 package in Ubuntu:
  New
Status in llvm-toolchain-17 package in Ubuntu:
  New
Status in llvm-toolchain-18 package in Ubuntu:
  New
Status in gcc-10 source package in Noble:
  New
Status in gcc-11 source package in Noble:
  New
Status in gcc-12 source package in Noble:
  New
Status in gcc-13 source package in Noble:
  New
Status in gcc-14 source package in Noble:
  New
Status in gcc-8 source package in Noble:
  New
Status in gcc-9 source package in Noble:
  New
Status in linux source package in Noble:
  Confirmed
Status in llvm-toolchain-14 source package in Noble:
  Confirmed
Status in llvm-toolchain-15 source package in Noble:
  New
Status in llvm-toolchain-16 source package in Noble:
  New
Status in llvm-toolchain-17 source package in Noble:
  New
Status in llvm-toolchain-18 source package in Noble:
  New

Bug description:
  Some tests related to the address sanitizer are occasionally failing
  on amd64 (also for llvm-toolchain-15 and 16):

  --
  FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
  746s  TEST 'LLVM regression suite :: test_leaksan.c' 
FAILED 
  746s Script:
  746s --
  746s : 'RUN: at line 4';   /usr/bin/clang-14 -o 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
-fsanitize=address -g 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
  746s : 'RUN: at line 5';   env ASAN_OPTIONS="log_path=stdout:exitcode=0"  
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s : 'RUN: at line 6';   grep -q "detected memory leaks" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s --
  746s Exit Code: 139
  746s
  746s Command Output (stderr):
  746s --
  746s 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
 line 3:  3335 Segmentation fault  (core dumped) env 
ASAN_OPTIONS="log_path=stdout:exitcode=0" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  --

  If you run the test manually you'll notice that it works but
  eventually crashes:

  
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8631==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5e9c3441ed12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5e9c3445acb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x7e84e1e280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  

[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64

[Seth Arnold]

** Also affects: llvm-toolchain-15 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: llvm-toolchain-16 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: llvm-toolchain-17 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: llvm-toolchain-18 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-9 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-10 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-11 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-12 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-13 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gcc-14 (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/2048768

Title:
  Autopkgtest failures on amd64

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in gcc-12 package in Ubuntu:
  New
Status in gcc-13 package in Ubuntu:
  New
Status in gcc-14 package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in Ubuntu:
  New
Status in llvm-toolchain-16 package in Ubuntu:
  New
Status in llvm-toolchain-17 package in Ubuntu:
  New
Status in llvm-toolchain-18 package in Ubuntu:
  New
Status in gcc-10 source package in Noble:
  New
Status in gcc-11 source package in Noble:
  New
Status in gcc-12 source package in Noble:
  New
Status in gcc-13 source package in Noble:
  New
Status in gcc-14 source package in Noble:
  New
Status in gcc-8 source package in Noble:
  New
Status in gcc-9 source package in Noble:
  New
Status in linux source package in Noble:
  Confirmed
Status in llvm-toolchain-14 source package in Noble:
  Confirmed
Status in llvm-toolchain-15 source package in Noble:
  New
Status in llvm-toolchain-16 source package in Noble:
  New
Status in llvm-toolchain-17 source package in Noble:
  New
Status in llvm-toolchain-18 source package in Noble:
  New

Bug description:
  Some tests related to the address sanitizer are occasionally failing
  on amd64 (also for llvm-toolchain-15 and 16):

  --
  FAIL: LLVM regression suite :: test_leaksan.c (38 of 45)
  746s  TEST 'LLVM regression suite :: test_leaksan.c' 
FAILED 
  746s Script:
  746s --
  746s : 'RUN: at line 4';   /usr/bin/clang-14 -o 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
-fsanitize=address -g 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c
  746s : 'RUN: at line 5';   env ASAN_OPTIONS="log_path=stdout:exitcode=0"  
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s : 'RUN: at line 6';   grep -q "detected memory leaks" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  746s --
  746s Exit Code: 139
  746s
  746s Command Output (stderr):
  746s --
  746s 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script:
 line 3:  3335 Segmentation fault  (core dumped) env 
ASAN_OPTIONS="log_path=stdout:exitcode=0" 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 
2>&1 > 
/tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out
  --

  If you run the test manually you'll notice that it works but
  eventually crashes:

  
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8631==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5e9c3441ed12 in __interceptor_malloc 
(/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12)
 (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193)
  #1 0x5e9c3445acb8 in main 
/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7
  #2 0x7e84e1e280cf  (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: 
f0b834daa3d05a80967e9ec2f990a1ea71c958fa)

  SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s).
  
ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ 
./test_leaksan.c.tmp

  =
  ==8634==ERROR: LeakSanitizer: detected memory leaks

  Direct leak of 7 byte(s) in 1 object(s) allocated from:
  #0 0x5f19be5f6d12 in 

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

[Ubuntu SRU Bot]

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

systemd/249.11-0ubuntu3.12 (arm64)


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

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

[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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms

[Anthony Wong]

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

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

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

Title:
  Simplify kcontrol naming on Intel MTL platforms

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:
  New
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  New
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]
  We found some laptops from Lenovo and HP with Intel MTL platform suffer the 
same MIC-Mute led not working problem just like lp:2049569.

  [Fix]
  lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly 
with MTL SoF FW. However, Lenovo and HP machines requires the additional 
patches from 
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
 to fix the kcontrol naming problem to align with the MTL SoF FW.

  [Test Case]
  1. Make sure the latest firmware-sof is installed.
  2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD 
icon.
  3. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.

  [Where problems could occur]
  It's only required for new sof-audio-pci-intel-mtl driver. The impact should 
be restricting. We may need more MTL machines to make sure the behavior is the 
aligned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2054121] Re: Random Freezing

[Daniel van Vugt]

1. Edit /etc/default/grub and add them to GRUB_CMDLINE_LINUX_DEFAULT=...

2. Run: sudo update-grub

3. Reboot.

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

Title:
  Random Freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random lockups in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 09:08:41 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
  InstallationDate: Installed on 2024-02-16 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3JKT3CA
  dmi.board.name: 32DD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305435660291
  dmi.chassis.type: 35
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
  dmi.product.family: ThinkStation P350 Tiny
  dmi.product.name: 30EF004VUS
  dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
  dmi.product.version: ThinkStation P350 Tiny
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2057484] Re: kernel worker event freezes during traffic on iwlwifi

[Mohegan]

With Mantic, the connection freezes after some times with 6.5.0-21
kernel...

So, I switched to Ubuntu 24.04 / Noble for testing. The connection is
much stable (but not MLO support).

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

Title:
  kernel worker event freezes during traffic  on iwlwifi

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

Bug description:
  With traffic on Intel Wifi 7 BE200 card, For a while kernel enter 100%
  cpu usage on a worker event thread and kworker/0:0-events_freezable is
  in D state.  System highly unresponsive during this time.

  Happens in 6.5.0-25, does not happen in 6.5.0-17

  
  Description:Ubuntu 22.04.4 LTS
  Release:22.04

Installed: 6.5.0-25.25~22.04.1
Candidate: 6.5.0-25.25~22.04.1
Version table:
   *** 6.5.0-25.25~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  linux-modules-6.5.0-25-generic:
Installed: 6.5.0-25.25~22.04.1
Candidate: 6.5.0-25.25~22.04.1
Version table:
   *** 6.5.0-25.25~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  filename:   
/lib/modules/6.5.0-25-generic/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
  license:GPL
  description:Intel(R) Wireless WiFi driver for Linux
  firmware:   iwlwifi-100-5.ucode
  firmware:   iwlwifi-1000-5.ucode
  firmware:   iwlwifi-135-6.ucode
  firmware:   iwlwifi-105-6.ucode
  firmware:   iwlwifi-2030-6.ucode
  firmware:   iwlwifi-2000-6.ucode
  firmware:   iwlwifi-5150-2.ucode
  firmware:   iwlwifi-5000-5.ucode
  firmware:   iwlwifi-6000g2b-6.ucode
  firmware:   iwlwifi-6000g2a-6.ucode
  firmware:   iwlwifi-6050-5.ucode
  firmware:   iwlwifi-6000-6.ucode
  firmware:   iwlwifi-7265D-29.ucode
  firmware:   iwlwifi-7265-17.ucode
  firmware:   iwlwifi-3168-29.ucode
  firmware:   iwlwifi-3160-17.ucode
  firmware:   iwlwifi-7260-17.ucode
  firmware:   iwlwifi-8265-36.ucode
  firmware:   iwlwifi-8000C-36.ucode
  firmware:   iwlwifi-9260-th-b0-jf-b0-46.ucode
  firmware:   iwlwifi-9000-pu-b0-jf-b0-46.ucode
  firmware:   iwlwifi-cc-a0-77.ucode
  firmware:   iwlwifi-QuZ-a0-jf-b0-77.ucode
  firmware:   iwlwifi-QuZ-a0-hr-b0-77.ucode
  firmware:   iwlwifi-Qu-b0-jf-b0-77.ucode
  firmware:   iwlwifi-Qu-c0-hr-b0-77.ucode
  firmware:   iwlwifi-Qu-b0-hr-b0-77.ucode
  firmware:   iwlwifi-ma-b0-mr-a0-83.ucode
  firmware:   iwlwifi-ma-b0-gf4-a0-83.ucode
  firmware:   iwlwifi-ma-b0-gf-a0-83.ucode
  firmware:   iwlwifi-ma-b0-hr-b0-83.ucode
  firmware:   iwlwifi-ma-a0-mr-a0-83.ucode
  firmware:   iwlwifi-ma-a0-gf4-a0-83.ucode
  firmware:   iwlwifi-ma-a0-gf-a0-83.ucode
  firmware:   iwlwifi-ma-a0-hr-b0-83.ucode
  firmware:   iwlwifi-ty-a0-gf-a0-83.ucode
  firmware:   iwlwifi-so-a0-gf-a0-83.ucode
  firmware:   iwlwifi-so-a0-hr-b0-83.ucode
  firmware:   iwlwifi-so-a0-jf-b0-83.ucode
  firmware:   iwlwifi-gl-c0-fm-c0-83.ucode
  firmware:   iwlwifi-gl-b0-fm-b0-83.ucode
  firmware:   iwlwifi-bz-a0-fm4-b0-83.ucode
  firmware:   iwlwifi-bz-a0-fm-c0-83.ucode
  firmware:   iwlwifi-bz-a0-fm-b0-83.ucode
  firmware:   iwlwifi-bz-a0-gf4-a0-83.ucode
  firmware:   iwlwifi-bz-a0-gf-a0-83.ucode
  firmware:   iwlwifi-bz-a0-hr-b0-83.ucode
  firmware:   iwlwifi-sc-a0-wh-a0-83.ucode
  firmware:   iwlwifi-sc-a0-gf4-a0-83.ucode
  firmware:   iwlwifi-sc-a0-gf-a0-83.ucode
  firmware:   iwlwifi-sc-a0-hr-b0-83.ucode
  firmware:   iwlwifi-sc-a0-hr-b0-83.ucode
  firmware:   iwlwifi-sc-a0-fm-c0-83.ucode
  firmware:   iwlwifi-sc-a0-fm-b0-83.ucode
  srcversion: CE34BB7E0E287E10FEC1E13
  alias:  pci:v8086dE440sv*sd*bc*sc*i*
  alias:  pci:v8086d7740sv*sd*bc*sc*i*
  alias:  pci:v8086dA840sv*sd*bc*sc*i*
  alias:  pci:v8086d272Bsv*sd*bc*sc*i*
  alias:  pci:v8086d2727sv*sd*bc*sc*i*
  alias:  pci:v8086d7E40sv*sd*bc*sc*i*
  alias:  pci:v8086d2729sv*sd*bc*sc*i*
  alias:  pci:v8086d7F70sv*sd*bc*sc*i*
  alias:  pci:v8086d54F0sv*sd*bc*sc*i*
  alias:  pci:v8086d51F1sv*sd*bc*sc*i*
  alias:  pci:v8086d51F1sv*sd*bc*sc*i*
  alias:  pci:v8086d51F0sv*sd*bc*sc*i*
  alias:  pci:v8086d7AF0sv*sd*bc*sc*i*
  alias:  pci:v8086d7A70sv*sd*bc*sc*i*
  alias:  pci:v8086d2725sv*sd*bc*sc*i*
  alias:  

[Kernel-packages] [Bug 2049922] Re: PCI ATS quirk patch needed for IDPF

[Ubuntu Kernel Bot]

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


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


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


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

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

Title:
  PCI ATS quirk patch needed for IDPF

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp-4.15 package in Ubuntu:
  New
Status in linux-gcp source package in Bionic:
  In Progress
Status in linux-gcp-4.15 source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Request from Google to include Intel patches for IDPF support if used from
  out-of-tree module to prevent system instability.

  [Fixes]
  f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
  a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")

  
  [Test Case]

  * Compile test
  * Boot test
  * Test on non-IDPF instance
  * Tested by Google

  [Where things could go wrong]

  * Low chance of regression, changes very isolated

  [Other Info]

  * SF #00376470

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2024-March/149567.html


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

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

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux-azure (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: linux-azure (Ubuntu Mantic)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Azure: hv: hyperv.h: Replace one-element array with flexible-array
  member

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  In Progress
Status in linux-azure source package in Mantic:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the inclusion of commit
  bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
  element array with flexible-array member')

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  This patch could cause seg faults if the logic does not correctly
  accommodate a flexible array member.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

[Launchpad Bug Tracker]

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

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

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

Title:
  Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of
  issues and supporting features from more recent kernels?

  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to
  the v6.7 now should ease the upgrade to the v6.8 later.

  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958

  Upstream ChangeLog:

  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
  - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/

  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )

  ChangeLog from Debian:

  iproute2 (6.8.0-1) unstable; urgency=medium

[ Ceppo ]
* Update Italian po-debconf translation (Closes: #1063002)

[ Luca Boccassi ]
* Add build dependency on libnsl-dev (Closes: #1065214)
* Switch to pkgconf
* Update upstream source from tag 'upstream/6.8.0'
* Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
  upstream
* Drop iproute2-doc package
* Drop tc/m_xt.so and tc/m_ipt.so, removed upstream

   -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +

  iproute2 (6.7.0-2) unstable; urgency=medium

    * Backport fix for 'ss' output

   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +

  iproute2 (6.7.0-1) unstable; urgency=medium

    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share

   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +

  iproute2 (6.6.0-1) unstable; urgency=medium

    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream

   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +

  iproute2 (6.5.0-5) unstable; urgency=medium

    * Use dh-sequence-movetousr

   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100

  iproute2 (6.5.0-4) unstable; urgency=medium

    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS

   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100

  iproute2 (6.5.0-3) unstable; urgency=medium

    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100

  iproute2 (6.5.0-2) unstable; urgency=medium

    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)

   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100

  iproute2 (6.5.0-1) unstable; urgency=medium

    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides

    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)

    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2

   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100

  iproute2 (6.4.0-1) unstable; urgency=medium

    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides

   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100

  iproute2 (6.3.0-1) unstable; urgency=medium

    * Drop obsolete 

[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux

[Jason Youzwak]

I experienced a similar issue building 6.5.0-25 on Ubuntu 22.04.

I followed the steps in the "Build Your Own Kernel" post:
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

Specifically, the error occurs after I ran the build step with the
parameters:

fakeroot debian/rules binary-headers binary-generic binary-perarch

I tried the LLVM and CC tricks mentioned in the previous post, but it
did not help.

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

Title:
  Kernel build fails on debian/build/tools-
  perarch/tools/bpf/bpftool/vmlinux

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been attempting to build both the hwe-edge and lowlatency-hwe-
  next kernels from source. Both fail on bpftool not being present,
  though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is
  there.

  ```
  make[1]: Leaving directory 
'/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf'
  mv 
/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
 /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux
  mv: cannot stat 
'/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux':
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:713: 
/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] 
Error 1
  ```

  I've installed the related version of libbpf1 and libbpf-devel, but
  still seeing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+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 2000791] Re: When my laptop wakes up from sleep, it displays a message each time

[vadim]

And where are the updates? Fedora suppresses all this, although the same errors 
are also present there. 
Is it possible to make the grub suppress these messages?

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

Title:
  When my laptop wakes up from sleep, it displays a message each time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my laptop wakes up from sleep, it displays a message each time:

  Message 0002007 (seq 11) timeout
  PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 return -110
  chip reset

  Every time my laptop wakes up from sleep, there are more messages, and
  the messages are reset when it is rebooted.

  I have an acer laptop,i updated the bios to the latest version, it
  didn't work and i have the latest version of ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 18:47:00 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.4.0, 5.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2022-12-07 (23 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Acer Aspire A715-42G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=7683ad64-565f-4b56-9d11-27156bba9f9f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2022
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000791/+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 2000791] Re: When my laptop wakes up from sleep, it displays a message each time

[vadim]

[   50.765796] mt7921e :04:00.0: Message 00020007 (seq 3) timeout
[   50.765819] mt7921e :04:00.0: PM: dpm_run_callback(): 
pci_pm_resume+0x0/0x110 returns -110
[   50.765839] mt7921e :04:00.0: PM: failed to resume async: error -110

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

Title:
  When my laptop wakes up from sleep, it displays a message each time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my laptop wakes up from sleep, it displays a message each time:

  Message 0002007 (seq 11) timeout
  PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 return -110
  chip reset

  Every time my laptop wakes up from sleep, there are more messages, and
  the messages are reset when it is rebooted.

  I have an acer laptop,i updated the bios to the latest version, it
  didn't work and i have the latest version of ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 18:47:00 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.4.0, 5.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2022-12-07 (23 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Acer Aspire A715-42G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=7683ad64-565f-4b56-9d11-27156bba9f9f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2022
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000791/+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 2057960] [NEW] Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4

[Anderson Soares Ferreira]

Public bug reported:

Since I've upgraded my server's to Ubuntu 22.04.4  I'm facing problems to make 
my fcoe setup to work correctly.
Firstly, some context. We have a HPE Synergy appliance with a bunch of Synergy 
480 Gen10 servers still running Ubuntu 20.04. 
Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi Function 
network adapters with two of them dedicated to storage communication through 
FCoE.

Recently, I've upgraded one of them to Ubuntu 22.04 and realized that after the 
upgrade, all the Fibre Channel LUNs have disappeared. During the diagnostic 
process I noticed that both network (bnx2x) and fcoe (fcoe, bnx2fc) kernel 
drivers have been loaded properly, FCoE vlans were correctly detected by 
fcoe-utils, but there was no connection between the server and the storage and 
the server could not detect any LUN.
I also noticed that fcoeadm was reporting the following status:

# fcoeadm -i
Description:  BCM57840 NetXtreme II Ethernet Multi Function
Revision: 11
Manufacturer: Broadcom Inc. and subsidiaries
Serial Number:9440C953B7F0

Driver:   bnx2x Unknown
Number of Ports:  1

Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f2.4093-fco
OS Device Name:host2
Node Name: 0x1a3d2725
Port Name: 0x1a3d2724
Fabric Name:   0x0
Speed: 20 Gbit
Supported Speed:   1 Gbit, 10 Gbit
MaxFrameSize:  2048 bytes
FC-ID (Port ID):   0x
State: Offline
Description:  BCM57840 NetXtreme II Ethernet Multi Function
Revision: 11
Manufacturer: Broadcom Inc. and subsidiaries
Serial Number:9440C953B7F0

Driver:   bnx2x Unknown
Number of Ports:  1

Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over 
ens3f3.4094-fco
OS Device Name:host3
Node Name: 0x1a3d2727
Port Name: 0x1a3d2726
Fabric Name:   0x0
Speed: 20 Gbit
Supported Speed:   1 Gbit, 10 Gbit
MaxFrameSize:  2048 bytes
FC-ID (Port ID):   0x
State: Offline

Although most of information displayed was correct, the port state was
always offline (what explains no storage connectivity) and the FC-ID
reported was 0x for both interfaces.

Supposing that something went wrong during the upgrade process, I decided to 
make a fresh install of the server and, for my surprise, the fcoe ports went 
online and all luns were detected correctly.
Unfortunately, the ports went offline again after a dist-upgrade.
Trying to understand what was happening I performed another fresh install of 
the Ubuntu 22.04, but this time collecting some information about kernel and 
packages versions from before and after dist-upgrade.
What I discovered was that all packages related (fcoe-utils, lldpad) had the 
same versions before and after, the only exception was the kernel itself. 
Before the dist-upgrade the kernel in use was 5.15.0-25-generic and after 
dist-upgrade the kernel was 5.15.0-100-generic.
Suspecting a kernel problem I installed and booted different kernel versions 
from 5.15.0-25 and 5.15.0-100 and discovered that the problem probably was 
introduced with kernel 5.15.0-94, since it is the first version showing the 
describe behavior.
Looking at the changelog of linux-modules package, I noticed some changes on 
fcoe and other scsi modules, right after the 5.15.0-91 version. 
Could those changes be the cause of the behavior observed on my server or just 
a coincidence? Is there any fix to it?

Thanks in advance.

Anderson

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-94-generic 5.15.0-94.104
ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136
Uname: Linux 5.15.0-94-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 14 11:03 seq
 crw-rw 1 root audio 116, 33 Mar 14 11:03 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
Date: Thu Mar 14 14:57:14 2024
HibernationDevice: RESUME=UUID=c4f1e832-fa46-4c58-913e-2093e8a4a4f0
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 002: ID 0424:2660 Microchip Technology, Inc. (formerly SMSC) Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 

[Kernel-packages] [Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out

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

Bug description:
  [Impact]
   * Issue is causing transmit hang on E810 ports with bonding enabled.
   * Based on the provided logs, TX hang can last for even a couple of 
minutes, but in most scenarios, the network will be recovered after the ice 
driver performs a PF reset (TX hang handler routine).
   * Originally, the issue was observed during Tempest tests on a newly 
created OpenStack cluster, resulting in a lack of certification.
  
  [Fix]
  * Initially, a workaround has been proposed by Intel engineers to disable 
LAG initialization [1].
This change has been tested in an environment where reproduction is 
easily achieved.
After multiple iterations, no reproduction has been observed.
  * Shortly after, Intel proposed a patch [2] to disable LAG initialization 
if NVM does not expose proper capabilities.
  
  [Test Plan]
  * To reproduce the issue, over a 20-node cluster was used with Ceph-based 
storage. The problem could sometimes manifest while deploying a cluster or 
after the cluster was already deployed during the Tempest test run.
  * The issue could appear on a random node, making reproduction hard to 
achieve.
  * Multiple stress tests on single host with similar configuration did not 
trigger a reproduction.
  
  [Where problems could occur]
  * All ice drivers with ice_lag_event_handler registered can expose the 
issue. This handler is not implemented in 20.04
  * CVL4.2 and older NVM images for E810 does not expose SRIOV LAG 
capabilities (CVL4.3 wasn't checked) meaning at some point NVM with this 
capability will be released.
Although potentialy issue is caused by using features without proper FW 
support [2], we want to take a closer look once NVMs with proper support are 
introduced.

  [1] - 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/comments/40
  [2] - 
https://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20231211/038588.html
 4d50fcdc2476eef94c14c6761073af5667bb43b6

  [Other Info]
  * Issue could be reproduced on custom 6.2 jammy-hwe kernel with ice 
driver backported from mainline kernel from before patch [2] was added.
  * Original description of the case below:
  
  

  I'm having issues with an Intel E810-XXV card on a Dell server under
  Ubuntu Jammy.

  Details:

  - hardware --> a1:00.0 Ethernet controller: Intel Corporation Ethernet
  Controller E810-XXV for SFP (rev 02)

  - tested with both GA and HWE kernels (`5.15.0-83-generic #92` and
  `6.2.0-32-generic #32~22.04.1-Ubuntu`) with the same results.

  - using a bond over the two ports of the same card, at 25Gbps to two
  different switches, bond is using LACP with hash layer3+4 and fast
  timeout. But I believe the bug is not directly related to bonding as
  the problem seems to be in the interface.

  - machine installed by maas. No issues during installation, but at
  that time bond is not formed yet, later when linux is booted, the bond
  is formed and works without issues for a while

  - it works for about 2 to 3 hours fine, then the issue starts (may or
  may not be related to network load, but it seems that it is triggered
  by some tests that I run after openstack finishes installing)

  - one of the legs of the bond freezes and everything that would go to
  that lag is discarded, in and out, ping to random external hosts start
  losing every second packet

  - after some time you can see on the kernel log messages about "NETDEV
  WATCHDOG: enp161s0f0 (ice): transmit queue 166 timed out" and a stack
  trace

  - the switch does log that the bond is flapping
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   

[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  AWS: arm64: pauth: don't sign leaf functions

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  From our experiments, we found that not signing leaf functions on AWS
  Graviton instances helps improve application performance. We would
  like to have the patch
  
https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8
  backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these
  performance improvements: NGINX 1%, MySQL 2%, PyTorch 2%

  [Test Plan]

  AWS tested.

  [Regression Potential]

  Arm64 binaries may not work correctly.

  [Other Info]

  SF: #00372369

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+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 2044131] Re: i915 regression introduced with 5.5 kernel

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  i915 regression introduced with 5.5 kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-hwe-5.15 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-5.15 source package in Noble:
  Invalid

Bug description:
  [ Impact ]
  Commit 8f4b1068e7fc3df1a77ac8151767e56b208cc87f introduced some timing checks 
which have been proven invalid for at least some hardware setups. A user trying 
to run Focal with HWE 5.15 kernel is not able to get any video output.
  After going through bisection between 5.4 and 5.5 this commit was identified. 
Reverting it on top of Focal HWE kernel fixes the issue.

  The issue has been addressed upstream in DRM tree
  (20c2dbff342aec13bf93c2f6c951da198916a455) and has been merge into
  linux-next (e0ef2daa8ca8ce4dbc2fd0959e383b753a87fd7d).

  dmesg and lspci from the affected configuration are attached to this
  bug.

  [ Test Plan ]
  1. Boot the affected hardware with Ubuntu desktop running kernel v5.5 or 
higher.
  2. Wait until boot finishes and see the blank screen.

  Actual result: there is no video output visible.
  Expected result: normal boot process should be visible (e.g. splash), then 
GUI should appear.

  [ Where problem could occur ]
  This bug was a result of assumptions in the checks that turned out to be not 
valid for some hardware. The checks were removed from global intel_mode_valid 
function and moved into connector specific .mode_valid() hooks, entirely 
skiping BXT/GLK DSI connectors.

  This should keep the checks where appropriate and skip for hardware
  that does not comply to them.

  [ Other info ]

  Original bug description:

  There is a regression preventing a user to upgrade from 5.4 kernel to 
anything that's higher than 5.5. When using such kernel the image orientation 
is wrong (rotated by 90°C). Also the kernel log contains:
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Unknown revid 0x06
  wrz 15 09:19:49 desktop kernel: rtw_8821ce :01:00.0: Firmware version 
24.8.0, H2C version 12
  wrz 15 09:19:49 desktop kernel: Console: switching to colour dummy device 
80x25
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: deactivate vga 
console
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] couldn't get memory 
information
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: vgaarb: changed VGA 
decodes: olddecodes=io+mem,decodes=io+mem:o>
  wrz 15 09:19:49 desktop kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/glk_dmc_ver1_04.bin (v>
  wrz 15 09:19:49 desktop kernel: 

  wrz 15 09:19:49 desktop kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-hwe-5.15-DZkSuT/linux-hwe-5.15-5.>
  wrz 15 09:19:49 desktop kernel: index 5 is out of range for type 'u32 [5]'

  (full stack trace attached)

  The video hardware in use is:
  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 
[8086:3185] (rev 06) (prog-if 00 [VGA controller])
  (...)
  Kernel driver in use: i915
  Kernel modules: i915

  The user wanted to upgrade from bionic to focal with HWE kernel (they
  needed it due to some networking hardware they wanted to have
  supported by the newer kernel).

  The user was testing mainline stable kernels and noticed that the last
  working kernel was the 5.4 series, while anything starting from 5.5
  and above is BROKEN (symptoms as described in the first paragraph
  above).

  Together with the user we have run a bisection between v5.4 and v5.5 on the 
upstream stable kernel and we were able to identify the first broken 

[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  Reject connection when malformed L2CAP signal packet is received

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

Bug description:
  The patch is merged in mainline kernel v6.7-rc7, so Noble kernel
  already have this fix. And this patch is CCed to sta...@vger.kernel.org,
  M and L kernel will have this fix with the SRU update sooner or later.
  For Jammy kernel, an OEM customer is waiting for this patch
  to be merged to Jammy kernel and OEM kernel, here I submit the
  review reqeust for Jammy only.

  [Impact]
  An OEM customer want to do the bluetooth profile testing suite (PTS)
  test, and they found if sending 2 commands and one of them is "unknown
  comands", the bluetooth stack doesn't reply the ack as expected, this
  broke the customer's PTS test.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  After applying the patch, test it with PTS:

  1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection
 over PSM 0x1011, which is the default PSM for l2test, the testing tool for
 L2CAP layer provided by bluez.

  2. Set device as connectable:
   $ sudo btmgmt connectable on

  3. Run l2test on the device in preparation for testing:
   $ sudo l2test -d

  4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate
 L2CAP connection automatically.

  5. Verify that the test verdict on the PTS is PASS.

  And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and
  my mobile phone, all worked as well as before.

  [Where problems could occur]
  This makes L2CAP implementation more conforming to the specification.
  It has possibility to make some bt devices could not work with patched
  kernel, but this possibility is very low, I tested the patched kernel
  with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all
  worked as well as before.



  [Impact]

  In the qualification test the from the Bluetooth SIG i.e. the
  Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C,
  packet containing the following L2CAP packets are sent:

  1. A malformed L2CAP_CONNECTION_REQ packet; and
  2. An L2CAP packet with unknown command.

  For compliance to the L2CAP specification, BlueZ is expected to send:

  1. An L2CAP_CONNECTION_RSP packet; and
  2. An L2CAP_COMMAND_REJECT_RSP packet.

  However, the later one is not sent.

  [Fix]
  Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add

  (Bluetooth: L2CAP: Send reject on command corrupted request)

  [Test]
  After applying the patch, test it with PTS:

  1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection
     over PSM 0x1011, which is the default PSM for l2test, the testing tool for
     L2CAP layer provided by bluez.

  2. Set device as connectable:
   $ sudo btmgmt connectable on

  3. Run l2test on the device in preparation for testing:
   $ sudo l2test -d

  4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate
     L2CAP connection automatically.

  5. Verify that the test verdict on the PTS is PASS.

  [Where problems could occur]
  This makes L2CAP implementation more conforming to the specification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  Don't WARN_ON_ONCE() for a broken discovery table

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

Bug description:
  SRU Justification

  [Impact]

    perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table

  The kernel warning message is triggered, when SPR MCC is used.

  [   17.945331] [ cut here ]
  [   17.946305] WARNING: CPU: 65 PID: 1 at
  arch/x86/events/intel/uncore_discovery.c:184
  intel_uncore_has_discovery_tables+0x4c0/0x65c
  [   17.946305] Modules linked in:
  [   17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
  5.4.17-2136.313.1-X10-2c+ #4

  It's caused by the broken discovery table of UPI.

  The discovery tables are from hardware. Except for dropping the broken
  information, there is nothing Linux can do. Using WARN_ON_ONCE() is
  overkilled.

  Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
  is dropped and the reason.

  [Fix]

  Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore:
  Don't WARN_ON_ONCE() for a broken discovery table')

  [Test]

  AWS tested

  [Regression potential]

  Low regression potential. Only the code that prints the warning has
  been changed.

  [Other Info]

  SF: #00347830

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-aws/5.15.0-1056.61
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-aws' to 'verification-done-jammy-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'.


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-aws-v2 
verification-needed-jammy-linux-aws

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

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

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2049922] Re: PCI ATS quirk patch needed for IDPF

[Thibf]

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

** Changed in: linux-gcp-4.15 (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

** No longer affects: linux-gcp-4.15 (Ubuntu Focal)

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

Title:
  PCI ATS quirk patch needed for IDPF

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp-4.15 package in Ubuntu:
  New
Status in linux-gcp source package in Bionic:
  In Progress
Status in linux-gcp-4.15 source package in Bionic:
  Fix Committed
Status in linux-gcp source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Request from Google to include Intel patches for IDPF support if used from
  out-of-tree module to prevent system instability.

  [Fixes]
  f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
  a18615b1cfc0 ("PCI: Disable ATS for specific Intel IPU E2000 devices")

  
  [Test Case]

  * Compile test
  * Boot test
  * Test on non-IDPF instance
  * Tested by Google

  [Where things could go wrong]

  * Low chance of regression, changes very isolated

  [Other Info]

  * SF #00376470

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2039720] Re: Intel IDPF support

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-gke/5.15.0-1054.59
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-gke' to 'verification-done-jammy-
linux-gke'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'.


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-gke-v2 
verification-needed-jammy-linux-gke

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

Title:
  Intel IDPF support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  In Progress
Status in linux-gcp source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  * Request from Google to include new Intel IDPF driver support

  [Fix]

  * Mantic - 24 clean cherry-picks, 1 backport from upstream
  * Jammy - 11 clean cherry-picks, 7 backports from upstream

  [Test Case]

  * Compile tested
  * Boot tested
  * Tested internally and by Google using neper 
(https://github.com/google/neper)
  * Networking is functional and throughput is as expected

  [Where things could go wrong]

  * Low chance of regression, changes have been upstream since 6.6 kernel
  * Bulk of changes in IDPF driver
  * Other changes to network drivers largely adding #include directives

  [Other Info]

  * SF #00368902

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 1958518] Re: split some large, lesser-used firmware files into -extra package

[A]

Are you kidding download 500 Mb if someone changed one line in some
config ?

I reverted to debian because of this.
You are mad.

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

Title:
  split some large, lesser-used firmware files into -extra package

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Jammy:
  Confirmed

Bug description:
  The linux-image-generic package depends on linux-firmware which is
  over half a gigabyte in size installed.  I will assume that quite many
  people do not have netronome hardware which weighs in at almost 150MB
  of that.  I kindly suggest to put such large firmware for less common
  hardware into its own linux-firmware-extra package which would be
  recommended by linux-firmare.

  Comments?

  I'm willing to help with the packaging provided that the changes have
  a chance to land.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+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 2057936] [NEW] Azure: hv: hyperv.h: Replace one-element array with flexible-array member

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')

[Test Plan]

Microsoft tested

[Regression Potential]

This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

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

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

** Changed in: linux-azure (Ubuntu)
   Status: New => Fix Released

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

Title:
  Azure: hv: hyperv.h: Replace one-element array with flexible-array
  member

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  New
Status in linux-azure source package in Mantic:
  New

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the inclusion of commit
  bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
  element array with flexible-array member')

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  This patch could cause seg faults if the logic does not correctly
  accommodate a flexible array member.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2057913] Re: package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10

[trackwitz]

The error occours because you are trying to build a dkms module for zfs version 
2.1.5 which only supports kernels up to version 5.18.x.
So there are some incompatabilities with your kernel because it's much newer 
causing the build to fail.

The only zfs version that supports kernel 6.7.x is zfs version 2.2.3,
however there are no Ubuntu packages available so it has to be build
from source.

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

Title:
  package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade:
  »installiertes zfs-dkms-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Using kernel 6.7.6-surface-1 on a Surface Pro 7.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.3
  Uname: Linux 6.7.6-surface-1 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   zfs-dkms:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Mar 14 11:16:27 2024
  ErrorMessage: »installiertes zfs-dkms-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2021-01-20 (1149 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.11
  SourcePackage: zfs-linux
  Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade: 
»installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 10 zurück
  UpgradeStatus: Upgraded to jammy on 2023-03-30 (350 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2057913/+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 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed

[Stefan Bader]

Mainline was and is nothing really supported. They are there because
they help debugging (instead of doing bisect builds). When we do
official hwe kernels they get built without module compression (going to
Jammy). When doing your own backports ensure you have "jammy" as the
target in the current changelog section (not UNRELEASED or noble).

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

Title:
  [LTS] cryptsetup-initramfs fails when kernel modules are compressed

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in cryptsetup source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete

Bug description:
  This is the same cause as the Mantic bug "cryptsetup autopkgtest fails
  with zstd compressed kernel modules"

  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120

  where hooks/cryptroot::add_modules() needs postfix wildcards after
  $glob.ko on 2 lines.

  It affects 22.04 LTS with recent kernel or local kernel built with
  CONFIG_MODULE_COMPRESS_*

  I think the fix needs cherry-picking into LTS release(s).

  https://salsa.debian.org/cryptsetup-
  team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750

  At boot-time it results in the cryptic (pun intended) messages:

  device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT)
  device-mapper: ioctl: error adding target to table
  device-mapper: reload ioctl on luks_os (253:0) failed: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+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 2057717] Re: dpkg linux-image-6.5.0-25-generic ever returns error

[Thiago Salles Santos]

I run the command 'apport-collect 2057717', the answer: "Package linux-
signed-hwe-6.5 not installed and no hook available, ignoring"


~$ apport-collect 2057717
Package linux-signed-hwe-6.5 not installed and no hook available, ignoring

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

Title:
  dpkg linux-image-6.5.0-25-generic ever returns error

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

Bug description:
  English:
  /etc/kernel/postinst.d/zz-update-grub:
  /usr/sbin/grub-probe: error: Failed to get canonical path from 
"rpool/ROOT/ubuntu_o2pu7m".
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: error processing package linux-image-6.5.0-25-generic (--configure):
 the installed subprocess, from the linux-image-6.5.0-25-generic package, 
the post-installation script returned exit status 1 error
  Errors were found during processing of:
 linux-image-6.5.0-25-generic
  E: The subprocess /usr/bin/dpkg returned an error code (1)

  Pt-BR:
  /etc/kernel/postinst.d/zz-update-grub:
  /usr/sbin/grub-probe: erro: falha ao obter o caminho canónico de 
"rpool/ROOT/ubuntu_o2pu7m".
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: erro ao processar o pacote linux-image-6.5.0-25-generic (--configure):
   o subprocesso instalado, do pacote linux-image-6.5.0-25-generic, o script 
post-installation retornou erro do status de saída 1
  Erros foram encontrados durante o processamento de:
   linux-image-6.5.0-25-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-25-generic 6.5.0-25.25~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_6_5_0_17_17_generic_101 zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 12 21:42:34 2024
  InstallationDate: Installed on 2022-07-12 (609 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.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/2057717/+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 2054121] Re: Random Freezing

[Allen]

I'm not sure how to do this:

"drm.debug=0xff loglevel=8"

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

Title:
  Random Freezing

Status in linux package in Ubuntu:
  New

Bug description:
  Random lockups in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 09:08:41 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
  InstallationDate: Installed on 2024-02-16 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3JKT3CA
  dmi.board.name: 32DD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305435660291
  dmi.chassis.type: 35
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
  dmi.product.family: ThinkStation P350 Tiny
  dmi.product.name: 30EF004VUS
  dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
  dmi.product.version: ThinkStation P350 Tiny
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2054121] Re: Random Freezing

[Allen]

Came in this morning and it was locked up. NO SSH.

Going to move back to 6.5

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755959/+files/prevboot.txt

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

Title:
  Random Freezing

Status in linux package in Ubuntu:
  New

Bug description:
  Random lockups in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 09:08:41 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
  InstallationDate: Installed on 2024-02-16 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2023
  dmi.bios.release: 1.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M3JKT3CA
  dmi.board.name: 32DD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN 3305435660291
  dmi.chassis.type: 35
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
  dmi.product.family: ThinkStation P350 Tiny
  dmi.product.name: 30EF004VUS
  dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
  dmi.product.version: ThinkStation P350 Tiny
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2051672] Re: Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

[Matthieu Baerts]

** Summary changed:

- Merge iproute2 with the latest Debian version: 6.7.0-2 from testing/unstable 
(main)
+ Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable 
(main)

** Description changed:

  A few versions have been released and Ubuntu Noble still has the 6.1
  version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
  import the latest version from Debian unstable fixing a bunch of issues
  and supporting features from more recent kernels?
  
  Please note that Ubuntu Noble 24.04 will probably be shipped with the
  v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1
  kernel, so missing the ones added to earlier versions. Switching to the
  v6.7 now should ease the upgrade to the v6.8 later.
  
  [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for-
  the-24-04-noble-numbat-release/41958
  
  Upstream ChangeLog:
  
  - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/
  - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/
  - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/
  - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/
  - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/
  - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/
+ - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/
  
  (Previous changelog:
  
https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22
  )
  
  ChangeLog from Debian:
+ 
+ iproute2 (6.8.0-1) unstable; urgency=medium
+ 
+   [ Ceppo ]
+   * Update Italian po-debconf translation (Closes: #1063002)
+ 
+   [ Luca Boccassi ]
+   * Add build dependency on libnsl-dev (Closes: #1065214)
+   * Switch to pkgconf
+   * Update upstream source from tag 'upstream/6.8.0'
+   * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged
+ upstream
+   * Drop iproute2-doc package
+   * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream
+ 
+  -- Luca Boccassi <>  Tue, 12 Mar 2024 14:02:38 +
  
  iproute2 (6.7.0-2) unstable; urgency=medium
  
    * Backport fix for 'ss' output
  
   -- Luca Boccassi <>  Mon, 22 Jan 2024 12:24:29 +
  
  iproute2 (6.7.0-1) unstable; urgency=medium
  
    * Add Italian debconf translation (Closes: #1056582)
    * Update upstream source from tag 'upstream/6.7.0'
    * Bump copyright year ranges in d/copyright
    * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch,
  merged upstream
    * Default config files moved from /usr/lib to /usr/share
  
   -- Luca Boccassi <>  Fri, 12 Jan 2024 21:47:59 +
  
  iproute2 (6.6.0-1) unstable; urgency=medium
  
    * Update upstream source from tag 'upstream/6.6.0'
    * Backport patch to fix configuration installation
    * Remove handling of qt_atm.so, dropped upstream
  
   -- Luca Boccassi <>  Sun, 05 Nov 2023 22:46:20 +
  
  iproute2 (6.5.0-5) unstable; urgency=medium
  
    * Use dh-sequence-movetousr
  
   -- Luca Boccassi <>  Tue, 24 Oct 2023 15:24:01 +0100
  
  iproute2 (6.5.0-4) unstable; urgency=medium
  
    * postinst: handle legacy config files only when upgrading from previous
  versions that shipped them
    * postinst: ensure that locally modified legacy config files are
  preserved as overrides on upgrade (Closes: #1051577)
    * Note configuration files location changes in NEWS
  
   -- Luca Boccassi <>  Sat, 16 Sep 2023 18:58:51 +0100
  
  iproute2 (6.5.0-3) unstable; urgency=medium
  
    * Remove further leftovers as part of upstream's move of config to /usr
  (Closes: #1051577)
  
   -- Luca Boccassi <>  Mon, 11 Sep 2023 09:42:12 +0100
  
  iproute2 (6.5.0-2) unstable; urgency=medium
  
    * Add maintscript to remove conffiles that upstream has moved to /usr
  (Closes: #1051577)
  
   -- Luca Boccassi <>  Sun, 10 Sep 2023 21:28:28 +0100
  
  iproute2 (6.5.0-1) unstable; urgency=medium
  
    [ Luca Boccassi ]
    * Use wildcard for Lintian overrides
  
    [ Peter Kvillegård ]
    * Add Swedish translation of debconf messages (Closes: #1050442)
  
    [ Luca Boccassi ]
    * Update upstream source from tag 'upstream/6.5.0'
    * Use cap_bpf instead of cap_sys_admin for ip vrf-exec
    * Package-provided config files are now shipped in /usr/iproute2 instead
  of /etc/iproute2
  
   -- Luca Boccassi <>  Sat, 09 Sep 2023 16:32:54 +0100
  
  iproute2 (6.4.0-1) unstable; urgency=medium
  
    * Fix patch header Forwarded field
    * Enable ELF metadata stamping
    * Update upstream source from tag 'upstream/6.4.0'
    * Update Lintian overrides
  
   -- Luca Boccassi <>  Fri, 30 Jun 2023 12:16:40 +0100
  
  iproute2 (6.3.0-1) unstable; urgency=medium
  
    * Drop obsolete conflicts/replaces
    * Update upstream source from tag 'upstream/6.3.0'
  
   -- Luca Boccassi <>  Tue, 13 Jun 2023 23:49:37 +0100
  
  iproute2 (6.1.0-3) unstable; urgency=medium
  
    * Ensure 

[Kernel-packages] [Bug 2057913] [NEW] package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1

[Corben]

Public bug reported:

Using kernel 6.7.6-surface-1 on a Surface Pro 7.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: zfs-dkms 2.1.5-1ubuntu6~22.04.3
Uname: Linux 6.7.6-surface-1 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 zfs-dkms:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Mar 14 11:16:27 2024
ErrorMessage: »installiertes zfs-dkms-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
InstallationDate: Installed on 2021-01-20 (1149 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.11
SourcePackage: zfs-linux
Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade: 
»installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 10 zurück
UpgradeStatus: Upgraded to jammy on 2023-03-30 (350 days ago)

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


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

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

Title:
  package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade:
  »installiertes zfs-dkms-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 10 zurück

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Using kernel 6.7.6-surface-1 on a Surface Pro 7.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.3
  Uname: Linux 6.7.6-surface-1 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   zfs-dkms:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Mar 14 11:16:27 2024
  ErrorMessage: »installiertes zfs-dkms-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
  InstallationDate: Installed on 2021-01-20 (1149 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.11
  SourcePackage: zfs-linux
  Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.3 failed to install/upgrade: 
»installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 10 zurück
  UpgradeStatus: Upgraded to jammy on 2023-03-30 (350 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2057913/+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 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed

[TJ]

Recent kernels: 6.8.0-25 from Noble and the mainline kernel builds from
e.g:

https://kernel.ubuntu.com/mainline/v6.8/amd64/

Used for ensuring support for recent hardware.

If these will be rebuilt without module compression for LTS/HWE kernel
releases then this issue isn't so vital, but it will make testing a
recent kernel (often asked for when hitting hardware/kernel issues)
extremely challenging and for most non-technical operators, impossible.

On balance I'd think adding those two wildcards is a win.

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

Title:
  [LTS] cryptsetup-initramfs fails when kernel modules are compressed

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in cryptsetup source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete

Bug description:
  This is the same cause as the Mantic bug "cryptsetup autopkgtest fails
  with zstd compressed kernel modules"

  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120

  where hooks/cryptroot::add_modules() needs postfix wildcards after
  $glob.ko on 2 lines.

  It affects 22.04 LTS with recent kernel or local kernel built with
  CONFIG_MODULE_COMPRESS_*

  I think the fix needs cherry-picking into LTS release(s).

  https://salsa.debian.org/cryptsetup-
  team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750

  At boot-time it results in the cryptic (pun intended) messages:

  device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT)
  device-mapper: ioctl: error adding target to table
  device-mapper: reload ioctl on luks_os (253:0) failed: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+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 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages

[Russell Jones]

Is this related to https://bugs.launchpad.net/ubuntu/+source/lxd-agent-
loader/+bug/2054814 ?

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

Title:
  dmesg spammed by virtui-fs and 9pnet-virtio messages

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu noble, as of 28 Feb 2024, on amd64, s390x, ppc64, seeing kernel
  messages after boot (running instances in a VM using virt-manager)

  uname -a
  Linux noble-amd64-efi 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 
30 10:27:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  [   30.638354] virtio-fs: tag  not found
  [   30.642316] 9pnet_virtio: no channels available for device config
  [   35.897615] virtio-fs: tag  not found
  [   35.901568] 9pnet_virtio: no channels available for device config
  [   41.141860] virtio-fs: tag  not found
  [   41.145513] 9pnet_virtio: no channels available for device config
  [   46.382040] virtio-fs: tag  not found
  [   46.386141] 9pnet_virtio: no channels available for device config
  [   51.632229] virtio-fs: tag  not found
  [   51.635727] 9pnet_virtio: no channels available for device config

  These are annoying when logging in via the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+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 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux

[Jonas Juffinger]

I tried building 6.1.81 on Ubuntu 22.04 and got the same error message.

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

Title:
  Kernel build fails on debian/build/tools-
  perarch/tools/bpf/bpftool/vmlinux

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been attempting to build both the hwe-edge and lowlatency-hwe-
  next kernels from source. Both fail on bpftool not being present,
  though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is
  there.

  ```
  make[1]: Leaving directory 
'/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf'
  mv 
/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
 /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux
  mv: cannot stat 
'/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux':
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:713: 
/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] 
Error 1
  ```

  I've installed the related version of libbpf1 and libbpf-devel, but
  still seeing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+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 2057808] Re: [LTS] cryptsetup-initramfs fails when kernel modules are compressed

[Steve Langasek]

You say "recent kernel or local kernel." What Ubuntu-provided kernel for
Ubuntu 22.04 LTS do you see this with?

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

Title:
  [LTS] cryptsetup-initramfs fails when kernel modules are compressed

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in cryptsetup source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete

Bug description:
  This is the same cause as the Mantic bug "cryptsetup autopkgtest fails
  with zstd compressed kernel modules"

  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120

  where hooks/cryptroot::add_modules() needs postfix wildcards after
  $glob.ko on 2 lines.

  It affects 22.04 LTS with recent kernel or local kernel built with
  CONFIG_MODULE_COMPRESS_*

  I think the fix needs cherry-picking into LTS release(s).

  https://salsa.debian.org/cryptsetup-
  team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750

  At boot-time it results in the cryptic (pun intended) messages:

  device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT)
  device-mapper: ioctl: error adding target to table
  device-mapper: reload ioctl on luks_os (253:0) failed: No such file or 
directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2057808/+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 1970069] Re: Annoying boot messages interfering with splash screen

[Daniel van Vugt]

Fedora 39:

CONFIG_FB_VESA=y
CONFIG_FB_EFI=y

Ubuntu 24.04:

# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set

In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you
want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose
help text says:

> you should still keep vesafb and others enabled as fallback
> if a system framebuffer is incompatible with simplefb.

So overall I don't think SimpleDRM *needs* any legacy fbdev like FB_EFI
or FB_VESA, they're just recommended as a fallback.

I'll do more testing in the coming days to verify if SimpleDRM is really
working as intended. But the main concern here is that we might have
broken some systems by disabling the legacy fbdev drivers. I'm not sure.
Anyone testing Noble with kernel 6.8 right now should be able to tell
us...

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2057785] Re: Mute/mic LEDs no function on some HP EliteBook

[Timo Aaltonen]

** Changed in: linux-oem-6.5 (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/2057785

Title:
  Mute/mic LEDs no function on some HP EliteBook

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Won't Fix
Status in linux-oem-6.5 source package in Noble:
  Won't Fix

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP EliteBook

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2057785/+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 2057717] Re: dpkg linux-image-6.5.0-25-generic ever returns error

[Juerg Haefliger]

Please run 'apport-collect 2057717'.

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

Title:
  dpkg linux-image-6.5.0-25-generic ever returns error

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

Bug description:
  English:
  /etc/kernel/postinst.d/zz-update-grub:
  /usr/sbin/grub-probe: error: Failed to get canonical path from 
"rpool/ROOT/ubuntu_o2pu7m".
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: error processing package linux-image-6.5.0-25-generic (--configure):
 the installed subprocess, from the linux-image-6.5.0-25-generic package, 
the post-installation script returned exit status 1 error
  Errors were found during processing of:
 linux-image-6.5.0-25-generic
  E: The subprocess /usr/bin/dpkg returned an error code (1)

  Pt-BR:
  /etc/kernel/postinst.d/zz-update-grub:
  /usr/sbin/grub-probe: erro: falha ao obter o caminho canónico de 
"rpool/ROOT/ubuntu_o2pu7m".
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: erro ao processar o pacote linux-image-6.5.0-25-generic (--configure):
   o subprocesso instalado, do pacote linux-image-6.5.0-25-generic, o script 
post-installation retornou erro do status de saída 1
  Erros foram encontrados durante o processamento de:
   linux-image-6.5.0-25-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-25-generic 6.5.0-25.25~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_6_5_0_17_17_generic_101 zfs
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 12 21:42:34 2024
  InstallationDate: Installed on 2022-07-12 (609 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.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/2057717/+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