[Bug 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms

This bug is awaiting verification that the linux-nvidia/7.0.0-1013.13 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-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. 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-nvidia-v2 verification-needed-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Released Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches:    - Speaker playback: aplay -D hw:0,2 tone.wav    - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz    - WirePlumber sees all devices    - Mute LEDs functional (speaker and mic)    - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions

[Bug 2154536] Re: Firefox crashes system and reboots on certain webpages

** Also 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/2154536 Title: Firefox crashes system and reboots on certain webpages Status in firefox package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: When I tried to open certain web pages on Firefox on an ARM64 machine (a ThinkPad X13s Gen 1 with a Snapdragon 8cx Gen 3 SoC), the screen would go black and the system would reboot. I have not tried it on chromium yet, but if that browser works, I will be using it until a patch is made. This happened to me twice on the following webpages https://swaywm.org and https://www.ti.com/tool/MSP-EXP430FR5994 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: firefox 1:1snap1-0ubuntu8 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic aarch64 ApportVersion: 2.34.0-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:22:42 2026 InstallationDate: Installed on 2026-05-28 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release arm64 (20260423.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> SnapChanges: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2154536/+subscriptions

[Bug 1040526] Re: Graphics dithered on Desktop image

Is this still an issue with a current release? ** Changed in: ubuntu-cdimage Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1040526 Title: Graphics dithered on Desktop image Status in Ubuntu CD Images: Incomplete Status in linux package in Ubuntu: Expired Bug description: The graphics on the install disk for the 20120821 Desktop image are dithered and ugly. See attached screen shot. WORKAROUND: Booting with kernel parameter: live video=ofonly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040526/+subscriptions

[Bug 2157970] [NEW] Enable micmute LED on HP EliteBook 6 G1a (AD3Q9ET#UUG)

Public bug reported: The HP EliteBook 6 G1a (SSID 103c:8e0d, SKU Number: AD3Q9ET#UUG) uses a Realtek ALC236 codec. Without a quirk no fixup is selected and the mic-mute LED stays off. It needs the same ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF quirk as the already-supported 14" variant (SSID 103c:8dfb). I've attached patch that enables mic-mute led with my current kernel (7.0.0-26-generic) Patch was built on top of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-26-generic 7.0.0-26.26 ProcVersionSignature: Ubuntu 7.0.0-26.26-generic 7.0.6 Uname: Linux 7.0.0-26-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:26:48 2026 HibernationDevice: UUID=e8d43458-12a7-473b-a92b-d47015438b66 InstallationDate: Installed on 2022-05-10 (1505 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-26-generic root=UUID=e8d43458-12a7-473b-a92b-d47015438b66 ro mitigations=off audit=0 apparmor=0 selinux=0 transparent_hugepage=always amd_pstate=active hibernate=nocompress,protect_image hibernate.compressor=lzo hibernate_compression_threads=8 resume=UUID=42953b41-f743-4d5b-ae16-f9f28892df68 amd_iommu=off iommu=noforce panic=0 snd_intel_dspcfg.dsp_driver=3 zswap.enabled=0 zswap.compressor=lz4 zswap.zpool=zsmalloc 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 2025-10-01 (265 days ago) dmi.bios.date: 05/12/2026 dmi.bios.release: 5.6 dmi.bios.vendor: HP dmi.bios.version: X76 Ver. 01.05.06 dmi.board.name: 8E0D dmi.board.vendor: HP dmi.board.version: KBC Version 58.31.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.49 dmi.modalias: dmi:bvnHP:bvrX76Ver.01.05.06:bd05/12/2026:br5.6:efr88.49:svnHP:pnHPEliteBook6G1a14inchNotebookNextGenAIPC:pvrSBKPFV3:rvnHP:rn8E0D:rvrKBCVersion58.31.00:cvnHP:ct10:cvr:skuAD3Q9ET#UUG:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC dmi.product.sku: AD3Q9ET#UUG dmi.product.version: SBKPFV3 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed resolute third-party-packages wayland-session ** Patch added: "v1_hpeb-6g1a-micmute.patch" https://bugs.launchpad.net/bugs/2157970/+attachment/5978564/+files/v1_hpeb-6g1a-micmute.patch -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157970 Title: Enable micmute LED on HP EliteBook 6 G1a (AD3Q9ET#UUG) Status in linux package in Ubuntu: New Bug description: The HP EliteBook 6 G1a (SSID 103c:8e0d, SKU Number: AD3Q9ET#UUG) uses a Realtek ALC236 codec. Without a quirk no fixup is selected and the mic-mute LED stays off. It needs the same ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF quirk as the already-supported 14" variant (SSID 103c:8dfb). I've attached patch that enables mic-mute led with my current kernel (7.0.0-26-generic) Patch was built on top of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-26-generic 7.0.0-26.26 ProcVersionSignature: Ubuntu 7.0.0-26.26-generic 7.0.6 Uname: Linux 7.0.0-26-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 12:26:48 2026 HibernationDevice: UUID=e8d43458-12a7-473b-a92b-d47015438b66 InstallationDate: Installed on 2022-05-10 (1505 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-26-generic root=UUID=e8d43458-12a7-473b-a92b-d47015438b66 ro mitigations=off audit=0 apparmor=0 selinux=0 transparent_hugepage=always amd_pstate=active hibernate=nocompress,protect_image hibernate.compressor=lzo hibernate_compression_threads=8 resume=UUID=42953b41-f743-4d5b-ae16-f9f28892df68 amd_iommu=off iommu=noforce panic=0 snd_intel_dspcfg.dsp_driver=3 zswap.enabled=0 zswap.compressor=lz4 zswap.zpool=zsmalloc 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 2025-10-01 (265 days ago) dmi.bios.date: 05/12/2026 dmi.bios.release: 5.6 dmi.bios.vendor: HP dmi.bios.version: X76 Ver. 01.05.06 dmi.board.name: 8E0D dmi.board.vendor: HP dmi.board.version: KBC Version 58.31.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.49 dmi.modalias: dmi:bvnHP:bvrX76Ver.01.05.06:bd05/12/2026:br5.6:efr88.49:svnHP:pnHPEliteBook6G1a14inchNotebookNextGenAIPC:pvrSBKPFV3:rvnHP:rn8E0D:rvrKBCVersion58.31.00:cvnHP:ct10:cvr:skuAD3Q9ET#UUG:pfa103C_5336ANHPEliteBook: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 6 G1a 14 inch Notebook Next Gen AI PC dmi.product.sku: AD3Q9ET#UUG dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2157970/+subscriptions

[Bug 2156867] Re: [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7

** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Assignee: (unassigned) => Bin Li (binli) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156867 Title: [SRU]Enable Realtek ALC287 + Cirrus CS35L56 Audio for Lenovo Yoga Pro 7 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware 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-firmware source package in Noble: In Progress 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-firmware 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 Status in linux source package in Stonking: In Progress Status in linux-firmware source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [ Impact ] Users running Ubuntu on newer Lenovo Yoga Pro 7 laptops experience critical audio subsystem degradation. The three primary failure points are: * Critically Low Speaker Volume: Sound output through the built-in speaker array is barely audible, even when userspace volume sliders are set to 100%. While the host Realtek ALC287 codec initializes, its companion Cirrus Logic CS35L56 smart amplifiers default to an uncalibrated, low-power fallback state ("FIRMWARE_MISSING") because the system lacks their manufacturer-supplied hardware-tuning profiles. * Non-Functional Speaker-Mute Keyboard LED: Pressing the F1 Audio Mute key on the keyboard toggles the stream status within PulseAudio/PipeWire correctly, but the physical amber LED hardware indicator on the keycap fails to illuminate. The software mute state is disconnected from the motherboard's GPIO controller. * Missing/Dead Microphone Array: The system completely fails to register or capture audio via the internal digital microphone array. The default driver stack attempts to locate the DMIC components on a digital sub-link connected directly to the main processor's AMD ACP block, whereas Lenovo routed the microphone hardware channels through the primary Realtek codec pins. [ Fix ] * Kernel Driver Fixes  - fc12cf16df9a ("ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11") - d0426510a9e1 ("ASoC: amd: acp: add DMI override for ACP70 flag")  - 17065203e1bc ("ALSA: hda/realtek:ALC269 fixup for Yoga Pro 7 15ASH11 mic mute LED")  - 83dca2530fb3 ("ALSA: hda/realtek: ALC269 fixup for Lenovo Yoga Pro 7 15ASH111 audio") * Firmware Environment Fixes  - d33a9c6d7661 ("cirrus: cs35l56: Update firmware for Cirrus Amps for a couple of Lenovo laptops")  - 604cb45fbe6d ("cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops")  - cc2cb17f5ed9 ("cirrus: cs35l56: Add firmware for Cirrus Amps for some ASUS laptops")  - 1d57ec2fdc3f ("cirrus: cs35l56: Add firmware for Cirrus Amps for some Lenovo laptops")  - 0c9b82b60972 ("cirrus: Add cs35l56 firmware symlinks for Asus UM5606KA") [ Test Plan ] Install the patched kernel package and updated linux-firmware payload on an affected Lenovo Yoga Pro 7, then reboot to check: 1. Verify Amp Calibration & Speaker Volume:   Play an audio stream at a standard volume level (30–50%). Confirm it produces crisp, loudly scaled audio. 2. Verify Microphone Capture:    Open Ubuntu Settings -> Sound -> Input. Confirm that the ghost "Digital Microphone" tied to the AMD ACP is gone, and a functioning Internal Stereo Microphone device is present.  Speak or tap on the chassis to confirm that the input visualizer bar responds dynamically to incoming audio data. 3 Verify Mute LED and Mic LED Illumination:    Press the physical F1/F4 Mute hotkey. The amber LED light on the keycap must illuminate immediately when muted, and cleanly shut off as soon as the system is unmuted. [ Where problems could occur ] Scope of Regression: Extremely isolated. All changes are heavily guarded behind rigid DMI string check loops inside vendor-specific sub-drivers (AMD ACP matching tables, Realtek HDA quirk lists, and specific sub-hardware ID firmware loading paths). Systems built by other vendors (such as Dell, HP, or ASUS) or other laptop lines will bypass these conditional rules entirely. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156867/+subscriptions

[Bug 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)

Kernel EOL, and this is not referenced in our hint database. Closing it. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1894964 Title: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build) Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Expired Status in linux source package in Groovy: Won't Fix Bug description: Issue found on 5.8.0-1001.1 - kvm Test build failed with: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' In file included from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In function ‘__func_get_name’: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38: warning: nested extern declaration of ‘__compiletime_assert_0’ [-Wnested-externs] 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~~~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15: note: in definition of macro ‘__compiletime_assert’ 16 | extern void prefix ## suffix(void) __compiletime_error(msg); \ | ^~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2: note: in expansion of macro ‘_compiletime_assert’ 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’ 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~~~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’ 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) | ^~~~~~~~~~~~~~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: note: in expansion of macro ‘BUILD_BUG_ON’ 20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID); | ^~~~~~~~~~~~ libbpf: failed to open format: No such file or directory Error: failed to load BTF from format: No such file or directory make[1]: *** [Makefile:190: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h] Error 2 make[1]: *** Deleting file '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h' make: *** [Makefile:157: all] Error 2 Please find attachment for the complete build log. As the ubuntu_kernel_selftests needs bpf to be built first, this will block the ubuntu_kernel_selftests/net to build as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+subscriptions

[Bug 2139264] Re: Internal microphone not detected on ASUS ExpertBook BM1503CDA (AMD Rembrandt)

I have important update to you. I was tired to wait and discovered the problem deeper by myself. It turned out, that it was needed to add my notebook modelname to linux kernel repo. Moreower, it turned out, that there are alredy commit for it https://github.com/torvalds/linux/commit/32fc4168fa56f6301d858c778a3d712774e9657e So the only thing you need to do is ship newer kernel version and it will work -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2139264 Title: Internal microphone not detected on ASUS ExpertBook BM1503CDA (AMD Rembrandt) Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: I am reporting an issue where the internal digital microphone (DMIC) is not recognized on my ASUS ExpertBook BM1503CDA. Hardware Environment: - Laptop: ASUS ExpertBook BM1503CDA - CPU: AMD Rembrandt (Ryzen 7000 series) - Audio: AMD ACP 6x Audio Coprocessor [1022:15e2] (rev 60) - Codec: Realtek ALC256 - Kernel: 6.14.0-37-generic (Ubuntu 24.04) Problem Description: The system only detects the "Headset Mic" (0x19), but the internal digital microphone is completely missing from the available input devices. I have already tried the following without success: 1. Installing 'firmware-sof-signed' and 'alsa-ucm-conf'. 2. Setting 'options snd-intel-dspcfg dsp_driver=3'. 3. The 'lsmod' output confirms that 'snd_sof_amd_rembrandt' is loaded, but the microphone remains unavailable. It seems my specific Subsystem ID (0x00aa0100) is missing a quirk or proper PDM initialization in the current kernel version. ALSA Information Link: Your ALSA information is located at http://alsa-project.org/db/?f=7020c96e27dc0c4bd3f152402becd235267bb12d --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: andrej 2330 F.... wireplumber /dev/snd/controlC0: andrej 2330 F.... wireplumber /dev/snd/seq: andrej 2323 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2025-11-03 (86 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK BM1503CDA Package: linux (not installed) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-37-generic root=UUID=c440e49f-5260-4f6d-943e-6a58c876cc2b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.14.0-37.37~24.04.1-generic 6.14.11 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.14.0-37-generic N/A linux-backports-modules-6.14.0-37-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.23 Tags: noble Uname: Linux 6.14.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/17/2025 dmi.bios.release: 5.24 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: BM1503CDA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: BM1503CDA 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:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrBM1503CDA.317:bd04/17/2025:br5.24:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKBM1503CDA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnBM1503CDA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK BM1503CDA 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/2139264/+subscriptions

[Bug 2155161] Re: Jabra Evolve 2 85 headset keeps reconnecting via usb

ok nevermind it started again after some time on usb: [ 1288.759916] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 1288.885086] usb 3-3: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.43 [ 1288.885107] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1288.885114] usb 3-3: Product: YubiKey OTP+FIDO+CCID [ 1288.885119] usb 3-3: Manufacturer: Yubico [ 1288.890045] input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0/0003:1050:0407.0012/input/input38 [ 1288.999954] hid-generic 0003:1050:0407.0012: input,hidraw10: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:00:14.0-3/input0 [ 1289.000645] hid-generic 0003:1050:0407.0013: hiddev5,hidraw11: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-0000:00:14.0-3/input1 [ 1702.177125] usbhid 5-2.3.1.1:1.0: can't add hid device: -32 [ 1702.177415] usbhid 5-2.3.1.1:1.0: probe with driver usbhid failed with error -32 [ 1702.178710] usb 5-2.3.1: USB disconnect, device number 13 [ 1702.178721] usb 5-2.3.1.1: USB disconnect, device number 14 [ 1702.192644] hid-generic 0003:413C:B06F.0014: hiddev3,hidraw7: USB HID v1.11 Device [Dell dock] on usb-0000:06:00.0-2.3.5/input0 [ 1702.279588] hid-generic 0003:413C:B06E.0015: hiddev0,hidraw4: USB HID v1.11 Device [Dell Thunderbolt Dock WD19TBS] on usb-0000:06:00.0-2.5/input0 [ 1702.385646] hid-generic 0003:413C:B06E.0016: hiddev0,hidraw4: USB HID v1.11 Device [Dell Thunderbolt Dock WD19TBS] on usb-0000:06:00.0-2.5/input0 [ 1702.612804] usb 5-2.3.1: new full-speed USB device number 15 using xhci_hcd [ 1702.705301] usb 5-2.3.1: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=15.46 [ 1702.705321] usb 5-2.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1702.710459] hub 5-2.3.1:1.0: USB hub found [ 1702.711513] hub 5-2.3.1:1.0: 4 ports detected [ 1702.999146] usb 5-2.3.1.1: new full-speed USB device number 16 using xhci_hcd [ 1703.085323] usb 5-2.3.1.1: New USB device found, idVendor=0b0e, idProduct=24ba, bcdDevice= 1.00 [ 1703.085359] usb 5-2.3.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1703.085365] usb 5-2.3.1.1: Product: Jabra Evolve2 85 [ 1703.085368] usb 5-2.3.1.1: SerialNumber: 70BF92F3DA64 [ 1703.665054] input: Jabra Evolve2 85 as /devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:02.0/0000:06:00.0/usb5/5-2/5-2.3/5-2.3.1/5-2.3.1.1/5-2.3.1.1:1.0/0003:0B0E:24BA.0017/input/input39 [ 1703.716591] jabra 0003:0B0E:24BA.0017: input,hiddev4,hidraw9: USB HID v1.11 Device [Jabra Evolve2 85] on usb-0000:06:00.0-2.3.1.1/input0 [ 1705.069063] input: Jabra Evolve2 85 (AVRCP) as /devices/virtual/input/input40 [ 1712.988616] usbhid 5-2.3.1.1:1.0: can't add hid device: -32 [ 1712.988769] usbhid 5-2.3.1.1:1.0: probe with driver usbhid failed with error -32 [ 1713.186779] usb 5-2.3.1: USB disconnect, device number 15 [ 1713.186797] usb 5-2.3.1.1: USB disconnect, device number 16 [ 1713.371786] usb 5-2.3.1: new full-speed USB device number 17 using xhci_hcd [ 1713.466229] usb 5-2.3.1: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=15.46 [ 1713.466251] usb 5-2.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1713.473551] hub 5-2.3.1:1.0: USB hub found [ 1713.474696] hub 5-2.3.1:1.0: 4 ports detected [ 1713.751720] usb 5-2.3.1.1: new full-speed USB device number 18 using xhci_hcd [ 1713.837075] usb 5-2.3.1.1: New USB device found, idVendor=0b0e, idProduct=24ba, bcdDevice= 1.00 [ 1713.837094] usb 5-2.3.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1713.837100] usb 5-2.3.1.1: Product: Jabra Evolve2 85 [ 1713.837105] usb 5-2.3.1.1: SerialNumber: 70BF92F3DA64 [ 1714.478820] input: Jabra Evolve2 85 as /devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:02.0/0000:06:00.0/usb5/5-2/5-2.3/5-2.3.1/5-2.3.1.1/5-2.3.1.1:1.0/0003:0B0E:24BA.0018/input/input41 [ 1714.530198] jabra 0003:0B0E:24BA.0018: input,hiddev4,hidraw9: USB HID v1.11 Device [Jabra Evolve2 85] on usb-0000:06:00.0-2.3.1.1/input0 [ 1717.134009] input: Jabra Evolve2 85 (AVRCP) as /devices/virtual/input/input42 [ 1723.798328] usbhid 5-2.3.1.1:1.0: can't add hid device: -32 [ 1723.798510] usbhid 5-2.3.1.1:1.0: probe with driver usbhid failed with error -32 [ 1723.939002] usb 5-2.3.1: USB disconnect, device number 17 [ 1723.939021] usb 5-2.3.1.1: USB disconnect, device number 18 [ 1724.151743] usb 5-2.3.1: new full-speed USB device number 19 using xhci_hcd [ 1724.244170] usb 5-2.3.1: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=15.46 [ 1724.244192] usb 5-2.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1724.249039] hub 5-2.3.1:1.0: USB hub found [ 1724.249747] hub 5-2.3.1:1.0: 4 ports detected -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155161 Title: Jabra Evolve 2 85 headset keeps reconnecting via usb Status in linux package in Ubuntu: New Bug description: As soon as i want to use any kind of usb connection with the headset the usb connects and reconnects over and over again. I made sure its not an issue of cable used or the usb hub in the docking station. by connecting it directly to the laptop. Although i could use usb with this headset on ubuntu lts 24 without any issues since i reinstalled with kubuntu 26 this occurs (guess it would happen in ubuntu 26 too) I gladly provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 3 16:10:16 2026 InstallationDate: Installed on 2026-05-12 (22 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. Precision 3581 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=UUID=e1d7f812-2942-4efe-80f9-510636bb0378 ro quiet cryptdevice=UUID=24e90ca6-128d-41d3-be29-328e50acf97d:luks-24e90ca6-128d-41d3-be29-328e50acf97d root=/dev/mapper/luks-24e90ca6-128d-41d3-be29-328e50acf97d splash nvidia-drm.modeset=1 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: 12/12/2025 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0V8YXF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd12/12/2025:br1.27:efr1.25:svnDellInc.:pnPrecision3581:pvr:rvnDellInc.:rn0V8YXF:rvrA00:cvnDellInc.:ct10:cvr:sku0C07:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3581 dmi.product.sku: 0C07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155161/+subscriptions

[Bug 2157782] [NEW] doca-ofed-26-01-dkms build failure for resolute 7.0.0-28 lmm

Public bug reported: With the following change introduced for 7.0.0-28: sunrpc: Kill RPC_IFDEBUG() BugLink: https://bugs.launchpad.net/bugs/2156385 [ Upstream commit adcc59114ccd402259c089b0fea24da5e4974563 ] RPC_IFDEBUG() is used in only two places. In one the user of the definition is guarded by ifdeffery, in the second one it's implied due to dprintk() usage. Kill the macro and move the ifdeffery to the regular condition with the variable defined inside, while in the second case add the same conditional and move the respective code there. We are having a build issue for doca-ofed module (https://launchpadlibrarian.net/865905515/buildlog_ubuntu-resolute- amd64.linux-main-modules_7.0.0-28.28_BUILDING.txt.gz). Note this issue is due to code duplication and fix is actually provided in the commit about as well. make[4]: Entering directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0 You are using: gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0 warning: pahole version differs from the one used to build the kernel The kernel was built with: 131 You are using: 0 CC [M] transport.o CC [M] rpc_rdma.o CC [M] verbs.o CC [M] frwr_ops.o CC [M] ib_client.o CC [M] svc_rdma.o CC [M] svc_rdma_backchannel.o CC [M] svc_rdma_transport.o CC [M] svc_rdma_sendto.o CC [M] svc_rdma_recvfrom.o svc_rdma_transport.c: In function ‘svc_rdma_accept’: svc_rdma_transport.c:489:9: error: implicit declaration of function ‘RPC_IFDEBUG’; did you mean ‘RPCDBG_DEBUG’? [-Wimplicit-function-declaration] 489 | RPC_IFDEBUG(struct sockaddr *sap); | ^~~~~~~~~~~ | RPCDBG_DEBUG svc_rdma_transport.c:489:21: error: expected expression before ‘struct’ 489 | RPC_IFDEBUG(struct sockaddr *sap); | ^~~~~~ svc_rdma_transport.c:651:9: error: ‘sap’ undeclared (first use in this function); did you mean ‘swap’? 651 | sap = (struct sockaddr *)&newxprt->sc_cm_id->route.addr.src_addr; | ^~~ | swap svc_rdma_transport.c:651:9: note: each undeclared identifier is reported only once for each function it appears in make[6]: *** [/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.build:289: svc_rdma_transport.o] Error 1 make[6]: *** Waiting for unfinished jobs.... make[5]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:2115: .] Error 2 make[4]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:248: __sub-make] Error 2 make[4]: Leaving directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' make[3]: *** [Makefile:248: __sub-make] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-7.0.0-28-generic' make[2]: *** [makefile:73: default] Error 2 make[2]: Leaving directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' ** Affects: linux-main-modules (Ubuntu) Importance: Undecided Status: New ** Affects: linux-main-modules (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-main-modules (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Resolute) ** No longer affects: kernel-sru-workflow -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2157782 Title: doca-ofed-26-01-dkms build failure for resolute 7.0.0-28 lmm Status in linux-main-modules package in Ubuntu: New Status in linux-main-modules source package in Resolute: New Bug description: With the following change introduced for 7.0.0-28: sunrpc: Kill RPC_IFDEBUG() BugLink: https://bugs.launchpad.net/bugs/2156385 [ Upstream commit adcc59114ccd402259c089b0fea24da5e4974563 ] RPC_IFDEBUG() is used in only two places. In one the user of the definition is guarded by ifdeffery, in the second one it's implied due to dprintk() usage. Kill the macro and move the ifdeffery to the regular condition with the variable defined inside, while in the second case add the same conditional and move the respective code there. We are having a build issue for doca-ofed module (https://launchpadlibrarian.net/865905515/buildlog_ubuntu-resolute- amd64.linux-main-modules_7.0.0-28.28_BUILDING.txt.gz). Note this issue is due to code duplication and fix is actually provided in the commit about as well. make[4]: Entering directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0 You are using: gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0 warning: pahole version differs from the one used to build the kernel The kernel was built with: 131 You are using: 0 CC [M] transport.o CC [M] rpc_rdma.o CC [M] verbs.o CC [M] frwr_ops.o CC [M] ib_client.o CC [M] svc_rdma.o CC [M] svc_rdma_backchannel.o CC [M] svc_rdma_transport.o CC [M] svc_rdma_sendto.o CC [M] svc_rdma_recvfrom.o svc_rdma_transport.c: In function ‘svc_rdma_accept’: svc_rdma_transport.c:489:9: error: implicit declaration of function ‘RPC_IFDEBUG’; did you mean ‘RPCDBG_DEBUG’? [-Wimplicit-function-declaration] 489 | RPC_IFDEBUG(struct sockaddr *sap); | ^~~~~~~~~~~ | RPCDBG_DEBUG svc_rdma_transport.c:489:21: error: expected expression before ‘struct’ 489 | RPC_IFDEBUG(struct sockaddr *sap); | ^~~~~~ svc_rdma_transport.c:651:9: error: ‘sap’ undeclared (first use in this function); did you mean ‘swap’? 651 | sap = (struct sockaddr *)&newxprt->sc_cm_id->route.addr.src_addr; | ^~~ | swap svc_rdma_transport.c:651:9: note: each undeclared identifier is reported only once for each function it appears in make[6]: *** [/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.build:289: svc_rdma_transport.o] Error 1 make[6]: *** Waiting for unfinished jobs.... make[5]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:2115: .] Error 2 make[4]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:248: __sub-make] Error 2 make[4]: Leaving directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' make[3]: *** [Makefile:248: __sub-make] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-7.0.0-28-generic' make[2]: *** [makefile:73: default] Error 2 make[2]: Leaving directory '/<<PKGBUILDDIR>>/staging_dir/linux-main-modules/fake_dkms_root_folder/doca-ofed-26.01-dkms/26.01.1.0.0.0.609.1/build/mlnx-nfsrdma' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-main-modules/+bug/2157782/+subscriptions

[Bug 2154481] Re: Generic questing kernel oops on bootup with newer Nvidia machines

This bug is awaiting verification that the linux- nvidia-6.17/6.17.0-1024.24 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux- nvidia-6.17' to 'verification-done-noble-linux-nvidia-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux- nvidia-6.17' to 'verification-failed-noble-linux-nvidia-6.17'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154481 Title: Generic questing kernel oops on bootup with newer Nvidia machines Status in linux package in Ubuntu: New Status in linux source package in Questing: New Bug description: The following boot logs were noted on Questing deployment on lubba with questing 6.17.0-29.29 deployment through testfinger: [ 69.979129] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000cc^M [ 69.979141] Mem abort info:^M [ 69.979145] ESR = 0x0000000096000004^M [ 69.979146] EC = 0x25: DABT (current EL), IL = 32 bits^M [ 69.979147] SET = 0, FnV = 0^M [ 69.979148] EA = 0, S1PTW = 0^M [ 69.979148] FSC = 0x04: level 0 translation fault^M [ 69.979149] Data abort info:^M [ 69.979150] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000^M [ 69.979150] CM = 0, WnR = 0, TnD = 0, TagAccess = 0^M [ 69.979151] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0^M [ 69.979152] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000112a9e000^M [ 69.979154] [00000000000000cc] pgd=0000000000000000, p4d=0000000000000000^M [ 69.979158] Internal error: Oops: 0000000096000004 [#1] SMP^M [^[[0;32m OK ^[[0m] Listening on ^[[ 70.055117] Modules linked in: nouveau(+) gpu_sched drm_gpuvm drm_exec drm_ttm_helper ttm dax_hmem cxl_acpi drm_display_helper cxl_port cxl_core ast cec nvidia_cspmu rc_core einj ipmi_ssif(+) i2c_algo_bit arm_smmuv3_pmu arm_cspmu_module arm_spe_pmu uio_pdrv_genirq acpi_power_meter uio mlx5_fwctl acpi_ipmi spi_nor fwctl ipmi_devintf mtd cppc_cpufreq ipmi_msghandler sch_fq_codel efi_pstore dm_multipath nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear mlx5_ib ib_uverbs macsec ib_core mlx5_dpll uas polyval_ce usb_storage ghash_ce sm4_ce_gcm sm4_ce_ccm mlx5_core sm4_ce i2c_smbus nvme mlxfw sm4_ce_cipher nvme_core psample sm4 nvme_keyring sm3_ce tls sha3_ce xhci_pci_renesas pci_hyperv_intf nvme_auth i2c_tegra aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher^M [ 70.138368] CPU: 0 UID: 0 PID: 816 Comm: kworker/0:3 Not tainted 6.17.0-29-generic #29-Ubuntu PREEMPT(voluntary) ^M [ 70.148863] Hardware name: /P3880, BIOS 01.02.01 20240207^M [ 70.155180] Workqueue: events work_for_cpu_fn^M [ 70.159639] pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)^M [ 70.166755] pc : bit_entry+0x20/0x160 [nouveau]^M [ 70.171466] lr : nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.176422] sp : ffff80008c943740^M [ 70.179804] x29: ffff80008c943740 x28: 0000000000028648 x27: 0000000000000030^M [ 70.187099] x26: 0000000000000180 x25: 0000000000000180 x24: 0000000000000019^M [ 70.194393] x23: ffff80008c9437f7 x22: 0000000000000070 x21: ffff80008c94383f^M [ 70.201688] x20: ffff80008c94383e x19: 0000000000000000 x18: ffff80008c93b0d8^M [ 70.208983] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000^M [ 70.216278] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000^M [ 70.223572] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc70f0fe8a6a8^M [ 70.230866] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000^M [ 70.238161] x5 : ffff0000a4944700 x4 : ffff80008c9437f7 x3 : ffff80008c9437f6^M [ 70.245456] x2 : ffff80008c943792 x1 : 0000000000000070 x0 : 0000000000000000^M [ 70.252752] Call trace:^M [ 70.255246] bit_entry+0x20/0x160 [nouveau] (P)^M [ 70.259929] nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.264517] nvbios_pmuEp+0x60/0x120 [nouveau]^M [ 70.269102] nvkm_gsp_fwsec_init+0x90/0x1e0 [nouveau]^M [ 70.274311] nvkm_gsp_fwsec_sb_ctor+0x2c/0x60 [nouveau]^M [ 70.279693] r535_gsp_rm_boot_ctor+0x2c/0x138 [nouveau]^M [ 70.285072] r535_gsp_oneinit+0x258/0x340 [nouveau]^M [ 70.290093] gh100_gsp_oneinit+0x280/0x450 [nouveau]^M [ 70.295200] nvkm_gsp_oneinit+0x2c/0x70 [nouveau]^M [ 70.300040] nvkm_subdev_oneinit_+0x60/0x150 [nouveau]^M [ 70.305327] nvkm_subdev_init_+0x4c/0x190 [nouveau]^M [ 70.310345] nvkm_subdev_init+0x74/0xd8 [nouveau]^M [ 70.315184] nvkm_device_init+0x180/0x298 [nouveau]^M [ 70.320216] nvkm_udevice_init+0x78/0xa0 [nouveau]^M [ 70.325157] nvkm_object_init+0x50/0x200 [nouveau]^M [ 70.330094] nvkm_ioctl_new+0x198/0x280 [nouveau]^M [ 70.334938] nvkm_ioctl+0xd8/0x300 [nouveau]^M [ 70.339335] nvkm_client_ioctl+0x1c/0x48 [nouveau]^M [ 70.344285] nvif_object_ctor+0xf8/0x218 [nouveau]^M [ 70.349225] nvif_device_ctor+0x44/0xf0 [nouveau]^M [ 70.354070] nouveau_drm_device_new+0x1ec/0x438 [nouveau]^M [ 70.359639] nouveau_drm_probe+0xdc/0x250 [nouveau]^M [ 70.364672] local_pci_probe+0x48/0xd8^M [ 70.368505] work_for_cpu_fn+0x28/0x58^M [ 70.372335] process_one_work+0x174/0x428^M [ 70.376432] worker_thread+0x310/0x440^M [ 70.380262] kthread+0x110/0x130^M [ 70.383558] ret_from_fork+0x10/0x20^M [ 70.387215] Code: a9bc7bfd 910003fd a9025bf5 12001c36 (b940cc01) ^M [ 70.393445] ---[ end trace 0000000000000000 ]---^M Similar error was also noted on hinyari with full boot log attached. This causes undefined behavior, where in some cases the kernel boots up as well. The issue was reported upstream: https://lore.kernel.org/all/176698808133.6372.2408917375327107249@copycat/ and the fix has been accepted: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau?h=v7.1-rc5&id=e8b3627bec357698f2d4d6dbf27cdcfa0e9d8715 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154481/+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.

I checked the attached logs. For config_B (locally built test kernel), the after-replug dmesg does not show the same fatal NVMe failure seen in config_A. In config_B/3-config_B.after_replug.log/dmesg3.log, all three replugged NVMe devices probe and complete queue setup: 10000:01:00.0 -> nvme0, queues ready at line 3611 10000:02:00.0 -> nvme1, queues ready at line 3615 10000:03:00.0 -> nvme2, queues ready at line 3660 So based on the attached dmesg, the locally built test kernel does not reproduce the same NVMe probe/reset/resource-clobbering failure as config_A. If the failure is still seen from userspace, please provide lsblk/nvme list before unplug and after replug, plus any I/O error output. -- 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 2155617] Re: Backlight device disappears and brightness breaks on kernel 6.17.0-23+ (Lenovo Legion 5 Pro, NVIDIA hybrid graphics)

Hi Vesa Thank you for your information. Could you try the command below to fix the issue? ``` sudo apt update sudo apt install linux-modules-nvidia-570-generic-hwe-24.04 sudo reboot ``` after reboot, please check if modules be loaded, and backlight nodes showup ``` lsmod | grep nvidia ls /sys/class/backlight ``` BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155617 Title: Backlight device disappears and brightness breaks on kernel 6.17.0-23+ (Lenovo Legion 5 Pro, NVIDIA hybrid graphics) Status in linux package in Ubuntu: New Bug description: On Ubuntu 24.04.2 LTS running on a Lenovo Legion 5 Pro 16ACH6H (AMD + NVIDIA RTX 3070 hybrid system), brightness control breaks starting from kernel 6.17.0-23-generic and remains broken on all newer kernels up to 6.17.0-35. The issue is fully reproducible. WORKING KERNEL: - 6.17.0-22-generic - Display session: X11 - NVIDIA proprietary driver in use - Backlight device present: /sys/class/backlight/nvidia_0 - Brightness control works normally BROKEN KERNELS: - 6.17.0-23-generic and newer (tested up to 6.17.0-35) - Wayland or X11 both affected - Backlight directory is empty: /sys/class/backlight/ SYMPTOMS: - Brightness stuck at 100% - No backlight device exposed in sysfs - Mouse cursor shows trailing/ghosting artifacts on Wayland - Display rendering instability EXPECTED BEHAVIOR: - /sys/class/backlight/nvidia_0 should be present - Brightness control should function via NVIDIA DRM backlight interface ACTUAL BEHAVIOR: - No backlight device is registered at all in /sys/class/backlight/ - GNOME brightness controls have no effect HARDWARE: - Lenovo Legion 5 Pro 16ACH6H - AMD Ryzen CPU (iGPU present but not used for display in working kernel) - NVIDIA RTX 3070 Mobile (primary display output via nvidia-drm) - NVIDIA proprietary driver active REGRESSION: - Kernel 6.17.0-22 works correctly - 6.17.0-23 introduces regression and all newer kernels inherit it This appears to be a regression in NVIDIA DRM backlight device registration (fbdev / sysfs exposure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155617/+subscriptions

[Bug 2156421] Re: bug on keyboard keys kernel 7

** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156421 Title: bug on keyboard keys kernel 7 Status in linux package in Ubuntu: Incomplete Bug description: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156421/+subscriptions