[РЕШЕНО] Ошибка № ...

среда

[Bug 2171307] Re: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10)

** Changed in: linux Status: Unknown => New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171307 Title: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10) Status in Linux: New Status in linux package in Ubuntu: New Bug description: **Summary** The speakers and headphone output do not work. GNOME and PipeWire only show "Dummy Output". The sound card `sof-soundwire` is registered, but the kernel finds no SoundWire machine driver for this laptop, so no speaker sink is created. **Hardware** - HP OmniBook X Flip Laptop 14-kb0xxx, BIOS F.10, audio subsystem ID 103c:8ea4 - Intel Core Ultra Series 3 (Panther Lake) audio controller, 8086:e428 - Realtek RT712 (SoundWire link 3), 2x TI TAS2783 speaker amps (link 2) **Versions** - Ubuntu 26.10, linux 7.3.0-9-generic (#9-Ubuntu, Oct 5 2026) - linux-firmware 20260915.git1522c78a.1ubuntu, firmware-sof-signed 2026.09-1 - alsa-ucm-conf 1.2.16.1-1ubuntu1, pipewire 1.6.8, wireplumber 0.5.17 **Steps** 1. Boot, open Settings > Sound. 2. Only "Dummy Output" is listed. `wpctl status` shows the same, and the card profile list is off / HiFi (unavailable) / pro-audio. **Expected:** speaker and headphone outputs. **Key log lines** ``` sof-audio-pci-intel-ptl 0000:00:1f.3: No SoundWire machine driver found for the ACPI-reported configuration: sof-audio-pci-intel-ptl 0000:00:1f.3: link 2 mfg_id 0x0102 part_id 0x0000 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: link 3 mfg_id 0x025d part_id 0x0712 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: Use SoundWire default machine driver with function topologies slave-tas2783 sdw:0:2:0102:0000:01:c: Direct firmware load for 8EA4-2-0xC.bin failed with error -2 slave-tas2783 sdw:0:2:0102:0000:01:9: Direct firmware load for 8EA4-2-0x9.bin failed with error -2 ``` Also `UBSAN: shift-out-of-bounds in sound/soc/sof/ipc4-topology.c:2471:13`. **Findings** - The TAS2783 driver requests `8EA4-2-0x{9,C}.bin`, but linux-firmware ships `8EA4-0-2-0x{9,C}.bin.zst` and `8EA4-1-2-0x{9,C}.bin.zst` (an extra index field). Creating symlinks for the requested names in `/lib/firmware` removes the load errors. - That does not restore sound. The kernel has no machine-driver match for RT712 + 2x TAS2783, and the ACPI tables do not describe the amps as SDCA speaker functions. Only the jack, mic and HDMI topologies get loaded, never the installed `sof-sdca-2amp-id2.tplg`. - I have not tested a kernel patch. This probably needs a `soc-acpi-intel-ptl-match.c` entry or equivalent. I have also filed it upstream with the SOF project. **Request:** please include audio support for this model in a kernel update, and align the TAS2783 firmware file naming between the kernel and linux-firmware packages. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kevin 8192 F.... wireplumber /dev/snd/seq: kevin 8188 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 20:56:37 2026 InstallationDate: Installed on 2026-10-17 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official amd64 (20261013) MachineType: HP HP OmniBook X Flip Laptop 14-kb0xxx ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=be9e4e6d-9ff2-4d3c-89fe-f954199f0334 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2026 dmi.bios.release: 15.10 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8EA4 dmi.board.vendor: HP dmi.board.version: 12.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.26 dmi.modalias: dmi:bvnInsyde:bvrF.10:bd04/16/2026:br15.10:efr12.26:svnHP:pnHPOmniBookXFlipLaptop14-kb0xxx:pvrType1ProductConfigId:rvnHP:rn8EA4:rvr12.26:cvnHP:ct31:cvrChassisVersion:skuDQ8R9EA#ABU:pfa103C_5335M8HPOmniBookX: dmi.product.family: 103C_5335M8 HP OmniBook X dmi.product.name: HP OmniBook X Flip Laptop 14-kb0xxx dmi.product.sku: DQ8R9EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2171307/+subscriptions

[Bug 2171297] Re: resolute: please disable CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT (as done for 26.10 in LP: #2169198); KHO scratch makes 13 GiB unusable for GPU / pinned memory

Hi, Thanks for the detailed bug report. I'll see if we can get this applied. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171297 Title: resolute: please disable CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT (as done for 26.10 in LP: #2169198); KHO scratch makes 13 GiB unusable for GPU / pinned memory Status in linux package in Ubuntu: New Bug description: [Impact] The resolute generic kernel ships CONFIG_KEXEC_HANDOVER_ENABLE_DEFAULT=y, so KHO is on at every boot with no kho= parameter. At boot KHO reserves scratch areas and marks their pageblocks MIGRATE_CMA. Only movable allocations can use those blocks. Anything unmovable or pinned can't use them: GPU buffers (amdgpu GTT on APUs), VFIO/PCI-passthrough guest memory, RDMA registrations. On a 128 GiB Ryzen AI Max+ 395 (Strix Halo, unified memory), the scratch is 13.3 GiB, about 10% of RAM. A single GPU process stops at 107 GiB under a 120 GiB GTT limit, with 13 GiB of RAM still free. With kho=off the same test reaches 117 GiB and stops only at RAM. Nothing on this machine uses kexec handover / live update. The scratch is reserved anyway. LP: #2143831 enabled KHO for resolute and said "The feature is disabled at runtime by default unless the cmdline kho=on is specified". The shipped config does the opposite. 26.10 already turned the default off (7.3.0-9.9, "[Config] Disable KEXEC_HANDOVER_ENABLE_DEFAULT", LP: #2169198, filed for a mini-iso hang). This bug asks for the same one-line config change on resolute. Debian and Fedora both leave the option unset (KHO only with kho=on). Proxmox proposed the same change in July 2026 for the same reason, pinned memory for passthrough guests: https://lore.proxmox.com/all/20260714124456.347992-1-d.csapak@proxmox.com/ [System] - Framework Desktop, AMD Ryzen AI Max+ 395, Radeon 8060S (gfx1151), 128 GB LPDDR5X - Ubuntu Server 26.04 LTS, linux-image-7.0.0-38-generic 7.0.0-38.38 - Stock cmdline apart from crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M - ttm pages_limit=31457280 (120 GiB GTT), swap off, ROCm 10.1 [Evidence that the CMA pages are KHO scratch] There is no CMA area: CmaTotal: 0 kB, /sys/kernel/mm/cma/ is empty, the boot log shows "0K cma-reserved", and CONFIG_CMA_SIZE_MBYTES=0. CmaFree is still non-zero, 14.27 GB five minutes after boot. /proc/pagetypeinfo, CMA column: DMA32 380 + Normal 6424 = 6804 pageblocks x 2 MiB = 13,608 MiB. /sys/kernel/debug/kho/out/scratch_len: 0x2f800000 = 760 MiB (lowmem; matches the 380 DMA32 blocks) 0x213e00000 = 8,510 MiB 0x10f200000 = 4,338 MiB total = 13,608 MiB, an exact match for the CMA pageblocks Boot log, same kernel, only kho=off added: KHO on: Memory: 114581060K/133474628K available (... 18849804K reserved, 0K cma-reserved) kho=off: Memory: 128515616K/133474628K available (... 4915232K reserved, 0K cma-reserved) difference: 13,934,572K = 13,608 MiB, the scratch total again (My guess, not verified: the scratch scales with early memblock reservations, so the 4 GiB crashkernel reservation is probably a large part of the 8.5 GiB global area. Machines with large crashkernel settings would then lose the most.) [Test case] A small HIP program allocates 1 GiB with hipMalloc, touches it with hipMemset, and repeats until hipMalloc fails or MemAvailable drops below 4 GiB. KHO on (default) kho=off allocated + touched 107 GiB 117 GiB stopped by hipMalloc out of memory the 4 GiB MemAvailable floor MemAvailable at stop 13.4 GiB 3.3 GiB CmaFree at stop 13.0 GiB 0 kernel log page allocation failure (below) none KHO on, at the point of failure: page allocation failure: order:0, mode:...(GFP_HIGHUSER|__GFP_ZERO|__GFP_RETRY_MAYFAIL) ... gpu_active:112960512kB ... free_cma:3419351 With kho=off: no CMA pageblocks in any zone, CmaFree: 0, no /sys/kernel/debug/kho. To check any machine without a GPU: if CmaTotal is 0 and CmaFree is non-zero in /proc/meminfo, or the CMA column in /proc/pagetypeinfo is non-zero with no CMA area, KHO scratch is reserved. Verify a fixed kernel: boot without kho=, then CmaFree should be 0 and /sys/kernel/debug/kho/out should not exist. [Workaround] Add kho=off to the kernel cmdline (e.g. a /etc/default/grub.d/ snippet, then update-grub). [Where problems could occur] Anyone who relies on KHO / live update without passing kho=on would need to add kho=on. On a general-purpose LTS kernel that group should be small, and LP: #2143831 already told users to expect kho=on. kdump's crashkernel reservation is separate and does not change. [Possibly related] - LP: #2152152, "KHO: Failed to reserve lowmem scratch buffer on every boot" (resolute, Confirmed). The same default causes it. - LP: #2161812, kdump capture kernel never reaches userspace on resolute. Not verified, but an August 2026 upstream patch reports that kdump kernels with KHO enabled by default reserve scratch out of the crashkernel area and fail early ("kho: do not reserve scratch memory in kdump kernel"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171297/+subscriptions

[Bug 2171818] [NEW] amdgpu reports incomplete modes list for screen attached via USB-C

Public bug reported: I have a laptop (with two AMD GPUs) that I often connect to a 4k DELL monitor using an USB-C cable. Sometimes amdgpu seems to set an incomplete list of supported modes for this monitor when I first connect it, so Gnome cannot use its stored configuration for it. This is clearly seen in the logs: gnome-shell[5629]: Failed to use stored monitor configuration: Invalid mode 3840x2160 (120,000) for monitor 'DEL DELL S2725QC' This might be a race condition, because the problem doesn't always happen. The logs in this report show the problem happening as the laptop wakes up from sleep (at 00:05) with the monitor connected. (But waking up from sleep is not required, I often see this problem when I connect the monitor to an already awake laptop.) Then at 00:12 I disconnected and reconnected the monitor, and this second time it got all of its modes properly enumerated. I never managed to reproduce the problem by repeatedly disconnecting and reconnecting the monitor, I've only ever experienced it on the first time it gets connected (per reboot). I've attached to this report: - /sys/class/drm/card*-*/status and modes for both the incorrect and correct states - system and user journalct output - ~/.config/monitors.xml - version info on relevant components ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC1: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC0: dszoboszlay 5088 F.... wireplumber /dev/snd/seq: dszoboszlay 5082 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 00:19:57 2026 InstallationDate: Installed on 2024-12-25 (665 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA402RK_GA402RK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-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 SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-24 (151 days ago) dmi.bios.date: 07/01/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402RK.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402RK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: gametopia dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402RK.313:bd07/01/2022:br5.24:efr3.12:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402RK_GA402RK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402RK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGZephyrusG14: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA402RK_GA402RK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "report.tgz" https://bugs.launchpad.net/bugs/2171818/+attachment/6011430/+files/report.tgz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171818 Title: amdgpu reports incomplete modes list for screen attached via USB-C Status in linux package in Ubuntu: New Bug description: I have a laptop (with two AMD GPUs) that I often connect to a 4k DELL monitor using an USB-C cable. Sometimes amdgpu seems to set an incomplete list of supported modes for this monitor when I first connect it, so Gnome cannot use its stored configuration for it. This is clearly seen in the logs: gnome-shell[5629]: Failed to use stored monitor configuration: Invalid mode 3840x2160 (120,000) for monitor 'DEL DELL S2725QC' This might be a race condition, because the problem doesn't always happen. The logs in this report show the problem happening as the laptop wakes up from sleep (at 00:05) with the monitor connected. (But waking up from sleep is not required, I often see this problem when I connect the monitor to an already awake laptop.) Then at 00:12 I disconnected and reconnected the monitor, and this second time it got all of its modes properly enumerated. I never managed to reproduce the problem by repeatedly disconnecting and reconnecting the monitor, I've only ever experienced it on the first time it gets connected (per reboot). I've attached to this report: - /sys/class/drm/card*-*/status and modes for both the incorrect and correct states - system and user journalct output - ~/.config/monitors.xml - version info on relevant components ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC1: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC0: dszoboszlay 5088 F.... wireplumber /dev/snd/seq: dszoboszlay 5082 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 00:19:57 2026 InstallationDate: Installed on 2024-12-25 (665 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA402RK_GA402RK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-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 SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-24 (151 days ago) dmi.bios.date: 07/01/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402RK.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402RK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: gametopia dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402RK.313:bd07/01/2022:br5.24:efr3.12:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402RK_GA402RK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402RK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGZephyrusG14: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA402RK_GA402RK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171818/+subscriptions

[Bug 2171282] Re: Wake-on-LAN from s2idle does not work on ASUS NUC 15 (Intel I226-V, igc); wake from S5 and USB wake from s2idle both work

Hi, Thanks for the detailed bug report. You suspect this is an upstream kernel issue, have you tried replicating this using the mainline kernels? You can find them here: http://kernel.ubuntu.com/mainline/ If you can still replicate it on the mainline kernels, consider opening a bug report upstream. I'm sure they would also appreciate if you could determine if this was always broken or whether it's a regression (and if so, what the last working release was and the following release that broke it). This would involve booting various mainline kernels and bisecting until you find the break. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ross Porter (rossporter506) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171282 Title: Wake-on-LAN from s2idle does not work on ASUS NUC 15 (Intel I226-V, igc); wake from S5 and USB wake from s2idle both work Status in linux package in Ubuntu: New Bug description: Hardware: ASUS NUC 15 (DSDT: NUC15CR), BIOS CRARL579.0032.2026.0704.0118 (latest) NIC: 56:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) , driver igc, interface enp86s0 Kernel: 7.0.0-30-generic (Kubuntu 26.04) Problem: Wake-on-LAN (magic packet) does not wake the system from poweroff (S5), s2idle or deep (S3) when running Kubuntu. The same hardware wakes correctly from poweroff when running a Fedora live system. Test results (same machine, same BIOS settings, same sender): - Power cut, then AC restored without booting an OS -> magic packet wakes the machine (firmware/BIOS WoL works) - Fedora KDE live, kernel 6.19.10-300, "ethtool -s <if> wol g", poweroff -> magic packet wakes the machine - Kubuntu 26.04 (7.0.0-30-generic), poweroff / s2idle / deep -> no wake - Kubuntu 24.04 live, poweroff -> no wake So this is not a kernel version regression (Fedora's 6.19 works, Ubuntu kernels both older and newer fail). It looks specific to the Ubuntu kernel (config or patches) or to the Ubuntu shutdown path. Verified on Kubuntu 26.04: - ethtool: "Supports Wake-on: pumbg", "Wake-on: g" - NetworkManager: 802-3-ethernet.wake-on-lan = magic - /sys/class/net/enp86s0/device/power/wakeup = enabled - /proc/acpi/wakeup: RP05 (0000:00:1c.0) and PXSX (0000:56:00.0) enabled - TLP not installed - Magic packet (102 bytes, UDP broadcast port 9) arrives at the NIC (confirmed with tcpdump) - BIOS: WoL from S4/S5 = Power On, ErP disabled Workarounds tried without success: - systemd unit running "ethtool -s enp86s0 wol g" right before poweroff - system-shutdown hook unbinding igc from 0000:56:00.0 before poweroff - additionally resetting the PCI device via sysfs before poweroff Possibly related, on every resume: igc 0000:56:00.0 enp86s0: Timeout reading IGC_PTM_STAT register Expected: the machine wakes on magic packet after poweroff/suspend, as it does with Fedora on identical hardware. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 17 08:12:39 2026 InstallationDate: Installed on 2026-10-13 (4 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. NUC15CRHU5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=b29c8153-e4da-4d83-99a0-13d0fe2d47f6 ro quiet splash 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/04/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: CRARL579.0032.2026.0704.0118 dmi.board.name: NUC15CRBU5 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 60AS00K0-MBJA03 dmi.chassis.type: 35 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 2.0 dmi.ec.firmware.release: 2.12 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvrCRARL579.0032.2026.0704.0118:bd07/04/2026:br5.32:efr2.12:svnASUSTeKCOMPUTERINC.:pnNUC15CRHU5:pvr90AR00Q2-M00050:rvnASUSTeKCOMPUTERINC.:rnNUC15CRBU5:rvr60AS00K0-MBJA03:cvnASUSTeKCOMPUTERINC.:ct35:cvr2.0:skuRNUC15CRHU500002:pfaCR: dmi.product.family: CR dmi.product.name: NUC15CRHU5 dmi.product.sku: RNUC15CRHU500002 dmi.product.version: 90AR00Q2-M00050 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171282/+subscriptions

[Bug 2171816] [NEW] Bluetooth adapter disappears after suspend on HP 15s (Realtek RTL8821CE, 0bda:b00a) and never returns

Public bug reported: Title: Bluetooth adapter disappears after suspend on HP 15s (Realtek RTL8821CE, 0bda:b00a) and never returns Description: Hardware: HP Laptop 15s-fq1xxx with a Realtek RTL8821CE combo card (WiFi + Bluetooth). The Bluetooth adapter is 0bda:b00a (Realtek Bluetooth 4.2 Adapter) on USB port 1-10. Environment: Xubuntu, kernel 7.0.0-38-generic. Problem: After suspend/resume, the Bluetooth adapter disappears from lsusb and never comes back. The system behaves as if the device was physically removed. BlueZ reports no adapter, and Blueman shows "no adapter detected". A reboot is the only way to restore Bluetooth. Key log evidence (at resume): kernel: usb 1-3: reset high-speed USB device number 2 using xhci_hcd kernel: usb 1-10: USB disconnect, device number 3 Copia The webcam (usb 1-3) resets correctly at resume, but the Bluetooth adapter (usb 1-10) is disconnected and never re-enumerated. After resume, /sys/bus/usb/devices/1-10/ no longer exists. Already tried, without success: Disabling USB autosuspend for the device (udev rule, power/control=on) Disabling global USB autosuspend (usbcore.autosuspend=-1) Disabling PCI runtime PM for 0000:01:00.0 PCI remove + rescan (/sys/bus/pci/devices/0000:01:00.0/remove + /sys/bus/pci/rescan) Resetting the xHCI controller (0000:00:14.0 remove + rescan) modprobe -r btusb && modprobe btusb systemd hooks in /etc/systemd/system-sleep/ (not executed) and a service on suspend.target USB device re-authorization via /sys/bus/usb/devices/1-10/authorized (node missing after resume) None of these bring the adapter back. The device is fully removed from the USB bus at resume. Request: Please investigate why the RTL8821CE Bluetooth adapter is not re-enumerated after suspend on this platform. This appears to be a firmware/driver-level issue with the combo card. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ale_pella 1767 F.... wireplumber /dev/snd/seq: ale_pella 1760 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Oct 21 23:19:36 2026 InstallationDate: Installed on 2026-09-26 (26 days ago) InstallationMedia: Xubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 30c9:0013 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15s-fq1xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=d478ca71-3afb-47e3-bc39-c33de1b8fc69 ro quiet splash 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/04/2023 dmi.bios.release: 15.30 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C9 dmi.board.vendor: HP dmi.board.version: 56.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnAMI:bvrF.30:bd07/04/2023:br15.30:efr56.33:svnHP:pnHPLaptop15s-fq1xxx:pvr:rvnHP:rn86C9:rvr56.33:cvnHP:ct10:cvrChassisVersion:sku1L6H9EA#ABZ:pfa103C_5335KVHPNotebook: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-fq1xxx dmi.product.sku: 1L6H9EA#ABZ dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171816 Title: Bluetooth adapter disappears after suspend on HP 15s (Realtek RTL8821CE, 0bda:b00a) and never returns Status in linux package in Ubuntu: New Bug description: Title: Bluetooth adapter disappears after suspend on HP 15s (Realtek RTL8821CE, 0bda:b00a) and never returns Description: Hardware: HP Laptop 15s-fq1xxx with a Realtek RTL8821CE combo card (WiFi + Bluetooth). The Bluetooth adapter is 0bda:b00a (Realtek Bluetooth 4.2 Adapter) on USB port 1-10. Environment: Xubuntu, kernel 7.0.0-38-generic. Problem: After suspend/resume, the Bluetooth adapter disappears from lsusb and never comes back. The system behaves as if the device was physically removed. BlueZ reports no adapter, and Blueman shows "no adapter detected". A reboot is the only way to restore Bluetooth. Key log evidence (at resume): kernel: usb 1-3: reset high-speed USB device number 2 using xhci_hcd kernel: usb 1-10: USB disconnect, device number 3 Copia The webcam (usb 1-3) resets correctly at resume, but the Bluetooth adapter (usb 1-10) is disconnected and never re-enumerated. After resume, /sys/bus/usb/devices/1-10/ no longer exists. Already tried, without success: Disabling USB autosuspend for the device (udev rule, power/control=on) Disabling global USB autosuspend (usbcore.autosuspend=-1) Disabling PCI runtime PM for 0000:01:00.0 PCI remove + rescan (/sys/bus/pci/devices/0000:01:00.0/remove + /sys/bus/pci/rescan) Resetting the xHCI controller (0000:00:14.0 remove + rescan) modprobe -r btusb && modprobe btusb systemd hooks in /etc/systemd/system-sleep/ (not executed) and a service on suspend.target USB device re-authorization via /sys/bus/usb/devices/1-10/authorized (node missing after resume) None of these bring the adapter back. The device is fully removed from the USB bus at resume. Request: Please investigate why the RTL8821CE Bluetooth adapter is not re-enumerated after suspend on this platform. This appears to be a firmware/driver-level issue with the combo card. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ale_pella 1767 F.... wireplumber /dev/snd/seq: ale_pella 1760 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Oct 21 23:19:36 2026 InstallationDate: Installed on 2026-09-26 (26 days ago) InstallationMedia: Xubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 30c9:0013 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Laptop 15s-fq1xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=d478ca71-3afb-47e3-bc39-c33de1b8fc69 ro quiet splash 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/04/2023 dmi.bios.release: 15.30 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C9 dmi.board.vendor: HP dmi.board.version: 56.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnAMI:bvrF.30:bd07/04/2023:br15.30:efr56.33:svnHP:pnHPLaptop15s-fq1xxx:pvr:rvnHP:rn86C9:rvr56.33:cvnHP:ct10:cvrChassisVersion:sku1L6H9EA#ABZ:pfa103C_5335KVHPNotebook: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-fq1xxx dmi.product.sku: 1L6H9EA#ABZ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171816/+subscriptions

[Bug 2171307] Re: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10)

Hi, Thanks for filing a bug report. As this is an upstream issue we'll wait to see what upstream does first and then mirror their change in Ubuntu. I've linked the upstream bug to this issue, if anything changes post a comment here and I'll be notified. ** Also affects: linux via https://github.com/thesofproject/linux/issues/5981 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ross Porter (rossporter506) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171307 Title: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10) Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: **Summary** The speakers and headphone output do not work. GNOME and PipeWire only show "Dummy Output". The sound card `sof-soundwire` is registered, but the kernel finds no SoundWire machine driver for this laptop, so no speaker sink is created. **Hardware** - HP OmniBook X Flip Laptop 14-kb0xxx, BIOS F.10, audio subsystem ID 103c:8ea4 - Intel Core Ultra Series 3 (Panther Lake) audio controller, 8086:e428 - Realtek RT712 (SoundWire link 3), 2x TI TAS2783 speaker amps (link 2) **Versions** - Ubuntu 26.10, linux 7.3.0-9-generic (#9-Ubuntu, Oct 5 2026) - linux-firmware 20260915.git1522c78a.1ubuntu, firmware-sof-signed 2026.09-1 - alsa-ucm-conf 1.2.16.1-1ubuntu1, pipewire 1.6.8, wireplumber 0.5.17 **Steps** 1. Boot, open Settings > Sound. 2. Only "Dummy Output" is listed. `wpctl status` shows the same, and the card profile list is off / HiFi (unavailable) / pro-audio. **Expected:** speaker and headphone outputs. **Key log lines** ``` sof-audio-pci-intel-ptl 0000:00:1f.3: No SoundWire machine driver found for the ACPI-reported configuration: sof-audio-pci-intel-ptl 0000:00:1f.3: link 2 mfg_id 0x0102 part_id 0x0000 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: link 3 mfg_id 0x025d part_id 0x0712 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: Use SoundWire default machine driver with function topologies slave-tas2783 sdw:0:2:0102:0000:01:c: Direct firmware load for 8EA4-2-0xC.bin failed with error -2 slave-tas2783 sdw:0:2:0102:0000:01:9: Direct firmware load for 8EA4-2-0x9.bin failed with error -2 ``` Also `UBSAN: shift-out-of-bounds in sound/soc/sof/ipc4-topology.c:2471:13`. **Findings** - The TAS2783 driver requests `8EA4-2-0x{9,C}.bin`, but linux-firmware ships `8EA4-0-2-0x{9,C}.bin.zst` and `8EA4-1-2-0x{9,C}.bin.zst` (an extra index field). Creating symlinks for the requested names in `/lib/firmware` removes the load errors. - That does not restore sound. The kernel has no machine-driver match for RT712 + 2x TAS2783, and the ACPI tables do not describe the amps as SDCA speaker functions. Only the jack, mic and HDMI topologies get loaded, never the installed `sof-sdca-2amp-id2.tplg`. - I have not tested a kernel patch. This probably needs a `soc-acpi-intel-ptl-match.c` entry or equivalent. I have also filed it upstream with the SOF project. **Request:** please include audio support for this model in a kernel update, and align the TAS2783 firmware file naming between the kernel and linux-firmware packages. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kevin 8192 F.... wireplumber /dev/snd/seq: kevin 8188 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 20:56:37 2026 InstallationDate: Installed on 2026-10-17 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official amd64 (20261013) MachineType: HP HP OmniBook X Flip Laptop 14-kb0xxx ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=be9e4e6d-9ff2-4d3c-89fe-f954199f0334 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2026 dmi.bios.release: 15.10 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8EA4 dmi.board.vendor: HP dmi.board.version: 12.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.26 dmi.modalias: dmi:bvnInsyde:bvrF.10:bd04/16/2026:br15.10:efr12.26:svnHP:pnHPOmniBookXFlipLaptop14-kb0xxx:pvrType1ProductConfigId:rvnHP:rn8EA4:rvr12.26:cvnHP:ct31:cvrChassisVersion:skuDQ8R9EA#ABU:pfa103C_5335M8HPOmniBookX: dmi.product.family: 103C_5335M8 HP OmniBook X dmi.product.name: HP OmniBook X Flip Laptop 14-kb0xxx dmi.product.sku: DQ8R9EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2171307/+subscriptions

[Bug 2171811] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2171811/+attachment/6011394/+files/CurrentDmesg.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171811 Title: Intel Wireless-AC 9462 Bluetooth (8087:0aaa, ibt-0040-1020) repeatedly crashes with "Hardware error 0x0c" Status in linux package in Ubuntu: New Bug description: The Intel Bluetooth controller on an ASUS Vivobook 14 (X1404VA) crashes repeatedly while a Bluetooth HID device is connected. Each crash logs "Bluetooth: hci0: Hardware error 0x0c" followed by "Exception info". The connected mouse/keyboard disconnects and reconnects a second or two later, which can happen every few seconds. Sometimes the controller stops responding entirely and the kernel resets it: Bluetooth: hci0: Opcode 0x2042 failed: -110 Bluetooth: hci0: command 0x2042 tx timeout Bluetooth: hci0: Initiating acpi reset method Bluetooth: hci0: Reset after hardware error failed (-19) After that, the controller comes back as hci1 and loads its firmware again. Steps to reproduce: 1. Pair and connect a Bluetooth mouse (reproduced with a Logitech MX Master 3S and a Logi M196; also a Logitech MX Mechanical keyboard). 2. Use the computer normally. 3. Watch: journalctl -k -f | grep -i bluetooth Expected: the Bluetooth connection stays stable. Actual: "Hardware error 0x0c" appears anywhere from every few seconds to every few minutes, and the HID devices reconnect after each error. Observations: - Reproduced on kernels 7.0.0-14, 7.0.0-15 and 7.0.0-38-generic (crashes since April 2026), so it does not look like a regression from one kernel update. - Happens only while a Bluetooth HID device is connected, with different mice from different product lines. The frequency varies a lot: some multi-day sessions had no errors. - Persists after a full power-off and cold boot. - Wi-Fi is connected on 5 GHz (channel 161), so 2.4 GHz Wi-Fi/Bluetooth coexistence seems unlikely to be the cause. iwlwifi bt_coex_active is at its default (Y). - Bluetooth USB autosuspend is not active (power/control = on). System: - Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic (7.0.0-38.38) - ASUSTeK Vivobook X1404VA, BIOS X1404VA.313 (07/22/2025) - Wi-Fi: Intel Wireless-AC 9462 (CNVi, PCI 8086:51f1), Raptor Lake PCH - Bluetooth: USB 8087:0aaa, firmware intel/ibt-0040-1020.sfi, firmware version 151-5.24 (timestamp 2024.5, build 151) - linux-firmware 20260319.git217ca6e4.1ubuntu - BlueZ 5.85 --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: junior 3443 F.... wireplumber /dev/snd/seq: junior 3438 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-04-28 (176 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 2b7e:b868 Sonix Technology Co., Ltd. ASUS HD webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X1404VA_X1404VA 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=/vmlinuz-7.0.0-38-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 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: Upgraded to resolute on 2026-04-28 (176 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sudo uinput users _MarkForUpload: True dmi.bios.date: 07/22/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X1404VA.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X1404VA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX1404VA.313:bd07/22/2025:br5.27:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX1404VA_X1404VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX1404VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobook: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop X1404VA_X1404VA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171811/+subscriptions

[Bug 2171811] AlsaInfo.txt

apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2171811/+attachment/6011392/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171811 Title: Intel Wireless-AC 9462 Bluetooth (8087:0aaa, ibt-0040-1020) repeatedly crashes with "Hardware error 0x0c" Status in linux package in Ubuntu: New Bug description: The Intel Bluetooth controller on an ASUS Vivobook 14 (X1404VA) crashes repeatedly while a Bluetooth HID device is connected. Each crash logs "Bluetooth: hci0: Hardware error 0x0c" followed by "Exception info". The connected mouse/keyboard disconnects and reconnects a second or two later, which can happen every few seconds. Sometimes the controller stops responding entirely and the kernel resets it: Bluetooth: hci0: Opcode 0x2042 failed: -110 Bluetooth: hci0: command 0x2042 tx timeout Bluetooth: hci0: Initiating acpi reset method Bluetooth: hci0: Reset after hardware error failed (-19) After that, the controller comes back as hci1 and loads its firmware again. Steps to reproduce: 1. Pair and connect a Bluetooth mouse (reproduced with a Logitech MX Master 3S and a Logi M196; also a Logitech MX Mechanical keyboard). 2. Use the computer normally. 3. Watch: journalctl -k -f | grep -i bluetooth Expected: the Bluetooth connection stays stable. Actual: "Hardware error 0x0c" appears anywhere from every few seconds to every few minutes, and the HID devices reconnect after each error. Observations: - Reproduced on kernels 7.0.0-14, 7.0.0-15 and 7.0.0-38-generic (crashes since April 2026), so it does not look like a regression from one kernel update. - Happens only while a Bluetooth HID device is connected, with different mice from different product lines. The frequency varies a lot: some multi-day sessions had no errors. - Persists after a full power-off and cold boot. - Wi-Fi is connected on 5 GHz (channel 161), so 2.4 GHz Wi-Fi/Bluetooth coexistence seems unlikely to be the cause. iwlwifi bt_coex_active is at its default (Y). - Bluetooth USB autosuspend is not active (power/control = on). System: - Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic (7.0.0-38.38) - ASUSTeK Vivobook X1404VA, BIOS X1404VA.313 (07/22/2025) - Wi-Fi: Intel Wireless-AC 9462 (CNVi, PCI 8086:51f1), Raptor Lake PCH - Bluetooth: USB 8087:0aaa, firmware intel/ibt-0040-1020.sfi, firmware version 151-5.24 (timestamp 2024.5, build 151) - linux-firmware 20260319.git217ca6e4.1ubuntu - BlueZ 5.85 --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: junior 3443 F.... wireplumber /dev/snd/seq: junior 3438 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-04-28 (176 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 2b7e:b868 Sonix Technology Co., Ltd. ASUS HD webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X1404VA_X1404VA 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=/vmlinuz-7.0.0-38-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 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: Upgraded to resolute on 2026-04-28 (176 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sudo uinput users _MarkForUpload: True dmi.bios.date: 07/22/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X1404VA.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X1404VA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX1404VA.313:bd07/22/2025:br5.27:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX1404VA_X1404VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX1404VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobook: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop X1404VA_X1404VA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171811/+subscriptions

[Bug 2171810] [NEW] Mainline Kernel Builds Stopped

Public bug reported: kernel.ubuntu.com/mainline has not published new builds since mid- September 2026. Evidence (checked 2026-10-21): - Latest daily: 2026-09-17 (7.3.0-070300rc3daily20260917). No daily dirs after that date. - Latest tagged dir: v7.3-rc3 (2026-09-14). v7.3-rc4, rc5, rc6, rc7 and v7.3 (final, tagged upstream 2026-10-18) do not exist. - https://kernel.ubuntu.com/mainline/v7.3/ returns 404. - The last daily run itself built fine on amd64, arm64, armhf, ppc64el and s390x. amd64 self-tests failed (rc=2). i386 build failed after 8s (rc=2). riscv64 reported success in 10s with no .debs. This looks like the scheduler/trigger stopped, not a compile failure. Similar multi-week stalls happened in Oct 2023 and Sep 2024. Request: please restore the build pipeline, and publish v7.3-rc4 through v7.3 if possible. Commands used: curl -s https://kernel.ubuntu.com/mainline/ | grep -E 'v7\.3' curl -s https://kernel.ubuntu.com/mainline/daily/ | grep -oE 'href="[0-9-]+/"' | tail -5 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171810 Title: Mainline Kernel Builds Stopped Status in linux package in Ubuntu: New Bug description: kernel.ubuntu.com/mainline has not published new builds since mid- September 2026. Evidence (checked 2026-10-21): - Latest daily: 2026-09-17 (7.3.0-070300rc3daily20260917). No daily dirs after that date. - Latest tagged dir: v7.3-rc3 (2026-09-14). v7.3-rc4, rc5, rc6, rc7 and v7.3 (final, tagged upstream 2026-10-18) do not exist. - https://kernel.ubuntu.com/mainline/v7.3/ returns 404. - The last daily run itself built fine on amd64, arm64, armhf, ppc64el and s390x. amd64 self-tests failed (rc=2). i386 build failed after 8s (rc=2). riscv64 reported success in 10s with no .debs. This looks like the scheduler/trigger stopped, not a compile failure. Similar multi-week stalls happened in Oct 2023 and Sep 2024. Request: please restore the build pipeline, and publish v7.3-rc4 through v7.3 if possible. Commands used: curl -s https://kernel.ubuntu.com/mainline/ | grep -E 'v7\.3' curl -s https://kernel.ubuntu.com/mainline/daily/ | grep -oE 'href="[0-9-]+/"' | tail -5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171810/+subscriptions

вторник

[Bug 2171324] Re: snd-usb-audio: PreSonus StudioLive 16.0.2 USB stays at 44.1 kHz after another program opens it at 44.1 kHz (needs power cycle)

Thank you very much for reporting this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171324 Title: snd-usb-audio: PreSonus StudioLive 16.0.2 USB stays at 44.1 kHz after another program opens it at 44.1 kHz (needs power cycle) Status in linux package in Ubuntu: New Bug description: Subject: snd-usb-audio: PreSonus StudioLive 16.0.2 USB stays at 44.1 kHz after another program opens it at 44.1 kHz (needs power cycle) Device: PreSonus StudioLive 16.0.2 USB (idVendor=194f, idProduct=0901), USB audio, 18 capture channels, rates 44100/48000. System: Ubuntu 24.04 (MATE), kernel 6.8.0-146-generic, PipeWire 1.0.5. Hardware: MSI MPG Z490 Gaming Plus, xHCI controller. Problem: When PipeWire is not holding the device open (idle), any program that opens it directly at 44100 Hz leaves it at 44.1 kHz. Everything on the system then plays about 1.45 semitones lower and slower. Opening it again at 48000 Hz does not fix it. Re-enumerating the device does not fix it (echo 0/1 > /sys/bus/usb/devices/1-1/authorized). Only a power cycle of the console restores 48 kHz. Reproduce (device idle, a video playing through the console at 48 kHz): arecord -D plughw:CARD=USB,DEV=0 -r 44100 -f S16_LE -c 2 -d 2 /dev/null Pitch drops right away. /proc/asound/USB/stream0 then shows "Momentary freq = 44099 Hz" on the playback endpoint. usbmon shows a single SET_CUR (clock) request to 44100 Hz, with no request back to 48000 Hz afterwards: Co:1:041:0 s 21 01 0100 2900 0004 4 = 44ac0000 Audacity 4 triggers the same thing when it probes the sound cards at startup (strace shows it opening /dev/snd/pcmC4D0c and pcmC4D0p). Audacity causes this issue at start. Questions: 1. Is this a console firmware behaviour or a snd-usb-audio issue? 2. Did earlier kernels reset the clock differently? (My old Ubuntu 20.04 setup with PulseAudio did not show it.) 3. Is a quirk for this device appropriate? ╭─(skyern@skyern-desktop:~)─(dim. 18 oct. 26 • 12:47:32) ╰──▸ sudo /usr/sbin/alsa-info.sh --no-upload lsusb -v -d 194f:0901 > ~/lsusb.txt 2>&1 uname -r [sudo] Mot de passe de skyern : sudo: /usr/sbin/alsa-info.sh : commande introuvable 6.8.0-147-generic ╭─(skyern@skyern-desktop:~)─(dim. 18 oct. 26 • 12:48:03) ╰──▸ cat /proc/version_signature > version.log ╭─(skyern@skyern-desktop:~)─(dim. 18 oct. 26 • 12:48:04) ╰──▸ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: No such device ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-147-generic 6.8.0-147.147 ProcVersionSignature: Ubuntu 6.8.0-147.147-generic 6.8.12 Uname: Linux 6.8.0-147-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sun Oct 18 12:45:21 2026 HibernationDevice: RESUME=UUID=d89378d1-1a70-4271-9daa-987ddf5435be InstallationDate: Installed on 2016-09-30 (3670 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Micro-Star International Co., Ltd. MS-7C75 ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-147-generic root=UUID=6055cc62-8cbc-4e99-b10c-2632d39bf84a ro quiet splash nvidia-drm.modeset=1 scsi_mod.dev_flags_ignore=1 libata.noacpi=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-147-generic N/A linux-backports-modules-6.8.0-147-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to noble on 2026-10-12 (6 days ago) dmi.bios.date: 06/09/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.C0 dmi.board.asset.tag: Default string dmi.board.name: MPG Z490 GAMING PLUS (MS-7C75) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.C0:bd06/09/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C75:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ490GAMINGPLUS(MS-7C75):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7C75 dmi.product.sku: Default string 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/2171324/+subscriptions

[Bug 2171338] Re: Kernel panic in update_blocked_averages() on Ubuntu 24.04, linux 6.8.0-147-generic

Thank you very much for reporting this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171338 Title: Kernel panic in update_blocked_averages() on Ubuntu 24.04, linux 6.8.0-147-generic Status in linux package in Ubuntu: New Bug description: Description: On October 18, 2026, at approximately 17:18 CEST, my Ubuntu 24.04 LTS desktop became completely unresponsive and required a hardware reset. After rebooting, systemd-pstore recovered an EFI PStore dump containing a kernel panic from the preceding boot. Affected kernel: 6.8.0-147-generic #147-Ubuntu Hardware: AMD Ryzen 5 2400G with integrated Radeon Vega graphics MSI B450I GAMING PLUS AC (MS-7A40) BIOS A.72 (2019-05-20) Crash signature: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0-147-generic #147-Ubuntu RIP: 0010:update_blocked_averages+0x111/0x300 Call Trace: _nohz_idle_balance.isra.0 run_rebalance_domains handle_softirqs __irq_exit_rcu irq_exit_rcu sysvec_call_function_single Kernel panic - not syncing: Fatal exception in interrupt The crash occurred after approximately 16,906 seconds of kernel uptime, consistent with the observed time of the system freeze. Additional observation: The instruction bytes shown in the initial exception report differ from those printed again during the panic: 41 03 fd <3f> 0f 87 41 83 fd <3f> 0f 87 This discrepancy may warrant investigation for possible code or memory corruption. The underlying cause has not been established. The crash occurred in the scheduler's idle load-balancing path. Although the amdgpu module was loaded, it does not appear in the failing call trace. Reproduction: Not currently reproducible on demand. Expected result: The system should remain operational. Actual result: Fatal kernel exception and complete system freeze requiring a hardware reset. The complete EFI PStore dump is available as an attachment. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-147-generic 6.8.0-147.147 ProcVersionSignature: Ubuntu 6.8.0-147.147-generic 6.8.12 Uname: Linux 6.8.0-147-generic x86_64 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 17:57:58 2026 InstallationDate: Installed on 2025-07-13 (462 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Micro-Star International Co., Ltd. MS-7A40 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-147-generic root=UUID=d068eac6-c411-4f4f-8553-f85206207b0e ro quiet splash reboot=pci vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-147-generic N/A linux-backports-modules-6.8.0-147-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2025-07-13 (462 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.72 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) 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:bvnAmericanMegatrendsInc.:bvrA.72:bd05/20/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 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/2171338/+subscriptions

[Bug 2152063] Re: uname omits the year of kernel build

[Bug 2171543] Re: linux 7.0.0-38: hard lockup when idle on Sandy Bridge W520, 6.8.0-146 unaffected

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171543 Title: linux 7.0.0-38: hard lockup when idle on Sandy Bridge W520, 6.8.0-146 unaffected Status in linux package in Ubuntu: New Bug description: After upgrading from Ubuntu 24.04 to 26.04 this machine hard-locks reliably while idle. The kernel stops executing entirely: no log entry, no panic, no MCE. Booting the previous kernel 6.8.0-146-generic on the same 26.04 userspace makes the problem disappear. Bad kernel: linux-image-7.0.0-38-generic 7.0.0-38.38 Good kernel: linux-image-6.8.0-146-generic 6.8.0-146.146 SYSTEM ThinkPad W520 (type 4284W84), BIOS 8BET56WW (1.36) Intel Core i7-2760QM (Sandy Bridge), microcode 0x2f intel-microcode 3.20260210.1ubuntu2 32 GB RAM (4 x 8 GB Crucial CT8G3S1339M, 1333 MT/s) Intel HD 3000 (i915) + NVIDIA Quadro 1000M (nouveau) Ubuntu 26.04.1 LTS, GNOME on Wayland, legacy BIOS boot, LVM root SYMPTOMS Complete hard lockup, always while idle, never under load. - Screen keeps showing the last rendered frame, no corruption - Keyboard and mouse dead, including the internal PS/2 keyboard - SysRq (REISUB) has no effect, kernel.sysrq=1 verified active - Hard disk LED dark, no I/O - Mouse LED sometimes off, sometimes lit (varies between occurrences) - Nothing in the journal, the log simply ends mid-operation EVIDENCE THAT THE MACHINE TRULY HALTS A 10-second watchdog logger with fsync after every write, plus the regular 10-minute sysstat-collect timer, were used as a heartbeat. Example, lockup at 17:08:30: ticks at 16:40, 16:50 and 17:00 are present; the ticks at 17:10, 17:20 and 17:30 are missing, and the machine was not restarted until 17:36. So the kernel stopped executing rather than merely losing input. TIME TO LOCKUP 7.0.0-38, nouveau loaded ............ 25 min / 35 min / 74 min 7.0.0-38, dGPU disabled in BIOS ..... 2 h 14 / 3 h 30 / 3 h 27 7.0.0-38, intel_idle.max_cstate=1 ... 3 h 27 6.8.0-146, dGPU disabled in BIOS .... 35 h 49 awake, NO LOCKUP Awake time excludes suspend; measured from gaps in the logger output, not from uptime. Nine lockups occurred in total under 7.0.0-38. RULED OUT Thermal - logger shows 57-74 degC package temperature and load ~1.2 at the moment of death, throttle counters static for hours Memory - memtest86+ clean overnight, no EDAC or MCE messages ever USB - no over-current, disconnect or xHCI errors in the entire journal history; the dead input includes the internal PS/2 keyboard C-states - intel_idle.max_cstate=1 verified active via /proc/cmdline and the cpuidle state list (only POLL and C1 left); no improvement OOM - 31 GB RAM with about 26 GB available Storage - HDD LED dark, no I/O stall pattern NOTE ON NOUVEAU With nouveau loaded the lockups came roughly four times as often. Disabling the discrete Quadro 1000M in the BIOS (Integrated Graphics) lengthened the mean time to failure from about 45 minutes to about 3 hours, but did not stop them. This looks like an aggravating factor rather than the cause. REPRODUCTION 1. Boot 7.0.0-38-generic on this hardware 2. Log into a GNOME Wayland session and leave the machine idle 3. Within a few hours the machine hard-locks as described Booting 6.8.0-146-generic and repeating the same usage does not reproduce it. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: falk 2515 F.... wireplumber /dev/snd/seq: falk 2398 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 21:01:54 2026 InstallationDate: Installed on 2020-01-14 (2471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 4284W84 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-06 (15 days ago) dmi.bios.date: 01/19/2012 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4284W84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8BET56WW(1.36):bd01/19/2012:br1.36:efr1.32:svnLENOVO:pn4284W84:pvrThinkPadW520:rvnLENOVO:rn4284W84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:pfaThinkPadW520: dmi.product.family: ThinkPad W520 dmi.product.name: 4284W84 dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171543/+subscriptions