apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2166710/+attachment/5999083/+files/AudioDevicesInUse.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166710 Title: choppy audio 2 channel music files Status in linux package in Ubuntu: Incomplete Bug description: Music files played with any player comes out choppy, hesitates stops. Videos or streaming (youtube netfilx etc) work fine. If I boot to earlier version - 22.1 no problem. Zorin is bad too! The GPU is a 9070xt 16gb via hdmi. [code] System: Kernel: 7.0.0-31-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required> Mobo: ASUSTeK model: ROG STRIX X870E-E GAMING WIFI v: Rev 1.xx serial: <superuser required> part-nu: SKU uuid: <superuser required> UEFI: American Megatrends v: 2402 date: 07/13/2026 Battery: Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: discharging Device-2: hidpp_battery_1 model: Logitech K350 serial: <filter> charge: 50% (should be ignored) rechargeable: yes status: N/A CPU: Info: 16-core model: AMD Ryzen 9 9950X bits: 64 type: MT MCP MCM smt: enabled arch: N/A rev: 0 cache: L1: 1.2 MiB L2: 16 MiB L3: 64 MiB Speed (MHz): avg: 1425 high: 5734 min/max: 624/5756 boost: enabled cores: 1: 2867 2: 624 3: 624 4: 5734 5: 5709 6: 624 7: 624 8: 624 9: 624 10: 3629 11: 624 12: 624 13: 624 14: 624 15: 624 16: 624 17: 624 18: 624 19: 624 20: 5731 21: 5730 22: 624 23: 624 24: 624 25: 624 26: 624 27: 624 28: 624 29: 624 30: 624 31: 624 32: 624 bogomips: 274697 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD vendor: ASRock driver: amdgpu v: kernel pcie: speed: 32 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:7550 class-ID: 0300 Device-2: AMD vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5, HDMI-A-2, Writeback-2 bus-ID: 7c:00.0 chip-ID: 1002:13c0 class-ID: 0300 temp: 46.0 C Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 9-2:3 chip-ID: 046d:082d class-ID: 0102 serial: <filter> Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1280x720 s-dpi: 96 s-size: 339x191mm (13.35x7.52") s-diag: 389mm (15.32") Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: marantz-AVR serial: <filter> res: 1280x720 hz: 60 dpi: 17 size: 1872x1053mm (73.7x41.46") diag: 1630mm (64.2") modes: max: 3840x2160 min: 720x400 API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.8-0ubuntu0.24.04.2 glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 9070 XT (radeonsi gfx1201 LLVM 20.1.2 DRM 3.64 7.0.0-31-generic) device-ID: 1002:7550 API: Vulkan v: 1.3.275 layers: 3 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: N/A device-ID: 1002:7550 device: 1 type: integrated-gpu driver: N/A device-ID: 1002:13c0 device: 2 type: cpu driver: N/A device-ID: 10005:0000 Audio: Device-1: AMD driver: snd_hda_intel v: kernel pcie: speed: 32 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab40 class-ID: 0403 Device-2: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 7c:00.1 chip-ID: 1002:1640 class-ID: 0403 Device-3: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-6:6 chip-ID: 0b05:1b9b class-ID: 0300 Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 9-2:3 chip-ID: 046d:082d class-ID: 0102 serial: <filter> API: ALSA v: k7.0.0-31-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Network: Device-1: MEDIATEK vendor: Foxconn driver: N/A pcie: speed: 8 GT/s lanes: 1 port: N/A bus-ID: 0c:00.0 chip-ID: 14c3:7927 class-ID: 0280 Device-2: Realtek vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 8 GT/s lanes: 1 port: d000 bus-ID: 0d:00.0 chip-ID: 10ec:8126 class-ID: 0200 IF: enp13s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-5.1:7 chip-ID: 0b05:17cb class-ID: fe01 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6 sub-v: 220e hci-v: 6 rev: 15bb class-ID: 7c0104 Drives: Local Storage: total: 18.66 TiB used: 5.55 TiB (29.8%) ID-1: /dev/nvme0n1 vendor: A-Data model: SX8200PNP size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: R0906I temp: 39.9 C scheme: GPT ID-2: /dev/nvme1n1 vendor: Kingston model: SNV3S1000G size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: ETFKIN.5 temp: 46.9 C scheme: GPT ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 990 EVO Plus 2TB size: 1.82 TiB speed: 126 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QKXG7 temp: 51.9 C scheme: GPT ID-4: /dev/nvme3n1 vendor: Western Digital model: WDS100T3X0C-00SJG0 size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 111110WD temp: 55.9 C scheme: GPT ID-5: /dev/sda vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 tech: HDD rpm: 5425 serial: <filter> fw-rev: 0214 scheme: GPT ID-6: /dev/sdb vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB speed: 6.0 Gb/s tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT Partition: ID-1: / size: 915.32 GiB used: 17.13 GiB (1.9%) fs: ext4 dev: /dev/nvme3n1p2 ID-2: /boot/efi size: 199.2 MiB used: 41.9 MiB (21.0%) fs: vfat dev: /dev/nvme2n1p2 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -1 file: /swapfile USB: Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-2: 2-0:1 info: super-speed hub ports: 5 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-4: 3-1:2 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 chip-ID: 2109:2822 class-ID: 0900 Device-1: 3-1.1:5 info: Logitech Unifying Receiver type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 98mA chip-ID: 046d:c52b class-ID: 0300 Hub-5: 3-4:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 174c:2074 class-ID: 0900 Hub-6: 3-5:4 info: ASMedia ASMT2307 ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1 chip-ID: 174c:2174 class-ID: 0900 Device-1: 3-5.1:7 info: ASUSTek Broadcom BCM20702A0 Bluetooth type: Bluetooth driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 100mA chip-ID: 0b05:17cb class-ID: fe01 serial: <filter> Device-2: 3-6:6 info: ASUSTek USB Audio type: audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 8 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 0b05:1b9b class-ID: 0300 Device-3: 3-7:8 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 16mA chip-ID: 0b05:1aa6 class-ID: 0300 serial: <filter> Hub-7: 4-0:1 info: super-speed hub ports: 5 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-8: 4-1:2 info: VIA Labs USB3.1 Hub ports: 4 rev: 3.2 speed: 10 Gb/s lanes: 1 chip-ID: 2109:0822 class-ID: 0900 Hub-9: 4-4:3 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0 speed: 5 Gb/s lanes: 1 power: 8mA chip-ID: 174c:3074 class-ID: 0900 Hub-10: 4-5:4 info: ASMedia ASMT2307 ports: 4 rev: 3.2 speed: 10 Gb/s lanes: 1 chip-ID: 174c:3174 class-ID: 0900 Device-1: 4-5.3:5 info: ASMedia ASM1051E SATA 6Gb/s bridge ASM1053E ASM1153 3Gb/s ASM1153E bridge type: mass storage driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s lanes: 1 chip-ID: 174c:55aa class-ID: 0806 serial: <filter> Device-2: 4-5.4:6 info: JMicron / USA USB Mass Storage type: mass storage driver: uas interfaces: 1 rev: 3.0 speed: 5 Gb/s lanes: 1 power: 896mA chip-ID: 152d:0577 class-ID: 0806 serial: <filter> Hub-11: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-12: 6-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003 class-ID: 0900 Hub-13: 7-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-14: 8-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Hub-15: 9-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Hub-16: 9-1:2 info: Terminus Hub ports: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 100mA chip-ID: 1a40:0101 class-ID: 0900 Device-1: 9-1.1:4 info: Linux Foundation Android type: abstract (modem),CDC-data driver: cdc_acm interfaces: 2 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 1d6b:0106 class-ID: 0a00 serial: <filter> Device-2: 9-1.2:5 info: QinHeng UsbMonitor type: abstract (modem),CDC-data driver: cdc_acm interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 500mA chip-ID: 1a86:ca21 class-ID: 0a00 serial: <filter> Device-3: 9-2:3 info: Logitech HD Pro Webcam C920 type: video,audio driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s lanes: 1 power: 500mA chip-ID: 046d:082d class-ID: 0102 serial: <filter> Hub-17: 10-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003 class-ID: 0900 Hub-18: 11-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s lanes: 1 chip-ID: 1d6b:0002 class-ID: 0900 Sensors: System Temperatures: cpu: 54.0 C mobo: 44.0 C Fan Speeds (rpm): cpu: 0 GPU: device: amdgpu temp: 45.0 C device: amdgpu temp: 46.0 C mem: 66.0 C fan: 8 watts: 8.00 Repos: Packages: pm: dpkg pkgs: 1994 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/danielrichter2007-grub-customizer-noble.list 1: deb [signed-by=/etc/apt/keyrings/danielrichter2007-grub-customizer-noble.gpg] https: //ppa.launchpadcontent.net/danielrichter2007/grub-customizer/ubuntu noble main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com zena main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu noble main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu noble-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu noble-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ noble-security main restricted universe multiverse Active apt repos in: /etc/apt/sources.list.d/google-chrome.sources 1: deb [arch=amd64] https: //dl.google.com/linux/chrome-stable/deb/ stable main Info: Memory: total: 32 GiB note: est. available: 30.51 GiB used: 2.97 GiB (9.7%) Processes: 558 Power: uptime: 13m states: freeze,mem suspend: deep wakeups: 0 hibernate: disabled Init: systemd v: 255 target: graphical (5) default: graphical Compilers: gcc: 13.3.0 Client: Unknown python3.12 client inxi: 3.3.34 [/code] --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: 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 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: 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 --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-09-07 (2 days ago) InstallationMedia: Linux Mint 22.2 "Zara" - Release amd64 20250828 IwConfig: lo no wireless extensions. enp13s0 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=3b7346f3-dda3-4267-9f76-779cee3c97d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-31-generic N/A linux-backports-modules-7.0.0-31-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: zena Uname: Linux 7.0.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 07/13/2026 dmi.bios.release: 24.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2402 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X870E-E GAMING 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.:bvr2402:bd07/13/2026:br24.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX870E-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166710/+subscriptions
среда
[Bug 2166130] Re: Bluetooth Issue
Jason, we have some more recent builds of the kernel available for debugging purposes. The documentation on how to install them is here: https://wiki.ubuntu.com/Kernel/MainlineBuilds Could you follow those instructions to install the mainline 7.3 kernel and see if the problem persists? You can download it here: https://kernel.ubuntu.com/mainline/v7.3-rc1/ Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166130 Title: Bluetooth Issue Status in linux package in Ubuntu: Triaged Bug description: btintel_pcie: Lunar Lake Bluetooth controller enters error state after firmware load (regression 7.0.0-28 → 7.0.0-29) Summary Intel Bluetooth (PCI ID 8086:A876) on Lenovo Yoga 9 14ILL10 (Lunar Lake) fails to initialize on kernels 7.0.0-29-generic and 7.0.0-30 generic. The btintel_pcie driver successfully loads both firmware stages (IML and PCI transport), but the controller enters an error state during the post-firmware reset. The “alive interrupt” times out and Intel Soft Reset fails with -ETIME (-62). Bluetooth worked correctly on kernel 7.0.0-28-generic with the same firmware files. The regression was introduced in 7.0.0-29. Steps to Reproduce Boot Lenovo Yoga 9 14ILL10 (model 83LC) with kernel 7.0.0-29-generic or 7.0.0-30-generic Bluetooth controller fails to initialize — bluetoothctl show reports “No default controller available” Expected Behavior Bluetooth controller initializes successfully (as it did on kernel 7.0.0-28-generic). Actual Behavior hciconfig shows hci0 with BD Address 00:00:00:00:00:00, state DOWN, 5 TX errors. bluetoothctlcontroller available.” Driver unbind/rebind reproduces the same failure — not a transient boot issue. show reports “No default System Information Distro: Ubuntu 26.04 (Resolute) Working kernel: 7.0.0-28-generic (confirmed working Aug 2–10, 2026) Broken kernels: 7.0.0-29-generic (7.0.0-29.29) and 7.0.0-30-generic (7.0.0-30.30) Machine: Lenovo Yoga 9 2-in-1 14ILL10, model 83LC SoC: Intel Lunar Lake BIOS: Q9CN22WW (01/09/2025) BT device: PCI 8086:A876, subsystem 8086:000E Driver: btintel_pcie (in-tree, /lib/modules/7.0.0-30-generic/kernel/drivers/bluetooth/btintel_pcie.ko.zst) Firmware: intel/ibt-0190-0291-iml.sfi + intel/ibt-0190-0291-pci.sfi (Firmware Version 107-8.26) linux-firmware: 20260319.git217ca6e4.1ubuntu Kernel Log (dmesg, annotated) Stage 1 — IML firmware: SUCCESS Bluetooth: hci0: Device revision is 0 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is disabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995 Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi Bluetooth: hci0: Boot Address: 0x30098800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 60577 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 2195 usecs Bluetooth: hci0: Waiting for device transition to d0 Bluetooth: hci0: Device moved to D0 in 0 usecs Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b Stage 2 — PCI transport firmware: FAILURE Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfiBluetooth: hci0: Boot Address: 0x10000800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Received gp1 mailbox interrupt ← repeated ~36 times Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 579658 usecs ← much slower than IML stage Bluetooth: hci0: Received gp1 mailbox interrupt Bluetooth: hci0: Controller in error state ← FAILURE POINT Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Failed to send frame (-62) Bluetooth: hci0: sending frame failed (-62) Bluetooth: hci0: Failed to send Intel Reset command Bluetooth: hci0: Intel Soft Reset failed (-62) Retry attempt: SAME FAILURE Bluetooth: hci0: Firmware download retry count: 1 [...IML firmware loads again successfully...] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi Bluetooth: hci0: Firmware loaded in 1033894 usecs Bluetooth: hci0: Controller in error state Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Intel Soft Reset failed (-62) Bluetooth: hci0: Received hw exception interrupt Bluetooth: hci0: Unsupported cnvi 0x00000000 ← hardware ID unreadable Bluetooth: hci0: Controller in error state Bluetooth: hci0: Failed to read MSFT supported features (-62) Comparison — working boot on 7.0.0-28 (May 29, 2026) Bluetooth: hci0: Device booted in 35237 usecs Bluetooth: hci0: Device moved to D0 in 51 usecs Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0190-0291-pci.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware timestamp 2025.25 buildtype 1 build 95112 Bluetooth: hci0: Firmware SHA1: 0x73cbad49 Bluetooth: hci0: Fseq status: Success (0x00) Bluetooth: hci0: Fseq executed: 00.00.04.202 Bluetooth: hci0: Fseq BT Top: 00.00.04.197 Additional Context rfkill reports Bluetooth as not blocked (soft or hard) The same failure reproduces after manual driver unbind/rebind (not a race condition at boot) A systemd sleep hook (/usr/lib/systemd/system-sleep/bluetooth-wakeup-fix) unbinds/rebinds this device around s2idle to prevent spurious wakeups — this is unrelated to the failure (the failure occurs on fresh boot before any sleep cycle) Kernel 7.0.0-29-generic tested and confirmed broken — same failure as 7.0.0-30 Regression bisected to the 7.0.0-28 → 7.0.0-29 kernel transition ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jkredfoot 6048 F.... pipewire jkredfoot 6063 F.... wireplumber /dev/snd/seq: jkredfoot 6048 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 22:36:48 2026 InstallationDate: Installed on 2026-02-16 (198 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 83LC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=ff800d1a-2b21-4bc4-a94c-5194f1b6a033 ro quiet splash snd_sof.sof_debug=0x1 snd_soc_sof_sdw.dyndbg=+p crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (110 days ago) dmi.bios.date: 01/09/2025 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: Q9CN22WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 2-in-1 14ILL10 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrQ9CN22WW:bd01/09/2025:br1.22:efr1.22:svnLENOVO:pn83LC:pvrYoga92-in-114ILL10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct31:cvrYoga92-in-114ILL10:skuLENOVO_MT_83LC_BU_idea_FM_Yoga92-in-114ILL10:pfaYoga92-in-114ILL10: dmi.product.family: Yoga 9 2-in-1 14ILL10 dmi.product.name: 83LC dmi.product.sku: LENOVO_MT_83LC_BU_idea_FM_Yoga 9 2-in-1 14ILL10 dmi.product.version: Yoga 9 2-in-1 14ILL10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166130/+subscriptions
[Bug 2165844] Re: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write
Indeed, the fix commit does seem promising. It helps the kernel team to have confirmation via a test that the problem is actually fixed rather than speculating. So if Artem is able to confirm for us that the bug goes away, that should help speed up the process of getting the fix into the kernel :-) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165844 Title: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Any buffered write() to an ntfs3-mounted volume can hit a BUG_ON in the generic iomap write path and panic the kernel. An unprivileged process (rsync, uid 1000) took the whole machine down; the system froze instantly, then kdump rebooted into the capture kernel. [Impact] This is reachable from unprivileged userspace with a plain write(2) syscall. Whatever the state of the NTFS volume, the correct outcome is -EIO returned to the caller, not a kernel panic. Reproducing it needs nothing but a writable NTFS mount, which udisks/GNOME Files creates by default when a user clicks a Windows partition. [Environment] Ubuntu 26.04, linux-image-7.0.0-30-generic 7.0.0-30.30, x86_64 ASUS ROG STRIX B550-XE GAMING WIFI, BIOS 3607 NTFS volume: 1.8 TB Windows system partition, mounted read-write by udisks (driver ntfs3, POSIX ACLs enabled) [What happened] Writing to the NTFS mount, the kernel hit the assertion and died: kernel BUG at fs/iomap/buffered-io.c:1061! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 2 UID: 1000 PID: 18561 Comm: rsync Kdump: loaded Tainted: G O Hardware name: ASUS System Product Name/ROG STRIX B550-XE GAMING WIFI RIP: 0010:iomap_write_end+0x1e0/0x1f0 Call Trace: iomap_write_iter+0x171/0x340 iomap_file_buffered_write+0xa6/0x110 ntfs_file_write_iter+0x267/0x310 [ntfs3] vfs_write+0x25b/0x490 ksys_write+0x71/0xf0 __x64_sys_write+0x19/0x30 do_syscall_64+0x105/0x5a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e The faulting syscall was a 137-byte write(2) to fd 1 (ORIG_RAX 0x1, RDX 0x89) — an ordinary small buffered write, not anything exotic. The G/O taint is the out-of-tree NVIDIA module (595.84). It is unrelated to this code path; ntfs3, iomap and the write path are all in-tree. [Preceding symptom] About 14 minutes before the panic, ntfs3 logged a large burst of metadata repairs on the same volume: ntfs3(nvme0n1p2): ino=..., Correct links count -> N ntfs3: 15286 callbacks suppressed So the volume was not perfectly clean. That may well be what steers the write path into the bad state — but an inconsistent filesystem must not be able to panic the kernel, so it looks like a missing error path rather than a disk problem. [Reproducer] Not deterministic here, but the shape is simple: 1. Mount an NTFS volume read-write with ntfs3 (udisksctl mount is enough). 2. Run sustained buffered I/O against it (rsync of a large tree). The other reports linked below describe the same trace from ordinary file writes, including games writing save data. [Already reported elsewhere] Same trace, same line, on 7.0.x kernels since roughly April 2026: - https://github.com/CachyOS/linux-cachyos/issues/841 - https://discuss.cachyos.org/t/kernel-bug-in-iomap-write-end-triggered-by-ntfs3-buffered-write-linux-7-0-1-cachyos/28546 - https://bbs.archlinux.org/viewtopic.php?pid=2296728 - https://forum.manjaro.org/t/total-system-hangs-and-fs-iomap-kernel-panic-on-7-0-10-stable-on-6-18-lts/188283 I could not find an upstream fix. Upstream appears to be replacing ntfs3 with the new ntfsplus driver in 7.1 rather than fixing this one. [Suggestion for Ubuntu] Since 26.04 ships 7.0 and a user can trigger a kernel panic by copying files onto a Windows partition from the file manager, it may be worth either backporting a fix or having udisks default NTFS mounts to read-only until 7.1 lands via HWE. [Attached] Full kernel ring buffer from the kdump vmcore (VmCoreDmesg), plus the usual apport-collected hardware and package data. Sanitisation applied before upload: firewall log lines were dropped, and MAC addresses, the wireless BSSID/SSID and LAN IPv4 addresses were replaced with placeholders in VmCoreDmesg, CurrentDmesg and WifiSyslog. Nothing else was altered; the panic trace is untouched. An incomplete vmcore (2.3 GB, truncated because the machine was power-cycled during the dump) is available if it would help. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 11:45:03 2026 InstallationDate: Installed on 2026-07-12 (49 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name PackageArchitecture: amd64 ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=5778b2dd-b496-4525-b52f-223e5be557bc ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux Title: linux 7.0.0-30: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end() on ntfs3 buffered write UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 03/18/2024 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3607 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-XE GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3607:bd03/18/2024:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-XEGAMINGWIFI:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165844/+subscriptions
[Bug 2166226] Re: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30
Marc, we have some more recent builds of the kernel available for debugging purposes. The documentation on how to install them is here: https://wiki.ubuntu.com/Kernel/MainlineBuilds Could you follow those instructions to install the mainline 7.3 kernel and see if the problem persists? You can download it here: https://kernel.ubuntu.com/mainline/v7.3-rc1/ Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166226 Title: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30 Status in linux package in Ubuntu: Triaged Bug description: Ubuntu: 26.04.1 LTS Kernel: 7.0.0-30-generic, package 7.0.0-30.30 GPU: AMD Navi 23 / RX 6600 [1002:73ff], subsystem [1849:5217] Mesa: 26.0.8-1ubuntu0.3 linux-firmware: 20260319.git217ca6e4.1ubuntu The desktop first began stuttering and later stopped responding. At 16:41:37, amdgpu began reporting "Fence fallback timer expired". SysRq/NMI stack dumps repeatedly caught CPU 7 in amdgpu_device_rreg() from the display/vblank IRQ handler, while other CPUs were waiting in smp_call_function_many_cond(). AMDGPU later reported: ring sdma1 timeout, signaled seq=72398, emitted seq=72398 Starting sdma1 ring reset The reset did not complete. Repeated stack dumps for over three minutes showed the amdgpu-reset-dev worker in: amdgpu_device_rreg sdma_v5_2_stop_queue amdgpu_sdma_reset_engine sdma_v5_2_reset_queue amdgpu_job_timedout drm_sched_job_timedout Four seconds before the first amdgpu warning, an ASMedia ASM4242 USB4 bridge at 17:00.0 reported that it could not transition from D3cold to D0. This is on a different PCIe root port, so its relationship is unknown. The kernel is tainted P/O because this is a ZFS-root system using the ZFS DKMS module. The amdgpu module itself is the stock Ubuntu kernel module. Frequency: Happens pretty reliably within 24 hours of boot Recovery required: Requires hard reset USB4 activity at the time: None ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 2 17:11:37 2026 IwDevWlp16s0Link: Not connected. MachineType: Micro-Star International Co., Ltd. MS-7E70 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5ck8oa@/vmlinuz-7.0.0-30-generic root=ZFS=rpool/ROOT/ubuntu_5ck8oa ro init_on_alloc=0 nmi_watchdog=1 softlockup_panic=1 hardlockup_panic=1 crashkernel=1G crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-05 (59 days ago) dmi.bios.date: 09/24/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.A31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: PRO X870E-P WIFI (MS-7E70) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.A31:bd09/24/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E70:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX870E-PWIFI(MS-7E70):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E70 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166226/+subscriptions
[Bug 2163723] Re: btintel_pcie NULL pointer call trace during boot on Intel Bluetooth PCIe controllers
This bug is awaiting verification that the linux-oem-7.0/7.0.0-1014.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-done- resolute-linux-oem-7.0'. If the problem still exists, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-failed- resolute-linux-oem-7.0'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-oem-7.0-v2 verification-needed-resolute-linux-oem-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163723 Title: btintel_pcie NULL pointer call trace during boot on Intel Bluetooth PCIe controllers Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-7.0 source package in Resolute: Fix Committed Status in linux source package in Stonking: In Progress Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [Impact] Bluetooth call trace shows up during boot on Dell systems with Intel PCIe Bluetooth controllers (CID: F14-DVT2-C1X). It can hang the system's shutdown/boot flow. Hit rate is about 1 in 500 boots. Error log: kernel: BUG: kernel NULL pointer dereference, address: 0000000000000db0 kernel: RIP: 0010:btintel_pcie_dump_debug_registers+0x20/0x8f0 [btintel_pcie] kernel: Call Trace: kernel: ? bt_err+0x7a/0xa7 [bluetooth] kernel: btintel_pcie_irq_msix_handler+0x1a2/0x230 [btintel_pcie] kernel: irq_thread_fn+0x26/0x70 kernel: irq_thread+0xbc/0x1c0 kernel: kthread+0xf7/0x130 kernel: ret_from_fork+0x195/0x2a0 kernel: ret_from_fork_asm+0x1a/0x30 The crash hits in the MSI-X interrupt thread while dumping debug registers, and the reset/coredump path around it has several races that can corrupt driver state or drop RX events during a coredump. [Fix] Eight btintel_pcie driver fixes, in dependency order. Merged in v7.2: e43b33bf8d671 Bluetooth: btintel_pcie: Load IOSF debug regs by controller variant 2d00975c841fa Bluetooth: btintel_pcie: Support Product level reset 975a70ff0aec8 Bluetooth: btintel_pcie: Add support for smart trigger dump 4d62d88e7ae6d Bluetooth: btintel_pcie: Add 50 ms delay before MAC init on BlazarIW f70f7f2512c6b Bluetooth: btintel_pcie: Separate coredump work from RX work These add product-level reset support, smart trigger coredumps, and a timing fix for BlazarIW fast-restart, and move coredump processing off the RX workqueue so RX events don't get dropped while a coredump runs. They land ahead of the reset-path rework below. Not yet in a released kernel, merged in the bluetooth-next tree (not yet released upstream): 603b91aeb20a2 Bluetooth: btintel_pcie: Refactor FLR to use device_reprobe() ca75417ab1793 Bluetooth: btintel_pcie: split coredump worker into per-trigger works bd8bee79e1fa8 Bluetooth: btintel_pcie: serialize reset_type with RECOVERY_IN_PROGRESS These rework the reset/coredump internals: FLR now shares the same teardown/re-init path as PLDR through device_reprobe() instead of an open-coded, easy-to-desync copy; the combined coredump worker is split into three single-purpose workers (coredump, hw-exception, fw-trigger) each owning one guard bit, closing a race where a duplicate IRQ could requeue while the previous coredump was still finishing; and reset_type is now written only after the RECOVERY_IN_PROGRESS bit is won, closing a window where two concurrent hardware-error events could pick different reset types for the same recovery attempt. These 3 follow-up patches were requested directly by the ODM (Hugh Chao) after testing showed the debug-register fix alone was not enough; they close races that the ODM's stress test could still trigger. [Test Plan] Reproduce on the affected Dell platform with the Intel PCIe Bluetooth controller: Run WB (wireless/Bluetooth) stress test across repeated boot cycles (the ODM's test hit the bug at roughly 1/500 boots). Without patches: btintel_pcie_dump_debug_registers NULL pointer dereference call trace shows up in dmesg during boot, can block shutdown. With patches: no call trace, no NULL pointer dereference across repeated boot/stress cycles. ODM confirmed the 3 bluetooth-next patches fixed the issue on their test kernel. [Where problems could occur] Could break the Bluetooth btintel_pcie driver's reset and coredump paths on Intel PCIe Bluetooth controllers (Blazar and Scorpius Peak families). If the IOSF base address selection by variant is wrong for some SKU, coredump reads would return garbage instead of crashing, making register dumps useless without an obvious symptom. If the FLR-to-device_reprobe() refactor has a bug, a function-level reset could leave the Bluetooth hci device half torn down, causing btintel_pcie_probe() to fail on reprobe and BT to stay non-functional after a reset event, instead of the driver silently working around it as before. If the split coredump workers or the RECOVERY_IN_PROGRESS serialization miss a case, two reset/coredump triggers could still race, corrupting a coredump buffer or leaving a stale reset_type, which would show up as an incomplete or garbled coredump, or the wrong reset variant (FLR vs PLDR) running when a hardware error hits. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2163723/+subscriptions
[Bug 2164504] Re: Speakers not detected on HP systems with TI TAS2783 SoundWire amps
This bug is awaiting verification that the linux-oem-7.0/7.0.0-1014.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-done- resolute-linux-oem-7.0'. If the problem still exists, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-failed- resolute-linux-oem-7.0'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-oem-7.0-v2 verification-needed-resolute-linux-oem-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2164504 Title: Speakers not detected on HP systems with TI TAS2783 SoundWire amps Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux-oem-7.0 source package in Noble: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Fix Committed Bug description: [Impact] Speakers do not show up on HP systems (CID: 202512-38250) with four TAS2783 SoundWire speaker amplifiers. The audio detect_sources test fails. Error log from the test: media.class:[Audio/Source] couldn't find The machine driver's card->components string never includes "spk:tas2783" because the TAS2783 entry in sdw_utils is missing .component_name. WirePlumber/PipeWire cannot match the speaker codec, so only a Dummy Output is shown and no Speaker sink or audio source is exposed. Happens with updated BIOS that already fixes the SDCA function type. [Fix] Add the missing component_name string to the TAS2783 entry in codec_info_list in sound/soc/sdw_utils/soc_sdw_utils.c: .component_name = "tas2783", With this, card->components includes "spk:tas2783" so WirePlumber/UCM can match the codec and build the Speaker device. Upstream commit: 79bec46381942 ASoC: sdw_utils: Add missed component_name strings for TI amps Merged in Linus' tree and linux-next for v7.1 (no released tag yet). Patch: https://patch.msgid.link/20260611125359.19839-1-baojun.xu@ti.com This is one of three pieces of the full fix. The BIOS update adds the missing mipi-sdca-control-dc-value for SDCA function type. This kernel patch exposes the codec name. A separate userspace patch (alsa-ucm- conf tas2783.conf, TI PR #812) provides the UCM profile. This SRU is for the kernel piece only. [Test Plan] On a HP system with 4x TAS2783 amps, BIOS Y90 99.15.23 or newer: 1. Check the speaker codec is matched: $ wpctl status Without patch: no Speaker device, only Dummy Output. With patch: a Speaker sink appears under Audio. 2. Run the failing test: $ sudo checkbox-cli run com.canonical.certification::audio/detect_sources Without patch: fails with "media.class:[Audio/Source] couldn't find". With patch: passes. Note: full speaker playback also needs the tas2783.conf UCM profile installed. [Where problems could occur] Could break ASoC SoundWire machine setup. The change only adds a string to one codec entry, so the risk is small. If the component_name does not match the UCM profile name, the Speaker still will not be created and the test keeps failing (no worse than today). If the component matching picks up the codec with a wrong UCM profile, there could be no speaker output or wrong default audio routing after boot. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2164504/+subscriptions
[Bug 2162038] Re: [SRU] Fix incorrect GTT calculation on the APU systems
This bug is awaiting verification that the linux-oem-7.0/7.0.0-1014.14 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-done- resolute-linux-oem-7.0'. If the problem still exists, change the tag 'verification-needed-resolute-linux-oem-7.0' to 'verification-failed- resolute-linux-oem-7.0'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-oem-7.0-v2 verification-needed-resolute-linux-oem-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162038 Title: [SRU] Fix incorrect GTT calculation on the APU systems Status in linux package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Resolute: New Status in linux-oem-7.0 source package in Resolute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2162038 [ Impact ] On AMD APU systems, there are few ways to tweak memory being used by the amdgpu driver. Notably: - VRAM size can be tweaked by: UMA carveout by the BIOS/sysfs interfaces. - GTT size can be tweaked by module parameters in the TTM module. Currently, the mechanisms above works independently. However, on APU systems, because total physical memory is shared among the above and is partitioned into them, the calculation needs to take the total physical memory into account. Otherwise the driver would be double- booking physical memory, leading to issues like [1]. [ Fix ] Cherry-pick the following commit: - drm/amdgpu: cap GTT size to physical RAM on APUs[2] [ Test Plan ] - Boot into the kernel with a large non-carveout memory space (~512MB out of 64G total memory) and accordingly set a large GTT (~48GB) via the ttm module parameter (ttm.pages_limit=12582912). - Lower the non-carveout memory space in BIOS/sysfs by increasing the UMA Frame Buffer Size (VRAM) to 48GB and reboot. - The previously set GTT value (~48GB) should be capped to the non-carveout space, showing the following message: [ 5.096745] amdgpu 0000:c3:00.0: 49152M of VRAM memory ready [ 5.096753] amdgpu 0000:c3:00.0: Capping GTT to 14654M to not exceed available system memory For reference, previously it shows: [ 4.980841] amdgpu 0000:c3:00.0: 49152M of VRAM memory ready [ 4.980843] amdgpu 0000:c3:00.0: 49152M of GTT memory ready. [ Where the problems could occur ] Because the old driver is double-counting memory sizes, a user with this update may feel that memory become less, when in fact that memory is double-counted and never exists. This impacts memory calculation on GTT for APU systems. [ Additional Information ] [1] https://github.com/ROCm/ROCm/issues/6004 [2] https://lore.kernel.org/amd-gfx/20260727194207.176803-1-harkirat.gill@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162038/+subscriptions
[Bug 2166167] Re: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint
Hey Gerard, thanks for your patience. Do you remember which kernel version it last worked on? Did you recently upgrade to a new version of Ubuntu, like 24.04 Noble to 26.04 Resolute? Finding a kernel version when it last worked will help us find the code that broke so we can fix it. Let me know, thanks :-) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166167 Title: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint Status in linux package in Ubuntu: Incomplete Bug description: After resuming from suspend, USB-C DisplayPort Alt Mode stops working. The external monitor briefly wakes up on cable plug/unplug but reports "no signal". All DP connectors show "disconnected" in /sys/class/drm/. The following warning repeats in dmesg on each cable plug: WARNING: drivers/usb/typec/class.c:311 typec_altmode_update_active+0x101/0x110 [typec] ucsi_altmode_update_active+0x116/0x1b0 [typec_ucsi] ucsi_check_altmodes+0x92/0xd0 [typec_ucsi] Hardware: Thinkpad with AMD HawkPoint (Ryzen AI / 8000 series) Kernel: 7.0.0-30-generic (Ubuntu 26.04) Connector: USB-C to DisplayPort cable Workaround: none found (module reload crashes the system) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Sep 2 11:39:23 2026 InstallationDate: Installed on 2025-07-01 (428 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: LENOVO 21ME000RFR ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (85 days ago) dmi.bios.date: 05/21/2026 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: R2LET41W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 21ME000RFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR2LET41W(1.22):bd05/21/2026:br1.22:efr1.13:svnLENOVO:pn21ME000RFR:pvrThinkPadP14sGen5AMD:rvnLENOVO:rn21ME000RFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21ME_BU_Think_FM_ThinkPadP14sGen5AMD:pfaThinkPadP14sGen5AMD: dmi.product.family: ThinkPad P14s Gen 5 AMD dmi.product.name: 21ME000RFR dmi.product.sku: LENOVO_MT_21ME_BU_Think_FM_ThinkPad P14s Gen 5 AMD dmi.product.version: ThinkPad P14s Gen 5 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166167/+subscriptions
[Bug 2166226] Re: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30
Thanks, Marc. This sounds like it could be a regression in the Ubuntu kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166226 Title: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30 Status in linux package in Ubuntu: Triaged Bug description: Ubuntu: 26.04.1 LTS Kernel: 7.0.0-30-generic, package 7.0.0-30.30 GPU: AMD Navi 23 / RX 6600 [1002:73ff], subsystem [1849:5217] Mesa: 26.0.8-1ubuntu0.3 linux-firmware: 20260319.git217ca6e4.1ubuntu The desktop first began stuttering and later stopped responding. At 16:41:37, amdgpu began reporting "Fence fallback timer expired". SysRq/NMI stack dumps repeatedly caught CPU 7 in amdgpu_device_rreg() from the display/vblank IRQ handler, while other CPUs were waiting in smp_call_function_many_cond(). AMDGPU later reported: ring sdma1 timeout, signaled seq=72398, emitted seq=72398 Starting sdma1 ring reset The reset did not complete. Repeated stack dumps for over three minutes showed the amdgpu-reset-dev worker in: amdgpu_device_rreg sdma_v5_2_stop_queue amdgpu_sdma_reset_engine sdma_v5_2_reset_queue amdgpu_job_timedout drm_sched_job_timedout Four seconds before the first amdgpu warning, an ASMedia ASM4242 USB4 bridge at 17:00.0 reported that it could not transition from D3cold to D0. This is on a different PCIe root port, so its relationship is unknown. The kernel is tainted P/O because this is a ZFS-root system using the ZFS DKMS module. The amdgpu module itself is the stock Ubuntu kernel module. Frequency: Happens pretty reliably within 24 hours of boot Recovery required: Requires hard reset USB4 activity at the time: None ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 2 17:11:37 2026 IwDevWlp16s0Link: Not connected. MachineType: Micro-Star International Co., Ltd. MS-7E70 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5ck8oa@/vmlinuz-7.0.0-30-generic root=ZFS=rpool/ROOT/ubuntu_5ck8oa ro init_on_alloc=0 nmi_watchdog=1 softlockup_panic=1 hardlockup_panic=1 crashkernel=1G crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-05 (59 days ago) dmi.bios.date: 09/24/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.A31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: PRO X870E-P WIFI (MS-7E70) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.A31:bd09/24/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E70:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX870E-PWIFI(MS-7E70):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E70 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166226/+subscriptions
вторник
[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.
Hi Kelvin, In Comment #51, the command failed because `10000:03:00.0` is the NVMe drive that was just removed. The bridge that stays behind is `10000:00:05.0` (bus 00, not bus 03). The correct manual commands to reset the empty slots on the current kernel are: echo 1 > /sys/bus/pci/devices/10000:00:03.0/reset_subordinate # Slot 65 echo 1 > /sys/bus/pci/devices/10000:00:05.0/reset_subordinate # Slot 66 Alternatively, I built a test kernel [1] where the VMD driver does this reset automatically upon drive removal, so no manual commands are needed. To test: 1. Boot normally (without iommu.strict=1). 2. Unplug the drives. If using the current kernel, run the two commands above while the slots are empty. (If using the new kernel, it resets automatically). 3. Replug the drives and check: nvme list lsblk 4. Repeat 3 cycles. https://drive.google.com/file/d/1nQbLM4vQP2qxFJ1Wa66udSzr2vhUhaVg/view?usp=sharing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions
[Bug 2161312] Re: System hangs on suspend (s2idle) with kernel 7.0.0-28-generic, works fine on 7.0.0-27
Two more updates: another confirmed occurrence of the GPU-reset-during- hibernate-resume signature, plus a distinct new failure mode (silently orphaned desktop session, no suspend ever logged) — and frequency data showing this class of bug is a regular, recurring problem rather than an occasional edge case. ## Update 1 (2026-09-03): another GPU reset during hibernation resume, kernel 7.0.0-27-generic Same signature as the 2026-08-19 update above: amdgpu 0000:04:00.0: ring sdma0 timeout, signaled seq=296951, emitted seq=296953 amdgpu 0000:04:00.0: GPU reset begin!. Source: 1 amdgpu 0000:04:00.0: [drm] *ERROR* dpcd_set_link_settings:1122/1127/1155: core_link_write_dpcd (...) failed amdgpu 0000:04:00.0: GPU pre asic reset failed with err, -22 amdgpu 0000:04:00.0: MODE2 reset amdgpu 0000:04:00.0: GPU reset succeeded, trying to resume amdgpu 0000:04:00.0: VRAM is lost due to GPU reset! amdgpu 0000:04:00.0: [drm] *ERROR* DPM disable vcn failed, ret = -62. This happened immediately on hibernation exit (image had frozen successfully, plenty of free-page margin, so not the ENOMEM case below). The machine kept running afterward in a degraded graphics state but became fully unresponsive roughly an hour later, with no orderly shutdown logged — required a hard power-off. ## Update 2 (2026-09-08): new failure mode — desktop session silently lost, suspend request never reaches logind, machine runs hot for hours, battery drained This is different from the amdgpu ring-timeout pattern above. Timeline: - ~19:00 — user triggers "Suspend" from the Plasma menu. No corresponding "The system will suspend now!" line from systemd-logind, no "PM: suspend entry" — the request never reached logind at all. No error of any kind logged either. - 1-2 hours later — laptop found running hot (fans presumably active, not asleep). A second suspend attempt is made; again nothing logged. - ~21:48 — an explicit, orderly shutdown finally happens (clean systemd-poweroff sequence). Right as this shutdown starts, kwin_wayland logs: kwin_core: Failed to open /dev/dri/renderD128 device (Unknown object '/org/freedesktop/login1/session/_33'.) kwin_core: Failed to open /dev/input/event5 device (Unknown object '/org/freedesktop/login1/session/_33'.) i.e. logind no longer recognized the Plasma session's own session object as valid — consistent with the interactive session having silently detached/orphaned itself well before the shutdown, explaining why neither suspend attempt could have worked: the session invoking them was already broken. - Next morning: lid-open did not wake anything (machine was genuinely off by then, from the 21:48 shutdown), and the battery was found drained — consistent with several hours of full operation (screen/fans active) between the first failed suspend (~19:00) and the eventual shutdown (~21:48), rather than genuine low-power suspend. No amdgpu errors, no OOM, no crash of any kind logged around the failed suspend attempts — the session simply stopped being able to act on sleep requests, silently. ## Frequency data (last 3 weeks, 2026-08-19 to 2026-09-09) Grepping this machine's journal for each known failure signature: - GPU reset during suspend/hibernate (ring timeout + MODE2 reset): 3 separate days (Aug 19, Sep 1, Sep 3) - Orphaned/lost logind session (this update's new pattern): 4 separate days (Aug 20, Aug 28, Sep 1, Sep 8) - Hibernation aborting cleanly with ENOMEM ("PM: hibernation: Error -12 creating image", safe failure, no data loss): 8 separate days (Aug 22, 25, 28, 29, 30, 31 [x2], Sep 3, Sep 6) Combined, some form of sleep/hibernate failure has occurred on the large majority of weeks since this was first reported, across multiple distinct failure modes (GPU driver hang, orphaned session, memory pressure) and across both kernel builds tested (7.0.0-27 and 7.0.0-28). This no longer looks like an occasional edge case — power-state transitions are broadly unreliable on this AMD Barcelo iGPU (amdgpu) platform under current Ubuntu 25.10 kernels. ## Hardware/software (unchanged) Dell Inspiron 14 5425, AMD Ryzen 7 5825U, AMD Barcelo iGPU (amdgpu), Ubuntu 25.10, KDE Plasma 6.5, Wayland. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161312 Title: System hangs on suspend (s2idle) with kernel 7.0.0-28-generic, works fine on 7.0.0-27 Status in linux package in Ubuntu: New Bug description: Hello Here is a bug occurring on my laptop. The analysis is from claude code. I hope it is relevant & complete. Thanks for your help. Summary System hangs permanently when entering suspend (s2idle) on kernel 7.0.0-28-generic; requires a hard power-off to recover. The exact same hardware suspended and resumed reliably dozens of times over 8 days on kernel 7.0.0-27-generic. The regression appeared immediately after the machine booted 7.0.0-28 for the first time — first suspend attempt on the new kernel already failed, and it failed again on the next boot. Hardware Machine: Dell Inspiron 14 5425 CPU: AMD Ryzen 7 5825U with Radeon Graphics GPU: AMD/ATI Barcelo iGPU (integrated, PCI 04:00.0) BIOS: 1.19.0 (2024-09-10) Sleep mode: only s2idle is offered by the platform (/sys/power/mem_sleep → [s2idle], no deep/S3 option available) Software Ubuntu 25.10 (Questing Quokka), KDE Plasma 6.5, Wayland session (kwin_wayland) Working kernel: linux-image-7.0.0-27-generic (7.0.0-27.27) Broken kernel: linux-image-7.0.0-28-generic (7.0.0-28.28) Steps to reproduce Boot into 7.0.0-28-generic. Trigger suspend (via systemd Suspend action / closing lid / GUI power menu). System freezes during or immediately after suspend entry: keyboard backlight stays lit, no reaction to any key or the power button short-press, screen never turns back on. Only recovery is holding the power button for a hard shutdown. Expected behavior System suspends and resumes normally, as it did consistently on 7.0.0-27-generic. Actual behavior System never comes back from suspend. journalctl shows the boot ending abruptly right after suspend entry, with no PM: suspend exit line and no orderly shutdown sequence — consistent with a full system hang, not a clean poweroff. Evidence from journalctl Working kernel (7.0.0-27), representative sample out of ~40 successful cycles between 2026-07-09 and 2026-07-17: juil. 16 19:31:46 kernel: PM: suspend entry (s2idle) juil. 17 14:48:21 kernel: PM: suspend exit Failing kernel (7.0.0-28), first attempt, boot ends here with no further log lines at all: juil. 20 10:42:38 root[18433]: Dell wakeup sources disabled - ALL including dock disconnect juil. 20 10:42:38 systemd-sleep[18388]: Performing sleep operation 'suspend'... juil. 20 10:42:38 kernel: PM: suspend entry (s2idle) [-- nothing further; next boot is a cold boot, not a resume --] Failing kernel (7.0.0-28), second attempt on a fresh boot, same pattern: juil. 20 12:32:59 systemd-sleep[26074]: Performing sleep operation 'suspend'... juil. 20 12:32:59 kernel: PM: suspend entry (s2idle) [-- nothing further --] Both failing boots are followed by a fresh cold boot (new boot ID in journalctl --list-boots), confirming the machine was hard power-cycled rather than resuming. Workaround Pinning the system to linux-image-7.0.0-27-generic (apt-mark hold) restores reliable suspend/resume. Additional notes A local dell-suspend-fix.service (disables PCI/USB/BT/WMI wakeup sources before sleep, standard workaround for this laptop's dock/eSATA wake-on-disconnect quirk) is present and unchanged across both the working and failing kernel — ruling it out as the cause. Not the known 7.0.0-28.28 AMDGPU/HMM ROCm performance regression (that one is a slowdown in compute workloads, not a hang) — this appears to be a separate, undocumented issue in the same kernel build. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 20 14:19:25 2026 InstallationDate: Installed on 2025-07-09 (376 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) IwDevWlp3s0Link: Not connected. MachineType: Dell Inc. Inspiron 14 5425 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=b239c123-a9a4-4924-bfc7-38c39f92e79b ro quiet splash acpi_backlight=native resume=UUID=871f8b5f-e842-4660-9c64-7661287c3695 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-09 (11 days ago) dmi.bios.date: 09/10/2024 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0J9C2M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.19.0 dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/10/2024:br1.19:svnDellInc.:pnInspiron145425:pvr1.19.0:rvnDellInc.:rn0J9C2M:rvrA00:cvnDellInc.:ct10:cvr1.19.0:sku0B46:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5425 dmi.product.sku: 0B46 dmi.product.version: 1.19.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161312/+subscriptions
[Bug 2143682] Re: applespi: keyboard/trackpad not working on MacBook8,1 without early initramfs module loading
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2143682 Title: applespi: keyboard/trackpad not working on MacBook8,1 without early initramfs module loading Status in linux package in Ubuntu: Expired Status in linux source package in Questing: Won't Fix Bug description: Heya folks, I know, really old macbook. Not a massive priority but doing my part to reduce e-waste :) On MacBook8,1 (Early 2015, 12" Retina), the internal keyboard and trackpad do not work after boot despite the applespi driver being loaded and the IOMMU fix (iommu/vt-d: Restore context entry setup order) being present in kernel 6.17. The touchpad does not appear in xinput list, though the keyboard device may partially initialize. Workaround: Adding spi_pxa2xx_pci, spi_pxa2xx_platform, and applespi to /etc/initramfs-tools/modules and rebuilding initramfs resolves the issue: sudo nano /etc/initramfs-tools/modules Add these lines: spi_pxa2xx_pci spi_pxa2xx_platform applespi sudo update-initramfs -u sudo reboot This suggests a timing/race condition where the SPI controller needs to be initialized before IOMMU finalizes device mappings. Hardware: MacBook8,1 (MacBook 12" Early 2015) Kernel: 6.17.0-5-generic Distribution: Xubuntu 24.04 --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: muratilyas 1711 F.... wireplumber /dev/snd/controlC0: muratilyas 1711 F.... wireplumber /dev/snd/seq: muratilyas 1705 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 25.10 InstallationDate: Installed on 2026-03-08 (3 days ago) InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1) MachineType: Apple Inc. MacBook8,1 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=6694b069-f4f4-495f-b8f2-c0c3203086af ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: questing Uname: Linux 6.17.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 01/12/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 481.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-BE0E8AC46FE800CC dmi.board.vendor: Apple Inc. dmi.board.version: MacBook8,1 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-BE0E8AC46FE800CC dmi.modalias: dmi:bvnAppleInc.:bvr481.0.0.0.0:bd01/12/2023:br0.1:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC:skuSystemSKU#: dmi.product.family: Crb dmi.product.name: MacBook8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: muratilyas 1738 F.... wireplumber /dev/snd/controlC0: muratilyas 1738 F.... wireplumber /dev/snd/seq: muratilyas 1724 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 25.10 InstallationDate: Installed on 2026-03-08 (3 days ago) InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1) MachineType: Apple Inc. MacBook8,1 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-16-generic root=UUID=6694b069-f4f4-495f-b8f2-c0c3203086af ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-16.16-generic 6.17.13 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: questing Uname: Linux 6.17.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 01/12/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 481.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-BE0E8AC46FE800CC dmi.board.vendor: Apple Inc. dmi.board.version: MacBook8,1 dmi.chassis.asset.tag: Chassis Board Asset Tag# dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-BE0E8AC46FE800CC dmi.modalias: dmi:bvnAppleInc.:bvr481.0.0.0.0:bd01/12/2023:br0.1:svnAppleInc.:pnMacBook8,1:pvr1.0:rvnAppleInc.:rnMac-BE0E8AC46FE800CC:rvrMacBook8,1:cvnAppleInc.:ct9:cvrMac-BE0E8AC46FE800CC:skuSystemSKU#: dmi.product.family: Crb dmi.product.name: MacBook8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143682/+subscriptions
[Bug 2166836] [NEW] 7.0.0-31-generic regression
Public bug reported: 7.0.0-31-generic causes shift and fn keys not to work. Initially could not log into device as I could not use caps. Eventually logged in using caps lock and could verify using evtest that neither shift key or the fn key was working My bluetooth keyboard shift and fn keys worked. Going back to 7.0.0-30-generic resolved the issue. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 9 13:26:06 2026 InstallationDate: Installed on 2026-07-22 (49 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83HM ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2025 dmi.bios.release: 1.71 dmi.bios.vendor: LENOVO dmi.bios.version: NYCN71WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 15ILL9 dmi.ec.firmware.release: 1.64 dmi.modalias: dmi:bvnLENOVO:bvrNYCN71WW:bd07/14/2025:br1.71:efr1.64:svnLENOVO:pn83HM:pvrYogaSlim715ILL9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrYogaSlim715ILL9:skuLENOVO_MT_83HM_BU_idea_FM_YogaSlim715ILL9:pfaYogaSlim715ILL9: dmi.product.family: Yoga Slim 7 15ILL9 dmi.product.name: 83HM dmi.product.sku: LENOVO_MT_83HM_BU_idea_FM_Yoga Slim 7 15ILL9 dmi.product.version: Yoga Slim 7 15ILL9 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2166836/+attachment/5998763/+files/lspci-vnvn.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166836 Title: 7.0.0-31-generic regression Status in linux package in Ubuntu: New Bug description: 7.0.0-31-generic causes shift and fn keys not to work. Initially could not log into device as I could not use caps. Eventually logged in using caps lock and could verify using evtest that neither shift key or the fn key was working My bluetooth keyboard shift and fn keys worked. Going back to 7.0.0-30-generic resolved the issue. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 9 13:26:06 2026 InstallationDate: Installed on 2026-07-22 (49 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 83HM ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2025 dmi.bios.release: 1.71 dmi.bios.vendor: LENOVO dmi.bios.version: NYCN71WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 15ILL9 dmi.ec.firmware.release: 1.64 dmi.modalias: dmi:bvnLENOVO:bvrNYCN71WW:bd07/14/2025:br1.71:efr1.64:svnLENOVO:pn83HM:pvrYogaSlim715ILL9:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrYogaSlim715ILL9:skuLENOVO_MT_83HM_BU_idea_FM_YogaSlim715ILL9:pfaYogaSlim715ILL9: dmi.product.family: Yoga Slim 7 15ILL9 dmi.product.name: 83HM dmi.product.sku: LENOVO_MT_83HM_BU_idea_FM_Yoga Slim 7 15ILL9 dmi.product.version: Yoga Slim 7 15ILL9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166836/+subscriptions