[Kernel-packages] [Bug 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

2023-10-09 Thread Bartosz Woronicz
Ok, let's see. Thank you.

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

Title:
  HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  $ apt show linux-firmware
  Package: linux-firmware
  Version: 20220329.git681281e4-0ubuntu3.17
  Priority: optional
  Section: misc
  Origin: Ubuntu
  Maintainer: Ubuntu Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 999 MB
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Conflicts: atmel-firmware
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdragon (<= 1.2-0ubuntu1)
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-restricted-common
  Download-Size: 254 MB
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.

  N: There are 2 additional records. Please use the '-a' switch to see
  them.

  
  # update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
  cryptsetup: WARNING: swap: couldn't determine device type, assuming default 
  (plain).
  cryptsetup: WARNING: Resume target swap uses a key file
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/g

[Kernel-packages] [Bug 2061177] [NEW] USB bus crashes when using Razer Kiyo Pro webcam

2024-04-12 Thread Bartosz Woronicz
Public bug reported:

When using camera I got often freezes of the camera input which are fixed after 
a while (2-3min) when having the videoconference with Google Meet.
But sometimes it crashes the whole bus and all usb devices are disconnected.

[25678.046793] usb 2-9.1: current rate 16000 is different from the runtime rate 
48000
[42784.602640] usb 2-9.1: current rate 16000 is different from the runtime rate 
48000
[44426.198611] loop40: detected capacity change from 0 to 58432
[48209.516942] usb 2-9.1: current rate 16000 is different from the runtime rate 
48000
[56137.044859] usb 2-9.1: current rate 16000 is different from the runtime rate 
48000
[56342.242010] xhci_hcd :00:14.0: xHCI host not responding to stop endpoint 
command
[56342.242037] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
[56342.242093] xhci_hcd :00:14.0: HC died; cleaning up
[56342.242149] usb 1-2: USB disconnect, device number 2
[56342.242381] usb 2-9: USB disconnect, device number 2
[56342.242385] usb 2-9.1: USB disconnect, device number 3
[56342.242389] uvcvideo 2-9.1:1.1: Failed to set UVC commit control : -110 
(exp. 26).
[56342.244294] usb 2-9.3: USB disconnect, device number 4
[56342.318435] usb 1-6: USB disconnect, device number 3
[56342.318439] usb 1-6.2: USB disconnect, device number 5
[56342.318818] usb 1-6.3: USB disconnect, device number 7
[56342.318819] usb 1-6.3.1: USB disconnect, device number 10
[56342.834579] usb 1-6.3.2: USB disconnect, device number 18
[56343.343380] usb 1-6.3.5: USB disconnect, device number 14
[56343.402226] usb 1-6.3.6: USB disconnect, device number 15
[56343.402443] usb 1-6.4: USB disconnect, device number 9
[56344.099416] usb 1-10: USB disconnect, device number 4
[56344.630587] usb 1-11: USB disconnect, device number 17
[56344.630731] suunto ttyUSB0: suunto converter now disconnected from ttyUSB0
[56344.630745] usb_serial_simple 1-11:1.0: device disconnected
[56344.630867] usb 1-12: USB disconnect, device number 8
[56344.702585] usb 1-13: USB disconnect, device number 11
[56344.771041] usb 1-14: USB disconnect, device number 13


Only thing I can see then via lsusb is

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The workaround is to login to the machine via SSH (as I don't have keyboard or 
mouse working)
and reload the xhci_pci module.

$ sudo rmmod xhci_pci xhci_pci_renesas
$ sudo modprobe xhci_pci xhci_pci_renesas

Then all starts working back again

The running kernel is:
Linux drakkar 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 
20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-25-generic 6.5.0-25.25~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Apr 12 20:26:26 2024
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.d.apport: 2023-08-24T03:09:53.125138

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


** Tags: amd64 apport-bug jammy

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

Title:
  USB bus crashes when using Razer Kiyo Pro webcam

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

Bug description:
  When using camera I got often freezes of the camera input which are fixed 
after a while (2-3min) when having the videoconference with Google Meet.
  But sometimes it crashes the whole bus and all usb devices are disconnected.

  [25678.046793] usb 2-9.1: current rate 16000 is different from the runtime 
rate 48000
  [42784.602640] usb 2-9.1: current rate 16000 is different from the runtime 
rate 48000
  [44426.198611] loop40: detected capacity change from 0 to 58432
  [48209.516942] usb 2-9.1: current rate 16000 is different from the runtime 
rate 48000
  [56137.044859] usb 2-9.1: current rate 16000 is different from the runtime 
rate 48000
  [56342.242010] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command
  [56342.242037] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [56342.242093] xhci_hcd :00:14.0: HC died; cleaning up
  [56342.242149] usb 1-2: USB disconnect, device number 2
  [56342.242381] usb 2-9: USB disconnect, device number 2
  [56342.242385] usb 2-9.1: USB disconnect, device number 3
  [56342.242389] uvcvideo 2-9.1:1.1: Failed to set UVC commit control : -110 
(exp. 26).
  [56342.244294] usb 2-9.3: USB disconnect, device number 4
  [56342.318435] usb 1-6: USB disconnect, device number 3
  [563

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

2023-12-06 Thread Bartosz Woronicz
What is the cards firmware ?

$ ethtool -i  |grep firmware-version

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Details:

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

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

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

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

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

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

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

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116, 33 Sep 15 03:13 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/215602/fd/10: Permission denied
   Cannot stat file /proc/323635/fd/10: Permission denied
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: maas
  CloudName: maas
  CloudPlatform: maas
  CloudSubPlatform: seed-dir (http://10.3.4.7:5248/MAAS/metadata/)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7525
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb

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

2023-12-07 Thread Bartosz Woronicz
@Andre,

I successfully installed on the machines with NVMUpdate64 tool. That is
on HPE machines.


$ sudo ./nvmupdate64e 

Intel(R) Ethernet NVM Update Tool
NVMUpdate version 1.39.56.8
Copyright(C) 2013 - 2023 Intel Corporation.


WARNING: To avoid damage to your device, do not stop the update or reboot or 
power off the system during this update.
Inventory in progress. Please wait [**+...]


Num Description  Ver.(hex)  DevId S:BStatus
=== ==  = == ==
01) Intel(R) Ethernet Network Adapter   4.48(4.30)   159B 00:016 Up to date
E810-XXV-2 
02) Intel(R) Ethernet Network Adapter N/A(N/A)   1521 00:072 Update not
I350-T4 for OCP NIC 3.0  available 


Tool execution completed with the following status: An error occurred accessing 
the device.
Press any key to exit.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

  Details:

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

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

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

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

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

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

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

  - the switch does log that the bond is flapping
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 12 20:05 seq
   crw-rw 1 root audio 116, 33 Sep 12 20:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-08-22 (24 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7515
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=cfb5f171-77e6-4fcd-947b-52901f51b26a ro
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-83-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/27/2023
  dmi.bios.release: 2.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.12.4
  dmi.board.name: 0J91V2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.12.4:bd07/27/2023:br2.12:svnDellInc.:pnPowerEdgeR7515:pvr:rvnDellInc.:rn0J91V2:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FD;ModelName=PowerEdgeR7515:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7515
  dmi.product.sku: SKU=08FD;ModelName=PowerEdge R7515
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 15 03:13 seq
   crw-rw 1 root audio 116

[Kernel-packages] [Bug 2046003] [NEW] Weirdly behaving CPU power setting on Thinkpad X1 carbon Intel i7-10710U

2023-12-08 Thread Bartosz Woronicz
Public bug reported:

On current kernel 5.15.0-89-generic I change the setting to power, but
when I check /sys nothing happens

root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave
root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
balance_performance
root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
default performance balance_performance balance_power power 
root@graf:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 
powersave
root@graf:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor 
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave
powersave

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-89-generic 5.15.0-89.99
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  8 21:24:31 2023
InstallationDate: Installed on 2021-04-15 (967 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20R10015US
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-89-generic 
root=/dev/mapper/ubuntu-root 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.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-89-generic N/A
 linux-backports-modules-5.15.0-89-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.23
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-24 (592 days ago)
dmi.bios.date: 11/08/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2QET54W(1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20R10015US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.19
dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET54W(1.48):bd11/08/2023:br1.48:efr1.19:svnLENOVO:pn20R10015US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R10015US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20R10015US
dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot from 2023-12-08 21-21-16.png"
   
https://bugs.launchpad.net/bugs/2046003/+attachment/5727581/+files/Screenshot%20from%202023-12-08%2021-21-16.png

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

Title:
  Weirdly behaving CPU power setting on Thinkpad X1 carbon Intel
  i7-10710U

Status in linux package in Ubuntu:
  New

Bug description:
  On current kernel 5.15.0-89-generic I change the setting to power, but
  when I check /sys nothing happens

  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
  performance powersave
  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference
  balance_performance
  root@graf:~# cat 
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences
  default performance balance_performance balance_power power 
  root@graf:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor 
  powersave
  root@graf:~# cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor 
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave
  powersave

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-89-generic 5.15.0-89.99
  ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
  Uname: Linux 5.15.0-89-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  8 21:24:31 2023
  InstallationDate: Installed on 2021-04-15 (967 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20R10015US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-89-generic 
root=/dev/mapper/ubuntu-root 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.
  RelatedPackageVersi

[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device

2024-08-06 Thread Bartosz Woronicz
Hi, i encounter that issue again in Supermicro AS-2015CS-TNR

Will try to get more information

** Changed in: maas
   Status: Expired => Incomplete

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

Title:
  No boot possible - Cannot open root device

Status in MAAS:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MaaS cannot boot on my X11DPi-NT and will therefore fail to
  commission. It will instantly fail after grub.

  It will fail to boot saying that is not able to open root device. I
  even tried supplying the squashfs via python on a different port as
  the url is somehow cut off a bit, but to no avail. The python
  webserver doesn't even see any connection try.

  ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
  python webserver: python3 -m http.server 8080)

  Steps to reproduce:

  1. Setup maas ;)
  2. Try to commision server
  3. See the kernel and initrd download fly by 
  4. Boom kernel panic

  Hardware:
  Supermicro X11DPi-NT with UEFI http Networkboot enabled
  NIC: Intel X722

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1950792/+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 1950792] Re: No boot possible - Cannot open root device

2023-07-26 Thread Bartosz Woronicz
I also encountered something similar, some computes randomly are unable to boot
I may check disabling this HTTP boot

$ maas root maas get-config name=kernel_opts
Success.
Machine-readable output follows:
"console=tty0 console=ttyS0,115200n8"


** Attachment added: "Screenshot from 2023-07-26 10-43-06.png"
   
https://bugs.launchpad.net/maas/+bug/1950792/+attachment/5688544/+files/Screenshot%20from%202023-07-26%2010-43-06.png

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

Title:
  No boot possible - Cannot open root device

Status in MAAS:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  MaaS cannot boot on my X11DPi-NT and will therefore fail to
  commission. It will instantly fail after grub.

  It will fail to boot saying that is not able to open root device. I
  even tried supplying the squashfs via python on a different port as
  the url is somehow cut off a bit, but to no avail. The python
  webserver doesn't even see any connection try.

  ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
  python webserver: python3 -m http.server 8080)

  Steps to reproduce:

  1. Setup maas ;)
  2. Try to commision server
  3. See the kernel and initrd download fly by 
  4. Boom kernel panic

  Hardware:
  Supermicro X11DPi-NT with UEFI http Networkboot enabled
  NIC: Intel X722

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1950792/+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 2032338] Re: After recent update in Jammy multiple firmware missing for nouveau nvidia

2023-08-30 Thread Bartosz Woronicz
It's even worse , on that kernel  6.2.0-26 
I cannot install nvidia-drivers at all

$ ubuntu-drivers list
shows empty

I reverted back to 5.19 (5.15 does not support my hardware in terms of
Intel GPU  (from i9 13900K)

but I am not happy because I cannot use livepatch here, as it is not
currently neither generic nor hwe kernel

$ canonical-livepatch status
last check: 8 minutes ago
kernel: 5.19.0-50.50-generic
server check-in: succeeded
kernel state: ✗ kernel not supported by Canonical
patch state: ✓ no livepatches needed for this kernel yet
tier: stable
machine id: 1fa2f83955d144959cf1921667076c87

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

Title:
  After recent update in Jammy multiple firmware missing for nouveau
  nvidia

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  $ apt show linux-firmware
  Package: linux-firmware
  Version: 20220329.git681281e4-0ubuntu3.17
  Priority: optional
  Section: misc
  Origin: Ubuntu
  Maintainer: Ubuntu Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 999 MB
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Conflicts: atmel-firmware
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdragon (<= 1.2-0ubuntu1)
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-restricted-common
  Download-Size: 254 MB
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.

  N: There are 2 additional records. Please use the '-a' switch to see
  them.

  
  # update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
  cryptsetup: WARNING: swap: couldn't determine device type, assuming default 
  (plain).
  cryptsetup: WARNING: Resume target swap uses a key file
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmw

[Kernel-packages] [Bug 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

2023-08-30 Thread Bartosz Woronicz
** Summary changed:

- After recent update in Jammy multiple firmware missing for nouveau nvidia
+ HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

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

Title:
  HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  $ apt show linux-firmware
  Package: linux-firmware
  Version: 20220329.git681281e4-0ubuntu3.17
  Priority: optional
  Section: misc
  Origin: Ubuntu
  Maintainer: Ubuntu Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 999 MB
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Conflicts: atmel-firmware
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdragon (<= 1.2-0ubuntu1)
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-restricted-common
  Download-Size: 254 MB
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.

  N: There are 2 additional records. Please use the '-a' switch to see
  them.

  
  # update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
  cryptsetup: WARNING: swap: couldn't determine device type, assuming default 
  (plain).
  cryptsetup: WARNING: Resume target swap uses a key file
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for 
module nouveau
  W: Possible mis

[Kernel-packages] [Bug 2032338] Re: HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

2023-09-01 Thread Bartosz Woronicz
on the recent 6.2.0-31 all seems fine

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

Title:
  HWE kernel 6.2.0 nouveau and nvidia drivers does not work (RTX 3060)

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  $ apt show linux-firmware
  Package: linux-firmware
  Version: 20220329.git681281e4-0ubuntu3.17
  Priority: optional
  Section: misc
  Origin: Ubuntu
  Maintainer: Ubuntu Kernel Team 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 999 MB
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Conflicts: atmel-firmware
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdragon (<= 1.2-0ubuntu1)
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-restricted-common
  Download-Size: 254 MB
  APT-Manual-Installed: yes
  APT-Sources: http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.

  N: There are 2 additional records. Please use the '-a' switch to see
  them.

  
  # update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic
  cryptsetup: WARNING: swap: couldn't determine device type, assuming default 
  (plain).
  cryptsetup: WARNING: Resume target swap uses a key file
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_ahesasc.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_asb.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/acr/ucode_unload.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga102/nvdec/scrubber.bin 
for module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga107/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga106/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/gpccs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_sig.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga104/gr/fecs_bl.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga103/gr/NET_img.bin for 
module nouveau
  W: Possible missing firmware /lib/firmware/nvidia/ga

[Kernel-packages] [Bug 2085520] [NEW] Sennheiser Momentum 3 loses sound from time to time

2024-10-24 Thread Bartosz Woronicz
Public bug reported:

>From time to time my headphones loses sound I had to switch the coded to 
>another one and back then I got sound back. 
The Ubuntu is 24.04.

Also I have problem that switching from Handsfree mode takes very long
(over 10s after closing the source of the call). Then Headset mode will
not appear.

I know that might be to the poor implementation of the bt protocol
stack, as my other headphones like  Sony WF-1000XM5 work flawlessly. Yet
maybe we could workaround that.

In the logs I can see:

[   38.289943] nvidia-nvlink: Unregistered Nvlink Core, major device number 508
[   38.832629] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   38.832632] Bluetooth: BNEP filters: protocol multicast
[   38.832635] Bluetooth: BNEP socket layer initialized
[   38.833670] Bluetooth: MGMT ver 1.22
[   38.835604] NET: Registered PF_ALG protocol family
[   38.864528] Bluetooth: RFCOMM TTY layer initialized
[   38.864537] Bluetooth: RFCOMM socket layer initialized
[   38.864540] Bluetooth: RFCOMM ver 1.11
[   43.330037] NOHZ tick-stop error: local softirq work is pending, handler 
#40!!!
[   62.341826] overlayfs: missing 'lowerdir'
[   64.118370] evm: overlay not supported
[   64.183442] Initializing XFRM netlink socket
[   72.115883] usb 2-2: current rate 16000 is different from the runtime rate 
48000
[   84.853403] lxdbr0: port 4(taped3c5c12) entered blocking state
[   84.853409] lxdbr0: port 4(taped3c5c12) entered disabled state
[   84.853424] taped3c5c12: entered allmulticast mode
[   84.853468] taped3c5c12: entered promiscuous mode
[   84.948340] lxdbr0: port 4(taped3c5c12) entered blocking state
[   84.948343] lxdbr0: port 4(taped3c5c12) entered forwarding state
[   85.655899] mpbr0: port 1(tapefc1ee6a) entered blocking state
[   85.655903] mpbr0: port 1(tapefc1ee6a) entered disabled state
[   85.655916] tapefc1ee6a: entered allmulticast mode
[   85.655948] tapefc1ee6a: entered promiscuous mode
[   85.820240] mpbr0: port 1(tapefc1ee6a) entered blocking state
[   85.820248] mpbr0: port 1(tapefc1ee6a) entered forwarding state
[   94.272004] Bluetooth: hci0: SCO packet for unknown connection handle 257
[   94.595188] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input29
[  135.366386] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
[  333.439217] loop81: detected capacity change from 0 to 26328
[  379.947981] NOHZ tick-stop error: local softirq work is pending, handler 
#81!!!
[  394.698913] NOHZ tick-stop error: local softirq work is pending, handler 
#01!!!
[  436.255845] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
[  929.184361] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
[  929.211082] NOHZ tick-stop error: local softirq work is pending, handler 
#10!!!
[ 6050.862825] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input30

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

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

** Description changed:

- From time to time my headphones loses sound I had to switch the coded to
- another one and back then I got sound back.
+ From time to time my headphones loses sound I had to switch the coded to 
another one and back then I got sound back. 
+ The Ubuntu is 24.04.
  
  Also I have problem that switching from Handsfree mode takes very long
  (over 10s after closing the source of the call). Then Headset mode will
  not appear.
  
  I know that might be to the poor implementation of the bt protocol
  stack, as my other headphones like  Sony WF-1000XM5 work flawlessly. Yet
  maybe we could workaround that.
  
  In the logs I can see:
  
  [   38.289943] nvidia-nvlink: Unregistered Nvlink Core, major device number 
508
  [   38.832629] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   38.832632] Bluetooth: BNEP filters: protocol multicast
  [   38.832635] Bluetooth: BNEP socket layer initialized
  [   38.833670] Bluetooth: MGMT ver 1.22
  [   38.835604] NET: Registered PF_ALG protocol family
  [   38.864528] Bluetooth: RFCOMM TTY layer initialized
  [   38.864537] Bluetooth: RFCOMM socket layer initialized
  [   38.864540] Bluetooth: RFCOMM ver 1.11
  [   43.330037] NOHZ tick-stop error: local softirq work is pending, handler 
#40!!!
  [   62.341826] overlayfs: missing 'lowerdir'
  [   64.118370] evm: overlay not supported
  [   64.183442] Initializing XFRM netlink socket
  [   72.115883] usb 2-2: current rate 16000 is different from the runtime rate 
48000
  [   84.853403] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.853409] lxdbr0: port 4(taped3c5c12) entered disabled state
  [   84.853424] taped3c5c12: entered allmulticast mode
  [   84.853468] taped3c5c12: entered promiscuous mode
  [   84.948340] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.948343] lxdbr0: port 4(taped3c5c12) entered forwarding state
  [   85.655899] mpbr0: port 1(tapefc1ee6a) entered blocking

[Kernel-packages] [Bug 2085520] Re: Sennheiser Momentum 3 loses sound from time to time

2024-10-24 Thread Bartosz Woronicz
I uploaded sosreport with
  
   sudo sos report -a --all-logs --case-id=2085520 --upload --batch

I hope you got it


```
Your sosreport has been generated and saved in:
/tmp/sosreport-drakkar-2085520-2024-10-24-fntenns.tar.xz

 Size   171.21MiB
 Owner  root
 sha256 384377438b825356eb2ce3034bc20639856f10255833dd17632ac3daa798e365

Please send this file to your support representative.

Attempting upload to Canonical Support File Server
Uploaded archive successfully
```

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

Title:
  Sennheiser Momentum 3 loses sound from time to time

Status in bluez package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  New

Bug description:
  From time to time my headphones loses sound I had to switch the coded to 
another one and back then I got sound back. 
  The Ubuntu is 24.04.

  Also I have problem that switching from Handsfree mode takes very long
  (over 10s after closing the source of the call). Then Headset mode
  will not appear.

  I know that might be to the poor implementation of the bt protocol
  stack, as my other headphones like  Sony WF-1000XM5 work flawlessly.
  Yet maybe we could workaround that.

  In the logs I can see:

  [   38.289943] nvidia-nvlink: Unregistered Nvlink Core, major device number 
508
  [   38.832629] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   38.832632] Bluetooth: BNEP filters: protocol multicast
  [   38.832635] Bluetooth: BNEP socket layer initialized
  [   38.833670] Bluetooth: MGMT ver 1.22
  [   38.835604] NET: Registered PF_ALG protocol family
  [   38.864528] Bluetooth: RFCOMM TTY layer initialized
  [   38.864537] Bluetooth: RFCOMM socket layer initialized
  [   38.864540] Bluetooth: RFCOMM ver 1.11
  [   43.330037] NOHZ tick-stop error: local softirq work is pending, handler 
#40!!!
  [   62.341826] overlayfs: missing 'lowerdir'
  [   64.118370] evm: overlay not supported
  [   64.183442] Initializing XFRM netlink socket
  [   72.115883] usb 2-2: current rate 16000 is different from the runtime rate 
48000
  [   84.853403] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.853409] lxdbr0: port 4(taped3c5c12) entered disabled state
  [   84.853424] taped3c5c12: entered allmulticast mode
  [   84.853468] taped3c5c12: entered promiscuous mode
  [   84.948340] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.948343] lxdbr0: port 4(taped3c5c12) entered forwarding state
  [   85.655899] mpbr0: port 1(tapefc1ee6a) entered blocking state
  [   85.655903] mpbr0: port 1(tapefc1ee6a) entered disabled state
  [   85.655916] tapefc1ee6a: entered allmulticast mode
  [   85.655948] tapefc1ee6a: entered promiscuous mode
  [   85.820240] mpbr0: port 1(tapefc1ee6a) entered blocking state
  [   85.820248] mpbr0: port 1(tapefc1ee6a) entered forwarding state
  [   94.272004] Bluetooth: hci0: SCO packet for unknown connection handle 257
  [   94.595188] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input29
  [  135.366386] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
  [  333.439217] loop81: detected capacity change from 0 to 26328
  [  379.947981] NOHZ tick-stop error: local softirq work is pending, handler 
#81!!!
  [  394.698913] NOHZ tick-stop error: local softirq work is pending, handler 
#01!!!
  [  436.255845] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.
  [  929.184361] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
  [  929.211082] NOHZ tick-stop error: local softirq work is pending, handler 
#10!!!
  [ 6050.862825] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2085520/+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 2085520] Re: Sennheiser Momentum 3 loses sound from time to time

2024-10-29 Thread Bartosz Woronicz
I added this option to pipewire.conf and seems work much better right
now

tail -1 /etc/pipewire/pipewire.conf 
module-allow-priority = false

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

Title:
  Sennheiser Momentum 3 loses sound from time to time

Status in bluez package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  New

Bug description:
  From time to time my headphones loses sound I had to switch the coded to 
another one and back then I got sound back. 
  The Ubuntu is 24.04.

  Also I have problem that switching from Handsfree mode takes very long
  (over 10s after closing the source of the call). Then Headset mode
  will not appear.

  I know that might be to the poor implementation of the bt protocol
  stack, as my other headphones like  Sony WF-1000XM5 work flawlessly.
  Yet maybe we could workaround that.

  In the logs I can see:

  [   38.289943] nvidia-nvlink: Unregistered Nvlink Core, major device number 
508
  [   38.832629] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   38.832632] Bluetooth: BNEP filters: protocol multicast
  [   38.832635] Bluetooth: BNEP socket layer initialized
  [   38.833670] Bluetooth: MGMT ver 1.22
  [   38.835604] NET: Registered PF_ALG protocol family
  [   38.864528] Bluetooth: RFCOMM TTY layer initialized
  [   38.864537] Bluetooth: RFCOMM socket layer initialized
  [   38.864540] Bluetooth: RFCOMM ver 1.11
  [   43.330037] NOHZ tick-stop error: local softirq work is pending, handler 
#40!!!
  [   62.341826] overlayfs: missing 'lowerdir'
  [   64.118370] evm: overlay not supported
  [   64.183442] Initializing XFRM netlink socket
  [   72.115883] usb 2-2: current rate 16000 is different from the runtime rate 
48000
  [   84.853403] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.853409] lxdbr0: port 4(taped3c5c12) entered disabled state
  [   84.853424] taped3c5c12: entered allmulticast mode
  [   84.853468] taped3c5c12: entered promiscuous mode
  [   84.948340] lxdbr0: port 4(taped3c5c12) entered blocking state
  [   84.948343] lxdbr0: port 4(taped3c5c12) entered forwarding state
  [   85.655899] mpbr0: port 1(tapefc1ee6a) entered blocking state
  [   85.655903] mpbr0: port 1(tapefc1ee6a) entered disabled state
  [   85.655916] tapefc1ee6a: entered allmulticast mode
  [   85.655948] tapefc1ee6a: entered promiscuous mode
  [   85.820240] mpbr0: port 1(tapefc1ee6a) entered blocking state
  [   85.820248] mpbr0: port 1(tapefc1ee6a) entered forwarding state
  [   94.272004] Bluetooth: hci0: SCO packet for unknown connection handle 257
  [   94.595188] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input29
  [  135.366386] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
  [  333.439217] loop81: detected capacity change from 0 to 26328
  [  379.947981] NOHZ tick-stop error: local softirq work is pending, handler 
#81!!!
  [  394.698913] NOHZ tick-stop error: local softirq work is pending, handler 
#01!!!
  [  436.255845] FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.
  [  929.184361] NOHZ tick-stop error: local softirq work is pending, handler 
#200!!!
  [  929.211082] NOHZ tick-stop error: local softirq work is pending, handler 
#10!!!
  [ 6050.862825] input: MOMENTUM 3 (AVRCP) as /devices/virtual/input/input30

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2085520/+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 2072651] Re: RED ERROR profiles/sap/server.c:sap_server_register() Sap driver initialization failed.

2024-11-24 Thread Bartosz Woronicz
*** This bug is a duplicate of bug 2072605 ***
https://bugs.launchpad.net/bugs/2072605

I have similar symptom

-- Boot eae21136928345238f36ceb7e6286634 --
Aug 20 09:15:40 drakkar systemd[1]: Starting Bluetooth service...
Aug 20 09:15:40 drakkar bluetoothd[3008]: Bluetooth daemon 5.64
Aug 20 09:15:40 drakkar systemd[1]: Started Bluetooth service.
Aug 20 09:15:40 drakkar bluetoothd[3008]: Starting SDP server
Aug 20 09:15:40 drakkar bluetoothd[3008]: Bluetooth management interface 1.22 
initialized
Aug 20 09:15:41 drakkar bluetoothd[3008]: Player registered: sender=:1.45 
path=/media_player0
Aug 20 09:15:41 drakkar bluetoothd[3008]: Endpoint registered: sender=:1.45 
path=/MediaEndpoint/A2DPSource/ldac
Aug 20 09:15:41 drakkar bluetoothd[3008]: Endpoint registered: sender=:1.45 
path=/MediaEndpoint/A2DPSink/sbc
Aug 20 09:15:41 drakkar bluetoothd[3008]: Endpoint registered: sender=:1.45 
path=/MediaEndpoint/A2DPSource/sbc
Aug 20 09:15:41 drakkar bluetoothd[3008]: Endpoint registered: sender=:1.45 
path=/MediaEndpoint/A2DPSink/sbc_xq
...skipping...
Nov 23 01:59:40 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/opus_05
Nov 23 01:59:40 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/opus_05_duplex
Nov 23 01:59:40 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/opus_05_duplex
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/ldac
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/aptx_hd
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_hd
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/aptx
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/sbc
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/sbc
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/sbc_xq
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/sbc_xq
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_ll_1
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_ll_0
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/faststream
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/faststream_duplex
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/opus_05
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/opus_05
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/opus_05_duplex
Nov 23 12:21:58 drakkar bluetoothd[27813]: Endpoint unregistered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/opus_05_duplex
Nov 23 12:21:58 drakkar bluetoothd[27813]: Battery Provider Manager destroyed
Nov 23 12:22:00 drakkar bluetoothd[27813]: Battery Provider Manager created
Nov 23 12:22:00 drakkar bluetoothd[27813]: 
profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Nov 23 12:22:00 drakkar bluetoothd[27813]: sap-server: Operation not permitted 
(1)
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/ldac
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/aptx_hd
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx_hd
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/aptx
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/aptx
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/sbc
Nov 23 12:22:00 drakkar bluetoothd[27813]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/sbc

Then I restart and it works but I got errors in the log

-- Boot 81555350be7142d89a95fbd6b142fa18 --
Nov 24 23:49:40 drakkar systemd[1]:

[Kernel-packages] [Bug 2085520] Re: Sennheiser Momentum 3 loses sound from time to time

2025-04-07 Thread Bartosz Woronicz
This seesm to be caused by other device like phone owning the output and
the implementation by Sennheiser is particually deficient in some what

If I list all UUIDs the proper output seems to be there

[MOMENTUM 3]# info 00:1B:66:E9:99:8F
Device 00:1B:66:E9:99:8F (public)
Name: MOMENTUM 3
Alias: MOMENTUM 3
Class: 0x00240404 (2360324)
Icon: audio-headset
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: SENNHEISER electronic G.. (fdce--1000-8000-00805f9b34fb)
UUID: Amazon.com Services, Inc. (fe03--1000-8000-00805f9b34fb)
UUID: Tile, Inc.(feec--1000-8000-00805f9b34fb)
UUID: Tile, Inc.(feed--1000-8000-00805f9b34fb)
UUID: Vendor specific   (1ddce62a-ecb1-4455-8153-0743c87aec9f)
UUID: Vendor specific   (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
Modalias: bluetooth:v0494p0046d8003
RSSI: 0xffd2 (-46)
TxPower: 0xffd8 (-40)
Battery Percentage: 0x28 (40)


yes the bluetooth audio card show only hands free

Card #106
Name: bluez_card.00_1B_66_E9_99_8F
Driver: module-bluez5-device.c
Owner Module: n/a
Properties:
api.bluez5.address = "00:1B:66:E9:99:8F"
api.bluez5.class = "0x240404"
api.bluez5.connection = "disconnected"
api.bluez5.device = ""
api.bluez5.icon = "audio-headset"
api.bluez5.id = "3"
api.bluez5.path = "/org/bluez/hci0/dev_00_1B_66_E9_99_8F"
bluez5.profile = "off"
device.alias = "MOMENTUM 3"
device.api = "bluez5"
device.bus = "bluetooth"
device.description = "MOMENTUM 3"
device.form_factor = "headset"
device.icon_name = "audio-headset-bluetooth"
device.name = "bluez_card.00_1B_66_E9_99_8F"
device.product.id = "0x0046"
device.string = "00:1B:66:E9:99:8F"
device.vendor.id = "bluetooth:0494"
media.class = "Audio/Device"
factory.id = "14"
client.id = "32"
object.id = "75"
object.serial = "106"
Profiles:
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
headset-head-unit: Headset Head Unit (HSP/HFP) (sinks: 1, 
sources: 1, priority: 1, available: yes)
headset-head-unit-cvsd: Headset Head Unit (HSP/HFP, codec CVSD) 
(sinks: 1, sources: 1, priority: 2, available: yes)
headset-head-unit-msbc: Headset Head Unit (HSP/HFP, codec mSBC) 
(sinks: 1, sources: 1, priority: 3, available: yes)
Active Profile: headset-head-unit-msbc
Ports:
headset-hf-input: Handsfree (type: Headset, priority: 0, 
latency offset: 0 usec, available)
Properties:
port.type = "headset"
Part of profile(s): headset-head-unit, 
headset-head-unit-cvsd, headset-head-unit-msbc
headset-hf-output: Handsfree (type: Headset, priority: 0, 
latency offset: 0 usec, available)
Properties:
port.type = "headset"
Part of profile(s): headset-head-unit, 
headset-head-unit-cvsd, headset-head-unit-msbc


If I reconnect the audio profiles reappear

Card #209
Name: bluez_card.00_1B_66_E9_99_8F
Driver: module-bluez5-device.c
Owner Module: n/a
Properties:
api.bluez5.address = "00:1B:66:E9:99:8F"
api.bluez5.class = "0x240404"
api.bluez5.connection = "disconnected"
api.bluez5.device = ""
api.bluez5.icon = "audio-headset"
api.bluez5.id = "3"
api.blue

[Kernel-packages] [Bug 2098014] Re: spice-vdagent seems not to be working in jammy when connecting from noble

2025-04-11 Thread Bartosz Woronicz
This is weird that generic kernel 5.15 does not have this driver
compiled


root@desktop-jammy:~# dpkg -S virtio-gpu.ko
linux-modules-6.8.0-57-generic: 
/lib/modules/6.8.0-57-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko


root@desktop-jammy:~# apt search linux-modules |grep installed

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

linux-modules-5.15.0-1073-kvm/jammy-updates,jammy-security,now 5.15.0-1073.78 
amd64 [installed,automatic]
linux-modules-6.8.0-57-generic/jammy-updates,jammy-security,now 
6.8.0-57.59~22.04.1 amd64 [installed,automatic]


Especially because the headers got the driver header file

root@desktop-jammy:~# dpkg -S virtio_gpu
linux-hwe-6.8-headers-6.8.0-57: 
/usr/src/linux-hwe-6.8-headers-6.8.0-57/include/uapi/linux/virtio_gpu.h
libgl1-mesa-dri:amd64: /usr/lib/x86_64-linux-gnu/dri/virtio_gpu_dri.so
linux-kvm-headers-5.15.0-1073: 
/usr/src/linux-kvm-headers-5.15.0-1073/include/uapi/linux/virtio_gpu.h


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

** Changed in: spice-vdagent (Ubuntu)
   Status: New => Invalid

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

Title:
  spice-vdagent seems not to be working in jammy when connecting from
  noble

Status in linux-kvm package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce

  1. Create LXD VM desktop-jammy on Ubuntu 24.04 (Noble) host
  lxc init --vm ubuntu:22.04 desktop-jammy
  2. lxc start desktop-noble
  3. lxc exec desktop-noble bash
  4. Install ubuntu-desktop metapackage
  apt update
  apt install -y ubuntu-desktop
  5. Set passwd for ubuntu user
  $ passwd ubuntu

  6. Disable systemd-networkd-wait-online.service (otherwise it will wait for 
timeout)
   systemctl disable --now systemd-networkd-wait-online.service

  7. Reboot

  8. Connect to the vga console
  lxc console --type=vga desktop-jammy
  Wait for login screen to load

  Expected result

  The GDM login menu should appear

  The actual result

  The screen is stuck.
  I saw that the daemon is not running
  root@desktop-jammy:~# systemctl status spice-vdagentd
  ○ spice-vdagentd.service - Agent daemon for Spice guests
   Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; 
vendor preset: enabled)
   Active: inactive (dead)
  TriggeredBy: ● spice-vdagentd.socket
  I started it
  root@desktop-jammy:~# systemctl start spice-vdagentd
  root@desktop-jammy:~# journalctl -u spice-vdagentd -f
  Feb 11 17:26:14 desktop-jammy systemd[1]: Starting Agent daemon for Spice 
guests...
  Feb 11 17:26:14 desktop-jammy systemd[1]: Started Agent daemon for Spice 
guests.
  root@desktop-jammy:~# systemctl status spice-vdagentd
  ● spice-vdagentd.service - Agent daemon for Spice guests
   Loaded: loaded (/lib/systemd/system/spice-vdagentd.service; indirect; 
vendor preset: enabled)
   Active: active (running) since Tue 2025-02-11 17:26:14 UTC; 9s ago
  TriggeredBy: ● spice-vdagentd.socket
  Process: 866 ExecStart=/usr/sbin/spice-vdagentd 
$SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS)
     Main PID: 867 (spice-vdagentd)
    Tasks: 2 (limit: 8872)
   Memory: 856.0K
  CPU: 6ms
   CGroup: /system.slice/spice-vdagentd.service
   └─867 /usr/sbin/spice-vdagentd

  Feb 11 17:26:14 desktop-jammy systemd[1]: Starting Agent daemon for Spice 
guests...
  Feb 11 17:26:14 desktop-jammy systemd[1]: Started Agent daemon for Spice 
guests.

  but still when I retry connecting to vga console the screen is stuck on 
loading and shows nothing
  When you check the systemd status it says
  root@desktop-jammy:~# systemd-analyze 
  Startup finished in 428ms (kernel) + 7.285s (userspace) = 7.713s 
  graphical.target reached after 7.141s in userspace

  When you try the same for ubuntu:24.04 all works as expected and you
  also see the system logs on loading before seeing the Login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: spice-vdagent 0.22.1-1
  ProcVersionSignature: Ubuntu 5.15.0-1073.78-kvm 5.15.168
  Uname: Linux 5.15.0-1073-kvm x86_64
  ApportVersion: 2.20.11-0ubuntu82.6
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  Date: Tue Feb 11 17:28:08 2025
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2107548] [NEW] igc driver does not survive ram suspend on hwe-6.11

2025-04-17 Thread Bartosz Woronicz
Public bug reported:

When resuming from ram suspend the the 2.5Gb Intel built-in card does not work 
(I-226V)
```
$ lspci |grep Ethernet
07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 
06)
```

```
mastier@drakkar:~$ sudo ip l sh eno1
23: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
altname enp7s0
mastier@drakkar:~$ sudo ip l s l dev eno1 up
RTNETLINK answers: No such device
mastier@drakkar:~$ sudo ip l sh eno1
23: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
altname enp7s0
```

The fix is re-insert module

```
[ 2687.927233] igc :07:00.0 eno1: PHC removed
[ 2692.020030] igc :07:00.0: PTM enabled, 4ns granularity
[ 2692.048418] igc :07:00.0 (unnamed net_device) (uninitialized): PHC added
[ 2692.073239] igc :07:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s 
PCIe x1 link)
[ 2692.073250] igc :07:00.0 eth0: MAC: a0:36:bc:ac:f6:8a
[ 2692.076482] igc :07:00.0 eno1: renamed from eth0
[ 2695.587200] igc :07:00.0 eno1: NIC Link is Up 2500 Mbps Full Duplex, 
Flow Control: RX
[ 6041.407826] igc :07:00.0 eno1: PHC removed
[ 6060.445029] igc :07:00.0: PTM enabled, 4ns granularity
[ 6060.473313] igc :07:00.0 (unnamed net_device) (uninitialized): PHC added
[ 6060.500429] igc :07:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 GT/s 
PCIe x1 link)
[ 6060.500444] igc :07:00.0 eth0: MAC: a0:36:bc:ac:f6:8a
[ 6060.504291] igc :07:00.0 eno1: renamed from eth0
[ 6063.991791] igc :07:00.0 eno1: NIC Link is Up 2500 Mbps Full Duplex, 
Flow Control: RX
```

After that it works back again

```
20: eno1:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
altname enp7s0
inet 192.168.101.153/24 brd 192.168.101.255 scope global dynamic 
noprefixroute eno1
   valid_lft 86359sec preferred_lft 86359sec
inet6 fe80::a236:bcff:feac:f68a/64 scope link 
   valid_lft forever preferred_lft forever
```

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.11.0-21-generic 6.11.0-21.21~24.04.1+1
ProcVersionSignature: Ubuntu 6.11.0-21.21~24.04.1-generic 6.11.11
Uname: Linux 6.11.0-21-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 17 11:27:12 2025
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_1mwuiv@/vmlinuz-6.11.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_1mwuiv ro init_on_alloc=0 intel_iommu=on iommu=pt 
vfio-pci.ids=10de:2504,10de:228e modprobe.blacklist=nouveau 
modprobe.blacklist=nvidia quiet
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.11.0-21-generic N/A
 linux-backports-modules-6.11.0-21-generic  N/A
 linux-firmware 20240318.git3b128b60-0ubuntu2.11
SourcePackage: linux-hwe-6.11
UpgradeStatus: Upgraded to noble on 2024-09-05 (224 days ago)
dmi.bios.date: 10/30/2024
dmi.bios.release: 18.5
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1805
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z790-A WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1805:bd10/30/2024:br18.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-AWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
mtime.conffile..etc.logrotate.d.apport: 2023-08-24T03:09:53.125138

** Affects: linux-hwe-6.11 (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-hwe-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2107548

Title:
  igc driver does not survive ram suspend on hwe-6.11

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

Bug description:
  When resuming from ram suspend the the 2.5Gb Intel built-in card does not 
work (I-226V)
  ```
  $ lspci |grep Ethernet
  07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V 
(rev 06)
  ```

  ```
  mastier@drakkar:~$ sudo ip l sh eno1
  23: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT 
group default qlen 1000
  link/ether a0:36:bc:

[Kernel-packages] [Bug 2107548] Re: igc driver does not survive ram suspend on hwe-6.11

2025-05-13 Thread Bartosz Woronicz
@Eduardo thanks I tried install all *.deb from the archive you shared but no 
luck
Seems I am missing some packages there in your archive

$ sudo dpkg -i *.deb
Selecting previously unselected package linux-buildinfo-6.11.0-26-generic.
(Reading database ... 304887 files and directories currently installed.)
Preparing to unpack 
linux-buildinfo-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb 
...
Unpacking linux-buildinfo-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-cloud-tools-6.11.0-26-generic.
Preparing to unpack 
linux-cloud-tools-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-cloud-tools-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-headers-6.11.0-26-generic.
Preparing to unpack 
linux-headers-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb ...
Unpacking linux-headers-6.11.0-26-generic (6.11.0-26.26~24.04.1eca01LP2107548) 
...


Selecting previously unselected package 
linux-hwe-6.11-lib-rust-6.11.0-26-generic.
Preparing to unpack 
linux-hwe-6.11-lib-rust-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-hwe-6.11-lib-rust-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-image-unsigned-6.11.0-26-generic.
Preparing to unpack 
linux-image-unsigned-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-image-unsigned-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-6.11.0-26-generic.
Preparing to unpack 
linux-modules-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb ...
Unpacking linux-modules-6.11.0-26-generic (6.11.0-26.26~24.04.1eca01LP2107548) 
...
Selecting previously unselected package linux-modules-extra-6.11.0-26-generic.
Preparing to unpack 
linux-modules-extra-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-extra-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-ipu6-6.11.0-26-generic.
Preparing to unpack 
linux-modules-ipu6-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-ipu6-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-ipu7-6.11.0-26-generic.
Preparing to unpack 
linux-modules-ipu7-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-ipu7-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-iwlwifi-6.11.0-26-generic.
Preparing to unpack 
linux-modules-iwlwifi-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-iwlwifi-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-usbio-6.11.0-26-generic.
Preparing to unpack 
linux-modules-usbio-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-usbio-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-modules-vision-6.11.0-26-generic.
Preparing to unpack 
linux-modules-vision-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb
 ...
Unpacking linux-modules-vision-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Selecting previously unselected package linux-tools-6.11.0-26-generic.
Preparing to unpack 
linux-tools-6.11.0-26-generic_6.11.0-26.26~24.04.1eca01LP2107548_amd64.deb ...
Unpacking linux-tools-6.11.0-26-generic (6.11.0-26.26~24.04.1eca01LP2107548) ...
Setting up linux-buildinfo-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
dpkg: dependency problems prevent configuration of 
linux-cloud-tools-6.11.0-26-generic:
 linux-cloud-tools-6.11.0-26-generic depends on 
linux-hwe-6.11-cloud-tools-6.11.0-26; however:
  Package linux-hwe-6.11-cloud-tools-6.11.0-26 is not installed.

dpkg: error processing package linux-cloud-tools-6.11.0-26-generic (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of 
linux-headers-6.11.0-26-generic:
 linux-headers-6.11.0-26-generic depends on linux-hwe-6.11-headers-6.11.0-26; 
however:
  Package linux-hwe-6.11-headers-6.11.0-26 is not installed.

dpkg: error processing package linux-headers-6.11.0-26-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-hwe-6.11-lib-rust-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
Setting up linux-modules-6.11.0-26-generic (6.11.0-26.26~24.04.1eca01LP2107548) 
...
Setting up linux-modules-extra-6.11.0-26-generic 
(6.11.0-26.26~24.04.1eca01LP2107548) ...
dpkg: dependency problems prevent configuration of 
linux-tools-6.11.0-26-generic:
 linux-tools-6.11.0-26-generic depends on 

[Kernel-packages] [Bug 2107548] Re: igc driver does not survive ram suspend on hwe-6.11

2025-06-27 Thread Bartosz Woronicz
I only have bridge create by LXD, libvirtd, docker0 but none of these
are in the netplan

mastier@drakkar:~$ sudo grep -iHR bridge /etc/netplan/
mastier@drakkar:~$ echo $?
1


mastier@drakkar:~$ brctl show
bridge name bridge id   STP enabled interfaces
br-151565677dbc 8000.02428964dc22   no  
docker0 8000.02426676e6de   no  
lxdbr0  8000.00163e39b254   no  tape65db9ea
veth3d333b46
veth6f7aa874
veth86de7fd3
veth9ef379a2
vethaaf09f1d
lxdbr1  8000.00163e5ed031   no  
mpbr0   8000.00163ea087b8   no  
virbr0  8000.525400411d62   yes


Also with newer kernel no change

mastier@drakkar:~$ sudo ip l sh eno1
2: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
altname enp7s0
mastier@drakkar:~$ sudo ip l s l dev eno1 up
RTNETLINK answers: No such device
mastier@drakkar:~$ uname -r
6.11.0-28-generic

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

Title:
  igc driver does not survive ram suspend on hwe-6.11

Status in linux-hwe-6.11 package in Ubuntu:
  Incomplete
Status in linux-hwe-6.11 source package in Noble:
  Incomplete

Bug description:
  When resuming from ram suspend the the 2.5Gb Intel built-in card does not 
work (I-226V)
  ```
  $ lspci |grep Ethernet
  07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V 
(rev 06)
  ```

  ```
  mastier@drakkar:~$ sudo ip l sh eno1
  23: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT 
group default qlen 1000
  link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
  altname enp7s0
  mastier@drakkar:~$ sudo ip l s l dev eno1 up
  RTNETLINK answers: No such device
  mastier@drakkar:~$ sudo ip l sh eno1
  23: eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT 
group default qlen 1000
  link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
  altname enp7s0
  ```

  The fix is re-insert module

  ```
  [ 2687.927233] igc :07:00.0 eno1: PHC removed
  [ 2692.020030] igc :07:00.0: PTM enabled, 4ns granularity
  [ 2692.048418] igc :07:00.0 (unnamed net_device) (uninitialized): PHC 
added
  [ 2692.073239] igc :07:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 
GT/s PCIe x1 link)
  [ 2692.073250] igc :07:00.0 eth0: MAC: a0:36:bc:ac:f6:8a
  [ 2692.076482] igc :07:00.0 eno1: renamed from eth0
  [ 2695.587200] igc :07:00.0 eno1: NIC Link is Up 2500 Mbps Full Duplex, 
Flow Control: RX
  [ 6041.407826] igc :07:00.0 eno1: PHC removed
  [ 6060.445029] igc :07:00.0: PTM enabled, 4ns granularity
  [ 6060.473313] igc :07:00.0 (unnamed net_device) (uninitialized): PHC 
added
  [ 6060.500429] igc :07:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 
GT/s PCIe x1 link)
  [ 6060.500444] igc :07:00.0 eth0: MAC: a0:36:bc:ac:f6:8a
  [ 6060.504291] igc :07:00.0 eno1: renamed from eth0
  [ 6063.991791] igc :07:00.0 eno1: NIC Link is Up 2500 Mbps Full Duplex, 
Flow Control: RX
  ```

  After that it works back again

  ```
  20: eno1:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether a0:36:bc:ac:f6:8a brd ff:ff:ff:ff:ff:ff
  altname enp7s0
  inet 192.168.101.153/24 brd 192.168.101.255 scope global dynamic 
noprefixroute eno1
 valid_lft 86359sec preferred_lft 86359sec
  inet6 fe80::a236:bcff:feac:f68a/64 scope link 
 valid_lft forever preferred_lft forever
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.11.0-21-generic 6.11.0-21.21~24.04.1+1
  ProcVersionSignature: Ubuntu 6.11.0-21.21~24.04.1-generic 6.11.11
  Uname: Linux 6.11.0-21-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 17 11:27:12 2025
  MachineType: ASUS System Product Name
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_1mwuiv@/vmlinuz-6.11.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_1mwuiv ro init_on_alloc=0 intel_iommu=on iommu=pt 
vfio-pci.ids=10de:2504,10de:228e modprobe.blacklist=nouveau 
modprobe.blacklist=nvidia quiet
  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.11.0-21-generic N/A
   linux-backports-modules-6.11.0-21-gen