[Kernel-packages] [Bug 2105421] [NEW] nct6687 not available in Ubuntu 24.10

2025-03-30 Thread Ar Rakin
Public bug reported:

Hello there,

I have a system with MSI PRO Z790-A MAX WIFI motherboard. I need the
nct6687 kernel module to monitor the sensors of the system, but the
kernel that's packaged for Ubuntu 24.10 does not seem to include
nct6687. I built it myself and installed it from
, however I got secure boot
errors when loading the module into the kernel: "Key was rejected by
service".

I do not want to disable secure boot, is there a specific package/kernel
update that I can install to fix this?

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

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

Title:
  nct6687 not available in Ubuntu 24.10

Status in linux package in Ubuntu:
  New

Bug description:
  Hello there,

  I have a system with MSI PRO Z790-A MAX WIFI motherboard. I need the
  nct6687 kernel module to monitor the sensors of the system, but the
  kernel that's packaged for Ubuntu 24.10 does not seem to include
  nct6687. I built it myself and installed it from
  , however I got secure boot
  errors when loading the module into the kernel: "Key was rejected by
  service".

  I do not want to disable secure boot, is there a specific
  package/kernel update that I can install to fix this?

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


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


[Kernel-packages] [Bug 2103970] Re: FFe: Sync firmware-sof 2025.01-1 from debian unstable

2025-03-30 Thread Jeremy Bícha
** Tags added: plucky upgrade-software-version

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

Title:
  FFe: Sync firmware-sof 2025.01-1 from debian unstable

Status in firmware-sof package in Ubuntu:
  Triaged
Status in firmware-sof source package in Plucky:
  Triaged

Bug description:
  Impact
  ==

  A new upstream release of firmware-sof was tagged on 2025.01-1 
(https://github.com/thesofproject/sof-bin/releases), it includes all patches we 
maintained as follows so we don't have to keep them in the new version:
  0001-Add-2.11-topology2-production-binaries.patch
  0002-Add-SOF-v2.11.1-signed-Intel-binaries-for-MTL-LNL-AR.patch
  0003-Add-missing-links-for-SOF-v2.11.1-signed-Intel-binar.patch
  0004-v2.2.x-Update-v2.2.12-topology-files-for-Intel-platf.patch
  0005-v2.11.x-add-new-2.11.2-topology2-production-binaries.patch
  0006-v2.11.x-add-new-2.11.3-topology2-production-binaries.patch
  0007-v2.2.x-Update-v2.2.13-topology-files-for-Intel-platf.patch 


  Upstream Changelog:
  ===

  v2025.01:
  
  * SOF v2.12 firmware binaries. For older Intel platforms, firmware from 
v2.2 stable.
  * SOF v2.12 tools. For older Intel platforms, tools from v2.2 stable.
  * SOF v2.12 DSP topologies. For older Intel platforms, topologies 
matching v2.2.13.

  
  v2024.09.2:
  
  * Updated DSP topology files for SOF2.11.3. Includes fix for 
thesofproject/sof#9681

  v2024.09.1:
  
  * New SOF v2.11 firmware binaries for Intel Arrow Lake platforms. No 
change to existing binaries for other platforms.
  * Add new DSP topology updates from both SOF2.11 and v2.2 stable trees. 
This extends hardware support to cover more product configurations.

  v2024.09:
  
  * SOF v2.11.1 FW binaries. For older Intel platforms, FW from v2.2 stable.
  * SOF v2.11 tools. For older Intel platforms, tools from v2.2 stable.
  * SOF v2.11 DSP topologies. For older Intel platforms, topologies 
matching v2.2.11.

  https://github.com/thesofproject/sof-bin/releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2103970/+subscriptions


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


[Kernel-packages] [Bug 2105425] Re: Support GPU driver on Qualcomm QCS6490 / SA8775

2025-03-30 Thread Masahiro Yamada
** Summary changed:

- Support GPU driver on Qualcomm IoT platforms
+ Support GPU driver on Qualcomm QCS6490 / SA8775

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

Title:
  Support GPU driver on Qualcomm QCS6490 / SA8775

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  [Impact]

  Qualcomm's graphic driver does not work because necessary firmware
  files are missing in Ubuntu's linux-firmware package.

  An example error:

   [  200.275893] adreno 3d0.gpu: [drm:adreno_zap_shader_load [msm]]
  *ERROR* Unable to load qcom/qcs6490/a660_zap.mbn

  
  [Fix]

  Import necessary firmware files from the upstream linux-firmware
  project.

  [Test Case]

  Install Ubuntu on the Qualcomm boards such as RB3G2, RB8, boards.
  Run a simple rendoring program such as 'kmscube'.

  [Where problems could occur]

  When we support the graphics driver (drivers/gpu/drm/msm/) for
  Qualcomm IoT platforms (https://ubuntu.com/download/qualcomm-iot).

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


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


[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing textures when switching users, switching VTs or resuming from suspend

2025-03-30 Thread Julien Olivier
The note in the summary is not quite correct: "And even then, only
desktops that use suspend/resume and VT switching may trigger it, if
ever."

In my case, it happens after any suspend / resume cycle, without ever
switching VT (or user).

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

Title:
  [nvidia] Corrupted/missing textures when switching users, switching
  VTs or resuming from suspend

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-550 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDe

[Kernel-packages] [Bug 2105421] Re: nct6687 not available in Ubuntu 24.10

2025-03-30 Thread Daniel Letzeisen
The kernel does have nct6683 module which supports nct6687, though the
voltage readings are not accurate. If you prefer the nct6687 module, it
would really help if they upstreamed it to kernel, but I don't see much
effort there: https://github.com/Fred78290/nct6687d/issues/52

If you want to sign your own kernel module:
https://wiki.ubuntu.com/UEFI/SecureBoot#How_can_I_do_non-automated_signing_of_drivers.3F


** Bug watch added: github.com/Fred78290/nct6687d/issues #52
   https://github.com/Fred78290/nct6687d/issues/52

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

Title:
  nct6687 not available in Ubuntu 24.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have a system with MSI PRO Z790-A MAX WIFI motherboard. I need the
  nct6687 kernel module to monitor the sensors of the system, but the
  kernel that's packaged for Ubuntu 24.10 does not seem to include
  nct6687. I built it myself and installed it from
  , however I got secure boot
  errors when loading the module into the kernel: "Key was rejected by
  service".

  I do not want to disable secure boot, is there a specific
  package/kernel update that I can install to fix this?

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


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


[Kernel-packages] [Bug 2093261] Re: obsolete 560 in Oracular and Plucky

2025-03-30 Thread Kuba Pawlak
** Also affects: nvidia-graphics-drivers-560 (Ubuntu Oracular)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-560 (Ubuntu Plucky)
   Importance: Undecided
   Status: Confirmed

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

Title:
  obsolete 560 in Oracular and Plucky

Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-560 source package in Oracular:
  New
Status in nvidia-graphics-drivers-560 source package in Plucky:
  Confirmed

Bug description:
  560 is EOL and need to be replaced with 570

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-560/+bug/2093261/+subscriptions


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


[Kernel-packages] [Bug 2105425] Re: Support GPU driver on Qualcomm IoT platforms

2025-03-30 Thread Masahiro Yamada
** Also affects: linux-firmware (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Masahiro Yamada (myamada)

** Changed in: linux-firmware (Ubuntu Noble)
 Assignee: (unassigned) => Masahiro Yamada (myamada)

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

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

Title:
  Support GPU driver on Qualcomm IoT platforms

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  [Impact]

  Qualcomm's graphic driver does not work because necessary firmware
  files are missing in Ubuntu's linux-firmware package.

  An example error:

   [  200.275893] adreno 3d0.gpu: [drm:adreno_zap_shader_load [msm]]
  *ERROR* Unable to load qcom/qcs6490/a660_zap.mbn

  
  [Fix]

  Import necessary firmware files from the upstream linux-firmware
  project.

  [Test Case]

  Install Ubuntu on the Qualcomm boards such as RB3G2, RB8, boards.
  Run a simple rendoring program such as 'kmscube'.

  [Where problems could occur]

  When we support the graphics driver (drivers/gpu/drm/msm/) for
  Qualcomm IoT platforms (https://ubuntu.com/download/qualcomm-iot).

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


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


[Kernel-packages] [Bug 2105421] Re: nct6687 not available in Ubuntu 24.10

2025-03-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  nct6687 not available in Ubuntu 24.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I have a system with MSI PRO Z790-A MAX WIFI motherboard. I need the
  nct6687 kernel module to monitor the sensors of the system, but the
  kernel that's packaged for Ubuntu 24.10 does not seem to include
  nct6687. I built it myself and installed it from
  , however I got secure boot
  errors when loading the module into the kernel: "Key was rejected by
  service".

  I do not want to disable secure boot, is there a specific
  package/kernel update that I can install to fix this?

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


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


[Kernel-packages] [Bug 2105425] [NEW] Support GPU driver on Qualcomm IoT platforms

2025-03-30 Thread Masahiro Yamada
Public bug reported:

[Impact]

Qualcomm's graphic driver does not work because necessary firmware files
are missing in Ubuntu's linux-firmware package.

An example error:

 [  200.275893] adreno 3d0.gpu: [drm:adreno_zap_shader_load [msm]]
*ERROR* Unable to load qcom/qcs6490/a660_zap.mbn


[Fix]

Import necessary firmware files from the upstream linux-firmware
project.

[Test Case]

Install Ubuntu on the Qualcomm boards such as RB3G2, RB8, boards.
Run a simple rendoring program such as 'kmscube'.

[Where problems could occur]

When we support the graphics driver (drivers/gpu/drm/msm/) for Qualcomm
IoT platforms (https://ubuntu.com/download/qualcomm-iot).

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Assignee: Masahiro Yamada (myamada)
 Status: New

** Affects: linux-firmware (Ubuntu Noble)
 Importance: High
 Assignee: Masahiro Yamada (myamada)
 Status: New

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

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

Title:
  Support GPU driver on Qualcomm IoT platforms

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Noble:
  New

Bug description:
  [Impact]

  Qualcomm's graphic driver does not work because necessary firmware
  files are missing in Ubuntu's linux-firmware package.

  An example error:

   [  200.275893] adreno 3d0.gpu: [drm:adreno_zap_shader_load [msm]]
  *ERROR* Unable to load qcom/qcs6490/a660_zap.mbn

  
  [Fix]

  Import necessary firmware files from the upstream linux-firmware
  project.

  [Test Case]

  Install Ubuntu on the Qualcomm boards such as RB3G2, RB8, boards.
  Run a simple rendoring program such as 'kmscube'.

  [Where problems could occur]

  When we support the graphics driver (drivers/gpu/drm/msm/) for
  Qualcomm IoT platforms (https://ubuntu.com/download/qualcomm-iot).

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


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


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

2025-03-30 Thread Jozef Behran
uname -a says "Linux user-ASUS-TUF-Gaming-A15-FA507NU-FA507NU
6.8.0-56-generic #58-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 14 15:33:28 UTC
2025 x86_64 x86_64 x86_64 GNU/Linux". The state is that now when
watching YouTube the kernel hangs (power cycle required).

-- 
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:
  Triaged

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
  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.

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


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


[Kernel-packages] [Bug 2092363] Re: Missing (but referenced) SOF firmware in pc-kernel – No Audio

2025-03-30 Thread Jürg Häfliger
The pc-kernel snap is basically a repackaging of the kernel Debian
package plus some additional things like firmware blobs. If a firmware
is not explicitly referenced by the kernel (listed in the output of
'modinfo ') it will not be included in the snap.

For the record, the snap repos are here:
https://code.launchpad.net/~canonical-kernel-snaps/+git

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

Title:
  Missing (but referenced) SOF firmware in pc-kernel – No Audio

Status in canonical-kernel-snaps:
  Confirmed
Status in pc-kernel-snap:
  Invalid
Status in apt package in Ubuntu:
  Invalid
Status in boot-managed-by-snapd package in Ubuntu:
  Invalid
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am encountering an issue with the pc-kernel snap on my HP EliteBook
  840 G11 laptop running Ubuntu 24.04.1 LTS with the new TPM+FDE
  feature. Despite testing multiple kernel channels, the system fails to
  detect any audio devices. However, when booting into a live session of
  Ubuntu 24.04.1 LTS, audio functions as expected. This suggests the
  issue may be related to the pc-kernel snap.

  Right now I'm on channel 24/stable (version: 6.8.0-50.51), but I have
  tried 24-hwe/stable and 24.10/stable as well.

  For reference, I have first tried to seek help in the support section over at 
Ubuntu Discourse, and I was encouraged to file a bug report here against the 
linux package on Discourse:
  
https://discourse.ubuntu.com/t/no-audio-device-detected-on-hp-elitebook-840-14-g11-running-ubuntu-24-04/51498/7

  Details:

  OS: Ubuntu 24.04.1 LTS
  Setup: TPM-backed Full Disk Encryption (FDE) using pc-kernel snap
  Kernel Channels Tried: 24-hwe/stable, 24/stable, 24.10/stable
  Issue: aplay -l reports "no sound card found"; only "Dummy output" is listed 
in Audio settings.
  Observation: Audio works correctly in a live session of Ubuntu 24.04.1 LTS.

  Listing audio devices:

  $ aplay -l
  aplay: device_list:277: no soundcards found...

  Relevant lspci Output:

  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Meteor Lake-P 
HD Audio Controller [8086:7e28] (rev 20)
  Subsystem: Hewlett-Packard Company Meteor Lake-P HD Audio Controller 
[103c:8c26]
  Kernel driver in use: sof-audio-pci-intel-mtl
  Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl

  Additional Notes:

  Could the issue be related to missing kernel drivers or modules, such as 
firmware-sof-signed?
  Reference: https://packages.ubuntu.com/noble/firmware-sof-signed

  Please let me know if additional details, logs, or steps are required.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-50-generic (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-50.51-generic 6.8.12
  Uname: Linux 6.8.0-50-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:kihen  3216 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 22 20:09:17 2024
  MachineType: HP HP EliteBook 840 14 inch G11 Notebook PC
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 simpledrmdrmfb
   1 i915drmfb
  ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 
console=tty1 panic=-1 quiet splash
  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-50-generic N/A
   linux-backports-modules-6.8.0-50-generic  N/A
   linux-firmwareN/A
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 06/20/2024
  dmi.bios.release: 2.6
  dmi.bios.vendor: HP
  dmi.bios.version: W70 Ver. 01.02.06
  dmi.board.name: 8C26
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.43.50
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.67
  dmi.modalias: 
dmi:bvnHP:bvrW70Ver.01.02.06:bd06/20/2024:br2.6:efr2.67:svnHP:pnHPEliteBook84014inchG11NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.43.50:cvnHP:ct10:cvr:sku8M4W7AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 14 inch G11 Notebook PC
  dmi.product.sku: 8M4W7AV
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2092363/+subscriptions


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


[Kernel-packages] [Bug 2092363] Re: Missing (but referenced) SOF firmware in pc-kernel – No Audio

2025-03-30 Thread Jürg Häfliger
And yes, not all required firmware is actually listed, so this might be
one of them.

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

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

** Changed in: boot-managed-by-snapd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: pc-kernel-snap
   Status: New => Invalid

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

Title:
  Missing (but referenced) SOF firmware in pc-kernel – No Audio

Status in canonical-kernel-snaps:
  Confirmed
Status in pc-kernel-snap:
  Invalid
Status in apt package in Ubuntu:
  Invalid
Status in boot-managed-by-snapd package in Ubuntu:
  Invalid
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am encountering an issue with the pc-kernel snap on my HP EliteBook
  840 G11 laptop running Ubuntu 24.04.1 LTS with the new TPM+FDE
  feature. Despite testing multiple kernel channels, the system fails to
  detect any audio devices. However, when booting into a live session of
  Ubuntu 24.04.1 LTS, audio functions as expected. This suggests the
  issue may be related to the pc-kernel snap.

  Right now I'm on channel 24/stable (version: 6.8.0-50.51), but I have
  tried 24-hwe/stable and 24.10/stable as well.

  For reference, I have first tried to seek help in the support section over at 
Ubuntu Discourse, and I was encouraged to file a bug report here against the 
linux package on Discourse:
  
https://discourse.ubuntu.com/t/no-audio-device-detected-on-hp-elitebook-840-14-g11-running-ubuntu-24-04/51498/7

  Details:

  OS: Ubuntu 24.04.1 LTS
  Setup: TPM-backed Full Disk Encryption (FDE) using pc-kernel snap
  Kernel Channels Tried: 24-hwe/stable, 24/stable, 24.10/stable
  Issue: aplay -l reports "no sound card found"; only "Dummy output" is listed 
in Audio settings.
  Observation: Audio works correctly in a live session of Ubuntu 24.04.1 LTS.

  Listing audio devices:

  $ aplay -l
  aplay: device_list:277: no soundcards found...

  Relevant lspci Output:

  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Meteor Lake-P 
HD Audio Controller [8086:7e28] (rev 20)
  Subsystem: Hewlett-Packard Company Meteor Lake-P HD Audio Controller 
[103c:8c26]
  Kernel driver in use: sof-audio-pci-intel-mtl
  Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl

  Additional Notes:

  Could the issue be related to missing kernel drivers or modules, such as 
firmware-sof-signed?
  Reference: https://packages.ubuntu.com/noble/firmware-sof-signed

  Please let me know if additional details, logs, or steps are required.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-50-generic (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-50.51-generic 6.8.12
  Uname: Linux 6.8.0-50-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:kihen  3216 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 22 20:09:17 2024
  MachineType: HP HP EliteBook 840 14 inch G11 Notebook PC
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB:
   0 simpledrmdrmfb
   1 i915drmfb
  ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 
console=tty1 panic=-1 quiet splash
  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-50-generic N/A
   linux-backports-modules-6.8.0-50-generic  N/A
   linux-firmwareN/A
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 06/20/2024
  dmi.bios.release: 2.6
  dmi.bios.vendor: HP
  dmi.bios.version: W70 Ver. 01.02.06
  dmi.board.name: 8C26
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.43.50
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.67
  dmi.modalias: 
dmi:bvnHP:bvrW70Ver.01.02.06:bd06/20/2024:br2.6:efr2.67:svnHP:pnHPEliteBook84014inchG11NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.43.50:cvnHP:ct10:cvr:sku8M4W7AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 14 inch G11 Notebook PC
  dmi.product.sku: 8M4W7AV
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2092363/+subscriptions


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


[Kernel-packages] [Bug 2103970] Re: FFe: Sync firmware-sof 2025.01-1 from debian unstable

2025-03-30 Thread Zixing Liu
** Changed in: firmware-sof (Ubuntu Plucky)
   Status: Triaged => Fix Committed

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

Title:
  FFe: Sync firmware-sof 2025.01-1 from debian unstable

Status in firmware-sof package in Ubuntu:
  Fix Committed
Status in firmware-sof source package in Plucky:
  Fix Committed

Bug description:
  Impact
  ==

  A new upstream release of firmware-sof was tagged on 2025.01-1 
(https://github.com/thesofproject/sof-bin/releases), it includes all patches we 
maintained as follows so we don't have to keep them in the new version:
  0001-Add-2.11-topology2-production-binaries.patch
  0002-Add-SOF-v2.11.1-signed-Intel-binaries-for-MTL-LNL-AR.patch
  0003-Add-missing-links-for-SOF-v2.11.1-signed-Intel-binar.patch
  0004-v2.2.x-Update-v2.2.12-topology-files-for-Intel-platf.patch
  0005-v2.11.x-add-new-2.11.2-topology2-production-binaries.patch
  0006-v2.11.x-add-new-2.11.3-topology2-production-binaries.patch
  0007-v2.2.x-Update-v2.2.13-topology-files-for-Intel-platf.patch 


  Upstream Changelog:
  ===

  v2025.01:
  
  * SOF v2.12 firmware binaries. For older Intel platforms, firmware from 
v2.2 stable.
  * SOF v2.12 tools. For older Intel platforms, tools from v2.2 stable.
  * SOF v2.12 DSP topologies. For older Intel platforms, topologies 
matching v2.2.13.

  
  v2024.09.2:
  
  * Updated DSP topology files for SOF2.11.3. Includes fix for 
thesofproject/sof#9681

  v2024.09.1:
  
  * New SOF v2.11 firmware binaries for Intel Arrow Lake platforms. No 
change to existing binaries for other platforms.
  * Add new DSP topology updates from both SOF2.11 and v2.2 stable trees. 
This extends hardware support to cover more product configurations.

  v2024.09:
  
  * SOF v2.11.1 FW binaries. For older Intel platforms, FW from v2.2 stable.
  * SOF v2.11 tools. For older Intel platforms, tools from v2.2 stable.
  * SOF v2.11 DSP topologies. For older Intel platforms, topologies 
matching v2.2.11.

  https://github.com/thesofproject/sof-bin/releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2103970/+subscriptions


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


[Kernel-packages] [Bug 2033307] Re: Most duplicate files in /lib/firmware are from firmware-sof-signed

2025-03-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firmware-sof (Ubuntu)
   Status: New => Confirmed

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

Title:
  Most duplicate files in /lib/firmware are from firmware-sof-signed

Status in firmware-sof package in Ubuntu:
  Confirmed

Bug description:
  Most duplicate files in /lib/firmware are from firmware-sof-signed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2033307/+subscriptions


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


[Kernel-packages] [Bug 2104938] Re: [ERAZER Crawler E30e] Backlight brightness not adjustable

2025-03-30 Thread Yosha872
Alessandro, if I remember well, after I used keyboard, the slider did
not appears in Gnome.

Currently I can not test more nor answer to Daniel because of this
issue: https://bugs.launchpad.net/ubuntu/+bug/2104936

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

Title:
  [ERAZER Crawler E30e] Backlight brightness not adjustable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 25.05: Gnome 48's dash does not allow be to adjust the screen
  brightness of my laptop ('light button' gauge graphic line is missing,
  sound gauge is present).

  ProblemType: Bug
  DistroRelease: Ubuntu 25.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.14.0-11.11-generic 6.14.0-rc7
  Uname: Linux 6.14.0-11-generic x86_64
  .proc.driver.nvidia.capabilities.fabric-imex-mgmt:
   DeviceFileMinor: 4323
   DeviceFileMode: 256
   DeviceFileModify: 1
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  570.86.16  Release 
Build  (dvs-builder@U16-I2-C04-15-2)  Fri Jan 24 21:05:28 UTC 2025
   GCC version:  gcc version 14.2.0 (Ubuntu 14.2.0-19ubuntu1)
  ApportVersion: 2.32.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 28 15:37:03 2025
  DistUpgraded: Fresh install
  DistroCodename: plucky
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-P GT1 [UHD Graphics] [8086:46a3] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:a554]
   NVIDIA Corporation GA107 [GeForce RTX 2050] [10de:25ad] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:a554]
  InstallationDate: Installed on 2025-03-28 (0 days ago)
  InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
  MachineType: MEDION Crawler E30e
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-11-generic 
root=UUID=f9796f07-9884-418e-9095-b044d814faaa ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2023
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RME1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NPxxRNA
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RME1:bd10/05/2023:br7.3:efr7.1:svnMEDION:pnCrawlerE30e:pvrNotApplicable:rvnMEDION:rnNPxxRNA:rvr1.0:cvnMEDION:ct10:cvrN/A:skuML-21000840086252:
  dmi.product.family: ERAZER
  dmi.product.name: Crawler E30e
  dmi.product.sku: ML-210008 40086252
  dmi.product.version: Not Applicable
  dmi.sys.vendor: MEDION
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.123-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 25.0.1-2ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.16-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.18-1

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


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


[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing textures when switching users, switching VTs or resuming from suspend

2025-03-30 Thread Daniel van Vugt
** Tags added: oracular

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Triaged => Won't Fix

** Description changed:

  [Impact]
  
  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:
  
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
- 
- Although it's so awkward to implement everywhere that realistically
- compositors will never support it fully. Instead we're waiting for an
- Nvidia driver fix.
  
  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.
  
  [Workarounds]
  
  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter
  
  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0
  
  [Test Plan]
  
  [Where problems could occur]
  
  [Original Bug Report]
  
  I recently installed ubuntu 20.04 on my computer, and I am running into
  an issue when I do the following:
  
  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user
  
  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.
  
  Screenshots: https://imgur.com/a/3ZFDLMc
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  [nvid

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

2025-03-30 Thread Leo Lin
Add another target to Plucky. This is meant for the 6.14 hwe kernel,
which oem-6.11 will eventually transit to.

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

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

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

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

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

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

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

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

-- 
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 package in Ubuntu:
  In Progress
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  Won't Fix
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Won't Fix
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  In Progress
Status in linux-oem-6.11 source package in Plucky:
  New

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]
  3. [PATCH] ASoC: amd: ps: use switch statements for acp pci revision id 
check[3]

  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
  [3] 
https://lore.kernel.org/alsa-devel/173945697146.151957.15841988796176463409.b4...@kernel.org/T/#m778380541979c1bb1f8bf5863e8a30015289b067

  [ 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 2096642] Re: No outputs detected on Nvidia with kernel 6.12

2025-03-30 Thread Daniel van Vugt
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: Fix Released => Won't Fix

** Changed in: nvidia-graphics-drivers-560 (Ubuntu)
   Status: Fix Released => Won't Fix

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

Title:
  No outputs detected on Nvidia with kernel 6.12

Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-560 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-570 package in Ubuntu:
  Fix Released

Bug description:
  With linux-kernel 6.12.0-10-generic the desktop is not shown on my Ubuntu 
25.04 system using KDE.
  I only see a black screen with a blinking text cursor. I cannot switch to 
alternative desktops.

  0b:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 
6GB] (rev a1)
  0b:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio 
Controller (rev a1)

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


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


[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing textures when switching users, switching VTs or resuming from suspend

2025-03-30 Thread Daniel van Vugt
Thanks for pointing that out. I've now corrected the text:

- suspend/resume and VT switching
+ suspend/resume or VT switching

** Description changed:

  [Impact]
  
  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:
  
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
  
  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
- only desktops that use suspend/resume and VT switching may trigger it,
- if ever. Even in development the bug cannot be reproduced reliably.
+ only desktops that use suspend/resume or VT switching may trigger it, if
+ ever. Even in development the bug cannot be reproduced reliably.
  
  [Workarounds]
  
  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter
  
  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0
  
  [Test Plan]
  
  [Where problems could occur]
  
  [Original Bug Report]
  
  I recently installed ubuntu 20.04 on my computer, and I am running into
  an issue when I do the following:
  
  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user
  
  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.
  
  Screenshots: https://imgur.com/a/3ZFDLMc
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  [nvidia] Corrup

[Kernel-packages] [Bug 2094969] Re: bluetooth/detect-output failed due to the lack of USB device id in btusb.c

2025-03-30 Thread En-Wei Wu
** Changed in: linux (Ubuntu Plucky)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  bluetooth/detect-output failed due to the lack of USB device id in
  btusb.c

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
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 Released
Status in linux source package in Plucky:
  Triaged
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  [Impact]
  BT hardware is not available on certain machines:

  1. Machine with MT7925 BT (USB VID/PID 13d3/3628)
  2. Machine with MT7925 BT (USB VID/PID 0489/e14e)

  [Fix]
  Add USB device IDs into device table in btusb.c fixes the issue.

  1. For VID/PID 13d3/3628, the patch has already been merged into
  linux-next:

  f597b8982d51 Bluetooth: btusb: Add new VID/PID 13d3/3628 for MT7925

  2. For VID/PID 0489/e14e, the patch is still under review. Out of the
  urgency, we're going to make a SAUCE patch first.

  
  [Test Plan]
  1. Install Ubuntu image and boot into the OS
  2. Run $ sudo checkbox-cli run 
com.canonical.certification::bluetooth/detect-output and see if the test is 
passed

  [Where problems could occur]
  The two BT hardware may have not yet been matured, so there might be issues 
in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094969/+subscriptions


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


[Kernel-packages] [Bug 2104321] Re: [rtw89_8852ce] Resume from suspend fails with "xtal si not ready" and "mac init fail"

2025-03-30 Thread Jürg Häfliger
** 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/2104321

Title:
  [rtw89_8852ce] Resume from suspend fails with "xtal si not ready" and
  "mac init fail"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  *1. Problem Overview:**

  WiFi connection fails after resuming from suspend (suspend-to-RAM /
  S3). The adapter is visible but does not scan for networks and cannot
  connect. WiFi functionality is only restored after a complete shutdown
  (cold boot); a simple reboot (warm boot) is not sufficient.

  **2. Affected Hardware:**

  * Laptop: Legion Pro 5 16ARX8 - Type 82WM - Model 82WM00ERUS
  * WiFi Card: Realtek RTL8852CE PCIe 802.11ax Wireless Network Controller
  * Identifiers (from lspci): [10ec:c852], Subsystem: [17aa:5852]
  * Driver in use: rtw89_8852ce

  **3. Affected Software:**

  * Distribution: Ubuntu 24.04.2 LTS (noble)
  * Current Kernel: 6.11.0-21-generic (problem also occurred with OEM kernel 
6.11.0-1017-oem)

  **4. Steps to Reproduce:**

  1.  Boot the system normally. WiFi connects and works correctly.
  2.  Suspend the system (e.g., via menu option or closing the lid).
  3.  Wait a few seconds.
  4.  Resume the system (e.g., open the lid or press the power button).

  **5. Expected Result:**

  WiFi should reconnect automatically or, at minimum, scan and display
  available networks, allowing manual connection.

  **6. Actual Result:**

  The WiFi icon might be present, but no networks are detected or displayed. 
Connection attempts fail. NetworkManager cannot initialize the interface 
correctly.
  The `sudo dmesg` command after resume shows repeating errors similar to:
 `rtw89_8852ce :03:00.0: xtal si not ready(W): offset=90 val=10 mask=10`
 `rtw89_8852ce :03:00.0: mac init fail, ret:-110`

  **7. Troubleshooting Attempts (Unsuccessful):**

  * Disabled "Fast Startup" in Windows 11 (dual boot setup).
  * Disabled WiFi power saving via NetworkManager (`wifi.powersave = 2`).
  * Reinstalled the `linux-firmware` package.
  * Tested the standard HWE (`-generic`) kernel instead of the OEM kernel.
  * Tested the `rtw89_core.disable_aspm=Y` module parameter.
  * Verified that BIOS/UEFI is up-to-date (checked via Windows).
  * Manually reloading the kernel modules (`sudo modprobe -r rtw89_8852ce 
rtw89_pci rtw89_core` followed by `sudo modprobe rtw89_8852ce`) after resuming 
also fails to restore WiFi functionality.

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


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


[Kernel-packages] [Bug 2092158] Re: [SRU] With certain configs (such as with NVIDIA GPU driver), Bluetooth HSP/HFP profile may be missing after suspend/resume

2025-03-30 Thread Yao Wei
On oracular with bluez 5.77.0-ubuntu2 with a unit with NVIDIA GPU with
Jabra Speak2 55 UC, this issue is reproducible.  Updating to -proposed
(5.77.0-ubuntu2.1), this issue is still reproducible, considering it
validation failed.

(p.s. this issue cannot be reproduced with AirPods Pro 2, probably the
device will try reconnecting HSP/HFP profile when it is not connected)

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

Title:
  [SRU] With certain configs (such as with NVIDIA GPU driver), Bluetooth
  HSP/HFP profile may be missing after suspend/resume

Status in Bluez Utilities:
  Fix Released
Status in OEM Priority Project:
  New
Status in PipeWire:
  Invalid
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Fix Committed
Status in bluez source package in Oracular:
  Fix Committed
Status in bluez source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

   * On system with NVIDIA proprietary driver and Bluetooth interface,
  when connecting to a Bluetooth headset, after doing a round of
  suspend/resume, A2DP interface would be reconnected, but not HSP/HFP.

   * This fix is suggested by upstream by reconnecting HSP/HFP (if not
  connected) when A2DP is connected.

  [ Test Plan ]

   * Find a system where NVIDIA proprietary driver is installed.

   * Connect it to a Bluetooth headset and see whether the above issue
  is reproducible.

   * Update bluez from -proposed, see whether HSP/HFP is available and
  after switching to HSP/HFP, mic and headphone are both working.

  [ Where problems could occur ]

   * The changed part would mainly affect the connection of Bluetooth
  headset.  If the fix brings regression, it would affect the connection
  and reconnection of Bluetooth devices.

  [ Original issue ]

  We found that with certain hardware configs, such as whether NVIDIA
  GPU is/is not available (but not always), can affect HSP/HFP profile
  after suspend/resume.  We will post debug information later on
  affected configs.

  [Reproducible Steps]
  1. Connect Bluetooth headphones
  2. Check that Bluetooth Handsfree is available in Sound settings
  3. Suspend the system and wake it up

  [Expected Behavior]
  Bluetooth Handsfree profile should be available after automatic reconnection

  [Actual Behavior]
  Bluetooth Handsfree profile is missing, one way to make it unreproducible on 
the system in question is to use prime-select to switch to Intel GPU:
    sudo prime-select intel
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-12-19 (0 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pipewire 1.0.5-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
  Tags: noble
  Uname: Linux 6.8.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.10
  InstallationDate: Installed on 2024-12-19 (0 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
  Package: pipewire 1.2.4-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcVersionSignature: Ubuntu 6.11.0-13.14-generic 6.11.0
  Tags: oracular
  Uname: Linux 6.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/2092158/+subscriptions


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


[Kernel-packages] [Bug 2092158] Re: [SRU] With certain configs (such as with NVIDIA GPU driver), Bluetooth HSP/HFP profile may be missing after suspend/resume

2025-03-30 Thread Yao Wei
On noble with bluez 5.72.0-0ubuntu5 with a unit with NVIDIA GPU,
connected to Jabra Speak2 55 UC Bluetooth speaker, this issue is
reproducible. Updating to -proposed (5.72.0-ubuntu5.2), this issue is
still reproducible, considering it validation failed.

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

Title:
  [SRU] With certain configs (such as with NVIDIA GPU driver), Bluetooth
  HSP/HFP profile may be missing after suspend/resume

Status in Bluez Utilities:
  Fix Released
Status in OEM Priority Project:
  New
Status in PipeWire:
  Invalid
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Fix Committed
Status in bluez source package in Oracular:
  Fix Committed
Status in bluez source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

   * On system with NVIDIA proprietary driver and Bluetooth interface,
  when connecting to a Bluetooth headset, after doing a round of
  suspend/resume, A2DP interface would be reconnected, but not HSP/HFP.

   * This fix is suggested by upstream by reconnecting HSP/HFP (if not
  connected) when A2DP is connected.

  [ Test Plan ]

   * Find a system where NVIDIA proprietary driver is installed.

   * Connect it to a Bluetooth headset and see whether the above issue
  is reproducible.

   * Update bluez from -proposed, see whether HSP/HFP is available and
  after switching to HSP/HFP, mic and headphone are both working.

  [ Where problems could occur ]

   * The changed part would mainly affect the connection of Bluetooth
  headset.  If the fix brings regression, it would affect the connection
  and reconnection of Bluetooth devices.

  [ Original issue ]

  We found that with certain hardware configs, such as whether NVIDIA
  GPU is/is not available (but not always), can affect HSP/HFP profile
  after suspend/resume.  We will post debug information later on
  affected configs.

  [Reproducible Steps]
  1. Connect Bluetooth headphones
  2. Check that Bluetooth Handsfree is available in Sound settings
  3. Suspend the system and wake it up

  [Expected Behavior]
  Bluetooth Handsfree profile should be available after automatic reconnection

  [Actual Behavior]
  Bluetooth Handsfree profile is missing, one way to make it unreproducible on 
the system in question is to use prime-select to switch to Intel GPU:
    sudo prime-select intel
  ---
  ProblemType: Bug
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2024-12-19 (0 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pipewire 1.0.5-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcVersionSignature: Ubuntu 6.8.0-51.52-generic 6.8.12
  Tags: noble
  Uname: Linux 6.8.0-51-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.10
  InstallationDate: Installed on 2024-12-19 (0 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
  Package: pipewire 1.2.4-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcVersionSignature: Ubuntu 6.11.0-13.14-generic 6.11.0
  Tags: oracular
  Uname: Linux 6.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/2092158/+subscriptions


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


[Kernel-packages] [Bug 2089273] Re: Add soundwire support for AMD platforms

2025-03-30 Thread Leo Lin
The config generated from Plucky (HEAD at e9549b2d5464) shows that all
relevant configs are enabled in 6.14:

$ ./debian/scripts/misc/annotations --arch amd64 --flavour generic
--export > .config

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

Title:
  Add soundwire support for AMD platforms

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Won't Fix
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in alsa-ucm-conf source package in Oracular:
  Fix Released
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  Invalid
Status in alsa-ucm-conf source package in Plucky:
  Fix Released
Status in linux source package in Plucky:
  Triaged
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  == linux ==

  [Impact]

  This patch series introduce soundwire support for AMD platform, as
  well as code reorganization in preparation for that.

  [Fix]
  Backport the AMD SoF driver from kernel 6.12 and its sdw_utils for dependency

  == alsa-ucm-conf ==
  [Impact]

  This patch series introduce soundwire support for AMD platform. The
  audio function won't work if no proper driver and alsa-ucm-conf
  installed.

  [Fix]
  Backport the patches from 
https://github.com/alsa-project/alsa-ucm-conf/pull/470 to support AMD SoF 
driver.

  [Test]

  1. Install the test kernel
  2. Install proper alsa-ucm-confs
  3. Confirm the audio function normally on the DUT with 1) AMD soundwire and 
2) existing Intel platforms using soundwire. Might include:

  * Checkbox audio test plan
  * Built-in speaker and built-in mic
  * Audio function when headphone is connected to the DUT.

  [Where problems could occur]

  Patches needed, other than 3 SAUCE patches that planned to upstream in
  6.13 cycle, are listed in [1] to [8] below.

  Soundwire used to appear mostly on Intel platforms and is almost
  always in combination with sof. To support AMD, it has to be
  refactored into a more generic framework (or at least that's what AMD
  people did).  This happens in patch series [1][2] and [3], extracting
  soundwire code from the sound/soc/intel directory to a more generic
  location, as well as rename/refactor things to better fit the ASoC
  context. This will impact all other soundwire platforms and if not
  done correctly, regression risk may be high.

  The all other patch sets other than [5] are AMD specific, so
  theoretically the impact is limited to AMD platforms with soundwire,
  which are rather uncommon.

  [1] 
https://lore.kernel.org/all/20240801091446.10457-1-vijendar.muku...@amd.com/
  [2] 
https://lore.kernel.org/lkml/20240913090631.1834543-1-vijendar.muku...@amd.com/
  [3] 
https://lore.kernel.org/all/20241101020802.1103181-1-vijendar.muku...@amd.com/
  [4] 
https://lore.kernel.org/all/20240924081846.1834612-1-vijendar.muku...@amd.com/
  [5] https://lore.kernel.org/all/20241105100557.1987917-1-shumi...@realtek.com/
  [6] 
https://lore.kernel.org/all/20241113115223.3274868-1-vijendar.muku...@amd.com/
  [7] 
https://lore.kernel.org/all/20241112185138.3235375-1-vijendar.muku...@amd.com/
  [8] 
https://lore.kernel.org/all/20241112161142.28974-1-mario.limoncie...@amd.com/
  [9] 
https://lore.kernel.org/linux-sound/173204812069.81544.393632760053179230.b4...@kernel.org/T/#me81566e214d388471ba39043bf594c8332421caf

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2089273/+subscriptions


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


[Kernel-packages] [Bug 2104321] Re: [rtw89_8852ce] Resume from suspend fails with "xtal si not ready" and "mac init fail"

2025-03-30 Thread Chris Chiu
Thank you for reporting this and helping make Ubuntu better. Could you
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:

$ apport-collect 2104321

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

Title:
  [rtw89_8852ce] Resume from suspend fails with "xtal si not ready" and
  "mac init fail"

Status in linux package in Ubuntu:
  New

Bug description:
  *1. Problem Overview:**

  WiFi connection fails after resuming from suspend (suspend-to-RAM /
  S3). The adapter is visible but does not scan for networks and cannot
  connect. WiFi functionality is only restored after a complete shutdown
  (cold boot); a simple reboot (warm boot) is not sufficient.

  **2. Affected Hardware:**

  * Laptop: Legion Pro 5 16ARX8 - Type 82WM - Model 82WM00ERUS
  * WiFi Card: Realtek RTL8852CE PCIe 802.11ax Wireless Network Controller
  * Identifiers (from lspci): [10ec:c852], Subsystem: [17aa:5852]
  * Driver in use: rtw89_8852ce

  **3. Affected Software:**

  * Distribution: Ubuntu 24.04.2 LTS (noble)
  * Current Kernel: 6.11.0-21-generic (problem also occurred with OEM kernel 
6.11.0-1017-oem)

  **4. Steps to Reproduce:**

  1.  Boot the system normally. WiFi connects and works correctly.
  2.  Suspend the system (e.g., via menu option or closing the lid).
  3.  Wait a few seconds.
  4.  Resume the system (e.g., open the lid or press the power button).

  **5. Expected Result:**

  WiFi should reconnect automatically or, at minimum, scan and display
  available networks, allowing manual connection.

  **6. Actual Result:**

  The WiFi icon might be present, but no networks are detected or displayed. 
Connection attempts fail. NetworkManager cannot initialize the interface 
correctly.
  The `sudo dmesg` command after resume shows repeating errors similar to:
 `rtw89_8852ce :03:00.0: xtal si not ready(W): offset=90 val=10 mask=10`
 `rtw89_8852ce :03:00.0: mac init fail, ret:-110`

  **7. Troubleshooting Attempts (Unsuccessful):**

  * Disabled "Fast Startup" in Windows 11 (dual boot setup).
  * Disabled WiFi power saving via NetworkManager (`wifi.powersave = 2`).
  * Reinstalled the `linux-firmware` package.
  * Tested the standard HWE (`-generic`) kernel instead of the OEM kernel.
  * Tested the `rtw89_core.disable_aspm=Y` module parameter.
  * Verified that BIOS/UEFI is up-to-date (checked via Windows).
  * Manually reloading the kernel modules (`sudo modprobe -r rtw89_8852ce 
rtw89_pci rtw89_core` followed by `sudo modprobe rtw89_8852ce`) after resuming 
also fails to restore WiFi functionality.

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


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


[Kernel-packages] [Bug 2104380] Re: Build failure when CONFIG_NET_SWITCHDEV=n due to CVE-2024-26837 fix backport

2025-03-30 Thread Chris Chiu
** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Koichiro Den (koichiroden)

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

Title:
  Build failure when CONFIG_NET_SWITCHDEV=n due to CVE-2024-26837 fix
  backport

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

Bug description:
  [ Impact ]

  Since jammy:linux commit 0158242f01a0 ("net: bridge: switchdev: Skip
  MDB replays of deferred events on offload"), the kernel build fails
  when CONFIG_NET_SWITCHDEV=n, as observed in e.g. jammy:linux-kvm. The
  error is as follows:

    /build/jammy/net/bridge/br_mdb.c: In function 'br_mdb_queue_one':
    /build/jammy/net/bridge/br_mdb.c:640:13: error: implicit declaration of 
function
    'switchdev_port_obj_act_is_deferred'; did you mean 
'switchdev_port_obj_add'? [-Werror=implicit- function-declaration]
  640 | switchdev_port_obj_act_is_deferred(dev, action, 
&mdb.obj)) {
  | ^~
  | switchdev_port_obj_add

  [ Fix ]

  Add a dummy implementation of switchdev_port_obj_act_is_deferred() for
  the CONFIG_NET_SWITCHDEV=n case. This approach was chosen because it
  is less risky and also requires minimal changes compared to the
  alternatives:

  * Backport 9776457c784f ("net: bridge: mdb: move all switchdev logic to 
br_switchdev.c"), which would involve resolving significant conflicts, or
  * Revert the CVE fix, cherry-pick nearly all prerequisite patches from [1] 
and [2], and then reapply the CVE fix.

  Note that register_switchdev_blocking_notifier() does nothing when
  CONFIG_NET_SWITCHDEV=n. Therefore, nbp_switchdev_(un)sync_objs (the
  sole caller of br_mdb_replay()) does not run in the first place.

  [1] 
https://lore.kernel.org/all/20211026142743.1298877-1-vladimir.olt...@nxp.com/
  [2] 
https://lore.kernel.org/all/20211027162119.2496321-1-vladimir.olt...@nxp.com/

  [ Test Plan ]

  Compile test with both CONFIG_NET_SWITCHDEV=y and
  CONFIG_NET_SWITCHDEV=n.

  [ Where problems could occur ]

  Any regressions caused by this tiny fix-the-fix patch should be caught
  during compilation.

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


-- 
Mailing list: https://launchpad.net/~kernel-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

2025-03-30 Thread Leo Lin
** Description changed:

  [ 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]
+ 3. [PATCH] ASoC: amd: ps: use switch statements for acp pci revision id 
check[3]
  
  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
+ [3] 
https://lore.kernel.org/alsa-devel/173945697146.151957.15841988796176463409.b4...@kernel.org/T/#m778380541979c1bb1f8bf5863e8a30015289b067
  
  [ 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

-- 
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 Released

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]
  3. [PATCH] ASoC: amd: ps: use switch statements for acp pci revision id 
check[3]

  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
  [3] 
https://lore.kernel.org/alsa-devel/173945697146.151957.15841988796176463409.b4...@kernel.org/T/#m778380541979c1bb1f8bf5863e8a30015289b067

  [ 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