date:20250228

Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2025-February/157326.html

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

Title:
  Enable Large Language Model (LLM) workloads using Intel NPU

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  New

Bug description:
  [ Impact ]

   * Enable larger LLM using intel NPU.

  [ Fix ]

   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range

  [ Test Plan ]

   * Built and boot tested

  [ Where problems could occur ]

   * Memory management issue when using intel NPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098972/+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 2098724] Re: Missing package linux-signatures-nvidia-6.11.0-18-generic

2025-02-28 Thread Juan Carlos

Missing package released (linux-signatures-nvidia-6.11.0-18), so I
upgraded and solved it for me.

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

Title:
  Missing package linux-signatures-nvidia-6.11.0-18-generic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed

Bug description:
  The latest update to linux-modules-nvidia-560-generic fails to install
  due to the dependency on linux-signatures-nvidia-6.11.0-18-generic
  (via linux-modules-nvidia-560-6.11.0-18-generic), which does not exist
  in the repositories.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-modules-nvidia-560-6.11.0-18-generic (not installed)
  ProcVersionSignature: Ubuntu 6.11.0-14.15-generic 6.11.0
  Uname: Linux 6.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Feb 17 23:18:34 2025
  InstallationDate: Installed on 2025-01-23 (25 days ago)
  InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 
(20241007.6)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-restricted-modules
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2098724/+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 2098111] Re: arm64: kernel image cannot be booted in UEFI despite EFI stub and ZBOOT

2025-02-28 Thread Tobias Heider

A few more observations below.

Running the file command on both gives us:

  linux/arch/arm64/boot$ file Image.gz
  Image.gz: gzip compressed data, max compression, from Unix, original size 
modulo 2^32 63220224

  linux/arch/arm64/boot$ file vmlinuz.efi
  vmlinuz.efi: PE32+ executable (EFI application) Aarch64 (stripped to external 
PDB), for MS Windows, 2 sections

This change does not change the binary size:

  -rw-r--r--  1 user ubuntu  19M Feb 18 12:34 Image.gz
  -rwxr-xr-x  1 user ubuntu  19M Feb 16 16:16 vmlinuz.efi

Compared to the uncompressed image:

  -rw-r--r--  1 user ubuntu  61M Feb 16 16:16 Image

As described in the initial report, Image.gz compresses the whole
binary, vmlinuz.efi only compresses the payload to be decompressed by
the stub. The stub code size is negligible so they are roughly the same
size.

Heinrich mentioned that there was a similar with Risc-V kernels in the
past where they tried to run the kernel directly from u-boot EFI.

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

Title:
  arm64: kernel image cannot be booted in UEFI despite EFI stub and
  ZBOOT

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The arm64 kernel image enables the EFI stub and ZBOOT options, among others, 
that should allow booting the kernel in a UEFI environment, as a signed PE 
binary.
  But the package ships the kernel image as a compressed gzip file, which UEFI 
cannot understand.

  I received a suggestion that this is down to having CONFIG_EFI_ZBOOT
  enabled but running "make install" instead of "make zinstall" (which
  is am arm specific thing and would do the right thing) at package
  build time, with some reference:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4c7be57f2772c8ce4e1e43c6a79b8f8d401a4795

  The vmlinuz in https://ports.ubuntu.com/pool/main/l/linux-
  signed/linux-image-6.12.0-15-generic_6.12.0-15.15_arm64.deb

  $ file vmlinuz-6.12.0-15-generic
  vmlinuz-6.12.0-15-generic: gzip compressed data, max compression, from Unix, 
original size modulo 2^32 60844424
  $ sbverify --list vmlinuz-6.12.0-15-generic
  Invalid DOS header magic
  Can't open image vmlinuz-6.12.0-15-generic

  After using gunzip on it:

  $ gunzip < vmlinuz-6.12.0-15-generic > unzip
  $ file unzip
  unzip: Linux kernel ARM64 boot executable Image, little-endian, 4K pages
  $ sbverify --list unzip
  signature 1
  image signature issuers:
   - /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. Master 
Certificate Authority
  image signature certificates:
   - subject: /C=GB/ST=Isle of Man/O=Canonical Ltd./OU=Secure Boot/CN=Canonical 
Ltd. Secure Boot Signing (2022 v1)
 issuer:  /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. 
Master Certificate Authority

  On the other hand, a Debian arm64 kernel:

  $ file vmlinuz-6.12.13-arm64 
  vmlinuz-6.12.13-arm64: Linux kernel ARM64 boot executable Image, 
little-endian, 4K pages
  $ sbverify --list vmlinuz-6.12.13-arm64 
  signature 1
  image signature issuers:
   - /CN=Debian Secure Boot CA
  image signature certificates:
   - subject: /CN=Debian Secure Boot Signer 2022 - linux
 issuer:  /CN=Debian Secure Boot CA

  Fedora:

  $ file vmlinuz
  vmlinuz: PE32+ executable (EFI application) Aarch64 (stripped to external 
PDB), for MS Windows, 2 sections

  I noticed this because I maintain the mkosi package in Debian, and I
  recently added autopkgtest, which is failing in Ubuntu Plucky:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  plucky/plucky/arm64/m/mkosi/20250212_040016_2ebac@/log.gz

  The autopkgtest uses mkosi to build a UKI using the kernel package, and boot 
it with EDK2 + systemd-boot, and fails because the kernel format is not 
recognized.
  Autopkgtest script:

  https://salsa.debian.org/systemd-
  team/mkosi/-/blob/debian/sid/debian/tests/mkosi?ref_type=heads

  To reproduce the failure with autopkgtest on x86-64:

  $ autopkgtest-buildvm-ubuntu-cloud -a arm64 -r plucky  --timeout 7200
  
  $ autopkgtest -s --pin-packages=plucky-proposed=mkosi --add-apt-source='deb 
http://ports.ubuntu.com plucky-proposed main universe' --timeout-factor=1000 
mkosi -B --test-name mkosi -- autopkgtest-virt-qemu --cpus 4 --ram-size 4096 
./autopkgtest-plucky-arm64.img --qemu-architecture=aarch64 --timeout-reboot 9000

  This will fail with:

  BdsDxe: starting Boot0001 "UEFI Misc Device" from PciRoot(0x0)/Pci(0x8,0x0)
  ../src/boot/linux.c:120@linux_exec: Bad kernel image: Load error
  ../src/boot/boot.c:2640@image_start: Failed to execute Ubuntu Plucky Puffin 
(development branch) (\EFI\Linux\ubuntu-6.12.0-15-generic.efi): Load error

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


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

[Kernel-packages] [Bug 2098935] Re: The ice driver may rarely return incorrect statistics counter values

2025-02-28 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  The ice driver may rarely return incorrect statistics counter values

Status in linux package in Ubuntu:
  New

Bug description:
  We have observed a very rare issue in Intel E810 environments where
  SNMP-retrieved TX/RX counter values are sometimes nearly twice the
  actual values.

  Upon investigation, we identified a problem in the process that
  updates the transmit and receive ring statistics in the ice driver.
  This issue occurs when the counter update process is executed
  simultaneously on different CPU cores.

  We have attached a patch to fix this issue.

  The function ice_update_vsi_ring_stats takes a pointer to a struct
  ice_vsi as an argument. This structure is allocated on the heap and
  shared across all CPU cores. The function resets the counter values to
  zero and then accumulates the values from each ring of the NIC.

  However, since struct ice_vsi is shared across all CPU cores, the following 
race condition can occur when ice_update_vsi_ring_stats is executed 
simultaneously on different CPUs:
1.  Multiple CPU cores reset the counter values in struct ice_vsi 
to zero at the same time.
2.  Each CPU core independently increments the counter values.

  As a result, the counter values may be updated to a higher-than-actual
  value.

  The attached patch modifies the implementation to store the counter
  values on the stack, initialize them to zero, increment them with the
  values from each ring, and finally update struct ice_vsi. By avoiding
  the use of shared data for intermediate calculations, this fix
  prevents the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098935/+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 2076217] Re: booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs sometimes

2025-02-28 Thread Robby Pocase

@philcox we've had internal discussions on this and are no longer able
to reproduce this. we suspect it was an underlying hardware issue on the
cloud. i'm not sure what the right bug status to move this to since we
technically didn't have a fix released.

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

Title:
  booting an 24.10 or 24.04 ec2 instance with SEV-SNP enabled hangs
  sometimes

Status in cloud-images:
  New
Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  I'm trying to test an EC2 instance with SEV-SNP enabled. But the boot
  process hangs at:

  [snipped]
  [0.609079] printk: legacy console [ttyS0] enabled
  [5.405931] ACPI: Core revision 20230628
  [5.430448] clocksource: hpet: mask: 0x max_cycles: 0x, 
max_idle_ns: 30580167144 ns
  [5.473066] APIC: Switch to symmetric I/O mode setup

  
  Steps to reproduce are:

  $ AWS_DEFAULT_REGION=eu-west-1 aws ec2 run-instances --image-id
  ami-005a44922e2ffd1fa --instance-type m6a.large --cpu-options
  AmdSevSnp=enabled --key-name toabctl --tag-specifications
  'ResourceType=instance,Tags=[{Key=Name,Value=toabctl-2410-sevsnp-
  testing}]'

  The AMI ami-005a44922e2ffd1fa is ubuntu/images-testing/hvm-ssd-
  gp3/ubuntu-oracular-daily-amd64-server-20240716 and does contain
  6.8.0-1008-aws .

  Attached is the full output from the EC2 serial console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2076217/+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 2098952] Re: Fix EPT level 5 support for Sierra Forest

Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2025-February/157313.html

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

Title:
  Fix EPT level 5 support for Sierra Forest

Status in linux-intel package in Ubuntu:
  New
Status in linux-intel source package in Noble:
  In Progress

Bug description:
  [ Impact ]

   * EPT level 5 support for Sierra forest hardware

  [ Fix ]

   * Upstream submission :
  
https://lore.kernel.org/all/20240812224820.34826-23-rick.p.edgeco...@intel.com/
  
https://lore.kernel.org/all/20240812224820.34826-24-rick.p.edgeco...@intel.com/

  A small part of the first patch needs to be dropped as is is not
  relevant anymore.

  [ Test Plan ]

   * Already released part of oracular:linux-intel
   * Compiled and tested separately based on noble:linux-intel

  [ Where problems could occur ]

   * Regression in TDX/KVM performance

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

2025-02-28 Thread Michał Fita

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2098670/+attachment/5859053/+files/ProcCpuinfoMinimal.txt

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

Title:
  amdgpu: No picture on main screen after wake up

Status in linux-meta-lowlatency-hwe-6.11 package in Ubuntu:
  Confirmed

Bug description:
  So far looks like any kernel after 6.8.0-49.49 has some bugs related
  to amdgpu and wakes. I tried HWE 6.11 hoping that would have enough
  bugfixes from upstream to get me sorted, but it's even worse than
  #2093268 as the screen is blank after unlock.

  My hardware is ThinkPad P16s Gen 1 with AMD.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-lowlatency-hwe-24.04 6.11.0-1009.10~24.04.1+1
  ProcVersionSignature: Ubuntu 6.11.0-1009.10~24.04.1-lowlatency 6.11.11
  Uname: Linux 6.11.0-1009-lowlatency x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 17 13:33:32 2025
  InstallationDate: Installed on 2023-04-28 (661 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  SourcePackage: linux-meta-lowlatency-hwe-6.11
  UpgradeStatus: Upgraded to noble on 2024-07-16 (216 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-04-28 (664 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Package: linux-image-lowlatency-hwe-24.04 6.11.0-1009.10~24.04.1+1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.11.0-1009.10~24.04.1-lowlatency 6.11.11
  Tags: noble wayland-session
  Uname: Linux 6.11.0-1009-lowlatency x86_64
  UpgradeStatus: Upgraded to noble on 2024-07-16 (219 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sbuild sudo 
vboxusers
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-04-28 (664 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Package: linux-image-lowlatency-hwe-24.04 6.11.0-1009.10~24.04.1+1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.11.0-1009.10~24.04.1-lowlatency 6.11.11
  Tags: noble
  Uname: Linux 6.11.0-1009-lowlatency x86_64
  UpgradeStatus: Upgraded to noble on 2024-07-16 (219 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sbuild sudo 
vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency-hwe-6.11/+bug/2098670/+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 2098108] Re: External monitor stays blank about 3 out of 4 times

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

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

** Changed in: linux (Ubuntu Noble)
 Assignee: Benjamin Wheeler (benjaminwheeler) => (unassigned)

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

Title:
  External monitor stays blank about 3 out of 4 times

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

Bug description:
  After rebooting into the new 6.11 HWE kernel, my external monitor
  stayed blank. Unplugging/replugging the monitor, or rebooting,
  sometimes (in about 1 out of 4 cases) fixes the problem.

  Note the monitor seems to be detected, because my desktop is extended
  into that (now invisible) region and windows placed on that extended
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2
  ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
  Uname: Linux 6.11.0-17-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 16:48:59 2025
  SourcePackage: linux-signed-hwe-6.11
  UpgradeStatus: Upgraded to noble on 2024-06-12 (245 days ago)

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

2025-02-28 Thread Timo Aaltonen

The verification of the Stable Release Update for linux-lowlatency-
hwe-6.8 has completed successfully and the package is now being released
to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2089533] Re: Jammy update: v5.15.172 upstream stable release

This bug was fixed in the package linux - 5.15.0-133.144

---
linux (5.15.0-133.144) jammy; urgency=medium

  * CVE-2025-0927
- SAUCE: fs: hfs/hfsplus: add key_len boundary check to hfs_bnode_read_key

linux (5.15.0-132.143) jammy; urgency=medium

  * jammy/linux: 5.15.0-132.143 -proposed tracker (LP: #2093735)

  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/2025.01.13)

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
Exit (LP: #2093146)
- kvm: x86: Fix xstate_required_size() to follow XSTATE alignment rule
- KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * Jammy update: v5.15.173 upstream stable release (LP: #2089541)
- 9p: Avoid creating multiple slab caches with the same name
- irqchip/ocelot: Fix trigger register address
- block: Fix elevator_get_default() checking for NULL q->tag_set
- HID: multitouch: Add support for B2402FVA track point
- HID: multitouch: Add quirk for HONOR MagicBook Art 14 touchpad
- bpf: use kvzmalloc to allocate BPF verifier environment
- crypto: marvell/cesa - Disable hash algorithms
- sound: Make CONFIG_SND depend on INDIRECT_IOMEM instead of UML
- drm/vmwgfx: Limit display layout ioctl array size to
  VMWGFX_NUM_DISPLAY_UNITS
- powerpc/powernv: Free name on error in opal_event_init()
- vDPA/ifcvf: Fix pci_read_config_byte() return code handling
- fs: Fix uninitialized value issue in from_kuid and from_kgid
- HID: multitouch: Add quirk for Logitech Bolt receiver w/ Casa touchpad
- HID: lenovo: Add support for Thinkpad X1 Tablet Gen 3 keyboard
- net: usb: qmi_wwan: add Fibocom FG132 0x0112 composition
- md/raid10: improve code of mrdev in raid10_sync_request
- mm/memory: add non-anonymous page check in the copy_present_page()
- udf: Allocate name buffer in directory iterator on heap
- udf: Avoid directory type conversion failure due to ENOMEM
- 9p: fix slab cache name creation for real
- Linux 5.15.173

  * Jammy update: v5.15.173 upstream stable release (LP: #2089541) //
CVE-2024-41080
- io_uring: fix possible deadlock in io_register_iowq_max_workers()

  * Jammy update: v5.15.172 upstream stable release (LP: #2089533)
- arm64: dts: rockchip: Fix rt5651 compatible value on rk3399-sapphire-
  excavator
- arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328
- arm64: dts: rockchip: Fix bluetooth properties on Rock960 boards
- arm64: dts: rockchip: Remove #cooling-cells from fan on Theobroma lion
- arm64: dts: rockchip: Fix LED triggers on rk3308-roc-cc
- arm64: dts: imx8mp: correct sdhc ipg clk
- ARM: dts: rockchip: fix rk3036 acodec node
- ARM: dts: rockchip: drop grf reference from rk3036 hdmi
- ARM: dts: rockchip: Fix the spi controller on rk3036
- ARM: dts: rockchip: Fix the realtek audio codec on rk3036-kylin
- NFSv3: only use NFS timeout for MOUNT when protocols are compatible
- NFS: Add a tracepoint to show the results of nfs_set_cache_invalid()
- NFSv3: handle out-of-order write replies.
- nfs: avoid i_lock contention in nfs_clear_invalid_mapping
- net: enetc: set MAC address to the VF net_device
- can: c_can: fix {rx,tx}_errors statistics
- net: phy: ti: add PHY_RST_AFTER_CLK_EN flag
- net: stmmac: Fix unbalanced IRQ wake disable warning on single irq case
- Revert "ALSA: hda/conexant: Mute speakers at suspend / shutdown"
- media: stb0899_algo: initialize cfr before using it
- media: dvb_frontend: don't play tricks with underflow values
- media: adv7604: prevent underflow condition when reporting colorspace
- scsi: sd_zbc: Use kvzalloc() to allocate REPORT ZONES buffer
- ALSA: firewire-lib: fix return value on fail in amdtp_tscm_init()
- media: pulse8-cec: fix data timestamp at pulse8_setup()
- media: v4l2-ctrls-api: fix error handling for v4l2_g_ctrl()
- pwm: imx-tpm: Use correct MODULO value for EPWM mode
- drm/amdgpu: Adjust debugfs eviction and IB access permissions
- drm/amdgpu: prevent NULL pointer dereference if ATIF is not supported
- thermal/drivers/qcom/lmh: Remove false lockdep backtrace
- dm cache: correct the number of origin blocks to match the target length
- dm cache: optimize dirty bit checking with find_next_bit when resizing
- dm-unstriped: cast an operand to sector_t to prevent potential uint32_t
  overflow
- ALSA: usb-audio: Add quirk for HP 320 FHD Webcam
- posix-cpu-timers: Clear TICK_DEP_BIT_POSIX_TIMER on clone
- io_uring: rename kiocb_end_write() local helper
- fs: create kiocb_{start,end}_write() helpers
- io_uring: use kiocb_{start,end}_write() helpers
- media: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in
  uvc_parse_format
- fs/proc: fix compile warning about variable 'vmcore_mmap_ops'
- usb: dwc3:

[Kernel-packages] [Bug 2089411] Re: python perf module missing in realtime kernel

This is because you still have the old broken wrapper installed. The
wrapper is provided by linux-tools-common from the main kernel (not
realtime). You must upgrade that package as well.

$ apt install linux-tools-common

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

Title:
  python perf module missing in realtime kernel

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

Bug description:
  [Impact]

  ubuntu@ubuntu-plucky:~$ python3 -c 'import perf; [print(c) for c in 
perf.cpu_map()]'
  Traceback (most recent call last):
    File "", line 1, in 
    File "/usr/lib/python3/dist-packages/perf/__init__.py", line 24, in 
  raise KernelNotFoundError()
  perf.KernelNotFoundError: WARNING: python perf module not found for kernel 
6.12.0-4-generic

  You may need to install the following packages for this specific kernel:
    linux-tools-6.12.0-4-generic-generic
  You may also want to install of the following package to keep up to date:
    linux-tools-generic

  This works only with the main generic kernel but not with any of the
  derivatives. Packaging is broken and the perf python modules is
  looking in the wrong place for the library.

  [Test Plan]

  Run:
  $ python3 -c 'import perf; [print(c) for c in perf.cpu_map()]'
  $ perf

  The above must not result in errors.

  [Where Problems Could Occur]

  Potential issues when using the perf python module or any
  scripts/binaries provided by the linux-tools packages.

  [Original Description]

  Issue is related to Bug #2051560
  In using tuned profile realtime-virtual-host under the realtime kernel, the 
operating system would lose network connection. Further viewing of the tuned 
logs pointed to the following error:

  ERRORtuned.units.manager: WARNING: python perf module not found
  for kernel 6.8.1-1011-realtime

  Researching online Bug #2051560 was discovered. However, it looks as
  if the realtime kernel was not listed as fixed to include the perf
  Python module that affects tuned.

  Server info:

  uname -a:

  Linux 6.8.1-1011-realtime #11-Ubuntu SMP PREEMPT_RT Tue Oct 8 17:19:16 UTC 
2024 x86_64 x86_64 x86_64 GNU/Linux
  ---

  lsb_release -crid:

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 24.04.1 LTS
  Release: 24.04
  Codename: noble

  ---

  apt policy linux-image-6.8.1-1011-realtime:

  linux-image-6.8.1-1011-realtime:
    Installed: 6.8.1-1011.11
    Candidate: 6.8.1-1011.11
    Version table:
   *** 6.8.1-1011.11 500
  500 https://esm.ubuntu.com/realtime/ubuntu noble/main amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Realtime kernel was installed via Ubuntu Pro subscription.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089411/+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 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

2025-02-28 Thread xiaochun Lee

Upgrade to kernel 6.8.0-56-generic, spi-nor error disappeared. Thanks!

** Attachment added: "The demsg of 6.8.0-56-generic log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070339/+attachment/5858937/+files/dmesg_6.8.0-56-generic.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/2070339

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2096624] Re: [SRU] Add Intel Touch Host Controller drivers

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

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

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

Title:
  [SRU] Add Intel Touch Host Controller drivers

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  Invalid
Status in linux-oem source package in Noble:
  In Progress
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  In Progress
Status in linux-oem source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  In Progress
Status in linux-oem source package in Plucky:
  Invalid
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [Impact]
  The new touchscreen on Intel LNL is lack of driver support.

  00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848]
  (rev 10)

  [Fix]
  Enable Intel THC driver to support it.
  [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12
  [4.122704] input: quicki2c-hid 27C6:012D as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13

  [Test]
  Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens.

  [Where problems could occur]
  It introduces a brand new driver, may break hid functions.

  Because this is a new feature driver, SRU for
  oracular/plucky/oem-6.11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2096624/+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 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

2025-02-28 Thread AaronMa

Verified the new kernel, there is no such error in attached dmesg.
set verification-done.

Thanks.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2097818] Re: OLED panel screen backlight brightness does not change with brightness hotkey(F6&F7 Key)

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

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

Title:
  OLED panel screen backlight brightness does not change with brightness
  hotkey(F6&F7 Key)

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  [Impact]
  In Dell platform OLED machine with eDP 1.5, monitor's brightness won't change 
when pressing brightness key F6/F7.

  [Fix]
  Cherry-pick the following patchset which has already landed in linux-next:
  https://patchwork.freedesktop.org/series/143910/#rev3

  which contains:

  5dfc37a6b77b drm/dp: Add eDP 1.5 bit definition
  9ee185564425 drm/dp: Increase eDP display control capability size
  9535c6a4c61c drm/i915/backlight: Use proper interface based on eDP version
  64481497924d drm/i915/backlight: Check Luminance based brightness control for 
VESA
  3f8a009a794e drm/i915/backlight: Modify function to get VESA brightness in 
Nits
  b68074efcfcf drm/i915/backlight: Add function to change brightness in nits 
for VESA
  8d502933ac20 drm/i915/backlight: Setup nits based luminance via VESA
  a5efc8dcfe71 drm/i915/backlight: Enable nits based luminance

  
===
  Besides, there will be a prerequisite patch needed in order to clean-apply 
the above patchset:

  6276706f33cc drm/i915/display: convert dp aux backlight to struct
  intel_display

  So there will be 9 patches in total.

  [Test Plan]
  1. Boot up the Ubuntu OEM image
  2. Wait until the screen shows the desktop
  3. Press brightness keys (F6 or F7) and see if the brightness has changed.

  [Where problems could occur]
  May cause regression on some monitors which use the old brightness-changed 
path (PWM path).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097818/+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 2077926] Re: crash in openzfs - 2.2.2 not supported on 6.8

** Changed in: zfs-linux (Ubuntu Plucky)
   Status: Confirmed => Fix Released

** Changed in: zfs-linux (Ubuntu Plucky)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Plucky)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: zfs-linux (Ubuntu Oracular)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Noble)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Oracular)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Noble)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

** Changed in: zfs-linux (Ubuntu Oracular)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  crash in openzfs - 2.2.2 not supported on 6.8

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Noble:
  In Progress
Status in zfs-linux source package in Oracular:
  In Progress
Status in zfs-linux source package in Plucky:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Seeing crash due to use-after-free. Logs included below SRU
  justification

  [Fix]

  * Backport 38c0324c0fb6: "Linux: Fix zfs_prune panics"

  [Test Plan]

  * Compile tested
  * Run through autopkgtest regression tests

  [Regression potential]

  * Changes isolated, minimal regression risk. Changes already in
  upstream ZFS

  Crash report on openzfs: https://github.com/openzfs/zfs/issues/16482

  > You should probably report this to Ubuntu or try it on 2.2.5
  vanilla, 2.2.2 doesn't claim to work on 6.8

  Distribution Version  24.04
  Kernel Version6.8.0-41-generic
  Architecture  intel x86-64
  OpenZFS Version   zfs-2.2.2-0ubuntu9, zfs-kmod-2.2.2-0ubuntu9

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: zfsutils-linux 2.2.2-0ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Aug 26 21:30:11 2024
  InstallationDate: Installed on 2024-08-16 (11 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2077926/+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 2077926] Re: crash in openzfs - 2.2.2 not supported on 6.8

Fixed in 2.2.7 release, which is now in Plucky

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

Title:
  crash in openzfs - 2.2.2 not supported on 6.8

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Noble:
  In Progress
Status in zfs-linux source package in Oracular:
  In Progress
Status in zfs-linux source package in Plucky:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * Seeing crash due to use-after-free. Logs included below SRU
  justification

  [Fix]

  * Backport 38c0324c0fb6: "Linux: Fix zfs_prune panics"

  [Test Plan]

  * Compile tested
  * Run through autopkgtest regression tests

  [Regression potential]

  * Changes isolated, minimal regression risk. Changes already in
  upstream ZFS

  Crash report on openzfs: https://github.com/openzfs/zfs/issues/16482

  > You should probably report this to Ubuntu or try it on 2.2.5
  vanilla, 2.2.2 doesn't claim to work on 6.8

  Distribution Version  24.04
  Kernel Version6.8.0-41-generic
  Architecture  intel x86-64
  OpenZFS Version   zfs-2.2.2-0ubuntu9, zfs-kmod-2.2.2-0ubuntu9

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: zfsutils-linux 2.2.2-0ubuntu9
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Aug 26 21:30:11 2024
  InstallationDate: Installed on 2024-08-16 (11 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2077926/+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 2096624] Re: [SRU] Add Intel Touch Host Controller drivers

- Plucky will likely incorporate these changes without extra effort.
- There is no urgent need to backport this to Oracular right now.
- We'll work on getting HWE kernels out as soon as possible.

https://lists.ubuntu.com/archives/kernel-team/2025-February/157324.html

** Changed in: linux (Ubuntu Oracular)
   Status: In Progress => Invalid

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

Title:
  [SRU] Add Intel Touch Host Controller drivers

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  Invalid
Status in linux-oem source package in Noble:
  In Progress
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Invalid
Status in linux-oem source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  In Progress
Status in linux-oem source package in Plucky:
  Invalid
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [Impact]
  The new touchscreen on Intel LNL is lack of driver support.

  00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848]
  (rev 10)

  [Fix]
  Enable Intel THC driver to support it.
  [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12
  [4.122704] input: quicki2c-hid 27C6:012D as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13

  [Test]
  Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens.

  [Where problems could occur]
  It introduces a brand new driver, may break hid functions.

  Because this is a new feature driver, SRU for
  oracular/plucky/oem-6.11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2096624/+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 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

2025-02-28 Thread Bastian Reuther

Hi Alex,

I encountered the same error in dmesg.

With the new kernel, the errors are gone and everything is working!

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

Title:
  Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
  (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu
  22.04/24.04 VMs, we are experiencing extremely low network speeds
  (100-200 KB/s) when running these VMs in a Proxmox 8.3.4 cluster with
  AMD CPUs and Broadcom NetXtreme-E network adapters (bnxt_en driver).

  With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as 
expected.
  Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are 
not affected.
  The same Xubuntu VM, when moved to a different Proxmox cluster (Intel 
CPUs, Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
  The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster 
with AMD CPUs, Broadcom NICs, and Ceph storage.

  Expected behavior:

  Network performance should be normal (10 Gbps or more) without issues.
  Actual behavior:

  Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow 
network speeds (100-200 KB/s).
  iperf3 tests show very low bandwidth (5-10 Mbps).
  Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) 
did not improve performance.
  Other VMs (Debian, Ubuntu Server) on the same cluster do not have this 
issue.
  The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu 
VM.

  Steps to reproduce:

  Proxmox environment:
  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph 
storage
  VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)

  Inside the Xubuntu VM:
  Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
  Test network performance:

  wget -O /dev/null http://speed.hetzner.de/1GB.bin
  iperf3 -c  -P 4

  → Speed is extremely slow (~200 KB/s - 5 Mbps).

  Reboot the VM with Kernel 6.8.0-31

  sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 
6.8.0-31-generic"
  sudo reboot

  → Network performance returns to normal (10 Gbps+).

  Hardware & environment details:
  Proxmox cluster (affected environment):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPUs
  Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
  Ceph storage backend
  VMs use VirtIO network adapter (virtio-net)
  Bridging on Broadcom NICs

  Working cluster (same Xubuntu VM, no issue):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  Intel CPUs
  Intel I350 NICs (igb driver)
  ZFS storage backend
  Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17

  Debugging information:

  Xubuntu VM Kernel versions (affected):

  uname -r
  6.8.0-53-generic
  6.11.0-17-generic

  Broadcom firmware version (Proxmox host):

  ethtool -i enp67s0f0np0 | grep firmware
  firmware-version: 229.0.154.0/pkg 229.1.123.0

  dmesg output related to bnxt_en NICs (Proxmox host):

  dmesg | grep bnxt
  [2.324347] bnxt_en :c5:00.0 (unnamed net_device) (uninitialized): 
Device requests max timeout of 60 seconds, may trigger hung task watchdog
  [2.364280] bnxt_en :c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 
10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b703, node addr 
14:23:f2:5d:18:14
  ...

  → No critical errors, but timeout warnings and performance degradation.
  Possible causes:

  🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
  🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
  🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 
6.8.0-53 and 6.11.0-17
  Next Steps & Further Tests

  Since this is a production system with 200+ running VMs, we will
  conduct further tests once we schedule maintenance.

  Planned additional tests:

  Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule 
out Xubuntu-specific issues).
  Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 
6.8.0-53 and 6.11.0-17.
  Check IRQ assignments and CPU affinity for VirtIO network interfaces.

  📌 If this issue is already reported, please link to the relevant bug report.
  📌 Otherwise, we are happy to provide further debugging information.
  Summary:

  Xubuntu VMs running Kernel 6.8.0-53 and 6.11.0-17 on a Proxmox 8.3.4 
cluster with AMD CPUs + Broadcom NICs suffer from extreme network slowdowns 
(~200 KB/s).
  Booting the same VM with Kernel 6.8.0-31 restores full performance.
  Same Kernels work fine on Intel-based Proxmox clusters.
  Disa

[Kernel-packages] [Bug 2099682] [NEW] linux-headers-6.11.0-17-generic 6......

2025-02-28 Thread cantoute

Public bug reported:

linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to
install/upgrade: le sous-processus paquet linux-
headers-6.11.0-17-generic script post-installation installé a renvoyé un
état de sortie d'erreur 11

this broke the boot

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2
ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Feb 21 12:37:26 2025
ErrorMessage: le sous-processus paquet linux-headers-6.11.0-17-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 11
InstallationDate: Installed on 2024-11-08 (105 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6.1
 apt  2.7.14build2
SourcePackage: linux-hwe-6.11
Title: package linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.11.0-17-generic 
script post-installation installé a renvoyé un état de sortie d'erreur 11
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package noble

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

Title:
  linux-headers-6.11.0-17-generic 6..

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

Bug description:
  linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to
  install/upgrade: le sous-processus paquet linux-
  headers-6.11.0-17-generic script post-installation installé a renvoyé
  un état de sortie d'erreur 11

  this broke the boot

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  Uname: Linux 6.8.0-52-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Feb 21 12:37:26 2025
  ErrorMessage: le sous-processus paquet linux-headers-6.11.0-17-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 11
  InstallationDate: Installed on 2024-11-08 (105 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6.1
   apt  2.7.14build2
  SourcePackage: linux-hwe-6.11
  Title: package linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.11.0-17-generic 
script post-installation installé a renvoyé un état de sortie d'erreur 11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.11/+bug/2099682/+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 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

2025-02-28 Thread Bastian Reuther

Hi again,

Markus and me are observing some interesting behavior with the network 
configuration.
Just for testing, we added an older kernel again:

Kernel:
root@hostname2:~# uname -ar
Linux hostname2 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 
20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

When using the Virtio network adapter, everything works as expected.
However, when we switch to the Intel E1000 network card, the network
speed drops significantly.

We will test older Kernel versions with E1000 to check when the bug
occurs first.

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

Title:
  Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
  (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu
  22.04/24.04 VMs, we are experiencing extremely low network speeds
  (100-200 KB/s) when running these VMs in a Proxmox 8.3.4 cluster with
  AMD CPUs and Broadcom NetXtreme-E network adapters (bnxt_en driver).

  With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as 
expected.
  Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are 
not affected.
  The same Xubuntu VM, when moved to a different Proxmox cluster (Intel 
CPUs, Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
  The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster 
with AMD CPUs, Broadcom NICs, and Ceph storage.

  Expected behavior:

  Network performance should be normal (10 Gbps or more) without issues.
  Actual behavior:

  Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow 
network speeds (100-200 KB/s).
  iperf3 tests show very low bandwidth (5-10 Mbps).
  Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) 
did not improve performance.
  Other VMs (Debian, Ubuntu Server) on the same cluster do not have this 
issue.
  The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu 
VM.

  Steps to reproduce:

  Proxmox environment:
  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph 
storage
  VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)

  Inside the Xubuntu VM:
  Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
  Test network performance:

  wget -O /dev/null http://speed.hetzner.de/1GB.bin
  iperf3 -c  -P 4

  → Speed is extremely slow (~200 KB/s - 5 Mbps).

  Reboot the VM with Kernel 6.8.0-31

  sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 
6.8.0-31-generic"
  sudo reboot

  → Network performance returns to normal (10 Gbps+).

  Hardware & environment details:
  Proxmox cluster (affected environment):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPUs
  Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
  Ceph storage backend
  VMs use VirtIO network adapter (virtio-net)
  Bridging on Broadcom NICs

  Working cluster (same Xubuntu VM, no issue):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  Intel CPUs
  Intel I350 NICs (igb driver)
  ZFS storage backend
  Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17

  Debugging information:

  Xubuntu VM Kernel versions (affected):

  uname -r
  6.8.0-53-generic
  6.11.0-17-generic

  Broadcom firmware version (Proxmox host):

  ethtool -i enp67s0f0np0 | grep firmware
  firmware-version: 229.0.154.0/pkg 229.1.123.0

  dmesg output related to bnxt_en NICs (Proxmox host):

  dmesg | grep bnxt
  [2.324347] bnxt_en :c5:00.0 (unnamed net_device) (uninitialized): 
Device requests max timeout of 60 seconds, may trigger hung task watchdog
  [2.364280] bnxt_en :c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 
10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b703, node addr 
14:23:f2:5d:18:14
  ...

  → No critical errors, but timeout warnings and performance degradation.
  Possible causes:

  🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
  🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
  🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 
6.8.0-53 and 6.11.0-17
  Next Steps & Further Tests

  Since this is a production system with 200+ running VMs, we will
  conduct further tests once we schedule maintenance.

  Planned additional tests:

  Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule 
out Xubuntu-specific issues).
  Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 
6.8.0-53 and 6.11.0-17.
  Check IRQ assignments and CPU affinity for VirtIO network interfaces.

  📌 If this issue is already rep

[Kernel-packages] [Bug 2099685] [NEW] GPIO sysfs disabled in raspi kernel

Public bug reported:

[Impact]

Core24 exposes the raspi GPIO sysfs interface. It's a deprecated kernel
interface that was disabled in Kinetic. Snapd needs to change but that
won't happen for core24 so we need to turn it back on :-(

See bug #2096665.

[Fix]

Enable CONFIG_GPIO_SYSFS

[Test Case]

See bug #2096665.

[Where Problems Could Occur]

GPIO access through sysfs might interfere with other GPIO users like
gpiod which is the official way nowadays.

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

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

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

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

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

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

Title:
  GPIO sysfs disabled in raspi kernel

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Noble:
  Confirmed

Bug description:
  [Impact]

  Core24 exposes the raspi GPIO sysfs interface. It's a deprecated
  kernel interface that was disabled in Kinetic. Snapd needs to change
  but that won't happen for core24 so we need to turn it back on :-(

  See bug #2096665.

  [Fix]

  Enable CONFIG_GPIO_SYSFS

  [Test Case]

  See bug #2096665.

  [Where Problems Could Occur]

  GPIO access through sysfs might interfere with other GPIO users like
  gpiod which is the official way nowadays.

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

2025-02-28 Thread Walther Freud

apport information

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

Title:
  System Freeze on suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently I put my Laptop into sleep mode like normal and later tried to wake 
it up but the machine was unresponsive.
  Interestingly opening the tty still worked (the second time it happened I 
pressed ctrl+f1 immediately after I noticed the freeze) but as soon as I 
interacted with the desktop environment (e.g. through a (normal) key press) the 
system froze completely.
  After a hard restart the same thing happened again after waking from sleep 
mode. I couldn't reproduce it the following days.
  From the logs (see attachments), I would extract that the problem is already 
at the time of entering sleep mode. Anyway would be very happy if you could 
look into this BUG: kernel NULL pointer dereference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:myuser 3271 F pipewire
   /dev/snd/controlC0:  myuser 3273 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 22
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2024-09-14 (160 days ago)
  InstallationMedia: Linux Mint 22 "Wilma" - Release amd64 20240721
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 03f0:1f4a HP, Inc HP USB Optical Mouse
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Acer Aspire E5-774G
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic 
root=UUID=a640493d-e5b1-4990-a53f-ec0a66f3e534 ro silent splash resume=/dev 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
  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.8.0-53-generic N/A
   linux-backports-modules-6.8.0-53-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.9
  Tags: wilma
  Uname: Linux 6.8.0-53-generic x86_64
  UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht 
installiert ist.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  _MarkForUpload: False
  dmi.bios.date: 05/26/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hulk_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.30
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.27:bd05/26/2017:br0.0:efr2.30:svnAcer:pnAspireE5-774G:pvrV1.27:rvnAcer:rnHulk_SK:rvrV1.27:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-774G_1160_1.27:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-774G
  dmi.product.sku: Aspire E5-774G_1160_1.27
  dmi.product.version: V1.27
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098959/+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 2097229] Re: Issues with Thunderbolt in initrd: Devices recognized but not working

2025-02-28 Thread Olaf Lessenich

@bemotion Thanks, you might be on to something here! I just checked with
`boltctl domains` and it lists "bootacl: 0/0", which according to the
manpage, means that BootACL is unsupported.

In my uefi settings, ThunderboltBoot, ThunderboltPreBoot, and
ThunderboltPorts are already enabled.

I just checked the bash_history from my previous notebook (that did
never have this issue with the same dock) and found that I once ran
something like this: `boltctl enroll
--policy=auto`. Back then I did this to get the ethernet port to work,
which was never an issue on the current machine. On the current machine,
the usb keyboard also worked completely fine during boot until October
last year, which I don't really understand. So either a new kernel or a
firmware update changed the behaviour. Currently, boltctl stated that
everything is authorized and enrolled, but the policy is stored as
"iommu" instead of "auto". I will also investigate this policy setting
further and also reach out to get some help from the Dell support.

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

Title:
Issues with Thunderbolt in initrd: Devices recognized but not working

Status in cryptsetup package in Ubuntu:
Confirmed
Status in initrd-tools package in Ubuntu:
Confirmed
Status in plymouth package in Ubuntu:
Confirmed
Status in thunderbolt-tools package in Ubuntu:
Confirmed

Bug description:
I'm facing an issue with Thunderbolt in initrd on a Lenovo ThinkPad
Yoga X1 Gen8 in conjunction with the Lenovo Thunderbolt 3 Dock (40AN,
Gen 2) when using Ubuntu 24 with Kernel 6.8 and 6.11.

Cross-checking the same Dock and the same SSD within another Laptop
(older HP ProBook 450 G6 with only USB 3.2 support, no Thunderbolt)
proofs my suspicion that the hardware works fine but it is some
software related issue.

Step to Step:
Up on starting the Laptop, USB generic drivers are loaded and the Dock is
recognized.
The Dock works flawlessly in pre-boot environments such as UEFI and GRUB with
the loaded USB generic driver.
As soon as GRUB is attempting to start the selected system and initrd is
loaded for the later prompt of the LUKS passphrase, I recognize the USB generic
drivers are loaded once more and the devices are being initialized as USB
devices.
After that, the USB connection seems to be "dropped" due to the Docks
Thunderbolt capability being recognized which causes initrd to load the
Thunderbolt module, which is prompted onscreen:

thunderbolt 1-0:1.1: new retimer found, vendor ...

thunderbolt 1-1: new device found, vendor ...

thunderbolt 1-1: Lenovo ThinkPad Thunderbolt 3 Dock

As soon as the Thunderbolt module is loaded the devices connected to
the Dock shut off: Monitors turn blank, Keyboard backlights and Mouse
status indicator LEDs turn off. I also assume the power supply to the
laptop via the same cable connection is dropped, as the Status LED of
the Dock is turning off, but do not know for sure.

This causes that only Monitors or Keyboards directly connected to the
Laptop via USB or HDMI will work for the stage of entering the LUKS
passphrase (the internal Monitor and Keyboard obviously do work as
intended -> which are directly connected via USB generic and not
Thunderbolt).

Deactivating Thunderbolt in the UEFI of the Lenovo machine proofs my
assumption again: The Dock works flawlessly in UEFI, GRUB as well as
the initrd/LUKS passphrase/plymouth environment as it is now acting as
USB device.

I suspect a faulty implementation of the Thunderbolt Module or Security
Policies prohibiting its use:
As soon as the LUKS passphrase is entered correct and the system starts to
load, the Thunderbolt module seem to be loaded new again and from that moment
on work properly: The Status LED of the Dock goes on and all devices connected
light up again - all while still loading modules (way before the Login screen
appears).

That is why I first was hoping for the best case of security policies
blocking Thunderbolt I/O in the initrd/LUKS passphrase/plymouth stage,
but I found no documentation if there is such and how to change that
policy which drives me to the conclusion that it is more likely a bug.

I also did not find any workaround to drop Thunderbolt for initrd and
set USB generic drivers only, which would help a lot until this bug is
fixed.

Here is some similar report that the issue exists since Kernel 5.4, but they
did not have the same conclusion/mentioning of USB-generic drivers vs.
Thunderbolt drivers:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215

Previous Stackexchange Ubuntu post by me regarding this behavior:

https://askubuntu.com/questions/1534913/issues-with-thunderbolt-and-initramfs-in-ubuntu-24-devices-assume-blocked

Another Users simil

[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2025-02-28 Thread Bug Watch Updater

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

Status in linux package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New
Status in linux package in Debian:
  Fix Released

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981&osId=785

  WORKAROUND: Use suspend to disk.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612916/+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 2098562] Re: Battery life reduced after upgrading to 6.8.0-53.55

2025-02-28 Thread Paul White

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 2098562

and then change the status of the bug to 'New'

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs

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

** Tags added: noble

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

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

Title:
  Battery life reduced after upgrading to 6.8.0-53.55

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating the kernel from 6.8.0-52 to 6.8.0-53 in noble, network
  adapter, brightness control, etc were missing which I fixed by
  downloading linux-image-6.8.0-53-generic package but after using for
  2-3 days I realized downgrade in battery life. Moreover I had capped
  charge limit to 90 but it charged to 100 but after reboot it got
  corrected but no improvement in battery life.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098562/+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 2098726] Re: Cannot set alias for USB NIC RTL8153

2025-02-28 Thread psl

I retested with Linux Mint 22.1 and I see the same result... :-( BTW,
kernel driver reports the same version...

$ uname -a
Linux t640 6.8.0-53-generic #55-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 17 15:37:52 
UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

$ sudo ethtool -i enxc84d442124e4
driver: r8152
version: v1.12.13
firmware-version: rtl8153a-4 v2 02/07/20
expansion-rom-version: 
bus-info: usb-:03:00.3-4.2
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

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

Title:
  Cannot set alias for USB NIC RTL8153

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 20.3, based on Ubuntu 20.04

  $ uname -a
  Linux mintbook 5.15.0-131-generic #141~20.04.1-Ubuntu SMP Thu Jan 16 18:38:51 
UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

  I have an ASUS notebook and it has no RJ45 socket. I use USB Gigabit
  adapter based on RTL8153. So far it worked OK but I have found today
  that I cannot configure alias with ifconfig. Try to configure alias IP
  address with ifconfig changes default interface. It looks like a bug
  in the RTL8153 driver.

  $ ethtool -i enx00e04c68002f
  driver: r8152
  version: v1.12.13
  firmware-version: rtl8153b-2 v1 10/23/19
  expansion-rom-version:
  bus-info: usb-:00:14.0-2
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: no

  $ lsusb | grep 8153
  Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter

  Steps to replicate:

  1) Connect USB adapter to a LAN, I assume I received IP address 192.168.1.11 
from DHCP server.
  2) check with ifconfig what is IP address on interface enx00e04c68002f
  3) define alias, 'sudo ifconfig enx00e04c68002f:33 192.168.33.11'
  4) check with ifconfig the result

  I see that there is no new interface enx00e04c68002f:33 and that IP
  address on interface enx00e04c68002f was changed to 192.168.33.11.
  That is a bug!

  Expected behavior:

  Interface enx00e04c68002f will keep IP address assigned from DHCP server, 
like 192.168.1.11
  New interface enx00e04c68002f:33 will be added with IP address 192.168.33.11

  This report is for an older kernel and older Ubuntu distribution. I
  assume the bug is still in the newer kernel, this has to be
  retested...

  ---

  When I use this method on my WiFi interface (based on rtl8821ce), IP alias 
works as expected. This points to an issue with r8152 driver...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psl   196710 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2022-04-12 (1043 days ago)
  InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X415EA_X415EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-131-generic 
root=UUID=24d0a025-dfb5-4009-9fdc-af9b242b1605 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-131.141~20.04.1-generic 5.15.168
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-131-generic N/A
   linux-backports-modules-5.15.0-131-generic  N/A
   linux-firmware  1.187.39
  Tags:  una
  Uname: Linux 5.15.0-131-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/14/2024
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X415EA.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X415EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX415EA.316:bd03/14/2024:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX415EA_X415EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX415EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X415EA_X415EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098726/+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 2099745] [NEW] Poor code generation in shipped zfs.ko resulting in ~5x zstd decompression (and likely compression too) slowdown. Freshly built zfs.ko from zfs-dkms is fine

2025-02-28 Thread Bruno Ricci

Public bug reported:

1. *  System info *:
  - lscpu | grep -E "Model name|Flags"

Model name:   Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Flags:fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities

  - lsb_release -rd

Description:  Ubuntu 24.04.2 LTS
Release:  24.04

apt-cache policy linux-modules-6.8.0-53-generic zfs-dkms

linux-modules-6.8.0-53-generic:
  Installed: 6.8.0-53.55
  Candidate: 6.8.0-53.55
  Version table:
 *** 6.8.0-53.55 500
500 http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
100 /var/lib/dpkg/status
zfs-dkms:
  Installed: 2.2.2-0ubuntu9.1
  Candidate: 2.2.2-0ubuntu9.1
  Version table:
 *** 2.2.2-0ubuntu9.1 500
500 http://gb.archive.ubuntu.com/ubuntu noble-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.2.2-0ubuntu9 500
500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages

2.  Summary *:
  - Poor code generation in the main zstd decompression loop in the shipped 
zfs.ko
is resulting in a ~5x decompression slowdown compared to a freshly built 
zfs.ko from zfs-dkms.
This issue is also likely affecting zstd compression.

3. *** Reproduction *:
  - Create a test dataset with encryption disabled (to remove a possible cause):
sudo zfs create -o encryption=off -o recordsize=128k -o compression=zstd 
rpool/test

  - Get some compressible file around ~500MB in size (anything will do as long 
as it is compressible).
For example: wget 
https://download.qt.io/archive/qt/4.8/4.8.2/qt-everywhere-opensource-src-4.8.2.tar.gz
gzip -d qt-everywhere-opensource-src-4.8.2.tar.gz

  - Benchmark sequential reads with fio:
mv -v qt-everywhere-opensource-src-4.8.2.tar 
qt-everywhere-opensource-src-4.8.2.tar.0.0
zpool sync
# Run the fio command a few times to ensure the data is in the ARC.
fio --name=qt-everywhere-opensource-src-4.8.2.tar --bs=128k --rw=read 
--numjobs=1 --iodepth=1 --size=500M --group_reporting --loops=10

4. ** Expected results :
  - The fio command in step 3 benchmarks sequential cached reads from the ARC.
We are therefore measuring single-threaded zstd decompression performance 
in zfs.ko.

  - With the shipped zfs.ko:

qt-everywhere-opensource-src-4.8.2.tar: (g=0): rw=randread, bs=(R) 
128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=1
fio-3.36
Starting 1 process
Jobs: 1 (f=1): [r(1)][100.0%][r=205MiB/s][r=1642 IOPS][eta 00m:00s]
qt-everywhere-opensource-src-4.8.2.tar: (groupid=0, jobs=1): err= 0: pid=4354: 
Fri Feb 21 13:22:43 2025
  read: IOPS=1651, BW=206MiB/s (216MB/s)(5000MiB/24223msec)
clat (usec): min=12, max=2677, avg=604.97, stdev=459.39
 lat (usec): min=12, max=2677, avg=605.02, stdev=459.39
clat percentiles (usec):
 |  1.00th=[   23],  5.00th=[   25], 10.00th=[   25], 20.00th=[   27],
 | 30.00th=[  202], 40.00th=[  519], 50.00th=[  660], 60.00th=[  758],
 | 70.00th=[  881], 80.00th=[ 1029], 90.00th=[ 1156], 95.00th=[ 1352],
 | 99.00th=[ 1680], 99.50th=[ 1745], 99.90th=[ 2057], 99.95th=[ 2114],
 | 99.99th=[ 2180]
   bw (  KiB/s): min=199936, max=219648, per=99.95%, avg=211264.00, 
stdev=5629.40, samples=48
   iops: min= 1562, max= 1716, avg=1650.50, stdev=43.98, samples=48
  lat (usec)   : 20=0.02%, 50=27.77%, 100=0.62%, 250=2.70%, 500=7.67%
  lat (usec)   : 750=20.08%, 1000=19.07%
  lat (msec)   : 2=21.91%, 4=0.17%
  cpu  : usr=0.19%, sys=99.72%, ctx=79, majf=0, minf=41
  IO depths: 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
 submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
 complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
 issued rwts: total=4,0,0,0 short=0,0,0,0 dropped=0,0,0,0
 latency   : target=0, window=0, percentile=100.00%, depth=1

Run status group 0 (all jobs):
   READ: bw=206MiB/s (216MB/s), 206MiB/s-206MiB/s (216MB/s-216MB/s), io=5000MiB 
(5243MB), run=24223-24223msec

  - With zfs.ko from zfs-dkms:

qt-everywhere-opensource-src-4.8.2.tar: (g=0): rw=read, bs=(R) 128KiB-128KiB, 
(W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=1
fio-3.36
Starting 1 p

[Kernel-packages] [Bug 2099748] [NEW] kworker/u32:2+events_unbound kernel thread making computer unusable until reboot

Public bug reported:

When viewing videos sometimes the kernel thread
kworker/u32:2+events_unbound starts to consume 100% CPU while the screen
response (including mouse) drops to less than 1 image per second. I
managed to crash the kernel and capture the core image of that crash
while the kernel was in this state (see debugging the kernel crashes)
but I am not sure what to do next to investigate this problem. I think
it should be possible to interrogate that dump somehow to see what
exactly was the kernel thread doing but I don't know how.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-53-generic 6.8.0-53.55
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
Uname: Linux 6.8.0-53-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:jozef  2671 F pipewire
 /dev/snd/controlC1:  jozef  2675 F wireplumber
 /dev/snd/controlC0:  jozef  2675 F wireplumber
 /dev/snd/controlC2:  jozef  2675 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 22 17:27:31 2025
InstallationDate: Installed on 2024-02-14 (374 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507NU_FA507NU
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic 
root=UUID=ac7c0a1e-2f8d-465c-9ec4-f8861895ec66 ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.8.0-53-generic N/A
 linux-backports-modules-6.8.0-53-generic  N/A
 linux-firmware20240318.git3b128b60-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2025-01-30 (24 days ago)
dmi.bios.date: 03/15/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FA507NU.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FA507NU
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507NU.306:bd03/15/2023:br5.24:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507NU_FA507NU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507NU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUS TUF Gaming A15
dmi.product.name: ASUS TUF Gaming A15 FA507NU_FA507NU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  kworker/u32:2+events_unbound kernel thread making computer unusable
  until reboot

Status in linux package in Ubuntu:
  New

Bug description:
  When viewing videos sometimes the kernel thread
  kworker/u32:2+events_unbound starts to consume 100% CPU while the
  screen response (including mouse) drops to less than 1 image per
  second. I managed to crash the kernel and capture the core image of
  that crash while the kernel was in this state (see debugging the
  kernel crashes) but I am not sure what to do next to investigate this
  problem. I think it should be possible to interrogate that dump
  somehow to see what exactly was the kernel thread doing but I don't
  know how.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-53-generic 6.8.0-53.55
  ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
  Uname: Linux 6.8.0-53-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:jozef  2671 F pipewire
   /dev/snd/controlC1:  jozef  2675 F wireplumber
   /dev/snd/controlC0:  jozef  2675 F wireplumber
   /dev/snd/controlC2:  jozef  2675 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 22 17:27:31 2025
  InstallationDate: Installed on 2024-02-14 (374 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507NU_FA507NU
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic 
root=UUID=ac7c0a1e-2f8d-465c-9ec4-f8861895ec66 ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  Rela

[Kernel-packages] [Bug 2099745] Re: Poor code generation in shipped zfs.ko resulting in ~5x zstd decompression (and likely compression too) slowdown. Freshly built zfs.ko from zfs-dkms is fine

2025-02-28 Thread Ubuntu Foundations Team Bug Bot

The attachment "Small patch to inline ZSTD_copy(4|8|16)" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Poor code generation in shipped zfs.ko resulting in ~5x zstd
  decompression (and likely compression too) slowdown. Freshly built
  zfs.ko from zfs-dkms is fine

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  1. *  System info *:
    - lscpu | grep -E "Model name|Flags"

  Model name:   Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Flags:fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities

    - lsb_release -rd

  Description:  Ubuntu 24.04.2 LTS
  Release:  24.04

  apt-cache policy linux-modules-6.8.0-53-generic zfs-dkms

  linux-modules-6.8.0-53-generic:
    Installed: 6.8.0-53.55
    Candidate: 6.8.0-53.55
    Version table:
   *** 6.8.0-53.55 500
  500 http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
  zfs-dkms:
    Installed: 2.2.2-0ubuntu9.1
    Candidate: 2.2.2-0ubuntu9.1
    Version table:
   *** 2.2.2-0ubuntu9.1 500
  500 http://gb.archive.ubuntu.com/ubuntu noble-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.2-0ubuntu9 500
  500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages

  2.  Summary *:
    - Poor code generation in the main zstd decompression loop in the shipped 
zfs.ko
  is resulting in a ~5x decompression slowdown compared to a freshly built 
zfs.ko from zfs-dkms.
  This issue is also likely affecting zstd compression.

  3. *** Reproduction *:
    - Create a test dataset with encryption disabled (to remove a possible 
cause):
  sudo zfs create -o encryption=off -o recordsize=128k -o compression=zstd 
rpool/test

    - Get some compressible file around ~500MB in size (anything will do as 
long as it is compressible).
  For example: wget 
https://download.qt.io/archive/qt/4.8/4.8.2/qt-everywhere-opensource-src-4.8.2.tar.gz
  gzip -d qt-everywhere-opensource-src-4.8.2.tar.gz

    - Benchmark sequential reads with fio:
  mv -v qt-everywhere-opensource-src-4.8.2.tar 
qt-everywhere-opensource-src-4.8.2.tar.0.0
  zpool sync
  # Run the fio command a few times to ensure the data is in the ARC.
  fio --name=qt-everywhere-opensource-src-4.8.2.tar --bs=128k --rw=read 
--numjobs=1 --iodepth=1 --size=500M --group_reporting --loops=10

  4. ** Expected results :
    - The fio command in step 3 benchmarks sequential cached reads from the ARC.
  We are therefore measuring single-threaded zstd decompression performance 
in zfs.ko.

    - With the shipped zfs.ko:

  qt-everywhere-opensource-src-4.8.2.tar: (g=0): rw=randread, bs=(R) 
128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=1
  fio-3.36
  Starting 1 process
  Jobs: 1 (f=1): [r(1)][100.0%][r=205MiB/s][r=1642 IOPS][eta 00m:00s]
  qt-everywhere-opensource-src-4.8.2.tar: (groupid=0, jobs=1): err= 0: 
pid=4354: Fri Feb 21 13:22:43 2025
    read: IOPS=1651, BW=206MiB/s (216MB/s)(5000MiB/24223msec)
  clat (usec): min=12, max=2677, avg=604.97, stdev=459.39
   lat (usec): min=12, max=2677, avg=605.02, stdev=459.39
  clat percentiles (usec):
   |  1.00th=[   23],  5.00th=[   25], 10.00th=[   25], 20.00th=[   27],
   | 30.00th=[  202], 40.00th=[  519], 50.00th=[  660], 60.00th=[  758],
   | 70.00th=[  881], 80.00th=[ 1029], 90.00th=[ 1156], 95.00th=[ 1352],
   | 99.00th=[ 1680], 99.50th=[ 1745], 99.90th=[ 2057], 99.95th=[ 2114],
   | 99.99th=[ 2180]
     bw (  KiB/s): min=199936, max=219648, per=99.95%, avg=211264.00, 
stdev=5629.40, samples=48
     iops: min= 1562, max= 1716, avg=1650.50, stdev=43.98, samples=48
    lat (usec)   : 20=0.02%, 50=27.

[Kernel-packages] [Bug 2099745] Re: Poor code generation in shipped zfs.ko resulting in ~5x zstd decompression (and likely compression too) slowdown. Freshly built zfs.ko from zfs-dkms is fine

2025-02-28 Thread Bruno Ricci

** Attachment added: "Freshly built zfs.ko from zfs-dkms against 
6.8.0-53-generic"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2099745/+attachment/5859404/+files/zfs-dkms.ko

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

Title:
  Poor code generation in shipped zfs.ko resulting in ~5x zstd
  decompression (and likely compression too) slowdown. Freshly built
  zfs.ko from zfs-dkms is fine

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  1. *  System info *:
    - lscpu | grep -E "Model name|Flags"

  Model name:   Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Flags:fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities

    - lsb_release -rd

  Description:  Ubuntu 24.04.2 LTS
  Release:  24.04

  apt-cache policy linux-modules-6.8.0-53-generic zfs-dkms

  linux-modules-6.8.0-53-generic:
    Installed: 6.8.0-53.55
    Candidate: 6.8.0-53.55
    Version table:
   *** 6.8.0-53.55 500
  500 http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
  zfs-dkms:
    Installed: 2.2.2-0ubuntu9.1
    Candidate: 2.2.2-0ubuntu9.1
    Version table:
   *** 2.2.2-0ubuntu9.1 500
  500 http://gb.archive.ubuntu.com/ubuntu noble-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.2.2-0ubuntu9 500
  500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages

  2.  Summary *:
    - Poor code generation in the main zstd decompression loop in the shipped 
zfs.ko
  is resulting in a ~5x decompression slowdown compared to a freshly built 
zfs.ko from zfs-dkms.
  This issue is also likely affecting zstd compression.

  3. *** Reproduction *:
    - Create a test dataset with encryption disabled (to remove a possible 
cause):
  sudo zfs create -o encryption=off -o recordsize=128k -o compression=zstd 
rpool/test

    - Get some compressible file around ~500MB in size (anything will do as 
long as it is compressible).
  For example: wget 
https://download.qt.io/archive/qt/4.8/4.8.2/qt-everywhere-opensource-src-4.8.2.tar.gz
  gzip -d qt-everywhere-opensource-src-4.8.2.tar.gz

    - Benchmark sequential reads with fio:
  mv -v qt-everywhere-opensource-src-4.8.2.tar 
qt-everywhere-opensource-src-4.8.2.tar.0.0
  zpool sync
  # Run the fio command a few times to ensure the data is in the ARC.
  fio --name=qt-everywhere-opensource-src-4.8.2.tar --bs=128k --rw=read 
--numjobs=1 --iodepth=1 --size=500M --group_reporting --loops=10

  4. ** Expected results :
    - The fio command in step 3 benchmarks sequential cached reads from the ARC.
  We are therefore measuring single-threaded zstd decompression performance 
in zfs.ko.

    - With the shipped zfs.ko:

  qt-everywhere-opensource-src-4.8.2.tar: (g=0): rw=randread, bs=(R) 
128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=1
  fio-3.36
  Starting 1 process
  Jobs: 1 (f=1): [r(1)][100.0%][r=205MiB/s][r=1642 IOPS][eta 00m:00s]
  qt-everywhere-opensource-src-4.8.2.tar: (groupid=0, jobs=1): err= 0: 
pid=4354: Fri Feb 21 13:22:43 2025
    read: IOPS=1651, BW=206MiB/s (216MB/s)(5000MiB/24223msec)
  clat (usec): min=12, max=2677, avg=604.97, stdev=459.39
   lat (usec): min=12, max=2677, avg=605.02, stdev=459.39
  clat percentiles (usec):
   |  1.00th=[   23],  5.00th=[   25], 10.00th=[   25], 20.00th=[   27],
   | 30.00th=[  202], 40.00th=[  519], 50.00th=[  660], 60.00th=[  758],
   | 70.00th=[  881], 80.00th=[ 1029], 90.00th=[ 1156], 95.00th=[ 1352],
   | 99.00th=[ 1680], 99.50th=[ 1745], 99.90th=[ 2057], 99.95th=[ 2114],
   | 99.99th=[ 2180]
     bw (  KiB/s): min=199936, max=219648, per=99.95%, avg=211264.00, 
stdev=5629.40, samples=48
     iops: min= 1562, max= 1716, avg=1650.50, stdev=43.98, samples=48
    lat (usec)   : 20=0.02%, 50=27.77%, 100=0.62%, 250=2.70%, 500=7.67%
    lat (usec)   : 750=20.08%, 1000=19.07%
    lat (msec)   : 2=21.91%, 4=0.17%
    cpu  : usr=0.19%, sys=99.72%, ctx=79, majf=0, minf=41
    IO de

[Kernel-packages] [Bug 2099745] Re: Poor code generation in shipped zfs.ko resulting in ~5x zstd decompression (and likely compression too) slowdown. Freshly built zfs.ko from zfs-dkms is fine

2025-02-28 Thread Bruno Ricci

** Patch added: "Small patch to inline ZSTD_copy(4|8|16)"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2099745/+attachment/5859405/+files/patch0-MEM_STATIC-on-ZSTD_copy4-8-16.patch

** Description changed:

  1. *  System info *:
-   - lscpu | grep -E "Model name|Flags"
+   - lscpu | grep -E "Model name|Flags"
  
  Model name:   Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Flags:fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl 
vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap 
clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp 
hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities
  
-   - lsb_release -rd
+   - lsb_release -rd
  
  Description:  Ubuntu 24.04.2 LTS
  Release:  24.04
  
  apt-cache policy linux-modules-6.8.0-53-generic zfs-dkms
  
  linux-modules-6.8.0-53-generic:
-   Installed: 6.8.0-53.55
-   Candidate: 6.8.0-53.55
-   Version table:
-  *** 6.8.0-53.55 500
- 500 http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 6.8.0-53.55
+   Candidate: 6.8.0-53.55
+   Version table:
+  *** 6.8.0-53.55 500
+ 500 http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  zfs-dkms:
-   Installed: 2.2.2-0ubuntu9.1
-   Candidate: 2.2.2-0ubuntu9.1
-   Version table:
-  *** 2.2.2-0ubuntu9.1 500
- 500 http://gb.archive.ubuntu.com/ubuntu noble-updates/universe amd64 
Packages
- 100 /var/lib/dpkg/status
-  2.2.2-0ubuntu9 500
- 500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
- 
+   Installed: 2.2.2-0ubuntu9.1
+   Candidate: 2.2.2-0ubuntu9.1
+   Version table:
+  *** 2.2.2-0ubuntu9.1 500
+ 500 http://gb.archive.ubuntu.com/ubuntu noble-updates/universe amd64 
Packages
+ 100 /var/lib/dpkg/status
+  2.2.2-0ubuntu9 500
+ 500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
  
  2.  Summary *:
-   - Poor code generation in the main zstd decompression loop in the shipped 
zfs.ko
- is resulting in a ~5x decompression slowdown compared to a freshly built 
zfs.ko from zfs-dkms.
- This issue is also likely affecting zstd compression.
- 
+   - Poor code generation in the main zstd decompression loop in the shipped 
zfs.ko
+ is resulting in a ~5x decompression slowdown compared to a freshly built 
zfs.ko from zfs-dkms.
+ This issue is also likely affecting zstd compression.
  
  3. *** Reproduction *:
-   - Create a test dataset with encryption disabled (to remove a possible 
cause):
- sudo zfs create -o encryption=off -o recordsize=128k -o compression=zstd 
rpool/test
+   - Create a test dataset with encryption disabled (to remove a possible 
cause):
+ sudo zfs create -o encryption=off -o recordsize=128k -o compression=zstd 
rpool/test
  
-   - Get some compressible file around ~500MB in size (anything will do as 
long as it is compressible).
- For example: wget 
https://download.qt.io/archive/qt/4.8/4.8.2/qt-everywhere-opensource-src-4.8.2.tar.gz
- gzip -d qt-everywhere-opensource-src-4.8.2.tar.gz
+   - Get some compressible file around ~500MB in size (anything will do as 
long as it is compressible).
+ For example: wget 
https://download.qt.io/archive/qt/4.8/4.8.2/qt-everywhere-opensource-src-4.8.2.tar.gz
+ gzip -d qt-everywhere-opensource-src-4.8.2.tar.gz
  
-   - Benchmark sequential reads with fio:
- mv -v qt-everywhere-opensource-src-4.8.2.tar 
qt-everywhere-opensource-src-4.8.2.tar.0.0
- zpool sync
- # Run the fio command a few times to ensure the data is in the ARC.
- fio --name=qt-everywhere-opensource-src-4.8.2.tar --bs=128k --rw=read 
--numjobs=1 --iodepth=1 --size=500M --group_reporting --loops=10
+   - Benchmark sequential reads with fio:
+ mv -v qt-everywhere-opensource-src-4.8.2.tar 
qt-everywhere-opensource-src-4.8.2.tar.0.0
+ zpool sync
+ # Run the fio command a few times to ensure the data is in the ARC.
+ fio --name=qt-everywhere-opensource-src-4.8.2.tar --bs=128k --rw=read 
--numjobs=1 --iodepth=1 --size=500M --group_reporting --loops=10
  
  4. ** Expected results :
-   - The fio command in step 3 benchmarks sequential cached read from the ARC.
- We are therefore measuring single-threaded zstd decompression performance 
in zfs.ko.
+

[Kernel-packages] [Bug 2098562] [NEW] Battery life reduced after upgrading to 6.8.0-53.55

You have been subscribed to a public bug:

After updating the kernel from 6.8.0-52 to 6.8.0-53 in noble, network
adapter, brightness control, etc were missing which I fixed by
downloading linux-image-6.8.0-53-generic package but after using for 2-3
days I realized downgrade in battery life. Moreover I had capped charge
limit to 90 but it charged to 100 but after reboot it got corrected but
no improvement in battery life.

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


** Tags: bot-comment
-- 
Battery life reduced after upgrading to 6.8.0-53.55
https://bugs.launchpad.net/bugs/2098562
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1547332] Re: [Feature Request] Provide option to install root to a ZFS formatted disk

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1547332

Title:
   [Feature Request] Provide option to install root to a ZFS formatted
  disk

Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  Now that ZFS tools and support will be included by default in 16.04,
  it would be great if we could install directly to a ZFS formatted disk
  using the graphical installer.

  Yes, I know that root can be manually installed to ZFS formated disk.
  See https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-install-Ubuntu-
  to-a-Native-ZFS-Root-Filesystem  But an option to install using the
  graphical installer would be nice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1547332/+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 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Won't Fix
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+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 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel

** Changed in: ubiquity (Ubuntu)
   Status: New => Won't Fix

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

Title:
  After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't
  update nvidia modules in kernel

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Won't Fix
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  SYSTEM:

  Laptop: ASUS ROG GL552VW
  OS: Ubuntu 20.04.2 LTS
  GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics
  Linux kernel version: 5.8.0-44-generic

  SUMMARY:

  From a fresh working install of Ubuntu 20.04, I downgraded from
  nvidia-driver-460 by installing nvidia-driver-440 (which actually is a
  transitional package to nvidia-driver-450 but I didn't know this).
  After reboot I couldn't reach login-screen and instead got a black
  screen.

  Problem was that sudo apt-get install nvidia-driver-440 did not insert
  nvidia modules v450 in kernel since never versions v460 were found.

  This was solved by uninstalling linux-modules-nvidia-460 packages and
  instead installing linux-modules-nvidia-450 packages (see WORKAROUND
  below for instructions).

  STEPS TO REPRODUCE:

  Install Ubuntu 20.04. During installation, allow for the installation
  of proprietary drivers.

  Once Ubuntu 20.04 has started, open a terminal and run the following:

  sudo add-apt-repository ppa:graphics-drivers/ppa
  sudo apt-get update
  sudo apt-get install nvidia-driver-440
  sudo shutdown reboot now

  PROBLEM:

  After reboot, you can't reach login screen. Instead you get stuck
  during bootup.

  WORKAROUND:

  WARNING: BETTER WORKAROUND PROBABLY EXISTS! DON'T JUST COPY-PASTE
  INSTRUCTIONS. PAY ATTENTION TO WHAT NVIDIA DRVER AND LINUX KERNEL
  VERSIONS ARE RELEVANT FOR YOU! Run dpkg --list | grep linux-image to
  see what linux kenrel versions you have installed.

  Remove the linux-modules-nvidia-460 packages and install the
  corresponding linux-modules-nvidia-450 packages. In my case I had
  Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed
  so I did as follows from recovery mode with network (instead of
  entering recovery mode, you should be able to press CTRL+ALT+F1 from
  the blank screen after bootup, login with username and password and
  then running these commands):

  sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic 
linux-modules-nvidia-460-5.8.0-43-generic
  sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic 
linux-modules-nvidia-450-5.8.0-43-generic
  sudo shutdown reboot now

  QUESTION:

  Why was the linux-modules-nvidia-460 packages installed by the Ubuntu
  installer to begin with? I ask since I later removed the linux-
  modules-nvidia-450 packages (OBSERVE: 450, not 460) and used the
  Additional Drivers GUI to update back to nvidia-driver-460. Now linux-
  modules-nvidia-460 packages are NOT installed but the following still
  outputs 460:

  modinfo nvidia | grep -i version

  LOG:

  This is a relevant part of /var/log/apt/term.log for when I installed
  nvidia-driver-440

  nvidia.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-modeset.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-modeset.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-drm.ko:
  Running module version sanity check.
  Error! Module version 450.102.04 for nvidia-drm.ko
  is not newer than what is already found in kernel 5.8.0-44-generic (460.39).
  You may override by specifying --force.

  nvidia-uvm.ko:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/

  This is a relevant part of /var/log/apt/term.log for when I installed
  packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules-
  nvidia-450-5.8.0-43-generic

  Building module:
  cleaning build area...
  unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 
'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.8.0-43-generic 
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/5.8.0-43-generic/build LD=/usr/bin/ld.bfd 
modules
  Signing module:
   - 
/var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-modeset.ko
   - 
/var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-uvm.ko
   - 
/var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-drm.ko
   - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nv

[Kernel-packages] [Bug 1857398] Re: ubiquity should support encryption by default with zfsroot, with users able to opt in to running change-key after install

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ubiquity should support encryption by default with zfsroot, with users
  able to opt in to running change-key after install

Status in ubiquity package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  zfs supports built-in encryption support, but the decision of whether
  a pool is encrypted or not must be made at pool creation time; it is
  possible to add encrypted datasets on top of an unencrypted pool but
  it is not possible to do an online change of a dataset (or a whole
  pool) to toggle encryption.

  We should therefore always install with encryption enabled on zfs
  systems, with a non-secret key by default, and allow the user to use
  'zfs change-key -o keylocation=prompt' after install to take ownership
  of the encryption and upgrade the security.

  This is also the simplest way to allow users to avoid having to choose
  between the security of full-disk encryption, and the advanced
  filesystem features of zfs since it requires no additional UX work in
  ubiquity.

  We should make sure that
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857040 is fixed
  first in the kernel so that enabling zfs encryption does not impose an
  unreasonable performance penalty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857398/+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 2081629] Re: bluetooth mouse no longer works after suspend/resume

2025-02-28 Thread Simon Dalley

Problem no longer occurs for me with recent and current updates of
Ubuntu 24.04.

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

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

Title:
  bluetooth mouse no longer works after suspend/resume

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I did a clean install of ubuntu Desktop 24.04.1,
  currently containing bluez 5.72-0ubuntu5.

  Went through normal pairing procedure with a fairly vanilla Dell mouse 
MS5120W. Worked fine.
  Suspended computer, resumed a few hours later. Mouse was now unresponsive.
  Bluetooth Settings said that Dell mouse was still connected. Attempted 
disconnect/reconnect from the interface - sluggish or no response from 
interface. Mouse remained unresponsive.
  Selected Forget about this Device, selected pairing mode again to set it up 
again from zero - worked.
  Continued working until the next suspend/resume.

  Ubuntu 23.10 did NOT exhibit this problem - mouse would wake up almost 
instantly as soon as you moved it again after resuming from suspend.
  Expected behavior: as per Ubuntu 23.10 above.

  Some messages emitted by bluetoothd in the system log:
  After resume:
  sap-server: Operation not permitted (1)
  One second later:
  Failed to load LTKs for hci0: Invalid Parameters (0x0d)
  Failed to load IRKs for hci0: Invalid Parameters (0x0d)

  When trying to move the mouse pointer half a minute later:
  profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic 
read failed: Request attribute has encountered an unlikely error
  profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: 
Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic 
read failed: Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:report_reference_cb() Read Report Reference 
descriptor failed: Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request 
attribute has encountered an unlikely error

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: bluez 5.72-0ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-45.45.1-lowlatency 6.8.12
  Uname: Linux 6.8.0-45-lowlatency x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 22 13:10:02 2024
  InstallationDate: Installed on 2024-09-16 (6 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.8.0-45-lowlatency 
root=UUID=f34d0195-1ab4-412e-9b6f-9a69bc9f1efb ro rootflags=subvol=@ quiet 
splash threadirqs vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: B550I AORUS PRO AX
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd10/29/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550IAORUSPROAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550IAORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B550 MB
  dmi.product.name: B550I AORUS PRO AX
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:89:D2:7A:1E:1C  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN ISCAN 
RX bytes:812296 acl:452 sco:0 events:18822 errors:0
TX bytes:32524 acl:452 sco:0 commands:2017 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081629/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled

** Changed in: ubiquity (Ubuntu)
   Status: New => Won't Fix

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

Title:
  No wifi after installation - does not work with secure boot enabled

Status in bcmwl package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Won't Fix

Bug description:
  After installation I noted that my broadcom wifi was not available.
  This is a regression from 20.04 where installation automatically
  installed the broadcom driver.

  So I tried to force the installation again - see trace below.

  The dialog message to enter the secure password appeared - however on
  reboot a confirmation to change the MOK state was not seen - the
  distro booted straight in.

  sudo apt install --reinstall bcmwl-kernel-source 
  [sudo] password for dad: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to 
upgrade.
  Need to get 1,546 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 
bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB]
  Fetched 1,546 kB in 0s (5,232 kB/s)   
  (Reading database ... 202371 files and directories currently installed.)
  Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ...
  Removing all DKMS Modules
  Done.
  Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over 
(6.30.223.271+bdcom-0ubuntu7) ...
  Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
  Loading new bcmwl-6.30.223.271+bdcom DKMS files...
  Building for 5.8.0-22-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-22-generic
  Done.

  wl.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/

  depmod

  DKMS: install completed.
  modprobe: ERROR: could not insert 'wl': Operation not permitted
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct 13 18:32:47 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 
(20201013)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 2081629] Re: bluetooth mouse no longer works after suspend/resume

2025-02-28 Thread Simon Dalley

The bluetooth mouse is now working properly again after suspend/resume.
Presumably came out in the wash after a system update.

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

Title:
  bluetooth mouse no longer works after suspend/resume

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I did a clean install of ubuntu Desktop 24.04.1,
  currently containing bluez 5.72-0ubuntu5.

  Went through normal pairing procedure with a fairly vanilla Dell mouse 
MS5120W. Worked fine.
  Suspended computer, resumed a few hours later. Mouse was now unresponsive.
  Bluetooth Settings said that Dell mouse was still connected. Attempted 
disconnect/reconnect from the interface - sluggish or no response from 
interface. Mouse remained unresponsive.
  Selected Forget about this Device, selected pairing mode again to set it up 
again from zero - worked.
  Continued working until the next suspend/resume.

  Ubuntu 23.10 did NOT exhibit this problem - mouse would wake up almost 
instantly as soon as you moved it again after resuming from suspend.
  Expected behavior: as per Ubuntu 23.10 above.

  Some messages emitted by bluetoothd in the system log:
  After resume:
  sap-server: Operation not permitted (1)
  One second later:
  Failed to load LTKs for hci0: Invalid Parameters (0x0d)
  Failed to load IRKs for hci0: Invalid Parameters (0x0d)

  When trying to move the mouse pointer half a minute later:
  profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic 
read failed: Request attribute has encountered an unlikely error
  profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: 
Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic 
read failed: Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:report_reference_cb() Read Report Reference 
descriptor failed: Request attribute has encountered an unlikely error
  profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request 
attribute has encountered an unlikely error

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: bluez 5.72-0ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-45.45.1-lowlatency 6.8.12
  Uname: Linux 6.8.0-45-lowlatency x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 22 13:10:02 2024
  InstallationDate: Installed on 2024-09-16 (6 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.8.0-45-lowlatency 
root=UUID=f34d0195-1ab4-412e-9b6f-9a69bc9f1efb ro rootflags=subvol=@ quiet 
splash threadirqs vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: B550I AORUS PRO AX
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd10/29/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550IAORUSPROAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550IAORUSPROAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B550 MB
  dmi.product.name: B550I AORUS PRO AX
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:89:D2:7A:1E:1C  ACL MTU: 1021:6  SCO MTU: 240:8
UP RUNNING PSCAN ISCAN 
RX bytes:812296 acl:452 sco:0 events:18822 errors:0
TX bytes:32524 acl:452 sco:0 commands:2017 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2081629/+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 2087507] Update Released

2025-02-28 Thread Timo Aaltonen

The verification of the Stable Release Update for linux-lowlatency-
hwe-6.8 has completed successfully and the package is now being released
to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Fix error of resume on rtl8168fp

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in linux-oem-6.8 source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  In Progress
Status in linux-oem-6.11 source package in Oracular:
  Invalid
Status in linux-oem-6.8 source package in Oracular:
  Invalid
Status in linux source package in Plucky:
  Fix Released
Status in linux-oem-6.11 source package in Plucky:
  Invalid
Status in linux-oem-6.8 source package in Plucky:
  Invalid

Bug description:
  [Impact]
  After resume r8169 has no link up and shows error:
  kernel: r8169 :02:00.1 enp2s0f1: PCI error (cmd = 0x0407, status_errs = 
0x)

  [Fix]
  Fix this by ignoring this bit on PCIe chip versions.
  commit: 10ce0db787004 r8169: avoid unsolicited interrupts
  The commit is already in 6.12-rc5.

  [Test]
  Tested on hardware, r8169fp works fine after resume.

  [Where problems could occur]
  It may break realtek ethernet.

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

Ok, we'll keep stepping back in time then.

Please try this one and let me know.

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

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

Title:
  brightness

Status in linux package in Ubuntu:
  New

Bug description:
  my laptop brightness automatically change after i adjust it manually.
  if i haven't adjust it after booting, the brightness wont change
  automatically. so i need to reboot if i don't want it to change
  automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-52-generic 6.8.0-52.53
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  Uname: Linux 6.8.0-52-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:msi1540 F pipewire
   /dev/snd/controlC0:  msi1544 F wireplumber
   /dev/snd/controlC2:  msi1544 F wireplumber
   /dev/snd/controlC1:  msi1544 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 15:25:31 2025
  InstallationDate: Installed on 2025-02-06 (3 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-52-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash acpi_osi=Linux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-52-generic N/A
   linux-backports-modules-6.8.0-52-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 1.22
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E14DKAMS.116
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14DK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.116:bd07/12/2023:br1.22:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku14DK.1:
  dmi.product.family: Modern
  dmi.product.name: Modern 14 B4MW
  dmi.product.sku: 14DK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097696/+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 2098375] Re: ZFS pool randomly encounters error condition and hangs

Let's try again with this kernel:

https://people.canonical.com/~tswhison/bugs/2098375/0001-422b741.tar.gz

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

Title:
  ZFS pool randomly encounters error condition and hangs

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 22.04 to 24.04 the ZFS pool becomes
  unstable and any operations on the mounted volumes hang indefinitely
  until the system is restarted. The mounted ZFS volumes are used for
  MariaDB. The pool is of a single entire drive.

  # apt list --installed|grep -i zfs

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  libzfs4linux/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed,automatic]
  zfs-initramfs/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed]
  zfs-zed/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed,automatic]
  zfsutils-linux/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed]

  
  # zpool status
pool: db
   state: ONLINE
scan: scrub repaired 0B in 03:41:14 with 0 errors on Sun Feb  9 04:05:15 
2025
  config:

NAMESTATE READ WRITE CKSUM
db  ONLINE   0 0 0
  nvme0n1   ONLINE   0 0 0

  errors: No known data errors

  
  # zfs list
  NAME   USED  AVAIL  REFER  MOUNTPOINT
  db1.21T   479G   228K  /db
  db/mysql  1.01T   479G  1.01T  /db/mysql
  db/mysql-log   204G   479G   204G  /db/mysql-log

  # zfs get all db
  NAME  PROPERTY  VALUE  SOURCE
  dbtype  filesystem -
  dbcreation  Sat Jun  3 13:41 2023  -
  dbused  1.21T  -
  dbavailable 479G   -
  dbreferenced228K   -
  dbcompressratio 2.33x  -
  dbmounted   yes-
  dbquota none   default
  dbreservation   none   default
  dbrecordsize128K   default
  dbmountpoint/dbdefault
  dbsharenfs  offdefault
  dbchecksum  on default
  dbcompression   lz4local
  dbatime offlocal
  dbdevices   on default
  dbexec  on default
  dbsetuidon default
  dbreadonly  offdefault
  dbzoned offdefault
  dbsnapdir   hidden default
  dbaclmode   discarddefault
  dbaclinheritrestricted default
  dbcreatetxg 1  -
  dbcanmount  on default
  dbxattr on default
  dbcopies1  default
  dbversion   5  -
  dbutf8only  off-
  dbnormalization none   -
  dbcasesensitivity   sensitive  -
  dbvscan offdefault
  dbnbmandoffdefault
  dbsharesmb  offdefault
  dbrefquota  none   default
  dbrefreservationnone   default
  dbguid  13462119194566498061   -
  dbprimarycache  alldefault
  dbsecondarycachealldefault
  dbusedbysnapshots   0B -
  dbusedbydataset 228K   -
  dbusedbychildren1.21T  -
  dbusedbyrefreservation  0B -
  dblogbias   throughput local
  dbobjsetid  54 -
  dbdedup offdefault
  dbmlslabel  none   default
  dbsync  standard   default
  dbdnodesize legacy default
  dbrefcompressratio  2.10x  -
  dbwritten   228K   -
  dblogicalused   2.82T  -
  dblogicalreferenced 210K   -
  dbvolmode   defaultdefault
  dbfilesystem_limit  none   default
  dbsnapshot_limitnone   default
  dbfilesystem_count  none

[Kernel-packages] [Bug 2098580] Re: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]

Hmm, it could be the same issue. I see this in your CurrentDmesg.txt:

RIP: 0010:do_zfs_log_rename+0x19d/0x1b0 [zfs]

If you are comfortable with calling this one a duplicate, we can mark it
as such. Let me know.

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

Title:
  Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]

Status in linux package in Ubuntu:
  New

Bug description:
  On two systems running Ubuntu 25.04 amd64 I see random crashes.

  KDE freezing. The mounts set to read-only. And fan spinning at max
  speed.

  See appended journal.txt for more details.

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

Re: [Kernel-packages] [Bug 2098802] Re: wired connection disappears after going back from suspension

2025-02-28 Thread Youssef Ibraheem

Yes. This issue has occurred recently after few updates and restarts 
from the system. Yesterday, I tried running some checks through HWINFO 
on WIN11, I also checked the bios for any potential of CMOS Battery 
failure on my MB as it's 4 years old, nothing seems out of the ordinary.

On 2/19/25 6:11 AM, Daniel Letzeisen wrote:
> Oh, I should also ask - Was this working for you (with 6.8 kernel)
> before updating to 6.11 kernel?
>

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

Title:
  wired connection disappears after going back from suspension

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

Bug description:

  No LSB modules are available.
  Description:  Ubuntu 24.04.2 LTS
  Release:  24.04
   youssef@youssef-Z490-VI

  * When I suspend my computer for a short while for any purpose and return to 
re-login, I find the internet connection is turned off. The machine is a PC 
with only a Wired Lan connection, which is working fine. The only way to 
resolve this is to either restart the machine or run the following:
  ```
  1- sudo modprobe -r igc
  then
  2- sudo modprobe -i igc

  ```

  Please note that the PC has a dual boot with Windows 11 installed, the
  connection works OK on Windows.

  * Expected:
  - Internet connection working after suspension
  * Happens:
  - Internet connection not working

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-drivers-common 1:0.9.7.6ubuntu3.1
  ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11
  Uname: Linux 6.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 18 22:18:40 2025
  InstallationDate: Installed on 2024-11-01 (109 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.11/+bug/2098802/+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 2098961] Re: Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

That's great news. OK, I have marked 0001-9c7ca38 as good. Let's keep
going.

Here's the next kernel to test:

https://people.canonical.com/~tswhison/bugs/2098961/0002-436fa21.tar.gz

Please try it and let me know whether good or bad.

Thanks!

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tim Whisonant (tswhison)

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/2098961

Title:
  Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17
  (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu
  22.04/24.04 VMs, we are experiencing extremely low network speeds
  (100-200 KB/s) when running these VMs in a Proxmox 8.3.4 cluster with
  AMD CPUs and Broadcom NetXtreme-E network adapters (bnxt_en driver).

  With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as 
expected.
  Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are 
not affected.
  The same Xubuntu VM, when moved to a different Proxmox cluster (Intel 
CPUs, Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
  The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster 
with AMD CPUs, Broadcom NICs, and Ceph storage.

  Expected behavior:

  Network performance should be normal (10 Gbps or more) without issues.
  Actual behavior:

  Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow 
network speeds (100-200 KB/s).
  iperf3 tests show very low bandwidth (5-10 Mbps).
  Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) 
did not improve performance.
  Other VMs (Debian, Ubuntu Server) on the same cluster do not have this 
issue.
  The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu 
VM.

  Steps to reproduce:

  Proxmox environment:
  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph 
storage
  VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)

  Inside the Xubuntu VM:
  Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
  Test network performance:

  wget -O /dev/null http://speed.hetzner.de/1GB.bin
  iperf3 -c  -P 4

  → Speed is extremely slow (~200 KB/s - 5 Mbps).

  Reboot the VM with Kernel 6.8.0-31

  sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 
6.8.0-31-generic"
  sudo reboot

  → Network performance returns to normal (10 Gbps+).

  Hardware & environment details:
  Proxmox cluster (affected environment):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  AMD CPUs
  Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
  Ceph storage backend
  VMs use VirtIO network adapter (virtio-net)
  Bridging on Broadcom NICs

  Working cluster (same Xubuntu VM, no issue):

  Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
  Intel CPUs
  Intel I350 NICs (igb driver)
  ZFS storage backend
  Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17

  Debugging information:

  Xubuntu VM Kernel versions (affected):

  uname -r
  6.8.0-53-generic
  6.11.0-17-generic

  Broadcom firmware version (Proxmox host):

  ethtool -i enp67s0f0np0 | grep firmware
  firmware-version: 229.0.154.0/pkg 229.1.123.0

  dmesg output related to bnxt_en NICs (Proxmox host):

  dmesg | grep bnxt
  [2.324347] bnxt_en :c5:00.0 (unnamed net_device) (uninitialized): 
Device requests max timeout of 60 seconds, may trigger hung task watchdog
  [2.364280] bnxt_en :c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 
10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b703, node addr 
14:23:f2:5d:18:14
  ...

  → No critical errors, but timeout warnings and performance degradation.
  Possible causes:

  🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
  🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
  🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 
6.8.0-53 and 6.11.0-17
  Next Steps & Further Tests

  Since this is a production system with 200+ running VMs, we will
  conduct further tests once we schedule maintenance.

  Planned additional tests:

  Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule 
out Xubuntu-specific issues).
  Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 
6.8.0-53 and 6.11.0-17.
  Check IRQ assignments and CPU affinity for VirtIO network interfaces.

  📌 If this issue is already reported, please link to the relevant bug report.
  📌 Otherwise, we are happy to provide further debugging information.
  Summary:

  Xubuntu VMs running

[Kernel-packages] [Bug 2098176] Re: [Enablement] TI AMP TAS2781 Enablement

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

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

Title:
  [Enablement]  TI AMP TAS2781 Enablement

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux-firmware source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  On HP platform with a new device TI AMP TAS2781, drivers and firmware need to 
be backported to OEM kernel for hardware enablement.

  [Fix]
  For drivers, cherry-pick the following commit from linux mainline:

  bb5f86ea50ff ALSA: hda/tas2781: Add tas2781 hda SPI driver

  For firmware, cherry-pick the following commit from upstream linux-
  firmware:

  68eeb2a5e89e ASoC: tas2781: Add regbin firmware by index for single
  device

  [Test Plan]
  1. Boot up Ubuntu OEM kernel
  2. Test if sound works fine

  [Where problems could occur]
  This backport is for the hardware enablement of the new device, so it has 
nothing to do with regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2098176/+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 2098171] Re: Remove genphy_config_eee_advert() that accesses eee_broken_modes in buggy manners

** Changed in: linux-oem-6.11 (Ubuntu Noble)
   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.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2098171

Title:
  Remove genphy_config_eee_advert() that accesses eee_broken_modes in
  buggy manners

Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  genphy_config_eee_advert() was removed in "net: phy: remove
  genphy_config_eee_advert"[1] before the phydev->eee_broken_modes was
  converted from a u32 to bitmap (underlyingly an array of unsigned
  long) in "net: phy: switch eee_broken_modes to linkmode bitmap and add
  accessor"[2]. The later one was backported to the OEM 6.11 kernel, but
  the former one wasn't.

  In the remaining genphy_config_eee_advert() in the OEM kernel, it will
  pass phy_device->eee_broken_modes to phy_modify_mmd_changed(), which
  assumes that eee_broken_modes is still an integer, leading to a bug
  that converts a pointer to an integer.

  gcc 13.3 will emit warning, while clang 18.1.3 and gcc 14 catch this
  error:

  drivers/net/phy/phy_device.c:2196:15: warning: address of array 
'phydev->eee_broken_modes' will always evaluate to 'true' 
[-Wpointer-bool-conversion]
   2196 | if (!phydev->eee_broken_modes)
| ~^~~~
  drivers/net/phy/phy_device.c:2200:10: error: incompatible pointer to integer 
conversion passing 'unsigned long[2]' to parameter of type 'u16' (aka 'unsigned 
short') [-Wint-conversion]
   2200 |  phydev->eee_broken_modes, 0);
|  ^~~~
  ./include/linux/phy.h:1438:11: note: passing argument to parameter 'mask' here
   1438 |u16 mask, u16 set);
|^
  1 warning and 1 error generated.

  This can be resolved by backporting [1] that fully replaces the
  genphy_config_eee_advert() in the 6.11 oem kernel.

  [ Test plan ]

  Compile the relevant part by the said compilers. For example on Noble:

  $ make LLVM=1 drivers/net/phy/

  The above error/warning message shouldn’t appear.

  This was introduced only in the 6.11 OEM kernel, which is intended for
  PCs under Noble certification. According to records from the
  certification team website, currently there’s no PC with Broadcom
  ethernet devices under certification, so in theory there’s no actual
  user for the relevant code.

  [ Where the problems could occur ]

  This access pattern to the phydev->eee_broken_modes happens only in
  genphy_config_eee_advert() in drivers/net/phy/bcm-phy-lib.c, which is
  also its only user. There’s only one place in the code where this
  function is used, and from the record on the certification website
  there hasn’t been any PC with Broadcom components undergoing Noble
  certification. So the impact should be limited.

  [1] 
https://lore.kernel.org/all/69d22b31-57d1-4b01-bfde-0c6a1df1e...@gmail.com/#r
  [2] 
https://lore.kernel.org/all/405734c5-0ed4-40e4-9ac9-91084b953...@gmail.com/#r

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2098171/+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 2093162] Re: Respect _WOV entry in BIOS when enabling microphone on AMD acp6x platforms

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

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

Title:
  Respect _WOV entry in BIOS when enabling microphone on AMD acp6x
  platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux-oem-6.8 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Fix Released
Status in linux-oem-6.11 source package in Oracular:
  Invalid
Status in linux-oem-6.8 source package in Oracular:
  Invalid
Status in linux source package in Plucky:
  Fix Released
Status in linux-oem-6.11 source package in Plucky:
  Invalid
Status in linux-oem-6.8 source package in Plucky:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  AMD acp6x driver may not respect BIOS settings and enables DMIC
  (digital microphone) unexpectedly.

  [Fix]

  * Upstream v6.13-rc1 commit 4095cf872084 ("ASoC: amd: yc: Fix for enabling 
DMIC on acp6x via _DSD entry")
  * And two following fixes also from v6.13-rcX: commit 984795e76def ("ASoC: 
amd: yc: Fix the wrong return value") and commit 88438444fddd ("ASoC: amd: ps: 
Fix for enabling DMIC on acp63 platform via _DSD entry")

  [Test Case]

  1) Check BIOS if microphone is turned on/off.
  2) Ensure that microphone is present or not in OS (acp6x device binds or not) 
to match this policy.
  3) Change policy in BIOS.
  4) Ensure that OS behavior matches.

  [Where problems could occur]

  This basically checks whether the value in _WOV valid and enabled.
  Existing systems might found their microphone disabled then, but
  that's to respect the settings in BIOS.

  [Other Info]

  This affects kernel >= v5.19, and some of the changes have been
  backported to v6.12.x and v6.11.x.

  == original bug report ==

  The context of it is a security risk that user turns off microphone in
  BIOS on Lenovo system but it still works in Ubuntu. The patch fixes it
  to look at what BIOS changes to decide whether to enable microphone.

  * 
https://github.com/torvalds/linux/commit/88438444f0244c8b2697713adcca3e71599e
 ("ASoC: amd: ps: Fix for enabling DMIC on acp63 platform via _DSD entry")
    - Fixes: 0386d765f27a ("ASoC: amd: ps: refactor acp device configuration 
read logic")
    - in v6.13-rc5
    - for >= v6.9
  * 
https://github.com/torvalds/linux/commit/4095cf872084ecfdfdb0e681f3e9ff9745acfa75
 ("ASoC: amd: yc: Fix for enabling DMIC on acp6x via _DSD entry")
    - Fixes: 5426f506b584 ("ASoC: amd: Add support for enabling DMIC on acp6x 
via _DSD")
    - in v6.13-rc1, v6.12.2, v6.11.11
    - for >= v5.19
  * 
https://github.com/torvalds/linux/commit/984795e76def5c903724b8d6a8228e356bbdf2af
    - Fixes: 4095cf872084 (ASoC: amd: yc: Fix for enabling DMIC on acp6x via 
_DSD entry)
    - in v6.13-rc3, v6.12.6
    - for >= v6.13-rc1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2093162/+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 2097554] Re: optimized default EPP for GNR family

2025-02-28 Thread Ubuntu Kernel Bot

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


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


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


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

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

Title:
  optimized default EPP for GNR family

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

Bug description:
  [ Impact ]

   * Update EPP default for balance_performance to 32. This will give
 better performance out of box using Intel P-State powersave governor
 while still offering power savings compared to performance governor.
   * Improvement of ~10% on perf per/watt.

  [ Fix ]

   * Clean cherry-pick from upstream:
 00e2c199cb378 cpufreq: intel_pstate: Update Balance-performance EPP for 
Granite Rapids

  [ Test Plan ]

   * Compiled and tested by intel.

  [ Where problems could occur ]

   * Performance or powersaving regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097554/+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 2097389] Re: VM boots slowly with large-BAR GPU Passthrough due to pci/probe.c redundancy

2025-02-28 Thread Ubuntu Kernel Bot

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


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


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


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

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

Title:
  VM boots slowly with large-BAR GPU Passthrough due to pci/probe.c
  redundancy

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

Bug description:
  SRU Justification:

  [ Impact ]

  VM guests that have large-BAR GPUs passed through to them will take 2x
  as long to initialize all device BARs without this patch

  [ Test Plan ]

  I verified that this patch applies cleanly to the Noble kernel
  and resolves the bug on DGX H100 and DGX A100. I observed no regressions.
  This can be verified on any machine with a sufficiently large BAR and the
  capability to pass through to a VM using vfio.

  To verify no regressions, I applied this patch to the guest kernel, then
  rebooted and confirmed that:
  1. The measured PCI initialization time on boot was ~50% of the unmodified 
kernel
  2. Relevant parts of /proc/iomem mappings, the PCI init section of dmesg 
output, and lspci -vv output remained unchanged between the system with the 
unmodified kernel and with the patched kernel
  3. The Nvidia driver still successfully loaded and was shown via nvidia-smi 
after the patch was applied

  [ Fix ]

  Roughly half of the time consuming device configuration options invoked during
  the PCI probe function can be eliminated by rearranging the memory and I/O 
disable/enable
  calls such that they only occur per-device rather than per-BAR. This is what 
the upstream
  patch does, and it results in roughly half the excess initialization time 
being eliminated
  reliably during VM boot.

  [ Where problems could occur ]

  I do not expect any regressions. The only callers of ABIs changed by
  this patch are also adjusted within this patch, and the functional
  change only removes entirely redundant calls to disable/enable PCI
  memory/IO.

  [ Additional Context ]

  Upstream patch: 
https://lore.kernel.org/all/20250111210652.402845-1-alex.william...@redhat.com/
  Upstream bug report: 
https://lore.kernel.org/all/cahta-uyp07fgm6t1ozqkqadsa5jrzo0reneyzgqzub4mdrr...@mail.gmail.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097389/+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 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

2025-02-28 Thread Ubuntu Kernel Bot

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


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


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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2098890] Re: package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries:
libcrypto.so.1.0.0: cannot open shared object file: No such file or
directory

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

Title:
  package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 127

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  El error se produjo después de una actualización fallida por falta de
  espacio en el disco.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-205-generic 5.4.0-205.225
  ProcVersionSignature: Ubuntu 5.4.0-204.224-generic 5.4.284
  Uname: Linux 5.4.0-204-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1815 F pulseaudio
   /dev/snd/controlC1:  usuario1815 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Feb 19 20:10:35 2025
  ErrorMessage: installed linux-image-5.4.0-205-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=8c591f82-46ce-4c78-bbdd-029a6d5b9abc
  InstallationDate: Installed on 2014-05-22 (3926 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA SATELLITE Z30-A
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-204-generic 
root=UUID=4ec37c46-0e2b-45a0-87e3-3ccd838a3db4 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.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.17
  SourcePackage: linux-signed
  Title: package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.30
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.30:bd02/05/2014:svnTOSHIBA:pnSATELLITEZ30-A:pvrPT248E-00800FCE:rvnTOSHIBA:rnSATELLITEZ30-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-A
  dmi.product.sku: PT248E
  dmi.product.version: PT248E-00800FCE
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2098890/+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 2098580] Re: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]

Let's see if we can determine when this started.

Could you please try the following kernel and let me know if the issue
exists?

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

For reference:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

For security best practices, please see: "Verifying mainline build
binaries"

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

Title:
  Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]

Status in linux package in Ubuntu:
  New

Bug description:
  On two systems running Ubuntu 25.04 amd64 I see random crashes.

  KDE freezing. The mounts set to read-only. And fan spinning at max
  speed.

  See appended journal.txt for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098580/+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 2098668] Re: nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

Another workaround would be to disable the offending services:

"sudo snapctl stop --disable firmware-updater.firmware-notifier"
"sudo systemctl disable fwupd-refresh"
"sudo systemctl disable fwupd"

Beware that this disables firmware updates for your hardware, though.
Also beware that I did not test this (yet). Your mileage may vary.

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

Title:
  nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

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

Bug description:
  I was reviewing logs while trying to find evidence of an unrelated
  issue (which turned out to be related, it is a nouveau driver crashing
  on DPCD requests, see the comments below) and found that fwupd.service
  fails to start due to a timeout. The logs below contain only the
  failure, I could not find the startup:

  2025-02-16T00:03:39.859015+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:03:39.859180+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:03:39.859258+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.456s CPU time.

  Here is another, probably incomplete instance. I attached the complete
  section of the log so maybe you can glean out what I missed. Here it
  is:

  2025-02-16T00:03:58.952797+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Starting fwupd.service - Firmware update daemon...
  2025-02-16T00:06:59.072774+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: start operation timed out. Terminating.
  2025-02-16T00:09:59.072836+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: State 'stop-sigterm' timed out. Killing.
  2025-02-16T00:09:59.073019+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Killing process 1192141 (fwupd) with signal S
  2025-02-16T00:10:48.774997+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:10:48.775165+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:10:48.775230+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.020s CPU time.

  There is another service called snap.firmware-updater.firmware-
  notifier.service that fails to start and is repeatedly trying to
  restart. My gut says it fails because it needs fwupd.service to be
  running. Here are some of the logs:

  2025-02-16T00:00:11.588457+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[2477]: Started snap.firmware-updater.firmware-notifier.service - 
Service for snap application firmware-updater.firmware-notifier.
  2025-02-16T00:00:11.669261+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
kernel: audit: type=1400 audit(1739660411.667:15250): apparmor="DENIED" 
operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" 
name="/proc/sys/vm/max_map_count" pid=1191308 comm="firmware-notifi" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  2025-02-16T00:00:11.672348+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
dbus-daemon[1184]: [system] Activating via systemd: service 
name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.19925' 
(uid=1000 pid=1191308 comm="/snap/firmware-updater/167/bin/firmware-notifier" 
label="snap.firmware-updater.firmware-notifier (enforce)")
  2025-02-16T00:00:36.677585+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: Unhandled exception:
  2025-02-16T00:00:36.677686+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms)
  2025-02-16T00:00:36.677704+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #0  DBusClient._callMethod 
(package:dbus/src/dbus_client.dart:1130)
  2025-02-16T00:00:36.677717+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
  2025-02-16T00:00:36.677730+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #1  DBusClient.callMethod 
(package:dbus/src/dbus_client.dart:621)
  2025-02-16T00:00:36.677743+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
  2025-02-16T00:00:36.677754+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #2  
DBusRemoteObject.getAllProperties (package:dbus/src/dbus_remote_object.dart:142)
  2025-02-16T00:00:36.6

[Kernel-packages] [Bug 2098375] Re: ZFS pool randomly encounters error condition and hangs

Let's see if we can determine when this started.

Could you please try the following kernel and let me know if the issue
exists?

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

For reference:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

For security best practices, please see: "Verifying mainline build
binaries"

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

Title:
  ZFS pool randomly encounters error condition and hangs

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 22.04 to 24.04 the ZFS pool becomes
  unstable and any operations on the mounted volumes hang indefinitely
  until the system is restarted. The mounted ZFS volumes are used for
  MariaDB. The pool is of a single entire drive.

  # apt list --installed|grep -i zfs

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  libzfs4linux/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed,automatic]
  zfs-initramfs/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed]
  zfs-zed/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed,automatic]
  zfsutils-linux/noble-updates,now 2.2.2-0ubuntu9.1 amd64 [installed]

  
  # zpool status
pool: db
   state: ONLINE
scan: scrub repaired 0B in 03:41:14 with 0 errors on Sun Feb  9 04:05:15 
2025
  config:

NAMESTATE READ WRITE CKSUM
db  ONLINE   0 0 0
  nvme0n1   ONLINE   0 0 0

  errors: No known data errors

  
  # zfs list
  NAME   USED  AVAIL  REFER  MOUNTPOINT
  db1.21T   479G   228K  /db
  db/mysql  1.01T   479G  1.01T  /db/mysql
  db/mysql-log   204G   479G   204G  /db/mysql-log

  # zfs get all db
  NAME  PROPERTY  VALUE  SOURCE
  dbtype  filesystem -
  dbcreation  Sat Jun  3 13:41 2023  -
  dbused  1.21T  -
  dbavailable 479G   -
  dbreferenced228K   -
  dbcompressratio 2.33x  -
  dbmounted   yes-
  dbquota none   default
  dbreservation   none   default
  dbrecordsize128K   default
  dbmountpoint/dbdefault
  dbsharenfs  offdefault
  dbchecksum  on default
  dbcompression   lz4local
  dbatime offlocal
  dbdevices   on default
  dbexec  on default
  dbsetuidon default
  dbreadonly  offdefault
  dbzoned offdefault
  dbsnapdir   hidden default
  dbaclmode   discarddefault
  dbaclinheritrestricted default
  dbcreatetxg 1  -
  dbcanmount  on default
  dbxattr on default
  dbcopies1  default
  dbversion   5  -
  dbutf8only  off-
  dbnormalization none   -
  dbcasesensitivity   sensitive  -
  dbvscan offdefault
  dbnbmandoffdefault
  dbsharesmb  offdefault
  dbrefquota  none   default
  dbrefreservationnone   default
  dbguid  13462119194566498061   -
  dbprimarycache  alldefault
  dbsecondarycachealldefault
  dbusedbysnapshots   0B -
  dbusedbydataset 228K   -
  dbusedbychildren1.21T  -
  dbusedbyrefreservation  0B -
  dblogbias   throughput local
  dbobjsetid  54 -
  dbdedup offdefault
  dbmlslabel  none   default
  dbsync  standard   default
  dbdnodesize legacy default
  dbrefcompressratio  2.10x  -
  dbwritten   228K   -
  dblogicalused   2.82T  -
  dblogicalreferenced 210K   -
  dbvolmode

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

2025-02-28 Thread xiaochun Lee

OK，We'll do it!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2098457] Re: Enable AMD ACP70/ACP71 and relevant soundwire support

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

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

Title:
  Enable AMD ACP70/ACP71 and relevant soundwire support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  This introduces support for the ACP70/ACP71 audio co-processors, as
  well as soundwire related integration. The main patchesets are:

  1. [PATCH V3 00/25] ASoC: amd: Add support for ACP7.0 & ACP7.1 platforms[1]
  2. [PATCH V4 0/6] soundwire: amd: code improvements and new platform 
support[2]

  As well as their dependent patches.

  [1] 
https://lore.kernel.org/alsa-devel/173946420611.270661.6294707599627839150.b4...@kernel.org/T/#mc726945cf0e97d7cbbc5a9dda3b33d42779ed3af
  [2] 
https://lore.kernel.org/alsa-devel/173920500520.65690.5365981028345549480.b4...@kernel.org/T/#m2d7a2b3b128813a2ee5fc45c8d31982c5f2d709c

  [ Test ]

  1. Test record/playback of built-in mic and speakers by, say, recording and 
playing the speaker test sound in the gnome control center.
  2. Connect to headphones and test playback and recording.
  3. Suspend the machine and test 1. and 2. again.
  4. Test the above 3 on a ACP63 machine.

  [ Where the problems could occur ]

  Most of the codes are AMD-specific. However, those patches contain
  refactors to the existing ACP63 codes. Errors in those refactoring may
  impact existing ACP63 platforms.

  The patch "[PATCH V3 19/25] ASoC: amd: ps: update file description and
  copyright year"[3] didn't get backported, because it conflicted due to
  the recent MODULE_IMPORT_NS() API change in cdd30ebb1b9f (module:
  Convert symbol namespace to string literal). This patch only change
  the module description and doesn't have real functional impact, so was
  not pulled in.

  [3] https://lore.kernel.org/alsa-
  
devel/173920500520.65690.5365981028345549480.b4...@kernel.org/T/#m39948f8b75ae43055b55a0ccc4dbec66de1eb269

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2098457/+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 2098890] Re: package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127

I don't think /etc/grub.d/bin/grubcfg_proxy is provided by an Ubuntu
package or it is ancient. Where does it come from?

$ dpkg -S /etc/grub.d/bin/grubcfg_proxy


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

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

Title:
  package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub
  exited with return code 127

Status in linux-signed package in Ubuntu:
  Incomplete

Bug description:
  El error se produjo después de una actualización fallida por falta de
  espacio en el disco.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-205-generic 5.4.0-205.225
  ProcVersionSignature: Ubuntu 5.4.0-204.224-generic 5.4.284
  Uname: Linux 5.4.0-204-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1815 F pulseaudio
   /dev/snd/controlC1:  usuario1815 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Feb 19 20:10:35 2025
  ErrorMessage: installed linux-image-5.4.0-205-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=8c591f82-46ce-4c78-bbdd-029a6d5b9abc
  InstallationDate: Installed on 2014-05-22 (3926 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA SATELLITE Z30-A
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-204-generic 
root=UUID=4ec37c46-0e2b-45a0-87e3-3ccd838a3db4 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.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.17
  SourcePackage: linux-signed
  Title: package linux-image-5.4.0-205-generic 5.4.0-205.225 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/05/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.30
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-A
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.30:bd02/05/2014:svnTOSHIBA:pnSATELLITEZ30-A:pvrPT248E-00800FCE:rvnTOSHIBA:rnSATELLITEZ30-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-A
  dmi.product.sku: PT248E
  dmi.product.version: PT248E-00800FCE
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2098890/+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 2098935] Re: The ice driver may rarely return incorrect statistics counter values

2025-02-28 Thread Masakazu Asama

Sorry, I forgot to include very important information about the environment.
This patch is intended for the following environment and has been tested in the 
same setup.

$ cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=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/2098935

Title:
  The ice driver may rarely return incorrect statistics counter values

Status in linux package in Ubuntu:
  New

Bug description:
  We have observed a very rare issue in Intel E810 environments where
  SNMP-retrieved TX/RX counter values are sometimes nearly twice the
  actual values.

  Upon investigation, we identified a problem in the process that
  updates the transmit and receive ring statistics in the ice driver.
  This issue occurs when the counter update process is executed
  simultaneously on different CPU cores.

  We have attached a patch to fix this issue.

  The function ice_update_vsi_ring_stats takes a pointer to a struct
  ice_vsi as an argument. This structure is allocated on the heap and
  shared across all CPU cores. The function resets the counter values to
  zero and then accumulates the values from each ring of the NIC.

  However, since struct ice_vsi is shared across all CPU cores, the following 
race condition can occur when ice_update_vsi_ring_stats is executed 
simultaneously on different CPUs:
1.  Multiple CPU cores reset the counter values in struct ice_vsi 
to zero at the same time.
2.  Each CPU core independently increments the counter values.

  As a result, the counter values may be updated to a higher-than-actual
  value.

  The attached patch modifies the implementation to store the counter
  values on the stack, initialize them to zero, increment them with the
  values from each ring, and finally update struct ice_vsi. By avoiding
  the use of shared data for intermediate calculations, this fix
  prevents the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098935/+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 2098726] Re: Cannot set alias for USB NIC RTL8153

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 2098726

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that and change the
bug status to '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/2098726

Title:
  Cannot set alias for USB NIC RTL8153

Status in linux package in Ubuntu:
  New

Bug description:
  Linux Mint 20.3, based on Ubuntu 20.04

  $ uname -a
  Linux mintbook 5.15.0-131-generic #141~20.04.1-Ubuntu SMP Thu Jan 16 18:38:51 
UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

  I have an ASUS notebook and it has no RJ45 socket. I use USB Gigabit
  adapter based on RTL8153. So far it worked OK but I have found today
  that I cannot configure alias with ifconfig. Try to configure alias IP
  address with ifconfig changes default interface. It looks like a bug
  in the RTL8153 driver.

  $ ethtool -i enx00e04c68002f
  driver: r8152
  version: v1.12.13
  firmware-version: rtl8153b-2 v1 10/23/19
  expansion-rom-version:
  bus-info: usb-:00:14.0-2
  supports-statistics: yes
  supports-test: no
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: no

  $ lsusb | grep 8153
  Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter

  Steps to replicate:

  1) Connect USB adapter to a LAN, I assume I received IP address 192.168.1.11 
from DHCP server.
  2) check with ifconfig what is IP address on interface enx00e04c68002f
  3) define alias, 'sudo ifconfig enx00e04c68002f:33 192.168.33.11'
  4) check with ifconfig the result

  I see that there is no new interface enx00e04c68002f:33 and that IP
  address on interface enx00e04c68002f was changed to 192.168.33.11.
  That is a bug!

  Expected behavior:

  Interface enx00e04c68002f will keep IP address assigned from DHCP server, 
like 192.168.1.11
  New interface enx00e04c68002f:33 will be added with IP address 192.168.33.11

  This report is for an older kernel and older Ubuntu distribution. I
  assume the bug is still in the newer kernel, this has to be
  retested...

  ---

  When I use this method on my WiFi interface (based on rtl8821ce), IP
  alias works as expected. This points to an issue with r8152 driver...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098726/+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 2097801] Re: Problems with kernel image 6.8.0-53

Let's see if we can narrow down where this happened.

I've prepared a first test kernel for you.

https://people.canonical.com/~tswhison/bugs/2097801/0001-166609c-headers.tar.gz
https://people.canonical.com/~tswhison/bugs/2097801/0001-166609c.tar.gz

Please try it out and let me know if you still see 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/2097801

Title:
  Problems with kernel image 6.8.0-53

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the Linux kernel image to 6.8.0-53 (Ubuntu 24.04) from 
6.8.0-52, Network Manager, Bluetooth, and other services no longer load at 
startup and disappear from the menu.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:glion  3071 F pipewire
   /dev/snd/controlC0:  glion  3076 F wireplumber
   /dev/snd/controlC1:  glion  3071 F pipewire
glion  3076 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2025-01-03 (40 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  IwConfig:
   lono wireless extensions.
   
   wlp2s0f0  no wireless extensions.
  MachineType: Dell Inc. Precision 5690
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 simpledrmdrmfb
   1 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-52-generic 
root=UUID=73f10a81-c28b-4e90-9e89-3a34c3c73fa1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  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.8.0-52-generic N/A
   linux-backports-modules-6.8.0-52-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.9
  Tags: noble
  Uname: Linux 6.8.0-52-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/15/2024
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 02RYDD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.17
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd12/15/2024:br1.9:efr1.17:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn02RYDD:rvrA00:cvnDellInc.:ct10:cvr:sku0CC8:
  dmi.product.family: Precision
  dmi.product.name: Precision 5690
  dmi.product.sku: 0CC8
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097801/+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 2098961] [NEW] Severe network performance issues with Kernel 6.8.0-53 and 6.11.0-17 (Xubuntu) on Proxmox 8.3 (bnxt_en + VirtIO)

2025-02-28 Thread Markus Fohrer

Public bug reported:

Since upgrading to Kernel 6.8.0-53 and 6.11.0-17 on Xubuntu 22.04/24.04
VMs, we are experiencing extremely low network speeds (100-200 KB/s)
when running these VMs in a Proxmox 8.3.4 cluster with AMD CPUs and
Broadcom NetXtreme-E network adapters (bnxt_en driver).

With Kernel 6.8.0-31 inside the same Xubuntu VM, everything works as 
expected.
Other VMs (Debian, Ubuntu Server) running on the same Proxmox cluster are 
not affected.
The same Xubuntu VM, when moved to a different Proxmox cluster (Intel CPUs, 
Intel NICs, ZFS storage), runs fine with Kernel 6.8.0-53 and 6.11.0-17.
The issue only affects Xubuntu VMs running on a Proxmox 8.3.4 cluster with 
AMD CPUs, Broadcom NICs, and Ceph storage.

Expected behavior:

Network performance should be normal (10 Gbps or more) without issues.
Actual behavior:

Xubuntu VMs with Kernel 6.8.0-53 and 6.11.0-17 experience extremely slow 
network speeds (100-200 KB/s).
iperf3 tests show very low bandwidth (5-10 Mbps).
Disabling GSO, TSO, and GRO (ethtool -K ens18 tso off gso off gro off) did 
not improve performance.
Other VMs (Debian, Ubuntu Server) on the same cluster do not have this 
issue.
The issue disappears when booting Kernel 6.8.0-31 inside the same Xubuntu 
VM.

Steps to reproduce:

Proxmox environment:
Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPU + Broadcom NetXtreme-E BCM57504 (bnxt_en driver) + Ceph storage
VMs running Xubuntu 22.04 or 24.04 with VirtIO network (virtio-net)

Inside the Xubuntu VM:
Install and boot Kernel 6.8.0-53 or Kernel 6.11.0-17
Test network performance:

wget -O /dev/null http://speed.hetzner.de/1GB.bin
iperf3 -c  -P 4

→ Speed is extremely slow (~200 KB/s - 5 Mbps).

Reboot the VM with Kernel 6.8.0-31

sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 
6.8.0-31-generic"
sudo reboot

→ Network performance returns to normal (10 Gbps+).

Hardware & environment details:
Proxmox cluster (affected environment):

Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
AMD CPUs
Broadcom NetXtreme-E BCM57504 25G SFP28 Ethernet (bnxt_en driver)
Ceph storage backend
VMs use VirtIO network adapter (virtio-net)
Bridging on Broadcom NICs

Working cluster (same Xubuntu VM, no issue):

Proxmox 8.3.4 (Kernel 6.8.12-8-pve)
Intel CPUs
Intel I350 NICs (igb driver)
ZFS storage backend
Same Xubuntu VM works fine with Kernel 6.8.0-53 and 6.11.0-17

Debugging information:

Xubuntu VM Kernel versions (affected):

uname -r
6.8.0-53-generic
6.11.0-17-generic

Broadcom firmware version (Proxmox host):

ethtool -i enp67s0f0np0 | grep firmware
firmware-version: 229.0.154.0/pkg 229.1.123.0

dmesg output related to bnxt_en NICs (Proxmox host):

dmesg | grep bnxt
[2.324347] bnxt_en :c5:00.0 (unnamed net_device) (uninitialized): 
Device requests max timeout of 60 seconds, may trigger hung task watchdog
[2.364280] bnxt_en :c5:00.0 eth0: Broadcom BCM57504 NetXtreme-E 
10Gb/25Gb/50Gb/100Gb/200Gb Ethernet found at mem b703, node addr 
14:23:f2:5d:18:14
...

→ No critical errors, but timeout warnings and performance degradation.
Possible causes:

🔹 Regression in virtio-net or bnxt_en driver in Kernel 6.8.0-53 and 6.11.0-17
🔹 Interaction issue between virtio-net and bnxt_en on AMD + Broadcom hardware
🔹 Proxmox bridge settings on Broadcom NICs interacting with Xubuntu's Kernel 
6.8.0-53 and 6.11.0-17
Next Steps & Further Tests

Since this is a production system with 200+ running VMs, we will conduct
further tests once we schedule maintenance.

Planned additional tests:

Test a fresh Ubuntu Server VM with Kernel 6.8.0-53 and 6.11.0-17 (to rule 
out Xubuntu-specific issues).
Verify bnxt_en and virtio-net driver versions in Kernel 6.8.0-31 vs. 
6.8.0-53 and 6.11.0-17.
Check IRQ assignments and CPU affinity for VirtIO network interfaces.

📌 If this issue is already reported, please link to the relevant bug report.
📌 Otherwise, we are happy to provide further debugging information.
Summary:

Xubuntu VMs running Kernel 6.8.0-53 and 6.11.0-17 on a Proxmox 8.3.4 
cluster with AMD CPUs + Broadcom NICs suffer from extreme network slowdowns 
(~200 KB/s).
Booting the same VM with Kernel 6.8.0-31 restores full performance.
Same Kernels work fine on Intel-based Proxmox clusters.
Disabling TSO, GSO, GRO does NOT fix the issue.
Likely a regression in virtio-net or bnxt_en.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-53-generic 6.8.0-53.55
ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
Uname: Linux 6.8.0-53-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:sysadmin   1219 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Feb 20 11:52:51 2025
InstallationDate: Installed on 2025-02-20 (0 days ago)
InstallationMedia: Xubuntu 24.04.1 LTS "No

[Kernel-packages] [Bug 2098732] Re: BUG: scheduling while atomic: kubelet/2388/0x00000002

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 2098732

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that and change the
bug status to 'Confirmed'.

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

Title:
  BUG: scheduling while atomic: kubelet/2388/0x0002

Status in linux-meta-realtime package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 22.04.5 LTS
  Release:22.04
  Kernel :5.15.0-1077-realtime

  Server Model :  Dell PowerEdge R660xs
  CPU Info :  Intel(R) Xeon(R) Gold 6426Y

  1. Symptom : "BUG: scheduling while atomic" bug occurred.
  2. Frequency : about once an hour
  3. Reproduction Scenario : Install RT kernel (5.15.0-1077-realtime) and 
kubernetes with containerd, calico CNI.
  Issue was not happend on generic kernel 5.15.0-131-generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-realtime/+bug/2098732/+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 2099280] [NEW] apply NVIDIA patches Feb 20, 2025

2025-02-28 Thread Brad Griffis

Public bug reported:

apply NVIDIA patches Feb 20, 2025

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

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

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

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

Title:
  apply NVIDIA patches Feb 20, 2025

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

Bug description:
  apply NVIDIA patches Feb 20, 2025

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2099280/+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 2096624] Re: [SRU] Add Intel Touch Host Controller drivers

** Changed in: linux-oem (Ubuntu Noble)
 Assignee: (unassigned) => Thibault Ferrante (thibf)

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

Title:
  [SRU] Add Intel Touch Host Controller drivers

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  Invalid
Status in linux-oem source package in Noble:
  In Progress
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  Invalid
Status in linux-oem source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  In Progress
Status in linux-oem source package in Plucky:
  Invalid
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [Impact]
  The new touchscreen on Intel LNL is lack of driver support.

  00:10.0 Digitizer Pen [0901]: Intel Corporation Device [8086:a848]
  (rev 10)

  [Fix]
  Enable Intel THC driver to support it.
  [4.122639] input: quicki2c-hid 27C6:012D Touchscreen as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input12
  [4.122704] input: quicki2c-hid 27C6:012D as 
/devices/pci:00/:00:10.0/0001:27C6:012D.0003/input/input13

  [Test]
  Tested on hardware, multi-touch works fine on Wacom and Goodix touchscreens.

  [Where problems could occur]
  It introduces a brand new driver, may break hid functions.

  Because this is a new feature driver, SRU for
  oracular/plucky/oem-6.11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2096624/+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 2089411] Re: python perf module missing in realtime kernel

2025-02-28 Thread Wesley Hershberger

All set, thanks.

```
wesley@oracular2:~$ uname -a
Linux oracular2 6.11.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Mon Feb 17 
15:51:31 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
wesley@oracular2:~$ python3 -c 'import perf; [print(c) for c in perf.cpu_map()]'
0
```

** Tags removed: verification-failed-oracular-linux
** Tags added: verification-done-oracular-linux

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

Title:
  python perf module missing in realtime kernel

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

Bug description:
  [Impact]

  ubuntu@ubuntu-plucky:~$ python3 -c 'import perf; [print(c) for c in 
perf.cpu_map()]'
  Traceback (most recent call last):
    File "", line 1, in 
    File "/usr/lib/python3/dist-packages/perf/__init__.py", line 24, in 
  raise KernelNotFoundError()
  perf.KernelNotFoundError: WARNING: python perf module not found for kernel 
6.12.0-4-generic

  You may need to install the following packages for this specific kernel:
    linux-tools-6.12.0-4-generic-generic
  You may also want to install of the following package to keep up to date:
    linux-tools-generic

  This works only with the main generic kernel but not with any of the
  derivatives. Packaging is broken and the perf python modules is
  looking in the wrong place for the library.

  [Test Plan]

  Run:
  $ python3 -c 'import perf; [print(c) for c in perf.cpu_map()]'
  $ perf

  The above must not result in errors.

  [Where Problems Could Occur]

  Potential issues when using the perf python module or any
  scripts/binaries provided by the linux-tools packages.

  [Original Description]

  Issue is related to Bug #2051560
  In using tuned profile realtime-virtual-host under the realtime kernel, the 
operating system would lose network connection. Further viewing of the tuned 
logs pointed to the following error:

  ERRORtuned.units.manager: WARNING: python perf module not found
  for kernel 6.8.1-1011-realtime

  Researching online Bug #2051560 was discovered. However, it looks as
  if the realtime kernel was not listed as fixed to include the perf
  Python module that affects tuned.

  Server info:

  uname -a:

  Linux 6.8.1-1011-realtime #11-Ubuntu SMP PREEMPT_RT Tue Oct 8 17:19:16 UTC 
2024 x86_64 x86_64 x86_64 GNU/Linux
  ---

  lsb_release -crid:

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 24.04.1 LTS
  Release: 24.04
  Codename: noble

  ---

  apt policy linux-image-6.8.1-1011-realtime:

  linux-image-6.8.1-1011-realtime:
    Installed: 6.8.1-1011.11
    Candidate: 6.8.1-1011.11
    Version table:
   *** 6.8.1-1011.11 500
  500 https://esm.ubuntu.com/realtime/ubuntu noble/main amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Realtime kernel was installed via Ubuntu Pro subscription.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089411/+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 2098972] Re: Enable Large Language Model (LLM) workloads using Intel NPU

** Description changed:

  [ Impact ]
  
   * Enable larger LLM using intel NPU.
-  * For Noble, only 37XX generation is covered as the others are not supported.
  
  [ Fix ]
  
   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range
  
  [ Test Plan ]
  
   * Built and boot tested
  
  [ Where problems could occur ]
  
   * Memory management issue when using intel NPU.

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

Title:
  Enable Large Language Model (LLM) workloads using Intel NPU

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  New

Bug description:
  [ Impact ]

   * Enable larger LLM using intel NPU.

  [ Fix ]

   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range

  [ Test Plan ]

   * Built and boot tested

  [ Where problems could occur ]

   * Memory management issue when using intel NPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098972/+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 2098972] Re: Enable Large Language Model (LLM) workloads using Intel NPU

** Description changed:

  [ Impact ]
  
-  * Enable larger LLM using intel NPU.
+  * Enable larger LLM using intel NPU.
+  * For noble, only 37XX generation is covered as the others are not supported.
  
  [ Fix ]
  
-  * Upstream commit:
+  * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range
  
  [ Test Plan ]
  
-  * Built and boot tested
+  * Built and boot tested
  
  [ Where problems could occur ]
  
-  * Memory management issue when using intel NPU
+  * Memory management issue when using intel NPU.

** Description changed:

  [ Impact ]
  
   * Enable larger LLM using intel NPU.
-  * For noble, only 37XX generation is covered as the others are not supported.
+  * For Noble, only 37XX generation is covered as the others are not supported.
  
  [ Fix ]
  
   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range
  
  [ Test Plan ]
  
   * Built and boot tested
  
  [ Where problems could occur ]
  
   * Memory management issue when using intel NPU.

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

Title:
  Enable Large Language Model (LLM) workloads using Intel NPU

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  New

Bug description:
  [ Impact ]

   * Enable larger LLM using intel NPU.
   * For Noble, only 37XX generation is covered as the others are not supported.

  [ Fix ]

   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range

  [ Test Plan ]

   * Built and boot tested

  [ Where problems could occur ]

   * Memory management issue when using intel NPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098972/+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 2097543] Re: [25.04 FEAT] pkey: add support for Secure Execution retrieved protected keys

2025-02-28 Thread Frank Heimes

Thank you for the update Massimiliano.
I think that allows me to update the status to Fix Committed.

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

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

Title:
  [25.04 FEAT] pkey: add support for Secure Execution retrieved
  protected keys

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Feature Description:

  Let the kernel pkey module generate keys represented by identifiers of
  secure execution retrievable keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2097543/+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 2097389] Re: VM boots slowly with large-BAR GPU Passthrough due to pci/probe.c redundancy

2025-02-28 Thread Mitchell Augustin

-proposed kernel verified to fix bug on DGX H100

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

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

Title:
  VM boots slowly with large-BAR GPU Passthrough due to pci/probe.c
  redundancy

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

Bug description:
  SRU Justification:

  [ Impact ]

  VM guests that have large-BAR GPUs passed through to them will take 2x
  as long to initialize all device BARs without this patch

  [ Test Plan ]

  I verified that this patch applies cleanly to the Noble kernel
  and resolves the bug on DGX H100 and DGX A100. I observed no regressions.
  This can be verified on any machine with a sufficiently large BAR and the
  capability to pass through to a VM using vfio.

  To verify no regressions, I applied this patch to the guest kernel, then
  rebooted and confirmed that:
  1. The measured PCI initialization time on boot was ~50% of the unmodified 
kernel
  2. Relevant parts of /proc/iomem mappings, the PCI init section of dmesg 
output, and lspci -vv output remained unchanged between the system with the 
unmodified kernel and with the patched kernel
  3. The Nvidia driver still successfully loaded and was shown via nvidia-smi 
after the patch was applied

  [ Fix ]

  Roughly half of the time consuming device configuration options invoked during
  the PCI probe function can be eliminated by rearranging the memory and I/O 
disable/enable
  calls such that they only occur per-device rather than per-BAR. This is what 
the upstream
  patch does, and it results in roughly half the excess initialization time 
being eliminated
  reliably during VM boot.

  [ Where problems could occur ]

  I do not expect any regressions. The only callers of ABIs changed by
  this patch are also adjusted within this patch, and the functional
  change only removes entirely redundant calls to disable/enable PCI
  memory/IO.

  [ Additional Context ]

  Upstream patch: 
https://lore.kernel.org/all/20250111210652.402845-1-alex.william...@redhat.com/
  Upstream bug report: 
https://lore.kernel.org/all/cahta-uyp07fgm6t1ozqkqadsa5jrzo0reneyzgqzub4mdrr...@mail.gmail.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097389/+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 2098668] Re: nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

I no longer suspect that this bug can cause Ubuntu to crash or behave
abnormally. I have the nouveau driver disabled for now but today I again
experienced this bug. The kernel thread name was
"kworker/u32:2+events_unbound". Time to file another bug.

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

Title:
  nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

Status in fwupd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I was reviewing logs while trying to find evidence of an unrelated
  issue (which turned out to be related, it is a nouveau driver crashing
  on DPCD requests, see the comments below) and found that fwupd.service
  fails to start due to a timeout. The logs below contain only the
  failure, I could not find the startup:

  2025-02-16T00:03:39.859015+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:03:39.859180+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:03:39.859258+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.456s CPU time.

  Here is another, probably incomplete instance. I attached the complete
  section of the log so maybe you can glean out what I missed. Here it
  is:

  2025-02-16T00:03:58.952797+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Starting fwupd.service - Firmware update daemon...
  2025-02-16T00:06:59.072774+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: start operation timed out. Terminating.
  2025-02-16T00:09:59.072836+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: State 'stop-sigterm' timed out. Killing.
  2025-02-16T00:09:59.073019+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Killing process 1192141 (fwupd) with signal S
  2025-02-16T00:10:48.774997+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:10:48.775165+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:10:48.775230+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.020s CPU time.

  There is another service called snap.firmware-updater.firmware-
  notifier.service that fails to start and is repeatedly trying to
  restart. My gut says it fails because it needs fwupd.service to be
  running. Here are some of the logs:

  2025-02-16T00:00:11.588457+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[2477]: Started snap.firmware-updater.firmware-notifier.service - 
Service for snap application firmware-updater.firmware-notifier.
  2025-02-16T00:00:11.669261+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
kernel: audit: type=1400 audit(1739660411.667:15250): apparmor="DENIED" 
operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" 
name="/proc/sys/vm/max_map_count" pid=1191308 comm="firmware-notifi" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  2025-02-16T00:00:11.672348+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
dbus-daemon[1184]: [system] Activating via systemd: service 
name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.19925' 
(uid=1000 pid=1191308 comm="/snap/firmware-updater/167/bin/firmware-notifier" 
label="snap.firmware-updater.firmware-notifier (enforce)")
  2025-02-16T00:00:36.677585+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: Unhandled exception:
  2025-02-16T00:00:36.677686+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms)
  2025-02-16T00:00:36.677704+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #0  DBusClient._callMethod 
(package:dbus/src/dbus_client.dart:1130)
  2025-02-16T00:00:36.677717+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
  2025-02-16T00:00:36.677730+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #1  DBusClient.callMethod 
(package:dbus/src/dbus_client.dart:621)
  2025-02-16T00:00:36.677743+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
  2025-02-16T00:00:36.677754+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #2  
DBusRemoteObject.getAllProperties (package:dbus/src/dbus_remote_object.dart:142)
  2025-02-16T00:00:36.64+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[11913

[Kernel-packages] [Bug 2098897] Re: Random crash or freeze when using high speed USB 4 devices

I enabled crash dumping and triggered the bug but found no crash dump.
So I now think that the USB subsystem in my computer is busted.

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

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

Title:
  Random crash or freeze when using high speed USB 4 devices

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When connecting a high speed external USB disk (essentially a M.2 NVMe
  disk in a box AXAGON EEM2-SG2), the system either locks up or
  instantly reboots. There is nothing in /var/syslog indicative of what
  exactly happened. The system is stable when not running any of these,
  so it is not a memory problem.

  I tried to look at Crash Dump Recipe
  
(https://wiki.ubuntu.com/Kernel/CrashdumpRecipe?action=show&redirect=KernelTeam%2FCrashdumpRecipe)
  but it looks pretty outdated to me, discussing Ubuntu 14 so I am not
  entirely sure if it is aplicable to my current system. I believe using
  this is necessary as there is nothing on the console when I trigger
  this bug from the console.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-53-generic 6.8.0-53.55
  ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
  Uname: Linux 6.8.0-53-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:jozef  2405 F pipewire
   /dev/snd/controlC1:  jozef  2410 F wireplumber
   /dev/snd/controlC0:  jozef  2410 F wireplumber
   /dev/snd/controlC2:  jozef  2410 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 19 21:46:46 2025
  InstallationDate: Installed on 2024-02-14 (372 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507NU_FA507NU
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic 
root=UUID=ac7c0a1e-2f8d-465c-9ec4-f8861895ec66 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-53-generic N/A
   linux-backports-modules-6.8.0-53-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2025-01-30 (21 days ago)
  dmi.bios.date: 03/15/2023
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FA507NU.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA507NU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507NU.306:bd03/15/2023:br5.24:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507NU_FA507NU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507NU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A15
  dmi.product.name: ASUS TUF Gaming A15 FA507NU_FA507NU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098897/+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 2098979] [NEW] [SRU] Add amdnpu firmware

Public bug reported:

OEM-6.14 and mainline 6.14 kernel include AMD XDNA NPU kernel module.
Without matching NPU firmware the kernel will show an error about
failing to load on many platforms.  This firmware should be SRU'ed into
Noble linux-firmware package to prevent this problem.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=52a3bca7

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

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

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

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

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

Title:
  [SRU] Add amdnpu firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Noble:
  New

Bug description:
  OEM-6.14 and mainline 6.14 kernel include AMD XDNA NPU kernel module.
  Without matching NPU firmware the kernel will show an error about
  failing to load on many platforms.  This firmware should be SRU'ed
  into Noble linux-firmware package to prevent this problem.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=52a3bca7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2098979/+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 2098979] Re: [SRU] Add amdnpu firmware

Plucky already rebased to new enough linux-firmware, so only need task
for noble.

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

Title:
  [SRU] Add amdnpu firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Noble:
  New

Bug description:
  OEM-6.14 and mainline 6.14 kernel include AMD XDNA NPU kernel module.
  Without matching NPU firmware the kernel will show an error about
  failing to load on many platforms.  This firmware should be SRU'ed
  into Noble linux-firmware package to prevent this problem.

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/commit/?id=52a3bca7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2098979/+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 2098534] Re: azure: backport "netfs: Fix missing xas_retry() calls in xarray iteration"

2025-02-28 Thread Vinicius Peixoto

** Description changed:

  [Impact]
  
  Microsoft has asked us to backport commit 7e043a80b5da ("netfs: Fix
  missing xas_retry() calls in xarray iteration") to the 5.15 Azure
  kernel.
  
  [Fix]
  
  Backported to the J:azure tree.
  
  [Test plan]
  
  Build tested only; Microsoft will test the bug fix.
  
  [Where problems could occur]
  
  Due to the significant delta between the Jammy 5.15 tree and commit
  7e043a80b5da, particularly w.r.t. fs/netfs/read_helper.c, that got split
  into multiple files in 5.17, as well as the change that introduced the
  usage of folios in netfslib, a manual backported was required. The
  changes, however, were relatively simple/self-contained, and as such
  this presents a medium regression risk. Any issues with this patch could
  manifest as either a null pointer dereference in
  netfs_rreq_unlock/netfs_rreq_unmark_after_write, or potentially as a
  hung thread when doing a lot of I/O on an netfs filesystem.
+ 
+ [Other info]
+ SF #00406192

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

Title:
  azure: backport "netfs: Fix missing xas_retry() calls in xarray
  iteration"

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Jammy:
  New

Bug description:
  [Impact]

  Microsoft has asked us to backport commit 7e043a80b5da ("netfs: Fix
  missing xas_retry() calls in xarray iteration") to the 5.15 Azure
  kernel.

  [Fix]

  Backported to the J:azure tree.

  [Test plan]

  Build tested only; Microsoft will test the bug fix.

  [Where problems could occur]

  Due to the significant delta between the Jammy 5.15 tree and commit
  7e043a80b5da, particularly w.r.t. fs/netfs/read_helper.c, that got
  split into multiple files in 5.17, as well as the change that
  introduced the usage of folios in netfslib, a manual backported was
  required. The changes, however, were relatively simple/self-contained,
  and as such this presents a medium regression risk. Any issues with
  this patch could manifest as either a null pointer dereference in
  netfs_rreq_unlock/netfs_rreq_unmark_after_write, or potentially as a
  hung thread when doing a lot of I/O on an netfs filesystem.

  [Other info]
  SF #00406192

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2098534/+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 2098969] Re: Add additional PCI ids for BMG support

Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2025-February/157321.html

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

Title:
  Add additional PCI ids for BMG support

Status in linux package in Ubuntu:
  New
Status in linux source package in Oracular:
  New
Status in linux source package in Plucky:
  New

Bug description:
  [ Impact ]

   * BMG driver not working on latest hardware

  [ Fix ]

   * Merged into linux-next:
  
https://patchwork.freedesktop.org/patch/msgid/20250128162015.3288675-1-shekhar.chau...@intel.com

  Missed the merge window for 6.14.

  [ Test Plan ]

   * Tested by intel

  [ Where problems could occur ]

   * BMG driver misbehaving with other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098969/+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 2098972] Re: Enable Large Language Model (LLM) workloads using Intel NPU

This is a public version of:
- https://bugs.launchpad.net/ubuntu/+bug/2096959 
- https://bugs.launchpad.net/ubuntu/+bug/2096958

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

Title:
  Enable Large Language Model (LLM) workloads using Intel NPU

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  New

Bug description:
  [ Impact ]

   * Enable larger LLM using intel NPU.

  [ Fix ]

   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range

  [ Test Plan ]

   * Built and boot tested

  [ Where problems could occur ]

   * Memory management issue when using intel NPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098972/+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 2095017] Re: SEV-SNP Causes Significant RSA Performance Degradation on Ubuntu 24.04

2025-02-28 Thread Jon Campbell

Hello Fabio,

Just wanted to check to see if after reproducing the behavior you were
able to identify any temporary fixes, or if any fixes are in the
pipeline.

Thanks

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

Title:
  SEV-SNP Causes Significant RSA Performance Degradation on Ubuntu 24.04

Status in linux-aws package in Ubuntu:
  New

Bug description:
  Description

  When SEV-SNP is enabled on Ubuntu 24.04, RSA operations experience a
  significant performance degradation (approximately 66% slower)
  compared to when SEV-SNP is disabled. This appears to be caused by the
  loss of crucial CPU instruction sets when SEV-SNP is enabled. The same
  performance degradation is not observed on Amazon Linux 2023 with SEV-
  SNP enabled.

  Environment

  • OS Version: Ubuntu 24.04.1 LTS (Noble Numbat)
  • Kernel Version: 6.8.0-1018-aws
  • CPU: AMD EPYC 7R13 Processor
  • Instance Type: AWS EC2 (SEV-SNP capable instance)
  • AMI ID: ami-036841078a4b68e14

  Performance Comparisons

  Performance Comparison: SEV-SNP Enabled vs Disabled
  Test Environment
  OS: Ubuntu 24.04.1 LTS (Noble Numbat)
  Kernel: 6.8.0-1018-aws
  Test Command: openssl speed -multi 2 rsa

  Results
  RSA Key Size  SEV-SNP Enabled (sign/s)SEV-SNP Disabled (sign/s)
  Performance Impact
  512 bits  11,365.333,597.3   -66.2%
  1024 bits 4,334.5 12,942.3   -66.5%
  2048 bits 637.5   1,854.3-65.6%
  3072 bits 203.1592.6 -65.7%
  4096 bits 89.4  260.2-65.6%
  7680 bits 9.9   28.7 -65.5%
  15360 bits1.8   5.3  -66.0%

  Analysis
  • SEV-SNP significantly impacts RSA performance, with a consistent decrease 
of about 65-66% across all key sizes.
  ==

  Performance Comparison: SEV-SNP Enabled vs Disabled on Amazon Linux
  2023

  Test Environment
  • OS: Amazon Linux 2023.6.20241212
  • Kernel: 6.1.119-129.201.amzn2023.x86_64
  • Test Command: openssl speed -multi 2 rsa
  • AMI: ami-0b4624933067d393a

  Results
  RSA Key Size  SEV-SNP Enabled (sign/s)SEV-SNP Disabled (sign/s)  
PerformImpact
  512 bits  33,067.835,244.7  
-6.2%
  1024 bits 12,338.713,159.0  
-6.2%
  2048 bits 1,755.9  1,881.4  
-6.7%
  3072 bits 560.0 599.6   
-6.6%
  4096 bits 245.6  262.4  
-6.4%
  7680 bits 27.229.0  
-6.2%
  15360 bits5.0 5.4   
-7.4%

  Analysis
  • The performance impact of SEV-SNP on Amazon Linux 2023 is significantly 
lower compared to the previous Ubuntu test.

  • The decrease in performance is consistently around 6-7% across all RSA key 
sizes.
  • Both SEV-SNP enabled and disabled instances show much higher performance 
compared to the Ubuntu instances in the previous test.

  Comparison with Ubuntu Results

  RSA Key Size  AL2023 Impact   Ubuntu Impact
  512 bits  -6.2%   -66.2%
  1024 bits -6.2%   -66.5%
  2048 bits -6.7%   -65.6%
  3072 bits -6.6%   -65.7%
  4096 bits -6.4%   -65.6%
  7680 bits -6.2%   -65.5%
  15360 bits-7.4%   -66.0%
  ==

  Missing CPU Flags with SEV-SNP Enabled:
  AVX
  AVX2
  VAES
  VPCLMULQDQ
  FMA
  XSAVE
  XSAVEOPT
  XSAVEC
  XGETBV1
  RDPRU

  * Update: FYI Same flags are also missing when we launch a AL2023
  instance with SEV-SNP enabled

  
  Impact on Crypto Subsystem:
  • Loss of optimized implementations:
  sha256-avx2
  sha512-avx2
  sha1-avx2
  polyval-clmulni
  Various VAES-based implementations

  Expected Behavior
  SEV-SNP should maintain access to these CPU instruction sets while providing 
memory encryption and integrity protection, as demonstrated by Amazon Linux 
2023's implementation of SEV-SNP, which shows only a 6-7% performance impact.

  Additional Evidence
  1. The performance impact is consistent across different key sizes
  2. The same hardware and configuration on Amazon Linux 2023 shows only 6-7% 
performance degradation with SEV-SNP enabled
  3. The missing CPU flags directly correlate with the performance degradation 
observed

  Steps to Reproduce
  1. Launch an SEV-SNP capable instance using Ubuntu 24.04 AMI
  2. Enable SEV-SNP
  3. Run openssl speed -multi 2 rsa
  4. Compare results with SEV-SNP disabled instance
  5. Verify CPU flags using cat /proc/cpuinfo

  Supporting Data
  • Com

[Kernel-packages] [Bug 2098668] Re: nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

I don't draw that same conclusion as you.  I feel you have two separate
issues that can cause severe problems.

If accessing the DPCD sysfs file provided by nouveau crashes in a way
that is enough to taint it there is certainly a nouveau bug (the
original one you filed here).

For this particular bug; the most important thing to triage it would be
to try a newer kernel and see if it's been fixed.  If it's been fixed in
a newer kernel then it's a backport effort for the kernel team to bring
that fix back to Ubuntu's kernel.  If it remains an issue in the latest
upstream kernel you should report it to the appropriate upstream bug
tracker:

https://gitlab.freedesktop.org/drm/nouveau

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

Title:
  nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN

Status in fwupd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I was reviewing logs while trying to find evidence of an unrelated
  issue (which turned out to be related, it is a nouveau driver crashing
  on DPCD requests, see the comments below) and found that fwupd.service
  fails to start due to a timeout. The logs below contain only the
  failure, I could not find the startup:

  2025-02-16T00:03:39.859015+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:03:39.859180+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:03:39.859258+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.456s CPU time.

  Here is another, probably incomplete instance. I attached the complete
  section of the log so maybe you can glean out what I missed. Here it
  is:

  2025-02-16T00:03:58.952797+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Starting fwupd.service - Firmware update daemon...
  2025-02-16T00:06:59.072774+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: start operation timed out. Terminating.
  2025-02-16T00:09:59.072836+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: State 'stop-sigterm' timed out. Killing.
  2025-02-16T00:09:59.073019+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Killing process 1192141 (fwupd) with signal S
  2025-02-16T00:10:48.774997+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Failed with result 'timeout'.
  2025-02-16T00:10:48.775165+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: Failed to start fwupd.service - Firmware update daemon.
  2025-02-16T00:10:48.775230+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[1]: fwupd.service: Consumed 1min 3.020s CPU time.

  There is another service called snap.firmware-updater.firmware-
  notifier.service that fails to start and is repeatedly trying to
  restart. My gut says it fails because it needs fwupd.service to be
  running. Here are some of the logs:

  2025-02-16T00:00:11.588457+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
systemd[2477]: Started snap.firmware-updater.firmware-notifier.service - 
Service for snap application firmware-updater.firmware-notifier.
  2025-02-16T00:00:11.669261+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
kernel: audit: type=1400 audit(1739660411.667:15250): apparmor="DENIED" 
operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" 
name="/proc/sys/vm/max_map_count" pid=1191308 comm="firmware-notifi" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  2025-02-16T00:00:11.672348+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
dbus-daemon[1184]: [system] Activating via systemd: service 
name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.19925' 
(uid=1000 pid=1191308 comm="/snap/firmware-updater/167/bin/firmware-notifier" 
label="snap.firmware-updater.firmware-notifier (enforce)")
  2025-02-16T00:00:36.677585+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: Unhandled exception:
  2025-02-16T00:00:36.677686+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms)
  2025-02-16T00:00:36.677704+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #0  DBusClient._callMethod 
(package:dbus/src/dbus_client.dart:1130)
  2025-02-16T00:00:36.677717+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: 
  2025-02-16T00:00:36.677730+01:00 user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU 
firmware-updater.firmware-notifier[1191308]: #1  DBusClient.callMethod 
(package:dbus/src/dbus_client.dart:621)
  2025-02-16T

[Kernel-packages] [Bug 2066187] Re: org.gnome.SettingsDaemon.XSettings.service fails to restart properly after AMD GPU reset event

> Unfortunately, I can't replicate this as I have no idea how to easily
trigger a GPU reset

On AMD systems You can use debugfs file you can do it with. For example
on my system:

# cat /sys/kernel/debug/dri/0/amdgpu_gpu_recover

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

Title:
  org.gnome.SettingsDaemon.XSettings.service fails to restart properly
  after AMD GPU reset event

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

Bug description:
  GNOME did not recover successfully from a GPU reset event. The system
  is still running but no direct interaction with it is possible.
  Keyboard appears to be running but the screen shows what was on it
  when the GPU crashed.

  Attached is a SYSLOG fragment showing the problem. At 04:12:09 the GPU
  crashed. At 04:17:06 the crash was detected and a GPU reset was
  issued. At 04:17:07 the org.gnome.SettingsDaemon.XSettings.service
  crashed with "failure status". Subsequent attempts to restart it (10
  shown) caused it to terminate with "timeout status".

  I reported this originally as an xorg bug because the computer became
  completely unusable and the only way to recover was a hard power-off.
  I could not even switch to another virtual console.

  I can't tell which package exactly this occured in because the package
  search does not work properly. It might be xorg itself but the failing
  org.gnome.SettingsDaemon.XSettings.service suggests the problem to be
  somewhere else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 20 17:42:42 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.2.0, 6.5.0-26-generic, x86_64: installed
   openrazer-driver/3.2.0, 6.5.0-35-generic, x86_64: installed
   virtualbox/6.1.50, 6.5.0-26-generic, x86_64: installed
   virtualbox/6.1.50, 6.5.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation Device [10de:28e1] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:14c3]
   Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev 0a) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:14c3]
  InstallationDate: Installed on 2024-02-14 (96 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507NU_FA507NU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-35-generic 
root=UUID=ac7c0a1e-2f8d-465c-9ec4-f8861895ec66 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2023
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: FA507NU.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA507NU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507NU.306:bd03/15/2023:br5.24:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507NU_FA507NU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507NU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A15
  dmi.product.name: ASUS TUF Gaming A15 FA507NU_FA507NU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post

[Kernel-packages] [Bug 2098972] Re: Enable Large Language Model (LLM) workloads using Intel NPU

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

Title:
  Enable Large Language Model (LLM) workloads using Intel NPU

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  New
Status in linux source package in Oracular:
  New

Bug description:
  [ Impact ]

   * Enable larger LLM using intel NPU.

  [ Fix ]

   * Upstream commit:
  83b6fa5844b5 accel/ivpu: Increase DMA address range

  [ Test Plan ]

   * Built and boot tested

  [ Where problems could occur ]

   * Memory management issue when using intel NPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098972/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2025-02-28 Thread Daniel van Vugt

** Summary changed:

- Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs)
+ Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.8 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-6.8 source package in Noble:
  Confirmed
Status in linux source package in Oracular:
  Fix Released
Status in linux-hwe-6.8 source package in Oracular:
  Confirmed

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2098944] Re: Failed to achieve more than 80% of the bandwidth on a 100Gbps connection during the network test

2025-02-28 Thread Kavya D

Applied network tuning techniques:

On SUT: 
- Disable firewall
- Install canonical-certification-server and certification-tools package
- Start-iperf3 -a [IP] -n 20 - for both the ports

On iPerf Server:
- Disable the firewall
- Install certification-tools package
- Start-iperf3 -a [IP] -n 20 - for both the ports

Running Network Test Manually:

Followed the guide [a] to optimize the network ports and manually executed the 
test using the command [b], but the test still showed only 25% bandwidth. Even 
after increasing the threads to 30, the issue remained unchanged.
[a] - 
https://certification.canonical.com/docs/programmes/server/Self-Test_Guide/appendix-d-network-performance-tuning/
[b] - sudo /usr/lib/checkbox-provider-base/bin/network.py test -i ens1f1 \ -t 
iperf --iperf3 --scan-timeout 3600 --fail-threshold 80 \ 
--cpu-load-fail-threshold 90 --runtime 900 --num_runs 4 --num-threads 20 \ 
--target 172.24.124.1

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

Title:
  Failed to achieve more than 80% of the bandwidth on a 100Gbps
  connection during the network test

Status in linux package in Ubuntu:
  New

Bug description:
  Server Details:
  SUT - Cisco UCS X210c M7
  Ubuntu OS - 22.04/24.04
  VIC/Ethernet Adapter - Cisco UCS VIC 15231 / UCSX-ML-V5D200G

  he SUT is configured to run the network test using the canonical-
  certification-server package, with both the SUT and iPerf test servers
  set up as per the Test Suite Guide. Both servers are in a 100Gb switch
  environment. The issue occurs with achieving 80-90% bandwidth during
  the network stress test, and this is observed on both blade and rack
  servers.

  However, when testing with 10G and 25G network speeds, 80-90% bandwidth is 
successfully achieved. Below is a list of network cards on which the network 
tests passed.
  Cisco UCS VIC 15427
  Cisco UCS VIC 15420

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098944/+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 2098730] Re: Kernel 6.8.0 memory leak

This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:

apport-collect 2098730

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that and change the
bug status to '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/2098730

Title:
  Kernel 6.8.0 memory leak

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We discovered a kernel memory leak in the Ubuntu 24.04 distribution
  using the 6.8.0 series kernel while testing on our cluster.

  After performing a fresh installation of Ubuntu Server 24.04 from the
  official ISO: `https://ubuntu.com/download/server/thank-
  you?version=24.04.1&architecture=amd64=1000 -F auid!=4294967295 -k access
```
  3. Reboot or run `augenrules --load`, then execute `auditctl -l` to verify 
that the audit rule above has been loaded.
  4. Run command `while :; do cat /proc/1/environ; done` as a normal user (uid 
>= 1000) to triger the audit events.
  5. Monitor kernel memory allocation by running either: 
```
watch -d -n 1 'cat /proc/meminfo | grep -i SUnreclaim'
```
or simply use 
```
slabtop -s c
```

  We tested several kernels within the 6.8.0 series, and this bug was
  present in all of them, including when installing HWE Kernel 6.8.0 in
  Ubuntu 22.04 via `apt install linux-generic-hwe-22.04`. However, after
  installing mainline kernels v6.8.1 or higher from
  https://kernel.ubunt.com/mainline/, this bug disappears, indicating it
  may have been fixed on upstream.

  Therefore, it is essential to update your stable repository's kernel
  and refresh your ISO accordingly.

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

2025-02-28 Thread Walther Freud

apport information

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

Title:
  System Freeze on suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently I put my Laptop into sleep mode like normal and later tried to wake 
it up but the machine was unresponsive.
  Interestingly opening the tty still worked (the second time it happened I 
pressed ctrl+f1 immediately after I noticed the freeze) but as soon as I 
interacted with the desktop environment (e.g. through a (normal) key press) the 
system froze completely.
  After a hard restart the same thing happened again after waking from sleep 
mode. I couldn't reproduce it the following days.
  From the logs (see attachments), I would extract that the problem is already 
at the time of entering sleep mode. Anyway would be very happy if you could 
look into this BUG: kernel NULL pointer dereference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:myuser 3271 F pipewire
   /dev/snd/controlC0:  myuser 3273 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 22
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2024-09-14 (160 days ago)
  InstallationMedia: Linux Mint 22 "Wilma" - Release amd64 20240721
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 03f0:1f4a HP, Inc HP USB Optical Mouse
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Acer Aspire E5-774G
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-53-generic 
root=UUID=a640493d-e5b1-4990-a53f-ec0a66f3e534 ro silent splash resume=/dev 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.8.0-53.55-generic 6.8.12
  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.8.0-53-generic N/A
   linux-backports-modules-6.8.0-53-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.9
  Tags: wilma
  Uname: Linux 6.8.0-53-generic x86_64
  UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht 
installiert ist.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  _MarkForUpload: False
  dmi.bios.date: 05/26/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hulk_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.30
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.27:bd05/26/2017:br0.0:efr2.30:svnAcer:pnAspireE5-774G:pvrV1.27:rvnAcer:rnHulk_SK:rvrV1.27:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-774G_1160_1.27:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-774G
  dmi.product.sku: Aspire E5-774G_1160_1.27
  dmi.product.version: V1.27
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098959/+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 2098508] Re: Hyper-V and MANA enhancements

2025-02-28 Thread John Cabaj

** Also affects: linux-azure (Ubuntu Plucky)
   Importance: Undecided
 Assignee: John Cabaj (john-cabaj)
   Status: In Progress

** Also affects: linux-azure-nvidia (Ubuntu Plucky)
   Importance: Undecided
 Assignee: John Cabaj (john-cabaj)
   Status: In Progress

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

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

** Changed in: linux-azure-nvidia (Ubuntu Oracular)
   Status: New => Won't Fix

** Changed in: linux-azure-nvidia (Ubuntu Oracular)
   Status: Won't Fix => Invalid

** Changed in: linux-azure-nvidia (Ubuntu Plucky)
   Status: In Progress => Invalid

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

Title:
  Hyper-V and MANA enhancements

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-nvidia package in Ubuntu:
  Invalid
Status in linux-azure source package in Noble:
  New
Status in linux-azure-nvidia source package in Noble:
  Fix Committed
Status in linux-azure source package in Oracular:
  New
Status in linux-azure-nvidia source package in Oracular:
  Invalid
Status in linux-azure source package in Plucky:
  In Progress
Status in linux-azure-nvidia source package in Plucky:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  * Microsoft requested patches to implement debugfs in MANA driver to
  improve debugging in userspace, improve available settings in ethtool,
  and vmbus enhancements to fix potential hang and improve throughput

  [Fix]

  * 6 clean cherry-picks from upstream
  * 1 simple backports from upstream

  [Test Plan]

  * Compile tested
  * Boot tested
  * Will be further tested by Microsoft

  [Regression potential]

  * Changes are largely localized to MANA and hyper-v. scsi change simply 
initializes as variable that should have already been initialized. Most changes 
have been upstreamed for some months.
  * Introduction of debugfs to MANA driver could introduce regressions if not 
well tested.

  [Other info]

  * SF#00406456

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2098508/+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 2095334] Re: No sound output from one of the speaker on HP ZBook[cs35l56]

2025-02-28 Thread AceLan Kao

** Tags added: verification-done-oracular

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

Title:
  No sound output from one of the speaker on HP ZBook[cs35l56]

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

Bug description:
  [Impact]
  No sound output from one of the speaker on HP ZBook[cs35l56]

  [Fix]
  This linux-firmware commit is required
  5e1e0ae5 cirrus: cs35l56: Correct some links to address the correct amp 
instance

  [Test]
  1. Boot to OS on HP ZBook with cs35l56 codec
  2. The sound can be output from both of the speakers

  [Where problems could occur]
  No new firmware is introduced, it just updates the wrong links.
  The changes are straight forward, and are not likely to lead to any 
regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2095334/+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 2098724] Re: Missing package linux-signatures-nvidia-6.11.0-18-generic

** Changed in: linux-restricted-modules (Ubuntu)
 Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler)

** Changed in: linux-restricted-modules (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux-restricted-modules (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Missing package linux-signatures-nvidia-6.11.0-18-generic

Status in linux-restricted-modules package in Ubuntu:
  Fix Released

Bug description:
  The latest update to linux-modules-nvidia-560-generic fails to install
  due to the dependency on linux-signatures-nvidia-6.11.0-18-generic
  (via linux-modules-nvidia-560-6.11.0-18-generic), which does not exist
  in the repositories.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-modules-nvidia-560-6.11.0-18-generic (not installed)
  ProcVersionSignature: Ubuntu 6.11.0-14.15-generic 6.11.0
  Uname: Linux 6.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Feb 17 23:18:34 2025
  InstallationDate: Installed on 2025-01-23 (25 days ago)
  InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 
(20241007.6)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-restricted-modules
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2098724/+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 1978133] Re: System freeze followed by kernel panic or blank screen

2025-02-28 Thread Bug Watch Updater

** Changed in: linux
   Status: Incomplete => 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/1978133

Title:
  System freeze followed by kernel panic or blank screen

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

Bug description:
  System keeps freezing in many different circumstances. I don't know
  how to reproduce this.

  Only happens on Ubuntu 22.04. Earlier versions were fine - tested
  Ubuntu impish and Debian bullseye.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-37-generic 5.15.0-37.39
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1593 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  9 12:22:34 2022
  InstallationDate: Installed on 2022-06-09 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic 
root=UUID=07f5275b-828a-4d4c-8cd5-73d429aea337 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-37-generic N/A
   linux-backports-modules-5.15.0-37-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd04/12/2022:br1.19:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1978133/+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 2082060] Re: memcpy: detected field-spanning write (size 8) of single field "lr + 1"

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

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

Title:
  memcpy: detected field-spanning write (size 8) of single field "lr +
  1"

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Noble:
  Confirmed
Status in zfs-linux source package in Oracular:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  * Having occurrences of "detected field-spanning write" on zpool
  import. Logs included below SRU justification

  [Fix]

  * Backport 6f50f8e16b7c: "zfs_log: add flex array fields to log record 
structs"
  * Backport c84a37ae93b5: "lua: add flex array field to TString type"

  [Test Plan]

  * Compile tested
  * Run through autopkgtest regression tests

  [Regression potential]

  * Changes already in upstream ZFS. lua changes are quite small. Otherwise 
adding
a new struct is added, which could lead to allocation issues if not managed
properly.

  I upgraded one of my systems to Oracular and noticed this error:

  memcpy: detected field-spanning write (size 8) of single field "lr +
  1" at /build/linux-3RcvoW/linux-6.11.0/debian/build/build-
  
generic/dkms/build/zfs/2.2.6/build/module/zfs/zfs_log.c:461
  (size 0)

  I'm running kernel 6.11.0-8-generic and zfs 2.2.6-1ubuntu1

  See also:

  memcpy: detected field-spanning write #16501 -
  https://github.com/openzfs/zfs/issues/16501

  memcpy: detected field-spanning write (size 7) of single field "sbuf" at 
/var/lib/dkms/zfs/2.2.99/build/module/lua/lstring.c:107 - 
https://github.com/openzfs/zfs/issues/16541
  ---
  ProblemType: Bug
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:danilo 3545 F pipewire
   /dev/snd/controlC0:  danilo 3550 F wireplumber
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.10
  InstallationDate: Installed on 2024-09-11 (15 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b47f Chicony Electronics Co., Ltd VGA Webcam
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 005: ID 04ca:3014 Lite-On Technology Corp. Qualcomm Atheros 
Bluetooth
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Acer Aspire ES1-572
  NonfreeKernelModules: zfs
  Package: linux (not installed)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x44vyn@/vmlinuz-6.11.0-8-generic 
root=ZFS=rpool/ROOT/ubuntu_x44vyn ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=1
  ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-8-generic N/A
   linux-backports-modules-6.11.0-8-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  Tags: oracular
  Uname: Linux 6.11.0-8-generic x86_64
  UnreportableReason: Este relatório é sobre o pacote que não foi instalado.
  UpgradeStatus: Upgraded to oracular on 2024-09-25 (1 days ago)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 06/20/2016
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd06/20/2016:br1.2:efr1.2:svnAcer:pnAspireES1-572:pvrV1.02:rvnAcer:rnT-Rex_SK:rvrV1.02:cvnAcer:ct10:cvrV1.02:skuAspireES1-572_1085_V1.02:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.02
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2082060/+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 2057693] Re: Activating autotrim results in high load average due to uninterruptible threads

This is already fixed in Plucky and Oracular (cv_wait_idle for vdev
autotrim), so only Noble is affected for now.

** Also affects: zfs-linux (Ubuntu Plucky)
   Importance: Medium
   Status: Fix Released

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

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

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

** Changed in: zfs-linux (Ubuntu Plucky)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

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

Title:
  Activating autotrim results in high load average due to
  uninterruptible threads

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Noble:
  In Progress
Status in zfs-linux source package in Oracular:
  Fix Released
Status in zfs-linux source package in Plucky:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  * High load averages when activating autotrim. Logs included below SRU
  justification

  [Fix]

  * Cherry-pick a0aa7a2ee3b5: "Autotrim High Load Average Fix"

  [Test Plan]

  * Compile tested
  * Run through autopkgtest regression tests

  [Regression potential]

  * Changes isolated, minimal regression risk. Changes already in
  upstream ZFS

  When activating the autotrim feature on any ZFS version starting from
  2.2.0 this will lead to a permanent increase of the load average (as
  diplayed in top) due to an uninterruptible vdev_autotrim thread for
  each vdev capable of TRIM.

  This issue has been reported
  (https://github.com/openzfs/zfs/issues/15453) as well as fixed
  (https://github.com/openzfs/zfs/pull/15781) upstream but the fix is
  not yet backported to Ubuntu.

  Since this bug was introduced with version 2.2.0 both mantic as well
  as noble are affected.

  How to reproduce:
  1. Create a pool with at least one TRIM-capable device
  2. run "zpool set autotrim=on "
  3. watch the output of "top" or "runtime" and see how the load average 
increases permanently even when the system is idle by one per vdev
  4. running "ps aux | grep -w D" will show the broken threads:

  [root@test ~]# ps aux | grep -w D\<
  root7193  0.0  0.0  0 0 ?D<   13:07   0:00 
[vdev_autotrim]

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2057693/+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 2082060] Re: memcpy: detected field-spanning write (size 8) of single field "lr + 1"

Both of the required fixes have been merged into ZFS 2.2.7, which is
already present in Plucky.

** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: zfs-linux (Ubuntu Oracular)
   Status: Confirmed => In Progress

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

** Changed in: zfs-linux (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Oracular)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Noble)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

** Changed in: zfs-linux (Ubuntu Oracular)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  memcpy: detected field-spanning write (size 8) of single field "lr +
  1"

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Noble:
  In Progress
Status in zfs-linux source package in Oracular:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  * Having occurrences of "detected field-spanning write" on zpool
  import. Logs included below SRU justification

  [Fix]

  * Backport 6f50f8e16b7c: "zfs_log: add flex array fields to log record 
structs"
  * Backport c84a37ae93b5: "lua: add flex array field to TString type"

  [Test Plan]

  * Compile tested
  * Run through autopkgtest regression tests

  [Regression potential]

  * Changes already in upstream ZFS. lua changes are quite small. Otherwise 
adding
a new struct is added, which could lead to allocation issues if not managed
properly.

  I upgraded one of my systems to Oracular and noticed this error:

  memcpy: detected field-spanning write (size 8) of single field "lr +
  1" at /build/linux-3RcvoW/linux-6.11.0/debian/build/build-
  
generic/dkms/build/zfs/2.2.6/build/module/zfs/zfs_log.c:461
  (size 0)

  I'm running kernel 6.11.0-8-generic and zfs 2.2.6-1ubuntu1

  See also:

  memcpy: detected field-spanning write #16501 -
  https://github.com/openzfs/zfs/issues/16501

  memcpy: detected field-spanning write (size 7) of single field "sbuf" at 
/var/lib/dkms/zfs/2.2.99/build/module/lua/lstring.c:107 - 
https://github.com/openzfs/zfs/issues/16541
  ---
  ProblemType: Bug
  ApportVersion: 2.30.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:danilo 3545 F pipewire
   /dev/snd/controlC0:  danilo 3550 F wireplumber
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 24.10
  InstallationDate: Installed on 2024-09-11 (15 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b47f Chicony Electronics Co., Ltd VGA Webcam
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 005: ID 04ca:3014 Lite-On Technology Corp. Qualcomm Atheros 
Bluetooth
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Acer Aspire ES1-572
  NonfreeKernelModules: zfs
  Package: linux (not installed)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x44vyn@/vmlinuz-6.11.0-8-generic 
root=ZFS=rpool/ROOT/ubuntu_x44vyn ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=1
  ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-8-generic N/A
   linux-backports-modules-6.11.0-8-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  Tags: oracular
  Uname: Linux 6.11.0-8-generic x86_64
  UnreportableReason: Este relatório é sobre o pacote que não foi instalado.
  UpgradeStatus: Upgraded to oracular on 2024-09-25 (1 days ago)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 06/20/2016
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd06/20/2016:br1.2:efr1.2:svnAcer:pnAspireES1-572:pvrV1.02:rvnAcer:rnT-Rex_SK:rvrV1.02:cvnAcer:ct10:cvrV1.02:skuAspireES1-572_1085_V1.02:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES

[Kernel-packages] [Bug 2094733] Re: External monitor not working after kernel update to 6.8.0-51 on Ubuntu 22.04 (DisplayPort over USB-C)

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

Title:
  External monitor not working after kernel update to 6.8.0-51 on Ubuntu
  22.04 (DisplayPort over USB-C)

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

Bug description:
  After upgrading the Linux kernel to version 6.8.0-51 on Ubuntu 22.04,
  the external monitor connected via DisplayPort through a docking
  station over USB-C stopped functioning. The monitor is no longer
  detected by the system, and no output is displayed. However, when
  connecting the same monitor via HDMI, it works as expected.

  Steps to Reproduce:
  Update the kernel to version 6.8.0-51 using unattended-upgrades or manual 
installation.
  Connect a docking station to the laptop via USB-C.
  Connect an external monitor to the docking station via DisplayPort.
  Check if the monitor is detected in the display settings or xrandr.
  Expected Behavior:
  The external monitor connected via the docking station using DisplayPort 
should be detected and function correctly, as it did in the previous kernel 
version 6.8.0-50.

  Observed Behavior:
  The monitor connected via DisplayPort through the docking station is not 
detected, and no output is displayed.
  Connecting the monitor via HDMI directly or through the docking station works 
as expected.
  Additional Information:
  Kernel version: 6.8.0-51 (affected), 6.8.0-50 (working).
  Ubuntu version: Ubuntu 22.04.5 LTS.
  Docking Station: Lenovo ThinkPad USB-C Dock, Type 40A9
  Connection setup: Laptop → USB-C → Docking Station → DisplayPort → Monitor.

  Workaround:
  Reverting to kernel version 6.8.0-50 resolves the issue, and the monitor 
functions as expected when connected via DisplayPort through the docking 
station.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-51-generic (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-50.51~22.04.1-generic 6.8.12
  Uname: Linux 6.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 14 08:51:54 2025
  InstallationDate: Installed on 2024-05-13 (246 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2094733/+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 2094733] Re: External monitor not working after kernel update to 6.8.0-51 on Ubuntu 22.04 (DisplayPort over USB-C)

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

** Changed in: linux-hwe-6.8 (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/2094733

Title:
  External monitor not working after kernel update to 6.8.0-51 on Ubuntu
  22.04 (DisplayPort over USB-C)

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

Bug description:
  After upgrading the Linux kernel to version 6.8.0-51 on Ubuntu 22.04,
  the external monitor connected via DisplayPort through a docking
  station over USB-C stopped functioning. The monitor is no longer
  detected by the system, and no output is displayed. However, when
  connecting the same monitor via HDMI, it works as expected.

  Steps to Reproduce:
  Update the kernel to version 6.8.0-51 using unattended-upgrades or manual 
installation.
  Connect a docking station to the laptop via USB-C.
  Connect an external monitor to the docking station via DisplayPort.
  Check if the monitor is detected in the display settings or xrandr.
  Expected Behavior:
  The external monitor connected via the docking station using DisplayPort 
should be detected and function correctly, as it did in the previous kernel 
version 6.8.0-50.

  Observed Behavior:
  The monitor connected via DisplayPort through the docking station is not 
detected, and no output is displayed.
  Connecting the monitor via HDMI directly or through the docking station works 
as expected.
  Additional Information:
  Kernel version: 6.8.0-51 (affected), 6.8.0-50 (working).
  Ubuntu version: Ubuntu 22.04.5 LTS.
  Docking Station: Lenovo ThinkPad USB-C Dock, Type 40A9
  Connection setup: Laptop → USB-C → Docking Station → DisplayPort → Monitor.

  Workaround:
  Reverting to kernel version 6.8.0-50 resolves the issue, and the monitor 
functions as expected when connected via DisplayPort through the docking 
station.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.8.0-51-generic (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-50.51~22.04.1-generic 6.8.12
  Uname: Linux 6.8.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 14 08:51:54 2025
  InstallationDate: Installed on 2024-05-13 (246 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: linux-signed-hwe-6.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2094733/+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 2098900] Re: Ubuntu 24.10 Fails to Resume from Suspend on Lenovo Legion Y545 (NVIDIA/Wayland)

2025-02-28 Thread Marlen T. B.

I've never messed with the kernel before. So I'll try it out first thing
on Saturday, and then I'll have two whole days to fix my computer,
before I need to use it for work again on Monday.

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

Title:
  Ubuntu 24.10 Fails to Resume from Suspend on Lenovo Legion Y545
  (NVIDIA/Wayland)

Status in linux package in Ubuntu:
  New

Bug description:
  **Summary:**
  My Lenovo Legion Y545 running Ubuntu 24.10 fails to resume properly from 
suspend.

  **System Details:**
  - **Laptop Model:** Lenovo Legion Y545
  - **OS:** Ubuntu 24.10
  - **Kernel Version:** 6.11.0-18-generic
  - **Display Server:** Wayland
  - **Graphics:** Intel UHD 630 / NVIDIA GTX 1650 (using `nvidia-driver-535`)

  **Steps to reproduce:**
  1. Put the laptop to sleep (via suspend)
  2. Attempt to wake it.
  3. Screen remains black, and requires hard shutdown to regain control.

  **Workaround**
  1. Turn off the external monitor via meta+P (and select built-in only)
  2. Suspend and resume works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: systemd 256.5-2ubuntu3.1
  ProcVersionSignature: Ubuntu 6.11.0-18.18-generic 6.11.11
  Uname: Linux 6.11.0-18-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 19 14:40:24 2025
  InstallationDate: Installed on 2024-08-15 (189 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 5986:2113 Bison Electronics Inc. SunplusIT Integrated 
Camera
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 81T2
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-18-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to oracular on 2024-10-26 (117 days ago)
  dmi.bios.date: 05/24/2022
  dmi.bios.release: 1.45
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.45
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN45WW:bd05/24/2022:br1.45:efr1.45:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098900/+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 2099682] Re: linux-headers-6.11.0-17-generic 6......

2025-02-28 Thread Daniel Letzeisen

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

dkms autoinstall on 6.11.0-17-generic/x86_64 failed for xtrx(10)

** This bug has been marked a duplicate of bug 2098021
   xtrx-dkms fails to build on kernel 6.11.x

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

Title:
  linux-headers-6.11.0-17-generic 6..

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

Bug description:
  linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to
  install/upgrade: le sous-processus paquet linux-
  headers-6.11.0-17-generic script post-installation installé a renvoyé
  un état de sortie d'erreur 11

  this broke the boot

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  Uname: Linux 6.8.0-52-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Feb 21 12:37:26 2025
  ErrorMessage: le sous-processus paquet linux-headers-6.11.0-17-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 11
  InstallationDate: Installed on 2024-11-08 (105 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6.1
   apt  2.7.14build2
  SourcePackage: linux-hwe-6.11
  Title: package linux-headers-6.11.0-17-generic 6.11.0-17.17~24.04.2 failed to 
install/upgrade: le sous-processus paquet linux-headers-6.11.0-17-generic 
script post-installation installé a renvoyé un état de sortie d'erreur 11
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Kernel-packages] [Bug 2097696] Re: brightness

2025-02-28 Thread mutamammil ula

the bug is still exist in v6.5, the phantom input appear randomly and it is
worse than in v6.8

Pada Kam, 20 Feb 2025 pukul 07.55 Tim Whisonant <2097...@bugs.launchpad.net>
menulis:

> Ok, so sounds like things were still broken in v6.8. Let's keep going
> back in time.
>
> Could you please try the following kernel and let me know?
>
> https://kernel.ubuntu.com/mainline/v6.5/amd64/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2097696
>
> Title:
>   brightness
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   my laptop brightness automatically change after i adjust it manually.
>   if i haven't adjust it after booting, the brightness wont change
>   automatically. so i need to reboot if i don't want it to change
>   automatically
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 24.04
>   Package: linux-image-6.8.0-52-generic 6.8.0-52.53
>   ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
>   Uname: Linux 6.8.0-52-generic x86_64
>   ApportVersion: 2.28.1-0ubuntu3.3
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/seq:msi1540 F pipewire
>/dev/snd/controlC0:  msi1544 F wireplumber
>/dev/snd/controlC2:  msi1544 F wireplumber
>/dev/snd/controlC1:  msi1544 F wireplumber
>   CRDA: N/A
>   CasperMD5CheckResult: unknown
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Feb  9 15:25:31 2025
>   InstallationDate: Installed on 2025-02-06 (3 days ago)
>   InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64
> (20240827.1)
>   MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW
>   ProcEnviron:
>LANG=en_US.UTF-8
>PATH=(custom, no user)
>SHELL=/bin/bash
>TERM=xterm-256color
>XDG_RUNTIME_DIR=
>   ProcFB: 0 amdgpudrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-52-generic
> root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash acpi_osi=Linux
> vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-6.8.0-52-generic N/A
>linux-backports-modules-6.8.0-52-generic  N/A
>linux-firmware
> 20240318.git3b128b60-0ubuntu2.7
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/12/2023
>   dmi.bios.release: 1.22
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: E14DKAMS.116
>   dmi.board.asset.tag: Default string
>   dmi.board.name: MS-14DK
>   dmi.board.vendor: Micro-Star International Co., Ltd.
>   dmi.board.version: REV:1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.116:bd07/12/2023:br1.22:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku14DK.1:
>   dmi.product.family: Modern
>   dmi.product.name: Modern 14 B4MW
>   dmi.product.sku: 14DK.1
>   dmi.product.version: REV:1.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097696/+subscriptions
>
>

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

Title:
  brightness

Status in linux package in Ubuntu:
  New

Bug description:
  my laptop brightness automatically change after i adjust it manually.
  if i haven't adjust it after booting, the brightness wont change
  automatically. so i need to reboot if i don't want it to change
  automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-52-generic 6.8.0-52.53
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  Uname: Linux 6.8.0-52-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:msi1540 F pipewire
   /dev/snd/controlC0:  msi1544 F wireplumber
   /dev/snd/controlC2:  msi1544 F wireplumber
   /dev/snd/controlC1:  msi1544 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  9 15:25:31 2025
  InstallationDate: Installed on 2025-02-06 (3 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-52-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash acpi_osi=Linux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restric

[Kernel-packages] [Bug 2098370] Re: 24.04.1 Suspends\Hibernates after desktop login using ext keyboard\monitor

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

Title:
  24.04.1 Suspends\Hibernates after desktop login using ext
  keyboard\monitor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded (side by side install) from 22.04 (fully working daily 
driver OS) to 24.4.1.
  My normal environment is a Dell precision M6700 laptop on a docking station 
with an external USB keyboard and external DP LCD monitor. Always powered from 
AC. laptop lid is always shut.

  Usual startup procedure as follows --> power on laptop via docking
  station power on button, (laptop boots grub2; hidden from view since
  lid is shut), eventually after 20 seconds DP monitor shows Ubuntu
  login prompt. I enter name\password and after 10 seconds get Ubuntu
  desktop on DP monitor. All well and good.

  However with 24.4.1 everything is the same up to the Ubuntu login prompt. 
After entering name\password the laptop then suspends\hibernates (fans stop, 
USB keyboard off, DP monitor no signal).
  If I then open the laptop lid slightly the laptop wakes up. Closing the 
laptop lid I get the logged in Ubuntu desktop on the DP monitor.

  How can I find out what is causing the laptop to go into
  suspend\hibernate following login when its lid is closed?

  No LSB modules are available.
  Description:  Ubuntu 24.04.2 LTS
  Release:  24.04
  Linux main-Precision-M6700 6.8.0-52-generic #53-Ubuntu SMP PREEMPT_DYNAMIC 
Sat Jan 11 00:06:25 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098370/+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 2098822] Re: [Ubuntu 24.04.01]SR-IOV virtual function interface are not registering after enabling SR-IOV on Broadcom Network Cards