[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)

[Launchpad Bug Tracker]

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

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

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

Title:
  Add Support for Broadcom 5760X Network adapters to 24.04 (patches in
  6.8)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Confirmed

Bug description:
  These patches are needed on top of v6.7 to support Broadcom 5760X
  Adapters.  These patches currently reside in the net-next tree and
  will be included in v6.8.

  Prerequisite commits in net-next today:

  c1056a59aee1 bnxt_en: Optimize xmit_more TX path
  ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings
  f07b58801bef bnxt_en: Add macros related to TC and TX rings
  f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for 
TX rings
  0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX
  877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal()
  5a3c585fa83f bnxt_en: New encoding for the TX opaque field
  ebf72319cef6 bnxt_en: Refactor bnxt_tx_int()
  9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
  7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures
  d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
  7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures
  34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque 
field

  These 13 patches below were submitted on 11/20/23 and accepted on
  11/21/23.  These are the initial patches with 5760X contents.

  1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips
  f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips
  c09d22674b94 bnxt_en: Modify RX ring indexing logic.
  6d1add95536b bnxt_en: Modify TX ring indexing logic.
  b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info 
struct.
  236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware 
calls
  6a4d0774f02d bnxt_en: Add support for new backing store query firmware API
  b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
  2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
  035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type
  76087d997a84 bnxt_en: Restructure context memory data structures
  e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
  aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free 
bp->ctx

  The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23.
  These are all the basic L2 patches for 5760X including the PCI IDs:

  2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs
  047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware 
interface
  7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields
  30c0bb63c2ea bnxt_en: Support new firmware link parameters
  cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic
  a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types 
for P7
  39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end().
  c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic.
  13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+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 2038782] Re: linux-firmware halts boot before grub screen on clean install-upgrade to Ubuntu 22.04.3

[Launchpad Bug Tracker]

[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  linux-firmware halts boot before grub screen on clean install-upgrade
  to Ubuntu 22.04.3

Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  
  System halts just after filesystem journaling after USB install of LTS Ubuntu 
22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system. 

  Another bug report from 2020 says their system gets past grub screen
  and then gets stuck, I don't even make it that far, no other bug
  reports I found seems similar. Since I can't get to grub, I can't
  adjust boot options because it's apparently not going to load the OS.

  I receive no errors. Since the OS isn't loaded, nothing shows up in
  the filesystem logs.

  
  Can CTRL+ALT+DEL reboot, but can't get past journaling and into GRUB.

  
  Since system won't proceed further after journaling completes, apport can't 
start or dump a report.


  
  Steps to Reproduce:
  ---

  * Boot from official USB 22.04.2 USB image made as per Ubuntu instructions 
using Ubuntu bootable disk tool 
  * Accept all installation defaults
  * reboot

  Once rebooted and at 22.04.2 desktop, open terminal and issue:

  * sudo apt update

  (You will be told 340+ packages need to be installed)

  * sudo apt upgrade

  (wait for apt upgrade to complete)

  * reboot

  After rebooting from upgrade, system halts after filesystem journaling
  (which reports filesystem is in a good state on my system), yet system
  will not continue to grub/OS boot options screen despite filesystem
  being OK.

  I left system running at that spot overnight, no change in the AM,
  still stuck at journaling screen.

  Again, journaling reports no errors, computer simply won't boot.


  HOW I VERIFIED:
  ---

  Wiped disk (full overwrite erase)

  Reinstalled as per above

  sudo apt update
  sudo apt-mark hold linux-firmware
  sudo apt upgrade
  reboot

  After above steps, system boots & runs (using same system now to write
  this bug report).

  At this time, the system is as fully patched as I can get it:

  user@myhost:~$ sudo apt list --upgradeable
  [sudo] password for user: 
  Listing... Done
  gjs/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  libgjs0g/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  linux-firmware/jammy-updates,jammy-updates 20220329.git681281e4-0ubuntu3.19 
all [upgradable from: 20220329.git681281e4-0ubuntu3.10]


  
  ADDITIONAL NOTES:
  

  Booting into a stand-alone memory test on the system finds no memory
  faults or errors.

  Video stress-test of all functions (2D, shaders, vector, bump, buffer,
  raytrace etc.) performed on the system prior to running "sudo apt
  upgrade".  No failure, no crash, frame rates on par with public
  benchmarks. Crushed the card at 4K resolution, and also ran it with
  eight 1k instances with no problems. Video card ruled out.

  Replaced hard disk with new disk from different vendor, (even though
  journal finds no errors), problem persisted.

  
  Simply placing a hold on linux-firmware package prevents the problem reliably 
regardless of hardware setup.

  
  System up and stable now across multiple reboots and software installs for 6 
hours and now has full software load, including qemu/kvm.


  
  DIAGNOSTICS
  ---

  user@myhost:~$ sudo lshw -short

  H/W path  Device  Class  Description
  
system System Product Name 
(SKU)
  /0busTUF GAMING B550-PLUS 
WIFI II
  /0/0  memory 64KiB BIOS
  /0/34 memory 64GiB System Memory
  /0/34/0   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/1   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/2   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/3   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/37 memory 512KiB L1 cache
  /0/38 memory 4MiB L2 cache
  /0/39 memory 32MiB L3 cache
  /0/3a processor

[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot

[Launchpad Bug Tracker]

This bug was fixed in the package kdump-tools - 1:1.8.2ubuntu1

---
kdump-tools (1:1.8.2ubuntu1) noble; urgency=medium

  * Merge from Debian unstable. Remaining changes:
- debian/control/tests: sleep while waiting for systemd service.
- Bump amd64 crashkernel from 384M-:128M to 512M-:192M.
- Add a systemd-resolved service dependency in order kdump-tools is able
  to resolve DNS when in kdump boot.
- Update default s390x crashkernel.
  - Install the updated zipl.conf with ucf, so users will be able to
decide whether to pick any crashkernel changes.

kdump-tools (1:1.8.2) unstable; urgency=medium

  * Disable the initramfs generation in our kernel-postinst hook when
we detect we are running in a chroot. LP: #2043059.

 -- dann frazier   Fri, 15 Dec 2023 15:06:42 -0700

** Changed in: kdump-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Installation errors out when installing in a chroot

Status in kdump-tools package in Ubuntu:
  Fix Released
Status in linux-nvidia package in Ubuntu:
  Invalid

Bug description:
  Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
 ...done.
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia
  cryptsetup: WARNING: Couldn't determine root device
  W: Couldn't identify type of root file system for fsck hook
  cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /var/lib/kdump/initramfs-tools

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia 
with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure):
   installed linux-image-5.15.0-1040-nvidia package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.15.0-1040-nvidia
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+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 2046584] [NEW] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28

[Eric Blevins]

Public bug reported:

After running for some time the GUI freezes.
This happens on a Raspberry PI 4 running Ubuntu 23.10 
Linux hawk1 6.5.0-1008-raspi #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 19:08:26 
UTC 2023 aarch64 aarch64 aarch64 GNU/Linux


This issue was also reported here:
https://github.com/raspberrypi/linux/issues/5674

Seems like this pull requests fixes it:
https://github.com/raspberrypi/linux/pull/5684


Some logs from the most recent incident:
2023-12-15T15:25:37.216748-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.263913-05:00 hawk1 kernel: [ 1045.576619] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.263548-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.278139-05:00 hawk1 gnome-shell[1293]: Cursor update failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.279826-05:00 hawk1 kernel: [ 1045.591912] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.298467-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.299916-05:00 hawk1 kernel: [ 1045.611834] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28 
2023-12-15T15:25:37.312469-05:00 hawk1 gnome-shell[1293]: Cursor update failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.315838-05:00 hawk1 kernel: [ 1045.626371] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.331875-05:00 hawk1 kernel: [ 1045.644563] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28 
2023-12-15T15:25:37.330814-05:00 hawk1 gnome-shell[1293]: Cursor update failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.349465-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
2023-12-15T15:25:37.352021-05:00 hawk1 kernel: [ 1045.662809] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.387925-05:00 hawk1 kernel: [ 1045.698223] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.435919-05:00 hawk1 kernel: [ 1045.749879] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
2023-12-15T15:25:37.471896-05:00 hawk1 kernel: [ 1045.784378] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28

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

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

Title:
  vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  After running for some time the GUI freezes.
  This happens on a Raspberry PI 4 running Ubuntu 23.10 
  Linux hawk1 6.5.0-1008-raspi #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 
19:08:26 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

  
  This issue was also reported here:
  https://github.com/raspberrypi/linux/issues/5674

  Seems like this pull requests fixes it:
  https://github.com/raspberrypi/linux/pull/5684


  Some logs from the most recent incident:
  2023-12-15T15:25:37.216748-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.263913-05:00 hawk1 kernel: [ 1045.576619] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
  2023-12-15T15:25:37.263548-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.278139-05:00 hawk1 gnome-shell[1293]: Cursor update 
failed: drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.279826-05:00 hawk1 kernel: [ 1045.591912] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
  2023-12-15T15:25:37.298467-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.299916-05:00 hawk1 kernel: [ 1045.611834] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28 
  2023-12-15T15:25:37.312469-05:00 hawk1 gnome-shell[1293]: Cursor update 
failed: drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.315838-05:00 hawk1 kernel: [ 1045.626371] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
  2023-12-15T15:25:37.331875-05:00 hawk1 kernel: [ 1045.644563] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28 
  2023-12-15T15:25:37.330814-05:00 hawk1 gnome-shell[1293]: Cursor update 
failed: drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.349465-05:00 hawk1 gnome-shell[1293]: Page flip failed: 
drmModeAtomicCommit: No space left on device
  2023-12-15T15:25:37.352021-05:00 hawk1 kernel: [ 1045.662809] vc4-drm gpu: 
[drm] *ERROR* Failed to allocate DLIST entry: -28
  2023-12-15T15:25:37.387925-05:0

[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot

[Sam Tannous]

You're correct.  It can fail for other reasons.  I don't think we could check 
the errno, could we?  It would be 1, "Operation not permitted".

If not, I think we can live with the last suggestion.

Thanks,

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

Title:
  Installation errors out when installing in a chroot

Status in kdump-tools package in Ubuntu:
  Triaged
Status in linux-nvidia package in Ubuntu:
  Invalid

Bug description:
  Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
 ...done.
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia
  cryptsetup: WARNING: Couldn't determine root device
  W: Couldn't identify type of root file system for fsck hook
  cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is MODULES=most, check:
  grep -r MODULES /var/lib/kdump/initramfs-tools

  Error please report bug on initramfs-tools
  Include the output of 'mount' and 'cat /proc/mounts'
  update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia 
with 1.
  run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
  dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure):
   installed linux-image-5.15.0-1040-nvidia package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.15.0-1040-nvidia
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+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 2046329] Re: Random kernel panics related to page fault in Ubuntu 23.04/23.10 server with QEMU

[Sibidharan]

I disabled iommu and still the crash happens and this happens very
randomly. Not as much frequent while gaming inside the Windows VM, but
still crash happens randomly. Someone please help me fix it, my server
is very unstable because of this.

[97751.636298] BUG: kernel NULL pointer dereference, address: 
[97751.636304] #PF: supervisor instruction fetch in kernel mode
[97751.636305] #PF: error_code(0x0010) - not-present page
[97751.636306] PGD 15645d067 P4D 15645d067 PUD 193973067 PMD 0 
[97751.636309] Oops: 0010 [#1] PREEMPT SMP NOPTI
[97751.636311] CPU: 5 PID: 0 Comm: swapper/5 Kdump: loaded Tainted: P   
O   6.5.0-14-generic #14-Ubuntu
[97751.636313] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 
1601 11/23/2023
[97751.636315] RIP: 0010:0x0
[97751.636349] Code: Unable to access opcode bytes at 0xffd6.
[97751.636350] RSP: 0018:ab35c01abdf8 EFLAGS: 00010046
[97751.636351] RAX: 58e7938ec63a RBX: ab35c01abdf8 RCX: 
[97751.636352] RDX:  RSI:  RDI: 
[97751.636353] RBP: 939541798000 R08:  R09: 
[97751.636353] R10:  R11:  R12: b5f80392
[97751.636354] R13: 93b3feb730c0 R14: 0005 R15: 939541798000
[97751.636355] FS:  () GS:93b3feb4() 
knlGS:
[97751.636356] CS:  0010 DS:  ES:  CR0: 80050033
[97751.636357] CR2: ffd6 CR3: 000105f14000 CR4: 00752ee0
[97751.636358] PKRU: 5554
[97751.636359] Call Trace:
[97751.636360]  
[97751.636362]  ? show_regs+0x6d/0x80
[97751.636367]  ? __die+0x24/0x80
[97751.636369]  ? page_fault_oops+0x99/0x1b0
[97751.636373]  ? do_user_addr_fault+0x316/0x6b0
[97751.636374]  ? exc_page_fault+0x83/0x1b0
[97751.636377]  ? asm_exc_page_fault+0x27/0x30
[97751.636380]  ? sched_clock_cpu+0x12/0x1e0
[97751.636384]  ? psi_task_switch+0x33/0x270
[97751.636387]  ? __schedule+0x391/0x770
[97751.636390]  ? schedule_idle+0x2a/0x50
[97751.636391]  ? do_idle+0xb7/0xf0
[97751.636393]  ? cpu_startup_entry+0x1d/0x20
[97751.636394]  ? start_secondary+0x129/0x160
[97751.636397]  ? secondary_startup_64_no_verify+0x17e/0x18b
[97751.636401]  
[97751.636402] Modules linked in: tls snd_seq_dummy snd_hrtimer rfcomm 
vhost_net tap xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM 
xt_MASQUERADE xt_conntrack nft_masq zfs(PO) spl(O) wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel vhost_vsock 
vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock nf_conntrack_netlink 
nfnetlink_acct nft_chain_nat ip6t_REJECT nf_reject_ipv6 ipt_REJECT 
nf_reject_ipv4 xt_multiport xt_cgroup xt_mark xt_owner xt_tcpudp nft_compat 
nf_tables nfnetlink overlay cmac algif_hash algif_skcipher bridge af_alg stp 
llc bnep openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 binfmt_misc nls_iso8859_1 snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda intel_rapl_msr snd_hda_ext_core 
intel_rapl_common snd_soc_acpi_intel_match
[97751.636439]  intel_uncore_frequency snd_soc_acpi 
intel_uncore_frequency_common snd_intel_dspcfg snd_intel_sdw_acpi 
intel_tcc_cooling x86_pkg_temp_thermal snd_hda_codec intel_powerclamp 
snd_hda_core coretemp snd_hwdep soundwire_generic_allocation soundwire_bus 
snd_soc_core iwlmvm kvm_intel snd_compress ac97_bus snd_pcm_dmaengine mac80211 
snd_pcm kvm libarc4 snd_seq_midi snd_seq_midi_event snd_rawmidi btusb btrtl 
cmdlinepart btbcm snd_seq irqbypass btintel spi_nor btmtk mfd_aaeon eeepc_wmi 
asus_nb_wmi snd_seq_device bluetooth mtd snd_timer asus_wmi rapl iwlwifi 
pmt_telemetry ledtrig_audio ecdh_generic spi_intel_pci pmt_class mei_hdcp snd 
intel_cstate mei_pxp sparse_keymap i2c_i801 platform_profile wmi_bmof soundcore 
input_leds spi_intel joydev i2c_smbus ecc cfg80211 intel_vsec acpi_tad acpi_pad 
mac_hid mei_me mei dm_multipath msr parport_pc ppdev lp parport efi_pstore 
dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq
[97751.636484]  libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid 
i915 drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul cec 
crc32_pclmul polyval_clmulni rc_core polyval_generic ghash_clmulni_intel 
drm_kms_helper aesni_intel nvme crypto_simd r8169 cryptd drm nvme_core ahci 
realtek intel_lpss_pci xhci_pci intel_lpss libahci nvme_common vmd idma64 
xhci_pci_renesas video wmi pinctrl_alderlake
[97751.636505] CR2: 

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

Title:
  

[Kernel-packages] [Bug 2045482] Re: USB-C to HDMI Sound Not Functioning

[Alex]

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

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

Title:
  USB-C to HDMI Sound Not Functioning

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hello there,

  I have Ubuntu 23.10 installed on a Dell XPS 13 9300 with a USB-C to
  HDMI adapter attached to a Samsung television. When I try to set the
  output sound to the Samsung Television, no sound output is heard.
  However, when setting to the internal speakers there is sound output.
  The cable and adapter are fine as I have tested the USB-C to HDMI
  adapter cable with another device and sound output is confirmed. I
  have not had this issue with previous iterations of Ubuntu such as
  23.04 & 22.04 LTS.

  
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-13-generic 6.5.0-13.13
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe8491 F wireplumber
   /dev/snd/seq:joe8485 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  2 16:07:39 2023
  InstallationDate: Installed on 2023-10-12 (51 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic 
root=UUID=41952781-0b82-430a-a2af-114815de54ab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-13-generic N/A
   linux-backports-modules-6.5.0-13-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0Y4GNJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd08/08/2023:br1.20:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr:sku096D:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

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

[queeup]

Happy to report, my problem solved with Gnome 45.1 & Fedora 39. No
disconnect or freeze with apple trackpad.


Fedora 39 Silverblue
Intel AX200 bluetooth
Apple Magic Trackpad V1 (05AC:030E)

```
$ uname -r
6.6.3-200.fc39.x86_64

$ rpm -qa iwlwifi*
iwlwifi-dvm-firmware-2023-1.fc39.noarch
iwlwifi-mvm-firmware-2023-1.fc39.noarch

```

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

Title:
  Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
  minutes

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got an Apple's Magic Trackpad. I paired it with Ubuntu
  18.04.2 LTS and worked out of the box, no special drivers needed.

  However, I experience frequent disconnections that last a few seconds
  (5-15 seconds usually), which are quite annoying, as the cursor stops
  responding during that interval. The trackpad connects by itself after
  that period. That usually happens every 20-40 minutes.

  I use the onboard bluetooth device of my laptop. I also have, at the
  same time, two more bluetooth devices (keyboard and mouse) and they do
  not experience that issue, just the trackpad. On ocassion I use
  bluetooth headphones which work just fine.

  First of all:

  Using the command "bluetoothctl" I get the following every time I
  experience a disconnection:

  [CHG] Device F4:1B:A1:33:F9:8D Connected: no
  [CHG] Device F4:1B:A1:33:F9:8D Connected: yes

  Checking "dmesg" I can see more information: (if I am not mistaken,
  this shows 4 disconnections)

  
  [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
  [ 1609.070797] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23
  [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 1676.917377] NET: Registered protocol family 38
  [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0
  [ 1872.815559] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24
  [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0
  [ 3101.683100] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98
  [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0
  [ 3110.683929] input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26
  [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID 
v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98

  
  And this is what journalctl -b shows at the moment of the 
disconnection/reconnection:

  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: removing device Apple Wireless Trackpad
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option 
"fd" "64" (1,63 m)˜
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - 
Apple Wireless Trackpad: device removed
  de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 
'array' failed
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
UnloadModule: "libinput"
  de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
systemd-logind: releasing fd for 13:80
  de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown 
main item tag 0x0
  de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25
  de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: 
input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 
64:5d:86:86:3f:98
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) 
config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1)
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input 
driver specified, ignoring this device.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This 
device may have been added with another device file.
  de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session

[Kernel-packages] [Bug 2046576] [NEW] Jammy update: v6.1.62 upstream stable release

[Timo Aaltonen]

Public bug reported:


SRU Justification

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

   v6.1.62 upstream stable release
   from git://git.kernel.org/


Linux 6.1.62
ASoC: SOF: sof-pci-dev: Fix community key quirk detection
ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection
misc: pci_endpoint_test: Add deviceID for J721S2 PCIe EP device support
tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks
tty: 8250: Add support for Intashield IX cards
tty: 8250: Add support for additional Brainboxes PX cards
tty: 8250: Fix up PX-803/PX-857
tty: 8250: Fix port count of PX-257
tty: 8250: Add support for Intashield IS-100
tty: 8250: Add support for Brainboxes UP cards
tty: 8250: Add support for additional Brainboxes UC cards
tty: 8250: Remove UC-257 and UC-431
tty: n_gsm: fix race condition in status line change on dead connections
usb: raw-gadget: properly handle interrupted requests
usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm()
usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" 
compatibility
PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device
ALSA: usb-audio: add quirk flag to enable native DSD for McIntosh devices
mmap: fix error paths with dup_anon_vma()
mm/mempolicy: fix set_mempolicy_home_node() previous VMA pointer
x86: KVM: SVM: always update the x2avic msr interception
perf evlist: Avoid frequency mode for the dummy event
power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint
ceph_wait_on_conflict_unlink(): grab reference before dropping ->d_lock
io_uring: kiocb_done() should *not* trust ->ki_pos if ->{read,write}_iter() 
failed
powerpc/mm: Fix boot crash with FLATMEM
r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en()
r8152: Check for unplug in rtl_phy_patch_request()
net: chelsio: cxgb4: add an error code check in t4_load_phy_fw
drm/amdgpu: Reserve fences for VM update
platform/mellanox: mlxbf-tmfifo: Fix a warning message
netfilter: nf_tables: audit log object reset once per table
LoongArch: Replace kmap_atomic() with kmap_local_page() in copy_user_highpage()
LoongArch: Export symbol invalid_pud_table for modules building
gpu/drm: Eliminate DRM_SCHED_PRIORITY_UNSET
drm/amdgpu: Unset context priority is now invalid
scsi: mpt3sas: Fix in error path
fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()
fbdev: omapfb: fix some error codes
drm/ttm: Reorder sys manager cleanup step
ASoC: codecs: tas2780: Fix log of failed reset via I2C.
ASoC: rt5650: fix the wrong result of key button
efi: fix memory leak in krealloc failure handling
netfilter: nfnetlink_log: silence bogus compiler warning
spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
fs/ntfs3: Avoid possible memory leak
fs/ntfs3: Fix directory element type detection
fs/ntfs3: Fix NULL pointer dereference on error in attr_allocate_frame()
fs/ntfs3: Fix possible NULL-ptr-deref in ni_readpage_cmpr()
fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)
fs/ntfs3: Write immediately updated ntfs state
fs/ntfs3: Add ckeck in ni_update_parent()
fbdev: atyfb: only use ioremap_uc() on i386 and ia64
Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport
powerpc/85xx: Fix math emulation exception
dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe
irqchip/stm32-exti: add missing DT IRQ flag translation
irqchip/riscv-intc: Mark all INTC nodes as initialized
net: sched: cls_u32: Fix allocation size in u32_init()
ASoC: tlv320adc3xxx: BUG: Correct micbias setting
coresight: tmc-etr: Disable warnings for allocation failures
ASoC: simple-card: fixup asoc_simple_probe() error handling

** Affects: linux-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Jammy update: v6.1.62 upstream stable release

Status in linux-oem-6.1 package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch ha

[Kernel-packages] [Bug 2046577] [NEW] Jammy update: v6.1.63 upstream stable release

[Timo Aaltonen]

Public bug reported:


SRU Justification

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

   v6.1.63 upstream stable release
   from git://git.kernel.org/


Linux 6.1.63
virtio/vsock: fix header length on skb merging
virtio/vsock: Fix uninit-value in virtio_transport_recv_pkt()
virtio/vsock: fix leaks due to missing skb owner
vsock/loopback: use only sk_buff_head.lock to protect the packet queue
virtio/vsock: don't drop skbuff on copy failure
virtio/vsock: remove redundant 'skb_pull()' call
virtio/vsock: don't use skbuff state to account credit
wifi: cfg80211: fix kernel-doc for wiphy_delayed_work_flush()
btrfs: use u64 for buffer sizes in the tree search ioctls
Revert "mmc: core: Capture correct oemid-bits for eMMC cards"
x86/amd_nb: Use Family 19h Models 60h-7Fh Function 4 IDs
io_uring/net: ensure socket is marked connected on connect retry
tracing/kprobes: Fix the order of argument descriptions
fbdev: fsl-diu-fb: mark wr_reg_wa() static
fbdev: imsttfb: fix a resource leak in probe
fbdev: imsttfb: Fix error path of imsttfb_probe()
spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies
ASoC: dapm: fix clock get name
ASoC: hdmi-codec: register hpd callback on component probe
ASoC: mediatek: mt8186_mt6366_rt1019_rt5682s: trivial: fix error messages
drm/syncobj: fix DRM_SYNCOBJ_WAIT_FLAGS_WAIT_AVAILABLE
RISC-V: Don't fail in riscv_of_parent_hartid() for disabled HARTs
netfilter: nat: fix ipv6 nat redirect with mapped and scoped addresses
netfilter: nft_redir: use `struct nf_nat_range2` throughout and deduplicate 
eval call-backs
netfilter: xt_recent: fix (increase) ipv6 literal buffer length
i2c: iproc: handle invalid slave state
r8169: respect userspace disabling IFF_MULTICAST
vsock/virtio: remove socket from connected/bound list on shutdown
virtio/vsock: replace virtio_vsock_pkt with sk_buff
blk-core: use pr_warn_ratelimited() in bio_check_ro()
nbd: fix uaf in nbd_open
tg3: power down device only on SYSTEM_POWER_OFF
nvme: fix error-handling for io_uring nvme-passthrough
net/smc: put sk reference if close work was canceled
net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
octeontx2-pf: Free pending and dropped SQEs
octeontx2-pf: qos send queues management
octeontx2-pf: Rename tot_tx_queues to non_qos_queues
selftests: pmtu.sh: fix result checking
net: stmmac: xgmac: Enable support for multiple Flexible PPS outputs
Fix termination state for idr_for_each_entry_ul()
net: r8169: Disable multicast filter for RTL8168H and RTL8107E
dccp/tcp: Call security_inet_conn_request() after setting IPv6 addresses.
dccp: Call security_inet_conn_request() after setting IPv4 addresses.
net: page_pool: add missing free_percpu when page_pool_init fail
octeontx2-pf: Fix holes in error code
octeontx2-pf: Fix error codes
inet: shrink struct flowi_common
bpf: Check map->usercnt after timer->timer is assigned
tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING
hsr: Prevent use after free in prp_create_tagged_frame()
llc: verify mac len before reading mac header
watchdog: ixp4xx: Make sure restart always works
Input: synaptics-rmi4 - fix use after free in rmi_unregister_function()
pwm: brcmstb: Utilize appropriate clock APIs in suspend/resume
pwm: sti: Reduce number of allocations and drop usage of chip_data
regmap: prevent noinc writes from clobbering cache
media: cec: meson: always include meson sub-directory in Makefile
media: dvb-usb-v2: af9035: fix missing unlock
media: cadence: csi2rx: Unregister v4l2 async notifier
media: cedrus: Fix clock/reset sequence
media: vidtv: mux: Add check and kfree for kstrdup
media: vidtv: psi: Add check for kstrdup
media: s3c-camif: Avoid inappropriate kfree()
media: mtk-jpegenc: Fix bug in JPEG encode quality selection
media: amphion: handle firmware debug message
media: bttv: fix use after free error due to btv->timeout timer
media: ov5640: Fix a memory leak when ov5640_probe fails
media: i2c: max9286: Fix some redundant of_node_put() calls
media: ov5640: fix vblank unchange issue when work at dvp mode
media: ov5640: Drop dead code using frame_interval
media: verisilicon: Do not enable G2 postproc downscale if source is narrower 
than destination
media: hantro: Check whether reset op is defined before use
pcmcia: ds: fix possible name leak in error path in pcmcia_device_add()
pcmcia: ds: fix refcount leak in pcmcia_device_add()
pcmcia: cs: fix possible hung task and memory leak pccardd()
rtc: pcf85363: fix wrong mask/val parameters in regmap_update_bits call
virt: sevguest: Fix passing a stack buffer

[Kernel-packages] [Bug 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command

[Aled Cuda]

Searching launchpad a bit more this seems possibly related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827

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

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729588/+files/ProcCpuinfoMinimal.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command

[Aled Cuda]

I have tried setting nfs_fasc through sysfs (after the module is loaded)
and remounting with "mount -o remount" but that does not clear the issue

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

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] Re: NFS latency spikes during openat syscalls associated with test_stateid RPC command

[Aled Cuda]

The server in question is a Synology NAS running 'DSM 7.2-64570 Update
3' but this at least on the surface appears to be a client side bug
because the same mounts on other machines (with the same options) are
fine and it can be cleared by a client reboot but not by a remount

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

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2046572/+attachment/5729591/+files/UdevDb.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729589/+files/ProcInterrupts.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729593/+files/acpidump.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729592/+files/WifiSyslog.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729590/+files/ProcModules.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729587/+files/ProcCpuinfo.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] Lsusb-v.txt

[Aled Cuda]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729586/+files/Lsusb-v.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] Lspci-vt.txt

[Aled Cuda]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729583/+files/Lspci-vt.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729581/+files/CurrentDmesg.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2046572/+attachment/5729582/+files/Lspci.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2046572/+attachment/5729584/+files/Lsusb.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] Lsusb-t.txt

[Aled Cuda]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729585/+files/Lsusb-t.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2046572/+attachment/5729579/+files/AlsaInfo.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Aled Cuda]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/2046572/+attachment/5729580/+files/CRDA.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/2046572

Title:
  NFS latency spikes during openat syscalls associated with test_stateid
  RPC command

Status in linux package in Ubuntu:
  New

Bug description:
  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious
  problems, an IPython instance in a conda environment installed in NFS
  takes around 2-3 minutes to start for example.

  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.

  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

  We're not using kerberos, just ip based authentication, our mount
  options are:

  exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
  
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

  We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm3334 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-04-05 (618 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IwConfig:
   lono wireless extensions.
   
   enp69s0   no wireless extensions.
   
   enp68s0   no wireless extensions.
  MachineType: ASUS System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
  ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-89-generic N/A
   linux-backports-modules-5.15.0-89-generic  N/A
   linux-firmware 1.187.39
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.15.0-89-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046572/+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 2046572] [NEW] NFS latency spikes during openat syscalls associated with test_stateid RPC command

[Aled Cuda]

Public bug reported:

About once a week the NFS mounts on our eda servers (the nfs clients)
slow to a crawl for a large number of workloads. strace reveals that
openat system calls for files in the mounts take between 0.1 and 0.3
seconds this can be seen directly by touching any file in the homedir
(this normally takes 0.001-0.002 seconds). This causes obvious problems,
an IPython instance in a conda environment installed in NFS takes around
2-3 minutes to start for example.

I originally thought that this was a manifestation of #2009325, but we
are on 5.15.0-89 and have seen this problem across several kernel
versions.

Additionally we don't see access rpc calls but we do see loads of test_stateid 
calls: 
- bursts of 300 or so periodically every couple seconds while idle
- 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no access calls)

We're not using kerberos, just ip based authentication, our mount
options are:

exoserver.example.com:/volume1/homes/cudaa on /home/cudaa type nfs4
(rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.219,local_lock=none,addr=xxx.xxx.xxx.146)

We see this on servers with both linux-image-5.15.0-89-generic and 
linux-headers-5.15.0-83-generic, and have seen it across a few versions (we 
have the hwe stack installed if that matters). I could upgrade them to 91 but 
the issue clears after a reboot and we don't have a reliable way to reproduce 
it so I'm going to keep one online for debugging.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm3334 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-04-05 (618 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
IwConfig:
 lono wireless extensions.
 
 enp69s0   no wireless extensions.
 
 enp68s0   no wireless extensions.
MachineType: ASUS System Product Name
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-89-generic 
root=UUID=ec5ca229-1bd1-461a-98fd-d0f4eba0dd26 ro fsck.mode=force 
fsck.repair=yes
ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-89-generic N/A
 linux-backports-modules-5.15.0-89-generic  N/A
 linux-firmware 1.187.39
RfKill:
 
Tags:  focal
Uname: Linux 5.15.0-89-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 03/04/2022
dmi.bios.release: 16.3
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1603
dmi.board.asset.tag: Default string
dmi.board.name: ROG ZENITH II EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: apport-collected focal

** Tags added: apport-collected focal

** Description changed:

  About once a week the NFS mounts on our eda servers (the nfs clients)
  slow to a crawl for a large number of workloads. strace reveals that
  openat system calls for files in the mounts take between 0.1 and 0.3
  seconds this can be seen directly by touching any file in the homedir
  (this normally takes 0.001-0.002 seconds). This causes obvious problems,
  an IPython instance in a conda environment installed in NFS takes around
  2-3 minutes to start for example.
  
  I originally thought that this was a manifestation of #2009325, but we
  are on 5.15.0-89 and have seen this problem across several kernel
  versions.
  
  Additionally we don't see access rpc calls but we do see loads of 
test_stateid calls: 
  - bursts of 300 or so periodically every couple seconds while idle
  - 380,452 test_stateid calls when an ipython instance is starting (zero 
access calls in the same period, when at idle we see 10,267 test_stateid calls 
over the same ~2:30 time period and again no

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[You-Sheng Yang]

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

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

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official 

[Kernel-packages] [Bug 2044150] Re: Missing CS35L41 firmware for HP G11 mWS models

[You-Sheng Yang]

verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.24.

** Tags added: verification-done-jammy

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing CS35L41 firmware for HP G11 mWS models. In dmesg output it
  has:

cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3   
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit 980373f58747 ("cirrus: Add CS35L41 firmware for HP G11 
models").

 
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe 
Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.65.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.85.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.bin: v0.65.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\gchen\Desktop\HP_Proj\HP_Warg14_103C8B45_220930_exported_tuning\6.61.1\tuning\230609\103C8C47_2306
  09_V01_A01.bin
 

 
  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == original bug report ==

  Upstream linux-firmware commit:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1580 F pulseaudio
   /dev/snd/controlC0:  u  1580 F pulseaudio
  CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img 
./boot/grub/grub.cfg ./casper/initrd
  CasperMD5CheckResult: fail
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-jammy-amd64-20230925-542
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-11-08 (34 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-stella-jammy-amd64-20230925-542
  IwConfig:
   lono wireless extensions.
   

[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200

[You-Sheng Yang]

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

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

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

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

Bug description:
  [SRU Justification]

  == linux-firmware ==

  [Impact]  

 


 
  Missing firmware for Intel BE200 on Intel Meteor Lake platform.   

 


 
  [Fix] 

 


 
  Needed firmware:  

 
  - WiFi:   

 
* a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with 
multiple RF modules")   
   
  - Bluetooth:  

 
* 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  


 
  The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and

 
  linux/noble.  

 


 
  [Test Case]   

 


 
  Boot with firmware blobs installed, and iwlwifi and btintel should probe  

 
  successfully without error.   

 


 
  [Where problems could occur]  
 

[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models

[You-Sheng Yang]

verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.24.

** Tags added: verification-done-jammy

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

Title:
  Missing CS35L41 firmware for Dell Oasis Models

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

Bug description:
  [SRU Justification]

  [Impact]
   
  Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:


 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis 
Models").
   
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe 
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94 
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176 
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin

  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == original bug report ==

  > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
  firmware.

  We probably need following firmware first.

  $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
  commit c8424cf03defa4a83b8305d1af7b1321ab62
  Author: Stefan Binding 
  Date: Thu Jul 13 17:16:45 2023 +0100

  cirrus: Add CS35L41 firmware for Dell Oasis Models

  Signed-off-by: Stefan Binding 

   WHENCE | 42 ++
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
   5 files changed, 42 insertions(+)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1052 F pulseaudio
  CasperMD5json:
   {
     "result": "skip"
   }
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
  DistributionChannelDescriptor:
   # This is the distribution channel descripto

[Kernel-packages] [Bug 2046569] [NEW] systemd's BPF IP filter causes kernel UBSAN (bpf/lpm_trie.c)

[Gabríel Arthúr Pétursson]

Public bug reported:

Execute the following command:

$ sudo systemd-run -t -p IPAddressDeny=any -p IPAddressAllow=::1 wget
http://[::1]

You can do this in the LiveCD, or on an installed system, the result is
the same.

Then, look through dmesg:

[  100.407555] 

[  100.407559] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/kernel/bpf/lpm_trie.c:194:14
[  100.407561] index 8 is out of range for type '__u8 [*]'
[  100.407563] CPU: 0 PID: 3726 Comm: wget Tainted: P   O   
6.5.0-9-generic #9-Ubuntu
[  100.407564] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
edk2-20230825-25.fc39 08/25/2023
[  100.407565] Call Trace:
[  100.407567]  
[  100.407569]  dump_stack_lvl+0x48/0x70
[  100.407581]  dump_stack+0x10/0x20
[  100.407583]  __ubsan_handle_out_of_bounds+0xc6/0x110
[  100.407587]  longest_prefix_match.isra.0+0x1bc/0x200
[  100.407590]  trie_lookup_elem+0x74/0xb0
[  100.407591]  bpf_prog_d668f615b93ed8ef_sd_fw_egress+0x64/0x86
[  100.407595]  __bpf_prog_run_save_cb+0x56/0x130
[  100.407597]  __cgroup_bpf_run_filter_skb+0x240/0x2e0
[  100.407599]  ip6_finish_output+0x183/0x360
[  100.407602]  ? nf_hook_slow+0x43/0xd0
[  100.407604]  ip6_output+0x70/0x150
[  100.407606]  ? __pfx_ip6_finish_output+0x10/0x10
[  100.407607]  ip6_xmit+0x2cb/0x6b0
[  100.407609]  ? ip6_dst_check+0xa3/0x110
[  100.407612]  ? __sk_dst_check+0x3d/0xb0
[  100.407614]  ? inet6_csk_route_socket+0x141/0x240
[  100.407618]  inet6_csk_xmit+0xef/0x160
[  100.407620]  __tcp_transmit_skb+0x572/0xa00
[  100.407623]  tcp_connect+0x401/0x4b0
[  100.407625]  tcp_v6_connect+0x54e/0x740
[  100.407627]  ? security_file_alloc+0x2e/0xf0
[  100.407630]  ? begin_current_label_crit_section+0x2b/0xe0
[  100.407633]  __inet_stream_connect+0x103/0x280
[  100.407636]  inet_stream_connect+0x3b/0x70
[  100.407637]  __sys_connect_file+0x6b/0x90
[  100.407640]  __sys_connect+0xb5/0xe0
[  100.407642]  __x64_sys_connect+0x18/0x30
[  100.407644]  do_syscall_64+0x59/0x90
[  100.407646]  ? do_syscall_64+0x68/0x90
[  100.407647]  ? exit_to_user_mode_prepare+0x30/0xb0
[  100.407651]  ? syscall_exit_to_user_mode+0x37/0x60
[  100.407654]  ? do_syscall_64+0x68/0x90
[  100.407655]  ? irqentry_exit+0x43/0x50
[  100.407656]  ? exc_page_fault+0x94/0x1b0
[  100.407658]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[  100.407661] RIP: 0033:0x7fc0ebf19164
[  100.407679] Code: 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 
00 00 90 f3 0f 1e fa 80 3d e5 c3 0d 00 00 74 13 b8 2a 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 18 89 54 24 0c 48 89
[  100.407681] RSP: 002b:7ffdc793a478 EFLAGS: 0202 ORIG_RAX: 
002a
[  100.407682] RAX: ffda RBX: 7ffdc793a500 RCX: 7fc0ebf19164
[  100.407683] RDX: 001c RSI: 7ffdc793a520 RDI: 0003
[  100.407684] RBP: 7ffdc793a520 R08: 0064 R09: 
[  100.407685] R10:  R11: 0202 R12: 0003
[  100.407685] R13: 0050 R14: 55c0f118a9c0 R15: 
[  100.407688]  
[  100.407688] 


ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1988 F wireplumber
 /dev/snd/seq:ubuntu 1984 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 17:17:56 2023
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-9-generic N/A
 linux-backports-modules-6.5.0-9-generic  N/A
 linux-firmware   

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

[Launchpad Bug Tracker]

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

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

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

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

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

Bug description:
  Hi,

  during boot the kernel logs the following messages:

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

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

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

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

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Fabio Augusto Miranda Martins]

For item 1:

 * Confirm that makedumpfile works as expected by triggering a kdump.

I can confirm that makedumpfile 1:1.6.7-1ubuntu2.5 from focal-
proposed/main worked well when I triggered a dump in a system:

ubuntu@fabio-small-makedumpfile:~$ sudo hostnamectl
   Static hostname: fabio-small-makedumpfile
 Icon name: computer-vm
   Chassis: vm
Machine ID: dee0adfb9aa54246b4d1e2fc62dd50f7
   Boot ID: adba6ba3977f4c758a7008013a7a6d1e
Virtualization: oracle
  Operating System: Ubuntu 20.04.6 LTS
Kernel: Linux 5.15.0-1049-oracle
  Architecture: x86-64
ubuntu@fabio-small-makedumpfile:~$ sudo kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x2c00
0xfd7f00
   /boot/vmlinuz-5.15.0-1049-oracle
kdump initrd: 
   /boot/initrd.img-5.15.0-1049-oracle
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-1049-oracle 
root=UUID=7d8611b4-d3e7-4f1a-a8f9-e1a7e5a2d2f9 ro console=tty1 console=ttyS0 
nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1 
crash_kexec_post_notifiers reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=1 irqpoll nousb" --initrd=/boot/initrd.img-5.15.0-1049-oracle 
/boot/vmlinuz-5.15.0-1049-oracle
ubuntu@fabio-small-makedumpfile:~$ sudo dpkg -l makedumpfile
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  makedumpfile   1:1.6.7-1ubuntu2.5 amd64VMcore extraction tool
ubuntu@fabio-small-makedumpfile:~$ sudo apt-cache policy makedumpfile
makedumpfile:
  Installed: 1:1.6.7-1ubuntu2.5
  Candidate: 1:1.6.7-1ubuntu2.5
  Version table:
 *** 1:1.6.7-1ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:1.6.7-1ubuntu2.4 500
500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal-updates/main 
amd64 Packages
 1:1.6.7-1ubuntu2 500
500 http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu focal/main amd64 
Packages


Output showing that it completed well:

[   54.490112] kdump-tools[676]: Starting kdump-tools:
[   54.876357] kdump-tools[686]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202312151524/dump-incomplete
Checking for memory holes : [100.0 %] \   [  
204.391465] reboot: Restarting system
   
And when I look at the crash, it's properly compressed (system had 1TB of RAM):

ubuntu@fabio-small-makedumpfile:~$ ls -lh /var/crash/202312151524
total 2.3G
-rw--- 1 root root 126K Dec 15 15:26 dmesg.202312151524
-rw--- 1 root root 2.3G Dec 15 15:26 dump.202312151524

Regards,
Fabio Martins

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the p

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

[Fabio Augusto Miranda Martins]

For item 2:

 * Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

Unfortunately I'm no longer able to reproduce the original issue.

Even running on the same hardware where this was originally noticed,
with the same kernel version (5.13.0-1027-oracle), makedumpfile from
focal-updates/main (1:1.6.7-1ubuntu2.4) is just working well:

[   53.223512] kdump-tools[693]: Starting kdump-tools:
[   53.623944] kdump-tools[702]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202312151415/dump-incomplete
Copying data  : [  196.965120] reboot: 
Restarting system
[ 22.0 %] | 

Unfortunately I don't have the information and I don't have access to
the original system to check what version of makedumpfile it was using
back then, so I could test the exact same makedumpfile+kernel versions.

I also tested kernel 5.13.0-1027-oracle + makedumpfile 1:1.6.7-1ubuntu2
from focal/main, and in this combinarion, makedumpfile fails with a
similar, but slightly different error, then falls back to cp:

[   53.721130] kdump-tools[690]: Starting kdump-tools:
[   54.121624] kdump-tools[699]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202312151434/dump-incomplete
[   54.249624] kdump-tools[719]: get_mm_sparsemem: Can't get the address of 
mem_section.
[   54.345410] kdump-tools[719]: The kernel version is not supported.
[   54.425405] kdump-tools[719]: The makedumpfile operation may be incomplete.
[   54.517391] kdump-tools[719]: makedumpfile Failed.
[   54.577916] kdump-tools[699]:  * kdump-tools: makedumpfile failed, falling 
back to 'cp'

However, using the latest makedumpfile from focal-updates/main
(1:1.6.7-1ubuntu2.4) fixes this situation, as mentioned / shown above.

Due to this reason, I can't conclude the item 2.

I'll work now on 1.

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

Title:
  makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
  pmd_pte."

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
   * On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with 
"__vtop4_x86_64: Can't get a valid pmd_pte."

   * makedumpfile falls back to cp for the dump, resulting in extremely
  large vmcores. This can impact both collection and analysis due to
  lack of space for the resulting vmcore.

   * This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
  
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

  commit 646456862df8926ba10dd7330abf3bf0f887e1b6
  Author: Kazuhito Hagio 
  Date:   Wed May 26 14:31:26 2021 +0900

  [PATCH] Increase SECTION_MAP_LAST_BIT to 5
  
  * Required for kernel 5.12
  
  Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
  ZONE_DEVICE section collisions") added a section flag
  (SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
  some machines like this:
  
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical 
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
  
  Increase SECTION_MAP_LAST_BIT to 5 to fix this.  The bit had not
  been used until the change, so we can just increase the value.
  
  Signed-off-by: Kazuhito Hagio 

  [Test Plan]
   * Confirm that makedumpfile works as expected by triggering a kdump.

   * Confirm that the patched makedumpfile works as expected on a system
  known to experience the issue.

   * Confirm that the patched makedumpfile is able to work with a cp-
  generated known affected vmcore to compress it. The unpatched version
  fails.

  [Where problems could occur]

   * This change could adversely affect the collection/compression of
  vmcores during a kdump situation resulting in fallback to cp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+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 2028065] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.24 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

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

Bug description:
  [SRU Justification]

  == linux-firmware ==

  [Impact]  

 


 
  Missing firmware for Intel BE200 on Intel Meteor Lake platform.   

 


 
  [Fix] 

 


 
  Needed firmware:  

 
  - WiFi:   

 
* a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with 
multiple RF modules")   
   
  - Bluetooth:  

 
* 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  


 
  The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and

 
  linux/noble.  

 
   

[Kernel-packages] [Bug 2028065] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.5 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

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

Bug description:
  [SRU Justification]

  == linux-firmware ==

  [Impact]  

 


 
  Missing firmware for Intel BE200 on Intel Meteor Lake platform.   

 


 
  [Fix] 

 


 
  Needed firmware:  

 
  - WiFi:   

 
* a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with 
multiple RF modules")   
   
  - Bluetooth:  

 
* 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  


 
  The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and

 
  linux/noble.  

 

[Kernel-packages] [Bug 2037390] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.24 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  In

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[Timo Aaltonen]

the test case requires testing with GA/HWE/OEM kernels, since they all
are affected

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party

[Kernel-packages] [Bug 2037390] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.5 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
 

[Kernel-packages] [Bug 2044150] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.24 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing CS35L41 firmware for HP G11 mWS models. In dmesg output it
  has:

cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3   
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit 980373f58747 ("cirrus: Add CS35L41 firmware for HP G11 
models").

 
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe 
Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.65.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.85.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.bin: v0.65.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\gchen\Desktop\HP_Proj\HP_Warg14_103C8B45_220930_exported_tuning\6.61.1\tuning\230609\103C8C47_2306
  09_V01_A01.bin
 

 
  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == orig

[Kernel-packages] [Bug 2044158] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.24 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing CS35L41 firmware for Dell Oasis Models

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

Bug description:
  [SRU Justification]

  [Impact]
   
  Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:


 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis 
Models").
   
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe 
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94 
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176 
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin

  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == original bug report ==

  > cs35l41-hda spi1-CS

[Kernel-packages] [Bug 2042039] Re: AUDIO POPPING After New Kernel install: 5.15.0-88.98

[Thomas Lindner]

For me this is solved with
5.15.0-91 and 6.2.0-39

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

Title:
  AUDIO POPPING After New Kernel install: 5.15.0-88.98

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  10.30.23 20:18

  RE: Linux Kernel 5.15.0-88.98

  ISSUE. BUG REPORT: New Kernel Makes Audio "POP".

  After upgrading to the New Kernel, whenever the audio is accessed, there is 
an annoying
  "popping sound", as if the channel is being turned on. This happens before 
any audio plays,
  sometimes after if the channel is shutting down. Audio output I am reporting 
is coming out
  of the 3.5mm TRRS speaker/mic jack to my headphones, etc.

  VERY ANNOYING, I rolled back to the previous kernel.

  I do have Pulse Audio installed, not sure if it might be an issue.
  Will report back if removal or reinstall fixes it.

  - Mic

  System:
Kernel: 5.15.0-87-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: 
Cinnamon 5.8.4
  tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria 
base: Ubuntu 22.04 jammy
  Machine:
Type: Laptop System: Acer product: Aspire E5-576G v: V1.47 serial: 

Mobo: KBL model: Ironman_SK v: V1.47 serial:  
UEFI-[Legacy]: Insyde
  v: 1.47 date: 09/06/2018
  Battery:
ID-1: BAT1 charge: 26.5 Wh (100.0%) condition: 26.5/62.2 Wh (42.7%) volts: 
12.7 min: 11.1
  model: PANASONIC AS16B5J serial:  status: Full
Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400 
serial: 
  charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Mouse M187 serial: 

  charge: 50% (should be ignored) status: N/A
  CPU:
Info: quad core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: 
Coffee Lake rev: A cache:
  L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 1471 high: 3156 min/max: 400/3400 cores: 1: 2498 2: 1973 
3: 1000 4: 794
  5: 796 6: 3156 7: 799 8: 758 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel UHD Graphics 620 vendor: Acer Incorporated ALI driver: i915 
v: kernel ports:
  active: DP-1 off: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917
Device-2: NVIDIA GP108M [GeForce MX150] vendor: Acer Incorporated ALI 
driver: nvidia
  v: 535.113.01 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 
10de:1d10
Device-3: Quanta HD WebCam type: USB driver: uvcvideo bus-ID: 1-7:6 
chip-ID: 0408:a030
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: DP-1 model: ViewSonic VX2757 res: 1920x1080 dpi: 82 diag: 686mm 
(27")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 
23.0.4-0ubuntu1~22.04.1
  direct render: Yes
  Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Acer Incorporated ALI 
driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
Sound Server-1: ALSA v: k5.15.0-87-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi 
v: kernel pcie:
  speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:24fb
IF: wlp3s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Acer Incorporated ALI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 
04:00.1
  chip-ID: 10ec:8168
IF: enp4s0f1 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
Local Storage: total: 1.36 TiB used: 143.29 GiB (10.3%)
ID-1: /dev/sda model: SD Ultra 3D 1TB size: 931.51 GiB speed: 6.0 Gb/s 
serial: 
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD4 size: 465.76 GiB 
speed: 6.0 Gb/s
  serial: 
  Partition:
ID-1: / size: 915.32 GiB used: 143.28 GiB (15.7%) fs: ext4 dev: /dev/sda3
ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
  Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: 
/swapfile
  Sensors:
System Temperatures: cpu: 48.0 C pch: 37.0 C mobo: N/A
Fan Speeds (RPM): N/A
  Repos:
Packages: 3240 apt: 3217 flatpak: 23
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/audio-recorder-ppa-jammy.list
  1: deb [signed-by=/etc/apt/keyrings/audio-recorder-ppa-jammy.gpg] https: 
//ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu jammy main
Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
  1: deb http: //packages.linuxmint.com victoria main upstream import 
backport
  2: deb http: //archive.ubuntu.com/ubu

[Kernel-packages] [Bug 2046063] Re: no boot to X with 5.15.0-91 and nvidia 390.157

[Jan Herold]

linux-headers-5.15.0-91 was not installed but the other associated
packages. Reinstalling of this version fixed the problem.

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

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

Title:
  no boot to X with 5.15.0-91 and nvidia 390.157

Status in linux-meta package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 20.04
  5.15.0-91-generic
  NVIDIA 390.157

  PC gets stuck at the terminal when booting. Can start startx manually,
  but the NVIDIA driver is not used.

  No problems with 5.15.0-89.

  I have another PC with NVIDIA 470.223.02, kernel 5.15.0-91 works
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2046063/+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 2046553] [NEW] i am unable to pair and connect blutooth sudo apt-get install fwupd sudo fwupdmgr update Reading package lists... Done Building dependency tree... Done Reading st

[deepshadow]

Public bug reported:

sudo apt-get install fwupd
sudo fwupdmgr update
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
fwupd is already the newest version (1.7.9-1~22.04.3).
fwupd set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Devices with no available firmware updates


i have configered also but no problem found
Type: Primary  Bus: USB
BD Address: 34:41:5D:32:F1:53  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:19216 acl:0 sco:0 events:2629 errors:0
TX bytes:603774 acl:0 sco:0 commands:2570 errors:0

please fix this

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1.1
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 18:29:38 2023
InstallationDate: Installed on 2023-08-31 (106 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More&Better]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 7490
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.product.sku: 081C
dmi.sys.vendor: Dell Inc.
hciconfig:

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


** Tags: amd64 apport-bug jammy

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

Title:
  i am unable to pair and connect blutoothsudo apt-get install
  fwupd sudo fwupdmgr update Reading package lists... Done Building
  dependency tree... Done Reading state information... Done fwupd is
  already the newest version (1.7.9-1~22.04.3). fwupd set to manually
  installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not
  upgraded. Devices with no available firmware updates  ** i
  have done this no updatws found but i am unable to connect bt devices
  such as earbud

Status in bluez package in Ubuntu:
  New

Bug description:
  sudo apt-get install fwupd
  sudo fwupdmgr update
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  fwupd is already the newest version (1.7.9-1~22.04.3).
  fwupd set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Devices with no available firmware updates


  i have configered also but no problem found
  Type: Primary  Bus: USB
BD Address: 34:41:5D:32:F1:53  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:19216 acl:0 sco:0 events:2629 errors:0
TX bytes:603774 acl:0 sco:0 commands:2570 errors:0

  please fix this

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 18:29:38 2023
  InstallationDate: Installed on 2023-08-31 (106 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More&Better]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=3e

[Kernel-packages] [Bug 2046551] [NEW] why turbostat report C-state with ACPI keyword on RPL-P?

[Ionut Nechita]

Public bug reported:

Hi Ubuntu Kernel Team,

I have one question regarding C-states and Thermal functions.

Why turbostat report three C-states with ACPI keyword(CxACPI)?

Shouldn't I see up to 8 states inclusive? C7-C8?

<
cpu0: POLL: CPUIDLE CORE POLL IDLE
cpu0: C1ACPI: ACPI FFH MWAIT 0x0
cpu0: C2ACPI: ACPI FFH MWAIT 0x21
cpu0: C3ACPI: ACPI FFH MWAIT 0x60
>

# sudo turbostat

turbostat version 2023.03.17 - Len Brown 
Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic 
root=UUID=33f926b8-92d0-49f9-8c4b-f387ad216fdf ro rootflags=subvol=@ quiet 
splash vt.handoff=7
CPUID(0): GenuineIntel 0x20 CPUID levels
CPUID(1): family:model:stepping 0x6:ba:2 (6:186:2) microcode 0x4305
CPUID(0x8000): max_extended_levels: 0x8008
CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM
CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp, HWPpkg, EPB
cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH TURBO)
CPUID(7): No-SGX Hybrid
CPUID(0x15): eax_crystal: 2 ebx_tsc: 104 ecx_crystal_hz: 3840
TSC: 1996 MHz (3840 Hz * 104 / 2 / 100)
CPUID(0x16): base_mhz: 2000 max_mhz: 4800 bus_mhz: 100
cpu0: MSR_MISC_PWR_MGMT: 0x30c2 (ENable-EIST_Coordination ENable-EPB 
DISable-OOB)
RAPL: 9362 sec. Joule Counter Range, at 28 Watts
cpu0: MSR_PLATFORM_INFO: 0x804043cf8811400
4 * 100.0 = 400.0 MHz max efficiency frequency
20 * 100.0 = 2000.0 MHz base frequency
cpu0: MSR_IA32_POWER_CTL: 0x00f4005f (C1E auto-promotion: ENabled)
cpu0: MSR_TURBO_RATIO_LIMIT: 0x282828282d2d3030
40 * 100.0 = 4000.0 MHz max turbo 8 active cores
40 * 100.0 = 4000.0 MHz max turbo 7 active cores
40 * 100.0 = 4000.0 MHz max turbo 6 active cores
40 * 100.0 = 4000.0 MHz max turbo 5 active cores
45 * 100.0 = 4500.0 MHz max turbo 4 active cores
45 * 100.0 = 4500.0 MHz max turbo 3 active cores
48 * 100.0 = 4800.0 MHz max turbo 2 active cores
48 * 100.0 = 4800.0 MHz max turbo 1 active cores
cpu0: MSR_SECONDARY_TURBO_RATIO_LIMIT: 0x2424242425252525
36 * 100.0 = 3600.0 MHz max turbo 8 active cores
36 * 100.0 = 3600.0 MHz max turbo 7 active cores
36 * 100.0 = 3600.0 MHz max turbo 6 active cores
36 * 100.0 = 3600.0 MHz max turbo 5 active cores
37 * 100.0 = 3700.0 MHz max turbo 4 active cores
37 * 100.0 = 3700.0 MHz max turbo 3 active cores
37 * 100.0 = 3700.0 MHz max turbo 2 active cores
37 * 100.0 = 3700.0 MHz max turbo 1 active cores
cpu0: MSR_CONFIG_TDP_NOMINAL: 0x0013 (base_ratio=19)
cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x000d00a0 (PKG_MIN_PWR_LVL1=0 PKG_MAX_PWR_LVL1=0 
LVL1_RATIO=13 PKG_TDP_LVL1=160)
cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00140118 (PKG_MIN_PWR_LVL2=0 PKG_MAX_PWR_LVL2=0 
LVL2_RATIO=20 PKG_TDP_LVL2=280)
cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0)
cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x0012 (MAX_NON_TURBO_RATIO=18 lock=0)
cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x7408 (UNdemote-C1, demote-C1, UNlocked, 
pkg-cstate-limit=8 (unlimited))
Uncore Frequency pkg0 die0: 400 - 4200 MHz (400 - 4200 MHz)
/dev/cpu_dma_latency: 20 usec (default)
current_driver: intel_idle
current_governor: menu
current_governor_ro: menu
cpu0: POLL: CPUIDLE CORE POLL IDLE
cpu0: C1ACPI: ACPI FFH MWAIT 0x0
cpu0: C2ACPI: ACPI FFH MWAIT 0x21
cpu0: C3ACPI: ACPI FFH MWAIT 0x60
cpu0: cpufreq driver: intel_pstate
cpu0: cpufreq governor: powersave
cpufreq intel_pstate no_turbo: 0
cpu0: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-Prefetch-pair 
L1-Prefetch L1-IP-Prefetch)
cpu0: MSR_PM_ENABLE: 0x0001 (HWP)
cpu0: MSR_HWP_CAPABILITIES: 0x0110193d (high 61 guar 25 eff 16 low 1)
cpu0: MSR_HWP_REQUEST: 0x3d06 (min 6 max 61 des 0 epp 0x0 window 0x0 pkg 
0x0)
cpu0: MSR_HWP_REQUEST_PKG: 0x8000ff01 (min 1 max 255 des 0 epp 0x80 window 0x0)
cpu0: MSR_HWP_INTERRUPT: 0x0001 (EN_Guaranteed_Perf_Change, 
Dis_Excursion_Min)
cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-Excursion_Min)
cpu0: EPB: 7 (custom)
cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 Joules, 
0.000977 sec.)
cpu0: MSR_PKG_POWER_INFO: 0x00e0 (28 W TDP, RAPL 0 - 0 W, 0.00 sec.)
cpu0: MSR_PKG_POWER_LIMIT: 0x4282dd80e0 (UNlocked)
cpu0: PKG Limit #1: ENabled (28.000 Watts, 28.00 sec, clamp ENabled)
cpu0: PKG Limit #2: ENabled (64.000 Watts, 0.002441* sec, clamp DISabled)
cpu0: MSR_VR_CURRENT_CONFIG: 0x03f0
cpu0: PKG Limit #4: 126.00 Watts (UNlocked)
cpu0: MSR_DRAM_POWER_LIMIT: 0x (UNlocked)
cpu0: DRAM Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_PP0_POLICY: 9
cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked)
cpu0: Cores Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_PP1_POLICY: 13
cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked)
cpu0: GFX Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled)
cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x8064 (100 C)
cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x8839 (43 C)
cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0203 (100 C, 100 C)
cpu0: MSR_PKGC3_IRTL: 0x (NOTvalid, 0 ns)
cpu0: MSR_PKGC6_IRTL: 0x00

[Kernel-packages] [Bug 2045913] Re: Update the NVIDIA 535 driver

[Dimitri John Ledkov]

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

** Also affects: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Importance: High
 Assignee: Alberto Milone (albertomilone)
   Status: In Progress

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Update the NVIDIA 535 driver

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Lunar:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  535.146.02

    * New upstream release (LP: #2045913):
  - Fixed a bug that could cause some multi-GPU systems to crash on
    suspend.
  - Fixed a bug that could cause the system to crash when an
    application is run with __NV_PRIME_RENDER_OFFLOAD=1.
  - Fixed a bug which prevented application profiles from getting
    applied to PRIME Render Offloaded applications running via
    Wine.
  - Disabled PRIME Display Offload Sink support for virtual
    displays on datacenter GPUs. This prevents unusable desktop
    layouts from getting automatically configured on systems with a
    mix of physical and virtual displays.
  - Fixed a bug that caused high CPU usage during system suspend,
    which could lead to the system not entering s2idle in some
    cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2045913/+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 2046547] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-comm

[Amr Mohamed Salah]

Public bug reported:

this happens when i try sudo apt install linux-tools-common

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 hwdata:amd64: Install
 linux-tools-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  amr 968 F pulseaudio
 /dev/snd/pcmC0D0p:   amr 968 F...m pulseaudio
 /dev/snd/seq:amr 965 f fluidsynth
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Dec 15 14:15:12 2023
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1045.51
InstallationDate: Installed on 2023-12-08 (6 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: LENOVO 80NT
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=bffe25dc-d460-4864-8139-25d9ea4308ed ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1045.51
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2015
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: CFCN21WW(V1.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo ideapad 5
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 500-15ISK
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvrCFCN21WW(V1.03):bd08/10/2015:br1.21:efr1.21:svnLENOVO:pn80NT:pvrLenovoideapad500-15ISK:rvnLENOVO:rnLenovoideapad5:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad500-15ISK:skuLENOVO_MT_80NT_BU_idea_FM_Lenovoideapad500-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80NT
dmi.product.sku: LENOVO_MT_80NT_BU_idea_FM_Lenovo ideapad 500-15ISK
dmi.product.version: Lenovo ideapad 500-15ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/acpidbg', which is also in package
  linux-intel-iotg-tools-common 5.15.0-1045.51

Status in linux package in Ubuntu:
  New

Bug description:
  this happens when i try sudo apt install linux-tools-common

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   hwdata:amd64: Install
   linux-tools-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr 968 F pulseaudio
   /dev/snd/pcmC0D0p:   amr 968 F...m pulseaudio
   /dev/snd/seq:amr 965 f fluidsynth
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Dec 15 14:15:12 2023
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-intel-iotg-tools-common 5.15.0-1045.51
  InstallationDate: Installed on 2023-12-08 (6 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: LENOVO 80NT
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=bffe25dc-d460-4864-8139-25d9ea4308ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-intel-iotg-tools-common 5.15.0-1045.51
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2015
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CFCN21WW(V1.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.boa

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[Juerg Haefliger]

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

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third

[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

[Juerg Haefliger]

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

Title:
  Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Mantic:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
  example:

    iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
    iwlwifi :00:14.3: no suitable firmware found!
    iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
    iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
    iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  And Bluetooth:

    Bluetooth: hci0: Failed to load Intel firmware file
  intel/ibt-0180-0041.sfi (-2)

  [Fix]

  There are plenty of commits to be SRUed in the WiFi part due to modifications 
to
  pnvm files. Intel may and may not update their unversioned pnvm file upon new
  releases, therefore on pulling any ucode version of iwlwifi firmware, the full
  history of an unversioned pnvm file has to be pulled as well, and each may or
  may not pull an older ucode version of that firmware.

  Most of the commits have been included in Mantic and newer. For Noble, it
  depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
  core80-39 release") that has been backported to Jammy and Mantic in bug 
2042716.

  Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
  types with multiple RF modules") is also being backported in bug 2028065.

  [Test Case]

  Boot with firmware blobs installed, and iwlwifi and btintel should probe
  successfully without error.

  [Where problems could occur]

  While this introduces support for new hardware on new platforms, expect every
  possible problem.

  [Other Info]

  We're to support oem-6.5/jammy, and mantic for best effort.

  V2: pull also core80 firmware blobs for AX211 on RPL and AX201.

  == original bug report ==

  WIFI FW:
    Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, 
rev=0x441, rfid=0x2010d000
    Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable 
firmware found!
    Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version 
required: iwlwifi-ma-b0-gf-a0-59
    Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version 
supported: iwlwifi-ma-b0-gf-a0-83
    Line 1121: [ 7.971721] iwlwifi :00:14.3: check 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

  Bluetooth FW:
    Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel 
firmware file intel/ibt-0180-0041.sfi (-2)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-jiayi-jammy-amd64-20230706-44
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-07-06 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-jiayi-jammy-amd64-20230706-44
  MachineType: Intel Corporation Meteor Lake Client Platform
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem 
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9004-oem N/A
   linux-backports-modules-6.5.0-9004-oem  N/A
   linux-firmware  
20220329.git681281e4-0ubuntu3.19+exp.83
  Tags: third-party-packages jammy
  Uname: Linux 6.5.0-9004-oem x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third pa

[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models

[Juerg Haefliger]

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

Title:
  Missing CS35L41 firmware for Dell Oasis Models

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

Bug description:
  [SRU Justification]

  [Impact]
   
  Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:


 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis 
Models").
   
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe 
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94 
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176 
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin

  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == original bug report ==

  > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
  firmware.

  We probably need following firmware first.

  $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
  commit c8424cf03defa4a83b8305d1af7b1321ab62
  Author: Stefan Binding 
  Date: Thu Jul 13 17:16:45 2023 +0100

  cirrus: Add CS35L41 firmware for Dell Oasis Models

  Signed-off-by: Stefan Binding 

   WHENCE | 42 ++
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
   cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
   5 files changed, 42 insertions(+)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1052 F pulseaudio
  CasperMD5json:
   {
     "result": "skip"
   }
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more 

[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200

[Juerg Haefliger]

** Changed in: linux-firmware (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

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

Title:
  Support for Intel Discrete Gale Peak2/BE200

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

Bug description:
  [SRU Justification]

  == linux-firmware ==

  [Impact]  

 


 
  Missing firmware for Intel BE200 on Intel Meteor Lake platform.   

 


 
  [Fix] 

 


 
  Needed firmware:  

 
  - WiFi:   

 
* a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with 
multiple RF modules")   
   
  - Bluetooth:  

 
* 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  
* ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth 
BE200") 
  


 
  The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and

 
  linux/noble.  

 


 
  [Test Case]   

 


 
  Boot with firmware blobs installed, and iwlwifi and btintel should probe  

 
  successfully without error.   

 


 
  [Where problems could occur]  
   

[Kernel-packages] [Bug 2044150] Re: Missing CS35L41 firmware for HP G11 mWS models

[Juerg Haefliger]

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

Title:
  Missing CS35L41 firmware for HP G11 mWS models

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

Bug description:
  [SRU Justification]

  [Impact]

  Missing CS35L41 firmware for HP G11 mWS models. In dmesg output it
  has:

cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3   
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
  
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
 

 
  [Fix] 
 

 
  Upstream commit 980373f58747 ("cirrus: Add CS35L41 firmware for HP G11 
models").

 
  [Test Case]   
 

 
  Expecting the right fw blobs are used:
 

 
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), 
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.wmfw: Fri 31 Mar 2023 10:42:49 W. Europe 
Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2 
v0.65.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.85.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c 
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 
cirrus/cs35l41-dsp1-spk-prot-103c8c71.bin: v0.65.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot: 
C:\Users\gchen\Desktop\HP_Proj\HP_Warg14_103C8B45_220930_exported_tuning\6.61.1\tuning\230609\103C8C47_2306
  09_V01_A01.bin
 

 
  [Where problems could occur]

  That's the official firmware to support this platform. No known
  problem so far.

  [Other Info]

  While this has been available on Mantic and Noble, we only nominate Jammy for
  oem-6.5.

  == original bug report ==

  Upstream linux-firmware commit:
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=980373f5874787b7d98a204feabdccc971c42dc0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1580 F pulseaudio
   /dev/snd/controlC0:  u  1580 F pulseaudio
  CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img 
./boot/grub/grub.cfg ./casper/initrd
  CasperMD5CheckResult: fail
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-jammy-amd64-20230925-542
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-11-08 (34 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-stella-jammy-amd64-20230925-542
  IwConfig:
   lono wireless extensions.
   
   enx00e04c6801ec  no wireless 

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

[Chengen Du]

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

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

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

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

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

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

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

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

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

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

  ==

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

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

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources on

[Kernel-packages] [Bug 2046534] Re: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration

[Chengen Du]

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

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

Title:
  Page fault in RDMA ODP triggers BUG_ON during MMU notifier
  registration

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

Bug description:
  [Impact]
  When a page fault is triggered in RDMA ODP, it registers an MMU notifier 
during the process.
  Unfortunately, an error arises due to a race condition where the mm is 
released while attempting to register a notifier.
  ==
  Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at 
mm/mmu_notifier.c:255!
  Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 
EFLAGS: 00010246
  Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: 
a0f913ba5800 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: 
c0b601c7 RDI: a0f913ba5850
  Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX:  RBX: 
c0b5a060 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: 
a1152ed3c400 RDI: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: 
a1163f4f50e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: 
 R12: a1152c923b80
  Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: 
a1163f7350e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: 
 R12: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: 
a1152c923bf8 R15: a114f8127800
  Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS:  () 
GS:a1163f4c() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: 
a1152ed3c478 R15: a1101cbfbc00
  Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS:  () 
GS:a1163f70() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 
001722472004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 
001f9f1fc004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace:
  Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.923112]  
mmu_notifier_get_locked+0x5f/0xe0
  Oct 14 23:38:32 bnode001 kernel: [1576115.923867] Call Trace:
  Oct 14 23:38:32 bnode001 kernel: [1576115.923870]  ? 
mmu_notifier_get_locked+0x79/0xe0
  Oct 14 23:38:32 bnode001 kernel: [1576115.924645]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
  Oct 14 23:38:32 bnode001 kernel: [1576115.925409]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
  Oct 14 23:38:32 bnode001 kernel: [1576115.926161]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.926906]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.927651]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.928393]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.929131]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.929866]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.930610]  
process_one_work+0x1eb/0x3b0
  Oct 14 23:38:32 bnode001 kernel: [1576115.931351]  
process_one_work+0x1eb/0x3b0
  Oct 14 23:38:32 bnode001 kernel: [1576115.932084]  worker_thread+0x4d/0x400
  Oct 14 23:38:32 bnode001 kernel: [1576115.932813]  worker_thread+0x4d/0x400
  Oct 14 23:38:32 bnode001 kernel: [1576115.933543]  kthread+0x104/0x140
  Oct 14 23:38:32 bnode001 kernel: [1576115.934272]  kthread+0x104/0x140
  Oct 14 23:38:32 bnode001 kernel: [1576115.934986]  ? 

[Kernel-packages] [Bug 2046534] Re: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration

[Chengen Du]

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Chengen Du (chengendu)

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

Title:
  Page fault in RDMA ODP triggers BUG_ON during MMU notifier
  registration

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New

Bug description:
  [Impact]
  When a page fault is triggered in RDMA ODP, it registers an MMU notifier 
during the process.
  Unfortunately, an error arises due to a race condition where the mm is 
released while attempting to register a notifier.
  ==
  Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at 
mm/mmu_notifier.c:255!
  Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 
EFLAGS: 00010246
  Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: 
a0f913ba5800 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: 
c0b601c7 RDI: a0f913ba5850
  Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX:  RBX: 
c0b5a060 RCX: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: 
a1152ed3c400 RDI: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: 
a1163f4f50e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: 
 R12: a1152c923b80
  Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: 
a1163f7350e0 R09: a11638c072c0
  Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: 
 R12: a1102dcd4300
  Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: 
a1152c923bf8 R15: a114f8127800
  Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS:  () 
GS:a1163f4c() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: 
a1152ed3c478 R15: a1101cbfbc00
  Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS:  () 
GS:a1163f70() knlGS:
  Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 
001722472004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS:  0010 DS:  ES:  
CR0: 80050033
  Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 
001f9f1fc004 CR4: 00760ee0
  Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0:  DR1: 
 DR2: 
  Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace:
  Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554
  Oct 14 23:38:32 bnode001 kernel: [1576115.923112]  
mmu_notifier_get_locked+0x5f/0xe0
  Oct 14 23:38:32 bnode001 kernel: [1576115.923867] Call Trace:
  Oct 14 23:38:32 bnode001 kernel: [1576115.923870]  ? 
mmu_notifier_get_locked+0x79/0xe0
  Oct 14 23:38:32 bnode001 kernel: [1576115.924645]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
  Oct 14 23:38:32 bnode001 kernel: [1576115.925409]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
  Oct 14 23:38:32 bnode001 kernel: [1576115.926161]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.926906]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.927651]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.928393]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.929131]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.929866]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
  Oct 14 23:38:32 bnode001 kernel: [1576115.930610]  
process_one_work+0x1eb/0x3b0
  Oct 14 23:38:32 bnode001 kernel: [1576115.931351]  
process_one_work+0x1eb/0x3b0
  Oct 14 23:38:32 bnode001 kernel: [1576115.932084]  worker_thread+0x4d/0x400
  Oct 14 23:38:32 bnode001 kernel: [1576115.932813]  worker_thread+0x4d/0x400
  Oct 14 23:38:32 bnode001 kernel: [1576115.933543]  kthread+0x104/0x140
  Oct 14 23:38:32 bnode001 kernel:

[Kernel-packages] [Bug 2046534] [NEW] Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration

[Chengen Du]

Public bug reported:

[Impact]
When a page fault is triggered in RDMA ODP, it registers an MMU notifier during 
the process.
Unfortunately, an error arises due to a race condition where the mm is released 
while attempting to register a notifier.
==
Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at 
mm/mmu_notifier.c:255!
Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 
EFLAGS: 00010246
Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: 
a0f913ba5800 RCX: 
Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: 
c0b601c7 RDI: a0f913ba5850
Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX:  RBX: 
c0b5a060 RCX: 
Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: 
a1152ed3c400 RDI: a1102dcd4300
Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: 
a1163f4f50e0 R09: a11638c072c0
Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: 
 R12: a1152c923b80
Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: 
a1163f7350e0 R09: a11638c072c0
Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: 
 R12: a1102dcd4300
Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: 
a1152c923bf8 R15: a114f8127800
Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS:  () 
GS:a1163f4c() knlGS:
Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: 
a1152ed3c478 R15: a1101cbfbc00
Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS:  () 
GS:a1163f70() knlGS:
Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS:  0010 DS:  ES:  
CR0: 80050033
Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 
001722472004 CR4: 00760ee0
Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS:  0010 DS:  ES:  
CR0: 80050033
Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 
001f9f1fc004 CR4: 00760ee0
Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0:  DR1: 
 DR2: 
Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3:  DR6: 
fffe07f0 DR7: 0400
Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0:  DR1: 
 DR2: 
Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554
Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace:
Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3:  DR6: 
fffe07f0 DR7: 0400
Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554
Oct 14 23:38:32 bnode001 kernel: [1576115.923112]  
mmu_notifier_get_locked+0x5f/0xe0
Oct 14 23:38:32 bnode001 kernel: [1576115.923867] Call Trace:
Oct 14 23:38:32 bnode001 kernel: [1576115.923870]  ? 
mmu_notifier_get_locked+0x79/0xe0
Oct 14 23:38:32 bnode001 kernel: [1576115.924645]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
Oct 14 23:38:32 bnode001 kernel: [1576115.925409]  
ib_umem_odp_alloc_child+0x15a/0x290 [ib_core]
Oct 14 23:38:32 bnode001 kernel: [1576115.926161]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.926906]  pagefault_mr+0x312/0x5d0 
[mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.927651]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.928393]  
pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.929131]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.929866]  
mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib]
Oct 14 23:38:32 bnode001 kernel: [1576115.930610]  process_one_work+0x1eb/0x3b0
Oct 14 23:38:32 bnode001 kernel: [1576115.931351]  process_one_work+0x1eb/0x3b0
Oct 14 23:38:32 bnode001 kernel: [1576115.932084]  worker_thread+0x4d/0x400
Oct 14 23:38:32 bnode001 kernel: [1576115.932813]  worker_thread+0x4d/0x400
Oct 14 23:38:32 bnode001 kernel: [1576115.933543]  kthread+0x104/0x140
Oct 14 23:38:32 bnode001 kernel: [1576115.934272]  kthread+0x104/0x140
Oct 14 23:38:32 bnode001 kernel: [1576115.934986]  ? 
process_one_work+0x3b0/0x3b0
Oct 14 23:38:32 bnode001 kernel: [1576115.934988]  ? kthread_park+0x90/0x90
Oct 14 23:38:32 bnode001 kernel: [1576115.935687]  ? 
process_one_work+0x3b0/0x3b0
Oct 14 23:38:32 bnode001 kernel: [1576115.935689]  ? kthread_park+0x90/0x90
Oct 14 23:38:32 bnode001 kernel: [1576115.936387]  ret_from_fork+0x1f/0x40
Oct 14 23:38:32 bnode001 kernel: [1576115.936389] ---[ end trace 
1823b59637af552f ]---
Oct 14 23:38:32 bnode001 kernel: [1576115.937077]  ret_from_fork+0x1f/0x40
==

[Kernel-packages] [Bug 2046525] Re: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found

[wang]

forget to install extra package,vmd.ko in extra package,close it

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

Title:
  Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not
  found

Status in linux-hwe package in Ubuntu:
  Invalid

Bug description:
  CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2
  Memory: Micron MTC10F1084S1RC56BG1  16G * 8
  PSU: CFF V4 GREA 1100 *2
  original kernel: 6.2.0-39 ubuntu 22.04.03
  upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1

  reproduce step:
  1.enable vmd and wait os 6.2.0-39 kernel up
  2.upgrade kerenl use "apt install linux-image-6.5.0-14"
  3.after upgrading, reboot

  Than occur the issue:
  volume group "ubuntu-vg" not found
  Cannot process volume group ubuntu-vg

  Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify
  ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But
  after upgrading, we found this new issue.

  you can check detail on attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2046525/+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 2046525] Re: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found

[wang]

forget to install extra package, vmd.ko in this package, close it

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

Title:
  Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not
  found

Status in linux-hwe package in Ubuntu:
  Invalid

Bug description:
  CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2
  Memory: Micron MTC10F1084S1RC56BG1  16G * 8
  PSU: CFF V4 GREA 1100 *2
  original kernel: 6.2.0-39 ubuntu 22.04.03
  upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1

  reproduce step:
  1.enable vmd and wait os 6.2.0-39 kernel up
  2.upgrade kerenl use "apt install linux-image-6.5.0-14"
  3.after upgrading, reboot

  Than occur the issue:
  volume group "ubuntu-vg" not found
  Cannot process volume group ubuntu-vg

  Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify
  ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But
  after upgrading, we found this new issue.

  you can check detail on attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2046525/+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 2046525] Re: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found

[wang]

forget to install extra package,vmd.ko in extra package， close it

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

Title:
  Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not
  found

Status in linux-hwe package in Ubuntu:
  Invalid

Bug description:
  CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2
  Memory: Micron MTC10F1084S1RC56BG1  16G * 8
  PSU: CFF V4 GREA 1100 *2
  original kernel: 6.2.0-39 ubuntu 22.04.03
  upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1

  reproduce step:
  1.enable vmd and wait os 6.2.0-39 kernel up
  2.upgrade kerenl use "apt install linux-image-6.5.0-14"
  3.after upgrading, reboot

  Than occur the issue:
  volume group "ubuntu-vg" not found
  Cannot process volume group ubuntu-vg

  Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify
  ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But
  after upgrading, we found this new issue.

  you can check detail on attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2046525/+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 2046525] Re: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found

[wang]

forget to install extra package,vmd.ko in extra package， close it

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

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

Title:
  Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not
  found

Status in linux-hwe package in Ubuntu:
  Invalid

Bug description:
  CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2
  Memory: Micron MTC10F1084S1RC56BG1  16G * 8
  PSU: CFF V4 GREA 1100 *2
  original kernel: 6.2.0-39 ubuntu 22.04.03
  upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1

  reproduce step:
  1.enable vmd and wait os 6.2.0-39 kernel up
  2.upgrade kerenl use "apt install linux-image-6.5.0-14"
  3.after upgrading, reboot

  Than occur the issue:
  volume group "ubuntu-vg" not found
  Cannot process volume group ubuntu-vg

  Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify
  ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But
  after upgrading, we found this new issue.

  you can check detail on attachment.

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