[Bug 2155117] [NEW] Hibernation fail

Public bug reported: I need to hard stop the computer to restart. 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: pass CurrentDesktop: KDE Date: Wed Jun 3 08:43:20 2026 HibernationDevice: RESUME=UUID=de72cf33-6e73-400a-a963-810f483fe78a InstallationDate: Installed on 2025-04-19 (410 days ago) InstallationMedia: Ubuntu-Studio 25.04 "Plucky Puffin" - Release amd64 (20250415.2) MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 15 M5506WA_M5506WA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=de72cf33-6e73-400a-a963-810f483fe78a ro quiet splash resume=UUID=de72cf33-6e73-400a-a963-810f483fe78a resume_offset=6623232 preempt=full threadirqs rcu_nocbs=all usbcore.autosuspend=-1 amd_pmc.disable_ps0_barrier=1 preempt=full threadirqs rcu_nocbs=all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (20 days ago) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M5506WA.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M5506WA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5506WA.316:bd01/05/2026:br5.35:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS15M5506WA_M5506WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5506WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSVivobookS15: dmi.product.family: ASUS Vivobook S 15 dmi.product.name: ASUS Vivobook S 15 M5506WA_M5506WA 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 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155117 Title: Hibernation fail Status in linux package in Ubuntu: New Bug description: I need to hard stop the computer to restart. 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: pass CurrentDesktop: KDE Date: Wed Jun 3 08:43:20 2026 HibernationDevice: RESUME=UUID=de72cf33-6e73-400a-a963-810f483fe78a InstallationDate: Installed on 2025-04-19 (410 days ago) InstallationMedia: Ubuntu-Studio 25.04 "Plucky Puffin" - Release amd64 (20250415.2) MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 15 M5506WA_M5506WA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=de72cf33-6e73-400a-a963-810f483fe78a ro quiet splash resume=UUID=de72cf33-6e73-400a-a963-810f483fe78a resume_offset=6623232 preempt=full threadirqs rcu_nocbs=all usbcore.autosuspend=-1 amd_pmc.disable_ps0_barrier=1 preempt=full threadirqs rcu_nocbs=all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (20 days ago) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M5506WA.316 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M5506WA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5506WA.316:bd01/05/2026:br5.35:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS15M5506WA_M5506WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5506WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSVivobookS15: dmi.product.family: ASUS Vivobook S 15 dmi.product.name: ASUS Vivobook S 15 M5506WA_M5506WA 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/2155117/+subscriptions

[Bug 2154418] Re: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes

** Changed in: linux (Ubuntu Questing) Status: In Progress => 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/2154418 Title: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: In Progress Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in alsa-ucm-conf source package in Questing: In Progress 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: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [ Impact ] Some newer audio configurations require SoundWire/SDCA updates for companion amplifier handling, AMD ACP7.0 Realtek match entries, Lenovo AMD SoundWire DMIC quirks, combined speaker component naming, and RT722 speaker mute control. Without these fixes, affected systems may fail to expose the expected audio topology, DMIC component naming, PCM numbering, or speaker mute switch needed by userspace/UCM. [ Fix ] Backport upstream commits: - f5cb3ee251b4 ("ASoC: SDCA: Add companion amp Function") - 7869f1c1123c ("ASoC: amd: acp: Add ACP7.0 match entries for Realtek parts") - 3acf517e1ae0 ("ASoC: amd: amd_sdw: add machine driver quirk for Lenovo models") - 68130eef1e0d ("ASoC: soc-component: re-add pcm_new()/pcm_free()") - fe33a69681e3 ("ASoC: amd: name back to pcm_new()/pcm_free()") - 5902e1f3c501 ("ASoC: amd: acp: update dmic_num logic for acp pdm dmic") - 371f6a1d2a97 ("ASoC: amd: acp-sdw-legacy: rename the dmic component name") - 3666dc0c47c3 ("ASoC: amd: ps: fix the pcm device numbering for acp pdm dmic") - 80a7916ca2d9 ("ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine") - 6b6f7263d626 ("ASoC: amd: acp: update DMI quirk and add ACP DMIC for Lenovo platforms") - 87a3f5c8ac20 ("ASoC: sdw_utils: cs42l43: allow spk component names to be combined") - bda41dd5e1dd ("ASoC: rt722-sdca: add FU06 Playback Switch for speaker mute control") [ Test Plan ] Boot affected hardware and verify: 1. Sound card probes successfully. 2. Expected ALSA PCMs and controls are present. 3. DMIC capture works on affected AMD SoundWire platforms. 4. Speaker playback works. 5. Speaker mute control is exposed and can be toggled by userspace. [ Where problems could occur ] The changes affect ASoC SoundWire/SDCA machine matching, component naming, PCM setup, and RT722 codec mute handling. Regressions could appear as sound card probe failures, changed component strings affecting UCM matching, missing or renumbered PCM devices, or incorrect speaker mute behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2154418/+subscriptions

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

For resolute this fix is merged at kernel 7.0.0-26.26, currently it's not in proposed yet. linux (7.0.0-26.26) resolute; urgency=medium * resolute/linux: 7.0.0-26.26 -proposed tracker (LP: #2154530) * Packaging resync (LP: #1786013) - Revert "UBUNTU: SAUCE: import Huawei ES3000_V2 (2.1.0.23)" - [Packaging] debian.master/dkms-versions -- remove dkms-versions (main/2026.05.18) * Fix mic mute led on a HP EliteBook 6 G2a platform (LP: #2150065) - ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2a Laptops * ov08x40 module mounted upside down on a certain DELL platforms (LP: #2146517) - SAUCE: media: ipu-bridge: Add DMI quirk for new Dell XPS laptops with upside down sensors - SAUCE: media: ipu-bridge: Add DMI quirk for Dell 14 laptops with upside down sensors * Support additional 2888x1808@30fps 900MHz for OVTI05C1 camera sensor (LP: #2147409) - SAUCE: media: ipu-bridge: Add 900MHz for OV05C10 - SAUCE: platform/x86: int3472: increase handshake delay to 50ms for OV05C10 * Support Samsung S5K3J1 sensor for Intel MIPI camera (LP: #2121852) - SAUCE: media: ipu-bridge: Support s5k3j1 sensor * [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms (LP: #2150196) - ASoC: Intel: soc-acpi-intel-ptl-match: drop rt722 monolithic match tables - ASoC: SOF: Intel: Add a is_amp flag to fix the wrong name prefix - ASoC: sdw_utils: add rt1320 and rt1321 dmic dai in codec_info_list -- 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 Committed 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 Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: New Status in alsa-ucm-conf source package in Resolute: Fix Committed 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 2150196] Re: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms

Installed the 26.04 and enabled the proposed channel, but the speaker is Dummy and no mic device. $ uname -an Linux Bowser-SIT-S11 7.0.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Mon May 25 15:54:34 UTC 2026 x86_64 GNU/Linux $ apt-cache policy alsa-ucm-conf alsa-ucm-conf: Installed: 1.2.15.3-1ubuntu1.2 Candidate: 1.2.15.3-1ubuntu1.2 Version table: *** 1.2.15.3-1ubuntu1.2 100 100 http://archive.ubuntu.com/ubuntu resolute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.2.15.3-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages -- 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 Committed 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 Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: New Status in alsa-ucm-conf source package in Resolute: Fix Committed 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 2154418] Re: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes

** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505879 ** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505880 ** Merge proposal linked: https://code.launchpad.net/~mapengyu/ubuntu/+source/alsa-ucm-conf/+git/alsa-ucm-conf/+merge/505881 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154418 Title: Backport ASoC SDCA, AMD SoundWire, and RT722 audio fixes Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: In Progress Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in alsa-ucm-conf source package in Questing: In Progress Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [ Impact ] Some newer audio configurations require SoundWire/SDCA updates for companion amplifier handling, AMD ACP7.0 Realtek match entries, Lenovo AMD SoundWire DMIC quirks, combined speaker component naming, and RT722 speaker mute control. Without these fixes, affected systems may fail to expose the expected audio topology, DMIC component naming, PCM numbering, or speaker mute switch needed by userspace/UCM. [ Fix ] Backport upstream commits: - f5cb3ee251b4 ("ASoC: SDCA: Add companion amp Function") - 7869f1c1123c ("ASoC: amd: acp: Add ACP7.0 match entries for Realtek parts") - 3acf517e1ae0 ("ASoC: amd: amd_sdw: add machine driver quirk for Lenovo models") - 68130eef1e0d ("ASoC: soc-component: re-add pcm_new()/pcm_free()") - fe33a69681e3 ("ASoC: amd: name back to pcm_new()/pcm_free()") - 5902e1f3c501 ("ASoC: amd: acp: update dmic_num logic for acp pdm dmic") - 371f6a1d2a97 ("ASoC: amd: acp-sdw-legacy: rename the dmic component name") - 3666dc0c47c3 ("ASoC: amd: ps: fix the pcm device numbering for acp pdm dmic") - 80a7916ca2d9 ("ASoC: amd: acp: add Lenovo P16s G5 AMD quirk for legacy SDW machine") - 6b6f7263d626 ("ASoC: amd: acp: update DMI quirk and add ACP DMIC for Lenovo platforms") - 87a3f5c8ac20 ("ASoC: sdw_utils: cs42l43: allow spk component names to be combined") - bda41dd5e1dd ("ASoC: rt722-sdca: add FU06 Playback Switch for speaker mute control") [ Test Plan ] Boot affected hardware and verify: 1. Sound card probes successfully. 2. Expected ALSA PCMs and controls are present. 3. DMIC capture works on affected AMD SoundWire platforms. 4. Speaker playback works. 5. Speaker mute control is exposed and can be toggled by userspace. [ Where problems could occur ] The changes affect ASoC SoundWire/SDCA machine matching, component naming, PCM setup, and RT722 codec mute handling. Regressions could appear as sound card probe failures, changed component strings affecting UCM matching, missing or renumbered PCM devices, or incorrect speaker mute behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2154418/+subscriptions

[Bug 2154785] Re: Enable device tree overlay configs for PCIe based devices

** 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/2154785 Title: Enable device tree overlay configs for PCIe based devices Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Questing: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: The following configuration options will allow PCIe FPGA devices to provide memory mapped access to IP cores in the same manner as FPGA- ARM based SoC solutions using existing drivers. - CONFIG_OF=y - CONFIG_OF_OVERLAY=y - CONFIG_DTC=y - CONFIG_PCI_DYNAMIC_OF_NODES=y This has been requested by AMD. Without these options enabled new drivers will need to be written just for the x86 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154785/+subscriptions

[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system

~sholeh-feathermoon Install 7.0.0-17 using this command: sudo apt install linux-generic/resolute-proposed And make sure to select the -17 kernel in your bootloader -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Triaged Status in linux source package in Resolute: Triaged Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions

[Bug 2154785] [NEW] Enable device tree overlay configs for PCIe based devices

Public bug reported: The following configuration options will allow PCIe FPGA devices to provide memory mapped access to IP cores in the same manner as FPGA-ARM based SoC solutions using existing drivers. - CONFIG_OF=y - CONFIG_OF_OVERLAY=y - CONFIG_DTC=y - CONFIG_PCI_DYNAMIC_OF_NODES=y This has been requested by AMD. Without these options enabled new drivers will need to be written just for the x86 platform. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) 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/2154785 Title: Enable device tree overlay configs for PCIe based devices Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Questing: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: The following configuration options will allow PCIe FPGA devices to provide memory mapped access to IP cores in the same manner as FPGA- ARM based SoC solutions using existing drivers. - CONFIG_OF=y - CONFIG_OF_OVERLAY=y - CONFIG_DTC=y - CONFIG_PCI_DYNAMIC_OF_NODES=y This has been requested by AMD. Without these options enabled new drivers will need to be written just for the x86 platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154785/+subscriptions

[Bug 2154162] Re: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument

Hi Alex, The install was block at the very beginning, there should be no log. But if you can guide how to collect, please share how-to. Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154162 Title: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 24.04.3 HWE kernel fails to install and displays stdin: Invalid argument The issue also happens with 24.04.4 HWE kernel installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154162/+subscriptions

[Bug 2154728] Re: GDS mitigation not enabled in Ubuntu kernel

** 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/2154728 Title: GDS mitigation not enabled in Ubuntu kernel Status in linux package in Ubuntu: New Bug description: TL;DR: Gather Data Sampling (GDS) vulnerability is not being mitigated in Ubuntu kernel because the config option CONFIG_MITIGATION_GDS is not enabled. This option is necessary so the microcode mitigation be enabled. I have an Intel CPU, and GDS should be mitigated by microcode, but since this config option is not enabled, I don't know if it's because performance or other reason, the mitigation in the microcode doesn't work. I'm comparing with my other kernel, the Liquorix, which has this config option enabled. With it I got: cat /sys/devices/system/cpu/vulnerabilities/gather_data_sampling Mitigation: Microcode Also, with the same kernel I got: sudo rdmsr 291 -a [sudo: authenticate] Password: CPU 0: 0 CPU 1: 0 CPU 2: 0 CPU 3: 0 CPU 4: 0 CPU 5: 0 CPU 6: 0 CPU 7: 0 CPU 8: 0 CPU 9: 0 CPU 10: 0 CPU 11: 0 CPU 12: 0 CPU 13: 0 CPU 14: 0 CPU 15: 0 0 is the correct value accordingly the Intel documentation. Without this option, the result for the command is 10, which means the mitigation is not being applied. How can we change that so the mitigation be put in place? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154728/+subscriptions

[Bug 2154769] Re: amdgpu forces YCbCr 4:4:4 on compatible HDMI monitors

** 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/2154769 Title: amdgpu forces YCbCr 4:4:4 on compatible HDMI monitors Status in linux package in Ubuntu: New Bug description: The amdgpu driver has a logic bug that forces YCbCr 4:4:4 on monitors that support the signal format, despite being suboptimal for desktop purposes. This YCbCr mode causes washed out colors and patterns due to the multiple lossy conversions (desktop framebuffer in RGB -> YCbCr over HDMI -> RGB for driving the LCD panel), as well as forcing "limited RGB (16-235)" which causes even further signal degradation. This is a widespread known issue, with multiple bug reports over the internet dating back to 2018, and with advanced EDID workarounds as the only solution: - https://lists.freedesktop.org/archives/amd-gfx/2021-May/063434.html - https://monado.freedesktop.org/edid-override.html - https://www.wezm.net/v2/posts/2020/linux-amdgpu-pixel-format/ - https://www.camillescott.org/2020/12/16/amdgpu-edid/ This is caused by the function fill_stream_properties_from_drm_display_mode in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c: /* TODO: un-hardcode */ if (drm_mode_is_420_only(info, mode_in) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if (drm_mode_is_420_also(info, mode_in) && aconnector && aconnector->force_yuv420_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR422)) && aconnector && aconnector->force_yuv422_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR422; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR444)) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR444; else timing_out->pixel_encoding = PIXEL_ENCODING_RGB; While YCbCr 4:2:0 and YCbCr 4:2:2 can be manually enabled and disabling using properties of the display, YCbCr 4:4:4 is forced by the function logic as long as supported by the display. Until the patches for manually changing the pixel encoding are merged (https://lkml.org/lkml/2026/3/24/1938 is the latest version from 2026, the first being from 2021), I suggest that the function is modified to *never* output YCbCr 4:4:4, by eg using a "#ifdef 0" block. Rationale being: - Intel and NVidia already prefer RGB 4:4:4, so this would make amdgpu behave as the other two mainstream drivers. - Unlike YCbCr 4:2:2 or 4:2:0 which result in lower bandwidth, YCbCr 4:4:4 uses the exact same HDMI bandwidth as RGB 4:4:4, so there is bandwidth budgetary reasons that would make it a preferred option over eg limited HDMI links. - YCbCr 4:4:4 is an optional mode specified in EDID. The CEA-861 standard *mandates* that all YCbCr 4:4:4 displays also support RGB, so supporting this mode does not allow using any more displays than RGB alone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154769/+subscriptions

[Bug 2154769] [NEW] amdgpu forces YCbCr 4:4:4 on compatible HDMI monitors

Public bug reported: The amdgpu driver has a logic bug that forces YCbCr 4:4:4 on monitors that support the signal format, despite being suboptimal for desktop purposes. This YCbCr mode causes washed out colors and patterns due to the multiple lossy conversions (desktop framebuffer in RGB -> YCbCr over HDMI -> RGB for driving the LCD panel), as well as forcing "limited RGB (16-235)" which causes even further signal degradation. This is a widespread known issue, with multiple bug reports over the internet dating back to 2018, and with advanced EDID workarounds as the only solution: - https://lists.freedesktop.org/archives/amd-gfx/2021-May/063434.html - https://monado.freedesktop.org/edid-override.html - https://www.wezm.net/v2/posts/2020/linux-amdgpu-pixel-format/ - https://www.camillescott.org/2020/12/16/amdgpu-edid/ This is caused by the function fill_stream_properties_from_drm_display_mode in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c: /* TODO: un-hardcode */ if (drm_mode_is_420_only(info, mode_in) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if (drm_mode_is_420_also(info, mode_in) && aconnector && aconnector->force_yuv420_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR422)) && aconnector && aconnector->force_yuv422_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR422; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR444)) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR444; else timing_out->pixel_encoding = PIXEL_ENCODING_RGB; While YCbCr 4:2:0 and YCbCr 4:2:2 can be manually enabled and disabling using properties of the display, YCbCr 4:4:4 is forced by the function logic as long as supported by the display. Until the patches for manually changing the pixel encoding are merged (https://lkml.org/lkml/2026/3/24/1938 is the latest version from 2026, the first being from 2021), I suggest that the function is modified to *never* output YCbCr 4:4:4, by eg using a "#ifdef 0" block. Rationale being: - Intel and NVidia already prefer RGB 4:4:4, so this would make amdgpu behave as the other two mainstream drivers. - Unlike YCbCr 4:2:2 or 4:2:0 which result in lower bandwidth, YCbCr 4:4:4 uses the exact same HDMI bandwidth as RGB 4:4:4, so there is bandwidth budgetary reasons that would make it a preferred option over eg limited HDMI links. - YCbCr 4:4:4 is an optional mode specified in EDID. The CEA-861 standard *mandates* that all YCbCr 4:4:4 displays also support RGB, so supporting this mode does not allow using any more displays than RGB alone. ** 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/2154769 Title: amdgpu forces YCbCr 4:4:4 on compatible HDMI monitors Status in linux package in Ubuntu: New Bug description: The amdgpu driver has a logic bug that forces YCbCr 4:4:4 on monitors that support the signal format, despite being suboptimal for desktop purposes. This YCbCr mode causes washed out colors and patterns due to the multiple lossy conversions (desktop framebuffer in RGB -> YCbCr over HDMI -> RGB for driving the LCD panel), as well as forcing "limited RGB (16-235)" which causes even further signal degradation. This is a widespread known issue, with multiple bug reports over the internet dating back to 2018, and with advanced EDID workarounds as the only solution: - https://lists.freedesktop.org/archives/amd-gfx/2021-May/063434.html - https://monado.freedesktop.org/edid-override.html - https://www.wezm.net/v2/posts/2020/linux-amdgpu-pixel-format/ - https://www.camillescott.org/2020/12/16/amdgpu-edid/ This is caused by the function fill_stream_properties_from_drm_display_mode in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c: /* TODO: un-hardcode */ if (drm_mode_is_420_only(info, mode_in) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if (drm_mode_is_420_also(info, mode_in) && aconnector && aconnector->force_yuv420_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR420; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR422)) && aconnector && aconnector->force_yuv422_output) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR422; else if ((connector->display_info.color_formats & BIT(DRM_OUTPUT_COLOR_FORMAT_YCBCR444)) && stream->signal == SIGNAL_TYPE_HDMI_TYPE_A) timing_out->pixel_encoding = PIXEL_ENCODING_YCBCR444; else timing_out->pixel_encoding = PIXEL_ENCODING_RGB; While YCbCr 4:2:0 and YCbCr 4:2:2 can be manually enabled and disabling using properties of the display, YCbCr 4:4:4 is forced by the function logic as long as supported by the display. Until the patches for manually changing the pixel encoding are merged (https://lkml.org/lkml/2026/3/24/1938 is the latest version from 2026, the first being from 2021), I suggest that the function is modified to *never* output YCbCr 4:4:4, by eg using a "#ifdef 0" block. Rationale being: - Intel and NVidia already prefer RGB 4:4:4, so this would make amdgpu behave as the other two mainstream drivers. - Unlike YCbCr 4:2:2 or 4:2:0 which result in lower bandwidth, YCbCr 4:4:4 uses the exact same HDMI bandwidth as RGB 4:4:4, so there is bandwidth budgetary reasons that would make it a preferred option over eg limited HDMI links. - YCbCr 4:4:4 is an optional mode specified in EDID. The CEA-861 standard *mandates* that all YCbCr 4:4:4 displays also support RGB, so supporting this mode does not allow using any more displays than RGB alone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154769/+subscriptions

[Bug 2154768] [NEW] After upgrading to linux-image-7.0.0-22-generic on Ubuntu 26.04 "Resolute Raccoon", the system fails to boot and shows a kernel panic. The previous kernel (7.0.0-15-generic) boots normally.

Public bug reported: == Steps to reproduce == 1. Run: sudo apt dist-upgrade 2. Reboot into the newly installed kernel 7.0.0-22-generic 3. System freezes immediately during boot with a kernel panic == Observed behaviour == The screen shows: Kernel Panic! Please reboot your computer. Fatal exception in interrupt With a Tux ASCII-Art in the top left corner. The CapsLock indicator LED starts blinking. Neither short nor long press of the power button triggers a reboot. A hardware reset (10 second power button hold) is required. No crash dump is available despite kdump-tools being active, suggesting the panic occurs before kdump is fully initialised. The entry for this boot attempt does not appear in journalctl. == Expected behaviour == System boots normally into 7.0.0-22-generic, as it does with 7.0.0-15-generic. == Workaround == Boot into the previous kernel (7.0.0-15-generic) via GRUB advanced options. == System information == Package: linux-image-7.0.0-22-generic 7.0.0-22.22 Working kernel: 7.0.0-15-generic System: Lenovo ThinkPad T14 Gen 5 Product name: 21MLCTO1WW BIOS version: N47ET28W (1.17) Architecture: x86_64 Ubuntu release: 26.04 "Resolute Raccoon" No external PPAs for kernel packages ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2154768/+attachment/5974946/+files/lspci-vnvn.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154768 Title: After upgrading to linux-image-7.0.0-22-generic on Ubuntu 26.04 "Resolute Raccoon", the system fails to boot and shows a kernel panic. The previous kernel (7.0.0-15-generic) boots normally. Status in linux package in Ubuntu: New Bug description: == Steps to reproduce == 1. Run: sudo apt dist-upgrade 2. Reboot into the newly installed kernel 7.0.0-22-generic 3. System freezes immediately during boot with a kernel panic == Observed behaviour == The screen shows: Kernel Panic! Please reboot your computer. Fatal exception in interrupt With a Tux ASCII-Art in the top left corner. The CapsLock indicator LED starts blinking. Neither short nor long press of the power button triggers a reboot. A hardware reset (10 second power button hold) is required. No crash dump is available despite kdump-tools being active, suggesting the panic occurs before kdump is fully initialised. The entry for this boot attempt does not appear in journalctl. == Expected behaviour == System boots normally into 7.0.0-22-generic, as it does with 7.0.0-15-generic. == Workaround == Boot into the previous kernel (7.0.0-15-generic) via GRUB advanced options. == System information == Package: linux-image-7.0.0-22-generic 7.0.0-22.22 Working kernel: 7.0.0-15-generic System: Lenovo ThinkPad T14 Gen 5 Product name: 21MLCTO1WW BIOS version: N47ET28W (1.17) Architecture: x86_64 Ubuntu release: 26.04 "Resolute Raccoon" No external PPAs for kernel packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154768/+subscriptions