вторник

[Bug 2174688] Re: [HDA/ALC897] ERYING Polestar H770 recording startup transient disappears with power_save=0

** 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/2174688 Title: [HDA/ALC897] ERYING Polestar H770 recording startup transient disappears with power_save=0 Status in linux package in Ubuntu: New Bug description: ## Problem and evidence An AnduinOS user reports a click, near-full-scale negative transient and distorted fade-in at the beginning of analogue microphone recordings. The same symptom occurs through direct ALSA capture with Audacity and EasyEffects closed. Temporarily changing only `snd_hda_intel.power_save` from 1 to 0 eliminates it immediately and after several idle minutes. A persistent setting was subsequently verified after reboot, with normal playback also working. These are results supplied by the affected user; the reporting maintainer does not own the hardware. The installed OS is AnduinOS, an Ubuntu derivative. Reproduction on an unmodified Ubuntu installation or Live image has not yet been performed. ## Hardware and software - Motherboard: ERYING Polestar H770. - Analogue codec: Realtek ALC897, reported as card 0/device 0; rear microphone pin 0x18, VREF_80. - Microphone: Comica LinkFlex AD2, connected to the rear motherboard microphone input. - Onboard controller: `00:1f.3`, Intel `8086:7a50`, PCI subsystem `8086:7270`, revision 11, `snd_hda_intel` in use. - Other HDA controllers: NVIDIA `10de:228e`, subsystem `1043:881d`; Intel `8086:e2f7`, subsystem `8086:1100`. - Initial OS report: AnduinOS 2.0.4, kernel `7.0.0-42-generic`. Workaround tests reported on `7.0.0-43-generic`. - PipeWire 1.6.2; corrected WirePlumber version 0.5.13. - Recording application: Audacity 3.7.8; package source and selected host/device are not yet documented. - Original `power_save=1`, `power_save_controller=Y`. Only `power_save` changed in the successful test; controller setting stayed Y. ## Reported reproduction and result 1. Start a recording through the rear microphone input with the original power-saving setting. The startup transient occurs, then the signal settles. 2. The user's direct capture command was `arecord -D plughw:0,0 -f cd -d 5 /tmp/alsa-mic-test.wav`; it produced the same fault with the higher-level audio applications closed. 3. Set `power_save=0` at runtime while leaving other settings unchanged. Immediate and post-idle recordings become clean. A small playback thud occurred during the parameter change itself. 4. Persist `options snd_hda_intel power_save=0`, rebuild initramfs and reboot: the user reports value 0, clean immediate/post-idle capture and normal playback. Windows capture on the same hardware was reported to work normally. A Linux kernel regression range has not been established. ## Request for maintainers Please advise whether a codec resume/de-pop fix or a narrowly matched power-management exception is appropriate, and which additional capture/codec diagnostics would distinguish them. The previously retrieved Ubuntu source at tag `Ubuntu-7.0.0-43.43` has no `8086:7270` entry in `power_save_denylist`. Its lookup uses PCI subsystem identifiers, not the primary controller device ID or codec ID. We are **not** proposing a blanket `8086:7270` entry: that identifier alone is insufficient evidence of an ERYING-specific match. The successful runtime workaround affects all devices of this driver and does not establish which exact upstream quirk is appropriate. ## Evidence and remaining diagnostic gaps - [Original report and direct ALSA reproduction](https://github.com/Anduin2017/AnduinOS/discussions/482). - [Temporary comparison](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19568477). - [Reboot, capture and playback verification](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19579355). - [Raw PCI output and Audacity version](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19657282). - [Matching Ubuntu driver source](https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/resolute/plain/sound/hda/controllers/intel.c?h=Ubuntu-7.0.0-43.43). Not yet supplied: full alsa-info output/codec dump, DMI board and BIOS identifiers, capture samples, exact installed kernel package revision, and an unmodified Ubuntu comparison. No measurements of power consumption are available. The separate Lenovo report is supporting context, not a confirmed duplicate with an identical root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174688/+subscriptions

[Bug 2174689] Re: [HDA/ALC233] Lenovo B40-80 built-in microphone startup distortion disappears with power_save=0

** 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/2174689 Title: [HDA/ALC233] Lenovo B40-80 built-in microphone startup distortion disappears with power_save=0 Status in linux package in Ubuntu: New Bug description: ## Problem and evidence A Lenovo B40-80 user reports startup distortion in recordings from the built-in microphone. Changing only `snd_hda_intel.power_save` to 0 resolves it, including recordings after idle. `power_save_controller` remains Y. The user has not performed a direct ALSA comparison with the original setting on this laptop. The observed reproduction is in Audacity 3.7.8. The reporting maintainer does not own this hardware. Reproduction on an unmodified Ubuntu installation or Live image has not yet been performed. ## Hardware and software - Lenovo B40-80; built-in microphone, not the external Comica used in the related desktop case. - AnduinOS 2.0.5, kernel `7.0.0-43-generic`. - Codec display name: Realtek ALC233; codec vendor ID `0x10ec0235`, codec subsystem ID `0x17aa3809`. - Analogue controller: `00:1b.0`, Intel `8086:9c20`, PCI subsystem `17aa:3902`, revision 04. - HDMI controller: `00:03.0`, Intel `8086:0a0c`, PCI subsystem `17aa:3902`, revision 0b. - Both PCI controllers use `snd_hda_intel`. - Current parameters: `power_save=0`, `power_save_controller=Y`, `pm_blacklist=-1`. - The laptop's original numeric timeout was not supplied. Only `power_save` was changed. - Audacity 3.7.8. Package source, selected audio host/device, and laptop-specific PipeWire/WirePlumber package versions remain unspecified. ## Reported comparison The built-in microphone had startup distortion in Audacity before the change. With `power_save=0`, recordings were clean, including after idle. The user retained the working configuration. Laptop-specific reboot, playback and suspend/resume checks were not explicitly reported; the fuller reboot/playback acceptance applies to the separate ERYING desktop. ## Request for maintainers Please advise on a codec resume/de-pop fix or appropriately scoped power-management exception, and which additional diagnostic data or comparison would be most useful. The previously retrieved Ubuntu source at tag `Ubuntu-7.0.0-43.43` has no `17aa:3902` entry in `power_save_denylist`. A straightforward PCI subsystem entry would match **both** the analogue and HDMI controllers shown here. We would like to avoid applying an exception more broadly than necessary. The codec subsystem `17aa:3809` must not be substituted for the PCI subsystem `17aa:3902` in that table. ## Evidence and remaining diagnostic gaps - [Laptop symptoms, microphone, codec and single-setting comparison](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19646208). - [Raw PCI output and Audacity version](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19657282). - [Matching Ubuntu driver source](https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/resolute/plain/sound/hda/controllers/intel.c?h=Ubuntu-7.0.0-43.43). Not yet supplied: full alsa-info output/codec dump, DMI/BIOS identifiers, recording samples, original timeout, package revisions and selected Audacity audio route. No direct ALSA before/after test, unmodified Ubuntu comparison or power measurement is claimed. The ERYING desktop case has stronger ALSA isolation evidence and is related context rather than an assumed identical defect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174689/+subscriptions

[Bug 2174716] Re: Lenovo ThinkPad T14s Gen 4 AMD (21F8): internal microphone not detected, snd_pci_ps finds no PDM device (ACP config 10)

** 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/2174716 Title: Lenovo ThinkPad T14s Gen 4 AMD (21F8): internal microphone not detected, snd_pci_ps finds no PDM device (ACP config 10) Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo ThinkPad T14s Gen 4 (AMD), machine type 21F8, BIOS R2EET51W (1.32), latest on LVFS OS: Ubuntu 26.04.1 LTS, kernel 7.0.0-43-generic (also tested: 7.0.0-14-generic, same result) Audio: AMD Audio Coprocessor [1022:15e2] rev 63 (PCI c3:00.5), subsystem 17aa:50d8, driver snd_pci_ps; codec ALC257 on HDA (c3:00.6) Problem: The internal (digital) microphone does not exist as a sound device. Only two HDA cards are present (HDMI and ALC257 analog). Recording from the default source gives pure silence (peak amplitude 0). The microphone worked without problems when the same laptop ran Windows, so the hardware is fine. Microphone is enabled in BIOS setup. Kernel log (snd_pci_ps loaded with dynamic debug): snd_pci_ps 0000:c3:00.5: ACP config value: 10 snd_pci_ps 0000:c3:00.5: No PDM or SoundWire manager devices found snd_pci_ps 0000:c3:00.5: get acp device config failed:-19 Observations: - snd_pci_ps is bound to the ACP device (not snd_pci_acp6x), so this is not the 6.8.x YC-variant conflict from LP #2061254. - Manually loading snd_ps_pdm_dma and snd_soc_ps_mach does not create any ACP sound card; no acp_*/dmic-* platform devices exist under /sys/devices. - The firmware ACPI tables contain AMD audio properties (SSDT7: acp-audio-device-type, acp-audio-ep-type, acp-audio-device-eps, ...) and AMDI0063/AMDI0052 in the DSDT, which Windows presumably uses to find the DMIC. Question: Is the ACP63 PDM detection in snd_pci_ps missing a case for this ACP config value / ACPI layout, or does it need a quirk for this platform? Happy to test patches. Attachments (collected on the machine): system info, audio dmesg, ACPI tables (DSDT, SSDT1-25), output of `ubuntu-bug linux` (automatic logs). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jarkko 4289 F.... wireplumber /dev/snd/controlC0: jarkko 4289 F.... wireplumber /dev/snd/seq: jarkko 4268 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 17 12:35:57 2026 InstallationDate: Installed on 2026-11-14 (3 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: LENOVO 21F8002JMX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=5bdb697e-d72d-43ad-a0e8-9cfc9ffccc12 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2026 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: R2EET51W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 21F8002JMX dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR2EET51W(1.32):bd07/10/2026:br1.32:efr1.19:svnLENOVO:pn21F8002JMX:pvrThinkPadT14sGen4:rvnLENOVO:rn21F8002JMX:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F8_BU_Think_FM_ThinkPadT14sGen4:pfaThinkPadT14sGen4: dmi.product.family: ThinkPad T14s Gen 4 dmi.product.name: 21F8002JMX dmi.product.sku: LENOVO_MT_21F8_BU_Think_FM_ThinkPad T14s Gen 4 dmi.product.version: ThinkPad T14s Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174716/+subscriptions

[Bug 2174761] Re: resolute/linux: apparmor: kernel fails to build with CONFIG_NETWORK_SECMARK=n

** 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/2174761 Title: resolute/linux: apparmor: kernel fails to build with CONFIG_NETWORK_SECMARK=n Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: A Resolute kernel fails to build when CONFIG_SECURITY_APPARMOR=y and CONFIG_NETWORK_SECMARK=n (for example, with CONFIG_SECURITY_SELINUX=n). Steps to reproduce:  1. Check out the Resolute kernel (master-next).  2. Set CONFIG_SECURITY_SELINUX=n and CONFIG_NETWORK_SECMARK=n, and keep     CONFIG_SECURITY_APPARMOR=y.  3. Build the kernel. The build fails in security/apparmor: ``` security/apparmor/lsm.c: In function 'apparmor_socket_sock_rcv_skb': security/apparmor/lsm.c:1907:14: error: implicit declaration of function 'aa_secmark_enabled' [-Werror=implicit-function-declaration] 1907 | if (!aa_secmark_enabled()) | ^~~~~~~~~~~~~~~~~~ security/apparmor/lsm.c:1921:63: error: 'struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1921 | if (label_mediates(label, AA_CLASS_NETV9_SKB) || skb->secmark) | ^~~~~~~ | mark security/apparmor/lsm.c: In function 'apparmor_inet_conn_request': security/apparmor/lsm.c:1949:63: error: 'struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1949 | if (label_mediates(label, AA_CLASS_NETV9_SKB) || skb->secmark) | ^~~~~~~ | mark security/apparmor/lsm.c: In function 'apparmor_ip_postroute': security/apparmor/lsm.c:1975:44: error: 'struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1975 | if (!aa_secmark_enabled() || !skb->secmark) | ^~~~~~~ | mark security/apparmor/lsm.c:1994:48: error: 'struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1994 | label = aa_secid_to_label(skb->secmark); /* may be NULL */ | ^~~~~~~ | mark security/apparmor/lsm.c: In function 'apparmor_ip_localout': security/apparmor/lsm.c:2066:14: error: 'struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 2066 | skb->secmark = out->secid; | ^~~~~~~ | mark security/apparmor/lsm.c: At top level: security/apparmor/lsm.c:1965:21: warning: 'apparmor_ip_postroute' defined but not used [-Wunused-function] 1965 | static unsigned int apparmor_ip_postroute(void *priv, | ^~~~~~~~~~~~~~~~~~~~~ cc1: some warnings being treated as errors make[4]: *** [scripts/Makefile.build:289: security/apparmor/lsm.o] Error 1 make[4]: *** Waiting for unfinished jobs.... security/apparmor/af_inet.c: In function 'match_addr_iface': security/apparmor/af_inet.c:1199:20: warning: unused variable 'tmp' [-Wunused-variable] 1199 | aa_state_t tmp = state; | ^~~ security/apparmor/af_inet.c: In function '__profile_skb_perm': security/apparmor/af_inet.c:1367:52: error: 'const struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1367 | skb->secmark, sk); | ^~~~~~~ | mark security/apparmor/af_inet.c: In function '__aa_sock_rcv_skb': security/apparmor/af_inet.c:1417:43: error: 'const struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1417 | seclabel = aa_secid_to_label(skb->secmark); /* may be NULL */ | ^~~~~~~ | mark security/apparmor/af_inet.c: In function '__aa_inet_conn_request': security/apparmor/af_inet.c:1451:43: error: 'const struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1451 | seclabel = aa_secid_to_label(skb->secmark); /* may be NULL */ | ^~~~~~~ | mark security/apparmor/af_inet.c: In function '__aa_ip_postroute': security/apparmor/af_inet.c:1485:43: error: 'const struct sk_buff' has no member named 'secmark'; did you mean 'mark'? 1485 | seclabel = aa_secid_to_label(skb->secmark); /* may be NULL */ | ^~~~~~~ | mark ``` Enabling CONFIG_SECURITY_SELINUX or CONFIG_NETWORK_SECMARK lets the build complete. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174761/+subscriptions

[Bug 2174770] Re: SRU request: cherry-pick ext4 stale-PTE fix (commit 9b25f381de6b) into Ubuntu 26.04 7.0 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/2174770 Title: SRU request: cherry-pick ext4 stale-PTE fix (commit 9b25f381de6b) into Ubuntu 26.04 7.0 kernel Status in linux package in Ubuntu: New Bug description: 1) Release of Ubuntu Ubuntu 26.04.1 LTS (Resolute Raccoon), Server install. 2) Package version linux-image-generic: Installed: 7.0.0-43.43 Candidate: 7.0.0-43.43 Running kernel: 7.0.0-43-generic #43-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 23 13:25:25 UTC 2026 3) What I expected to happen The system should remain stable serving large mmap'd model files from ext4 via the NVIDIA 595 open driver, without kernel panics during mm teardown, futex, or ext4 writeback paths. 4) What happened instead The host has suffered repeated wild-pointer kernel panics on 7.0.0-38, 7.0.0-42, and 7.0.0-43-generic: - BUG: unable to handle page fault in zap_pte_range / folio_remove_rmap_ptes during process exit - BUG: unable to handle page fault with a wild RIP in the futex path - BUG: unable to handle page fault in ext4_bio_write_folio during writeback - BUG: Bad page state in kswapd0 vmcores and dmesg are saved in /var/crash/. A near-identical public report exists at LP #2173885 (7.0.0-43-generic, NVIDIA 595 OOT, large mmap'd models, NULL-pointer crash in lruvec_stat_mod_folio -> folio_remove_rmap_ptes -> zap_pte_range). Root cause / fix requested The upstream fix is commit 9b25f381de6b ("ext4: unmap invalidated folios from page tables in mpage_release_unused_pages()"). It is in mainline 7.1+ and 7.3.x, but the upstream Linux 7.0 stable branch is EOL (last release 7.0.14, 2026-06-27), so it has not backported into Ubuntu 7.0 automatically. I verified it is absent from 7.0.0-43.43 and proposed 7.0.0-44.44. I am requesting a cherry-pick of 9b25f381de6b into the Ubuntu Resolute 7.0 kernel series. A backport patch against Ubuntu-7.0.0-44.44 is attached. Regression risk Very low: +15/-1 lines in fs/ext4/inode.c, only in the invalidate=true branch of mpage_release_unused_pages(), using the standard unmap_mapping_pages() helper. Attachments - ext4-stale-pte-fix-ubuntu-7.0.patch — proposed backport - release.log — lsb_release, uname, /proc/version_signature, apt-cache policy linux-image-generic - lspci-vnvn.log — lspci -vnvn Testing offered I can test a proposed 7.0.0-4x kernel build on the affected host and report whether the wild-pointer panics stop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174770/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-fde/5.15.0-1126.135)

All autopkgtests for the newly accepted linux-restricted-modules-azure-fde (5.15.0-1126.135) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf, i386) nvidia-graphics-drivers-390/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-fde [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

понедельник

[Bug 2174689] [NEW] [HDA/ALC233] Lenovo B40-80 built-in microphone startup distortion disappears with power_save=0

Public bug reported: ## Problem and evidence A Lenovo B40-80 user reports startup distortion in recordings from the built-in microphone. Changing only `snd_hda_intel.power_save` to 0 resolves it, including recordings after idle. `power_save_controller` remains Y. The user has not performed a direct ALSA comparison with the original setting on this laptop. The observed reproduction is in Audacity 3.7.8. The reporting maintainer does not own this hardware. Reproduction on an unmodified Ubuntu installation or Live image has not yet been performed. ## Hardware and software - Lenovo B40-80; built-in microphone, not the external Comica used in the related desktop case. - AnduinOS 2.0.5, kernel `7.0.0-43-generic`. - Codec display name: Realtek ALC233; codec vendor ID `0x10ec0235`, codec subsystem ID `0x17aa3809`. - Analogue controller: `00:1b.0`, Intel `8086:9c20`, PCI subsystem `17aa:3902`, revision 04. - HDMI controller: `00:03.0`, Intel `8086:0a0c`, PCI subsystem `17aa:3902`, revision 0b. - Both PCI controllers use `snd_hda_intel`. - Current parameters: `power_save=0`, `power_save_controller=Y`, `pm_blacklist=-1`. - The laptop's original numeric timeout was not supplied. Only `power_save` was changed. - Audacity 3.7.8. Package source, selected audio host/device, and laptop-specific PipeWire/WirePlumber package versions remain unspecified. ## Reported comparison The built-in microphone had startup distortion in Audacity before the change. With `power_save=0`, recordings were clean, including after idle. The user retained the working configuration. Laptop-specific reboot, playback and suspend/resume checks were not explicitly reported; the fuller reboot/playback acceptance applies to the separate ERYING desktop. ## Request for maintainers Please advise on a codec resume/de-pop fix or appropriately scoped power-management exception, and which additional diagnostic data or comparison would be most useful. The previously retrieved Ubuntu source at tag `Ubuntu-7.0.0-43.43` has no `17aa:3902` entry in `power_save_denylist`. A straightforward PCI subsystem entry would match **both** the analogue and HDMI controllers shown here. We would like to avoid applying an exception more broadly than necessary. The codec subsystem `17aa:3809` must not be substituted for the PCI subsystem `17aa:3902` in that table. ## Evidence and remaining diagnostic gaps - [Laptop symptoms, microphone, codec and single-setting comparison](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19646208). - [Raw PCI output and Audacity version](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19657282). - [Matching Ubuntu driver source](https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/resolute/plain/sound/hda/controllers/intel.c?h=Ubuntu-7.0.0-43.43). Not yet supplied: full alsa-info output/codec dump, DMI/BIOS identifiers, recording samples, original timeout, package revisions and selected Audacity audio route. No direct ALSA before/after test, unmodified Ubuntu comparison or power measurement is claimed. The ERYING desktop case has stronger ALSA isolation evidence and is related context rather than an assumed identical defect. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-sound -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2174689 Title: [HDA/ALC233] Lenovo B40-80 built-in microphone startup distortion disappears with power_save=0 Status in linux package in Ubuntu: New Bug description: ## Problem and evidence A Lenovo B40-80 user reports startup distortion in recordings from the built-in microphone. Changing only `snd_hda_intel.power_save` to 0 resolves it, including recordings after idle. `power_save_controller` remains Y. The user has not performed a direct ALSA comparison with the original setting on this laptop. The observed reproduction is in Audacity 3.7.8. The reporting maintainer does not own this hardware. Reproduction on an unmodified Ubuntu installation or Live image has not yet been performed. ## Hardware and software - Lenovo B40-80; built-in microphone, not the external Comica used in the related desktop case. - AnduinOS 2.0.5, kernel `7.0.0-43-generic`. - Codec display name: Realtek ALC233; codec vendor ID `0x10ec0235`, codec subsystem ID `0x17aa3809`. - Analogue controller: `00:1b.0`, Intel `8086:9c20`, PCI subsystem `17aa:3902`, revision 04. - HDMI controller: `00:03.0`, Intel `8086:0a0c`, PCI subsystem `17aa:3902`, revision 0b. - Both PCI controllers use `snd_hda_intel`. - Current parameters: `power_save=0`, `power_save_controller=Y`, `pm_blacklist=-1`. - The laptop's original numeric timeout was not supplied. Only `power_save` was changed. - Audacity 3.7.8. Package source, selected audio host/device, and laptop-specific PipeWire/WirePlumber package versions remain unspecified. ## Reported comparison The built-in microphone had startup distortion in Audacity before the change. With `power_save=0`, recordings were clean, including after idle. The user retained the working configuration. Laptop-specific reboot, playback and suspend/resume checks were not explicitly reported; the fuller reboot/playback acceptance applies to the separate ERYING desktop. ## Request for maintainers Please advise on a codec resume/de-pop fix or appropriately scoped power-management exception, and which additional diagnostic data or comparison would be most useful. The previously retrieved Ubuntu source at tag `Ubuntu-7.0.0-43.43` has no `17aa:3902` entry in `power_save_denylist`. A straightforward PCI subsystem entry would match **both** the analogue and HDMI controllers shown here. We would like to avoid applying an exception more broadly than necessary. The codec subsystem `17aa:3809` must not be substituted for the PCI subsystem `17aa:3902` in that table. ## Evidence and remaining diagnostic gaps - [Laptop symptoms, microphone, codec and single-setting comparison](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19646208). - [Raw PCI output and Audacity version](https://github.com/Anduin2017/AnduinOS/discussions/482#discussioncomment-19657282). - [Matching Ubuntu driver source](https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/resolute/plain/sound/hda/controllers/intel.c?h=Ubuntu-7.0.0-43.43). Not yet supplied: full alsa-info output/codec dump, DMI/BIOS identifiers, recording samples, original timeout, package revisions and selected Audacity audio route. No direct ALSA before/after test, unmodified Ubuntu comparison or power measurement is claimed. The ERYING desktop case has stronger ALSA isolation evidence and is related context rather than an assumed identical defect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174689/+subscriptions

[Bug 2174679] [NEW] [regression] 7.0.0-43: black screen after S3 resume, user.slice never thawed (HP OMEN, NVIDIA 580, worked on 7.0.0-42)

Public bug reported: After updating from linux 7.0.0-42.42 to 7.0.0-43.43, the laptop no longer comes back from suspend. Closing the lid suspends normally (S3 / "deep"). On opening the lid the kernel logs a clean resume, but the screen stays black and the machine has to be powered off by holding the power button. This is a regression: 7.0.0-42 resumes reliably on the same install with the same NVIDIA driver version. 7.0.0-42-generic: 32 resumes ("PM: suspend exit"), 32 x "Successfully thawed unit 'user.slice'" 7.0.0-43-generic: 5 resumes ("PM: suspend exit"), 0 x "Successfully thawed unit 'user.slice'" What the journal shows on 7.0.0-43: 1. Lid closed -> nvidia-suspend.service runs -> systemd-sleep: "Successfully froze unit 'user.slice'" -> "PM: suspend entry (deep)". 2. Lid opened -> "ACPI: PM: Waking up from system sleep state S3" -> "PM: suspend exit" -> "System returned from sleep operation 'suspend'". 3. The system-sleep post hooks start (hdparm and tlp output is logged). 4. Nothing further from systemd-sleep: no "user.slice: Unit now thawed", no "Finished systemd-suspend.service", and nvidia-resume.service is never started. 5. The journal stops completely about 6 seconds after resume, every time (5 of 5), until the forced power-off. On 7.0.0-42 the same sequence continues past step 3 within one second: user.slice is thawed, systemd-suspend.service finishes, nvidia- resume.service runs and the desktop returns. No NVRM/Xid messages, oops or panic are logged, and /sys/fs/pstore is empty. Steps to reproduce: 1. Boot 7.0.0-43-generic and log in to a Plasma Wayland session. 2. Close the lid (or suspend from the menu) and wait a few seconds. 3. Open the lid. Expected: the lock screen / desktop appears. Actual: black screen; the machine has to be force powered off. System: - Ubuntu 26.04.1 LTS, KDE Plasma (Wayland), kwin-wayland 4:6.6.6-0ubuntu0.1, sddm 0.21.0+git20250502.4fe234b-2ubuntu3 - HP OMEN by HP Laptop, BIOS F.16 (07/07/2021), Intel Core i7-8750H - Hybrid graphics: Intel UHD 630 (i915, drives the internal eDP panel) + NVIDIA GeForce GTX 1050 Ti Mobile; prime-select: nvidia - NVIDIA driver 580.178.04 (nvidia-driver-580 580.178.04-0ubuntu0.26.04.1), unchanged between the two kernels - Good: linux-image-7.0.0-42-generic 7.0.0-42.42 + linux-modules-nvidia-580-7.0.0-42-generic 7.0.0-42.42 - Bad: linux-image-7.0.0-43-generic 7.0.0-43.43 + linux-modules-nvidia-580-7.0.0-43-generic 7.0.0-43.43 - systemd 259.9-0ubuntu0.1, tlp 1.8.0-1ubuntu2 - /sys/power/mem_sleep = "s2idle [deep]" - Kernel command line: ro net.ifnames=0 biosdevname=0 quiet splash - modprobe options: nvidia_drm modeset=1, NVreg_PreserveVideoMemoryAllocations=1, NVreg_TemporaryFilePath=/var - nvidia-suspend, nvidia-resume and nvidia-hibernate services enabled Not yet tested: - Whether the machine is fully hung or only the display is dead (Caps Lock LED, SSH). - Whether SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false avoids it on 7.0.0-43. - Whether it happens with prime-select on-demand or with the nouveau driver. Attached: journal excerpts of one good resume on 7.0.0-42 and one failed resume on 7.0.0-43. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Nov 16 17:16:56 2026 InstallationDate: Installed on 2025-08-13 (461 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP OMEN by HP Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=0b7bcf0e-cc40-4f18-8bf7-a5d49dc76dff ro net.ifnames=0 biosdevname=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (186 days ago) dmi.bios.date: 07/07/2021 dmi.bios.release: 15.16 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.22 dmi.modalias: dmi:bvnAMI:bvrF.16:bd07/07/2021:br15.16:efr68.22:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.22:cvnHP:ct10:cvrChassisVersion:sku4CC49UA#ABA:pfa103C_5335KVHPOMEN: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2026-07-04T14:06:11.262878 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "resume Failed" https://bugs.launchpad.net/bugs/2174679/+attachment/6018684/+files/resume-FAILED-7.0.0-43.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2174679 Title: [regression] 7.0.0-43: black screen after S3 resume, user.slice never thawed (HP OMEN, NVIDIA 580, worked on 7.0.0-42) Status in linux package in Ubuntu: New Bug description: After updating from linux 7.0.0-42.42 to 7.0.0-43.43, the laptop no longer comes back from suspend. Closing the lid suspends normally (S3 / "deep"). On opening the lid the kernel logs a clean resume, but the screen stays black and the machine has to be powered off by holding the power button. This is a regression: 7.0.0-42 resumes reliably on the same install with the same NVIDIA driver version. 7.0.0-42-generic: 32 resumes ("PM: suspend exit"), 32 x "Successfully thawed unit 'user.slice'" 7.0.0-43-generic: 5 resumes ("PM: suspend exit"), 0 x "Successfully thawed unit 'user.slice'" What the journal shows on 7.0.0-43: 1. Lid closed -> nvidia-suspend.service runs -> systemd-sleep: "Successfully froze unit 'user.slice'" -> "PM: suspend entry (deep)". 2. Lid opened -> "ACPI: PM: Waking up from system sleep state S3" -> "PM: suspend exit" -> "System returned from sleep operation 'suspend'". 3. The system-sleep post hooks start (hdparm and tlp output is logged). 4. Nothing further from systemd-sleep: no "user.slice: Unit now thawed", no "Finished systemd-suspend.service", and nvidia-resume.service is never started. 5. The journal stops completely about 6 seconds after resume, every time (5 of 5), until the forced power-off. On 7.0.0-42 the same sequence continues past step 3 within one second: user.slice is thawed, systemd-suspend.service finishes, nvidia- resume.service runs and the desktop returns. No NVRM/Xid messages, oops or panic are logged, and /sys/fs/pstore is empty. Steps to reproduce: 1. Boot 7.0.0-43-generic and log in to a Plasma Wayland session. 2. Close the lid (or suspend from the menu) and wait a few seconds. 3. Open the lid. Expected: the lock screen / desktop appears. Actual: black screen; the machine has to be force powered off. System: - Ubuntu 26.04.1 LTS, KDE Plasma (Wayland), kwin-wayland 4:6.6.6-0ubuntu0.1, sddm 0.21.0+git20250502.4fe234b-2ubuntu3 - HP OMEN by HP Laptop, BIOS F.16 (07/07/2021), Intel Core i7-8750H - Hybrid graphics: Intel UHD 630 (i915, drives the internal eDP panel) + NVIDIA GeForce GTX 1050 Ti Mobile; prime-select: nvidia - NVIDIA driver 580.178.04 (nvidia-driver-580 580.178.04-0ubuntu0.26.04.1), unchanged between the two kernels - Good: linux-image-7.0.0-42-generic 7.0.0-42.42 + linux-modules-nvidia-580-7.0.0-42-generic 7.0.0-42.42 - Bad: linux-image-7.0.0-43-generic 7.0.0-43.43 + linux-modules-nvidia-580-7.0.0-43-generic 7.0.0-43.43 - systemd 259.9-0ubuntu0.1, tlp 1.8.0-1ubuntu2 - /sys/power/mem_sleep = "s2idle [deep]" - Kernel command line: ro net.ifnames=0 biosdevname=0 quiet splash - modprobe options: nvidia_drm modeset=1, NVreg_PreserveVideoMemoryAllocations=1, NVreg_TemporaryFilePath=/var - nvidia-suspend, nvidia-resume and nvidia-hibernate services enabled Not yet tested: - Whether the machine is fully hung or only the display is dead (Caps Lock LED, SSH). - Whether SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false avoids it on 7.0.0-43. - Whether it happens with prime-select on-demand or with the nouveau driver. Attached: journal excerpts of one good resume on 7.0.0-42 and one failed resume on 7.0.0-43. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Nov 16 17:16:56 2026 InstallationDate: Installed on 2025-08-13 (461 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP OMEN by HP Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=0b7bcf0e-cc40-4f18-8bf7-a5d49dc76dff ro net.ifnames=0 biosdevname=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (186 days ago) dmi.bios.date: 07/07/2021 dmi.bios.release: 15.16 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.22 dmi.modalias: dmi:bvnAMI:bvrF.16:bd07/07/2021:br15.16:efr68.22:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.22:cvnHP:ct10:cvrChassisVersion:sku4CC49UA#ABA:pfa103C_5335KVHPOMEN: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2026-07-04T14:06:11.262878 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174679/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-6.8/6.8.0-1070.76~22.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-aws-6.8 (6.8.0-1070.76~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-450-server/unknown (amd64) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.6 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2174560] Re: ACPI BIOS errors from \WBRF during s2idle on AMD systems

** 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/2174560 Title: ACPI BIOS errors from \WBRF during s2idle on AMD systems Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-7.3 package in Ubuntu: New Status in linux source package in Resolute: New Status in linux-oem-7.3 source package in Resolute: In Progress Status in linux source package in Stonking: New Status in linux-oem-7.3 source package in Stonking: Invalid Bug description: [Impact] On some AMD systems, the amd_s2idle test reports "ACPI BIOS errors found" and "Page faults found" on every suspend cycle (CID: not listed in the ticket). The WBRF driver sends the _DSM record argument as a package of integers. The spec says it must be a single buffer holding the header and the frequency ranges. Some firmware aborts the \WBRF method when it reads Arg2[0]: AE_AML_OPERAND_TYPE The error name comes from the upstream commit message. Hits 100% on affected systems (Wistron-built AMD platforms). [Fix] Pack the WBRF record into a little-endian buffer (number of ranges, action, then start/end pairs). Pass that buffer as the only element of the _DSM package. Upstream patch, not merged yet: https://lore.kernel.org/platform-driver-x86/20261102-superm1-wbrf-v1-1-b58d8d85277c@kernel.org/ platform/x86/amd: send WBRF DSM payload as buffer Author: Mario Limonciello (AMD) It fixes the original WBRF support, commit 58e82a62669d ("platform/x86/amd: Add support for AMD ACPI based Wifi band RFI mitigation feature"), which is in v6.10. [Test Plan] Run the s2idle check 3 times: $ sudo fwts s3 --s3-multiple=3 Without patch: "ACPI BIOS errors found" and "Page faults found" after each cycle. dmesg shows AE_AML_OPERAND_TYPE from \WBRF. With patch: no ACPI BIOS errors and no AE_AML_OPERAND_TYPE in dmesg. Tested on an OEM 7.3 kernel with this patch. The reporter confirmed there are no more ACPI errors. [Where problems could occur] Could break the AMD WBRF driver (drivers/platform/x86/amd/wbrf.c). That driver sends Wifi band records and retrieves them for the AMD GPU and Wifi drivers. If the buffer layout is wrong, firmware could read bad ranges or reject the call. Then Wifi band avoidance would stop working. The system could show Wifi interference with memory clocks, or the ACPI error could stay. Firmware that already accepted the old integer package could now fail with the buffer. The patch changes the argument for every system with WBRF,not just the broken ones. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2174560/+subscriptions

[Bug 2174613] Re: linux-amd-embedded: Add GMSL multi-camera support for the AMD ISP4

** 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/2174613 Title: linux-amd-embedded: Add GMSL multi-camera support for the AMD ISP4 Status in linux package in Ubuntu: New Status in linux source package in Resolute: Confirmed Bug description: This bug targets the linux-amd-embedded kernel (Ubuntu 26.04 Resolute, 7.0, amd64). linux-amd-embedded is not yet available in the archive, so the bug is filed against the linux package for now. [Impact] GMSL cameras (TEVS AR0821 modules with MAX96717 serializers, connected through a MAX96724 deserializer to the AMD ISP4) cannot be used with linux-amd-embedded: * There is no driver for the TEVS AR0821 camera module, and nothing creates the camera chain on x86, where it is not described in the firmware. * The MAX96717 and MAX96724 drivers can only be matched from DT. MAX96717 does not enable its RCLKOUT reference clock without a clock consumer, so the sensor does not boot. * With more than one camera on one CSI-2 port, the cameras are not separated by virtual channel and stream id, so only one camera gets valid frames. * Starting or stopping one camera reprograms or stops the deserializer and the ISP4 GMSL chain for all cameras, and opening one video node starts all cameras. [Fix] * UBUNTU: SAUCE patches from the AMD patch set: - media/amd/isp4: refcount shared GMSL chain across VCs - media: i2c: maxim-serdes: add MAX96717/MAX96724 and multi-VC stream fixes (ported to the upstream maxim-serdes framework in linux-amd-embedded) - media: i2c: add TEVS AR0821 and max_gmsl_cam glue - media/amd/isp4: start GMSL remotes per VC with enable_streams * UBUNTU: SAUCE patch from the ADI GMSL tree, part of the maxim-serdes framework used by the AMD patch set: - HACK: media: i2c: maxim-serdes: max_ser: ignore failed reset write * Enable VIDEO_TEVS and VIDEO_MAX_GMSL_CAM as modules on amd64. [Test Plan] * Build the linux-amd-embedded kernel for all flavours and check that updateconfigs passes. * Boot the kernel in an LXD VM and load the tevs, max96717, max96724 (with manual_instantiate=0) and amd_isp4_csi_capture modules. * On hardware with four GMSL cameras: load max_gmsl_cam, stream from all four video nodes at the same time, and check that starting and stopping one camera does not affect the others. [Where problems could occur] The changes affect the maxim-serdes framework and the MAX96717/MAX96724 drivers, and the stream start and stop of the remote subdevices in the AMD ISP4 driver. A regression could cause capture failures, corrupted or missing frames, or cameras that do not come up. The deserializer and serializer accept all media links without a format check, and selecting the GMSL links can take up to 1 s and does not fail when the links do not lock, so a cabling or power problem is reported only in the kernel log. The new modules are not loaded automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174613/+subscriptions

[Bug 2174656] Re: vxlan: regression from CVE-2026-98023 fix breaks EVPN multihoming (FRR remote-ES MACs rejected)

** 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/2174656 Title: vxlan: regression from CVE-2026-98023 fix breaks EVPN multihoming (FRR remote-ES MACs rejected) Status in linux package in Ubuntu: New Bug description: [Impact] The CVE-2026-98023 fix, 98fc57d16744 ("vxlan: reject dynamic fdb entries that reference a nexthop id"), rejects dynamic vxlan fdb entries that use an nhid. FRR installs remote MACs behind an EVPN multihomed Ethernet Segment exactly that way (dynamic + extern_learn + nhid), so every install fails: zebra: Extended Error: A nexthop fdb cannot be dynamic zebra: netlink-dp (NS 0) error: Invalid argument, type=RTM_NEWNEIGH(28) Traffic to those MACs is then flooded to every remote VTEP. Hosts on a multihomed segment get duplicate frames. Affected noble kernels: - HWE 7.0: 7.0.0-41 and later (7.0.0-44 in hwe-7.0-next still has it) - GA 6.8: 6.8.0-148 and later (6.8.0-151 in master-next still has it) [Fix] Upstream reverted the check in a race-free way: 7308ef8b4a6779a39f68d053c19b53a5c584a663 ("vxlan: Stop rejecting dynamic FDB entries with a nexthop ID", Cc: stable) It's queued for 5.10, 5.15, 6.1, 6.6, 6.12, 6.18 and 7.3 stable. Upstream 7.0.y and 6.8.y are EOL, so noble needs a direct cherry-pick. The queue-6.12 backport applies as a reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.12/vxlan-stop-rejecting-dynamic-fdb-entries-with-a-next.patch [Test Plan] ip link add vx0 type vxlan id 100 dstport 4789 local 192.0.2.10 external ip link set vx0 up ip nexthop add id 1 via 192.0.2.1 fdb ip nexthop add id 2 via 192.0.2.2 fdb ip nexthop add id 10 group 1/2 fdb bridge fdb add 00:00:5e:00:53:01 dev vx0 nhid 10 self dynamic extern_learn - Affected kernel: "Error: A nexthop fdb cannot be dynamic." - Fixed kernel: accepted, and shown by `bridge fdb show dev vx0`. Also: FRR EVPN-MH with a remote ES. zebra logs no RTM_NEWNEIGH errors and remote-ES MACs are in `bridge fdb show`. [Where problems could occur] vxlan fdb ageing (vxlan_cleanup) for entries that point to nexthop groups. That was the race the original fix targeted, and the upstream commit closes it a different way. Only vxlan fdb entries with an nhid are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174656/+subscriptions

[Bug 2174670] Re: [amdgpu][R9700] Regression in 7.0.0-42: BOCO runtime PM causes global OOM during Vulkan compute loads

** 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/2174670 Title: [amdgpu][R9700] Regression in 7.0.0-42: BOCO runtime PM causes global OOM during Vulkan compute loads Status in linux package in Ubuntu: New Bug description: ## Summary This is an Ubuntu kernel regression affecting a headless Radeon AI PRO R9700 in a hybrid-GPU system. The workload was stable with `7.0.0-38-generic`. Starting with `7.0.0-42-generic`, the R9700 reports `Using BOCO for runtime pm`, and large RADV/Vulkan compute/model-loading workloads can create very large `gpu_active` memory pressure followed by a global OOM cascade. The problem remains present in `7.0.0-43-generic`. Keeping only the R9700 awake with `power/control=on` completely prevents the failure and allows the identical workload to load and run successfully. Upstream AMDGPU report: https://gitlab.freedesktop.org/drm/amd/-/work_items/6147 ## Hardware and software - Ubuntu 26.04, amd64 - CPU/iGPU: AMD Ryzen 7 PRO 6850H / Radeon 680M - Discrete GPU: Radeon AI PRO R9700, PCI ID `1002:7551`, revision c0, 32 GiB VRAM - R9700 used as a headless compute GPU over PCIe/OCuLink - System RAM: 24 GB; swap: 12 GB - Vulkan: Mesa/RADV 26.0.8 - Firmware package: `20260319.git217ca6e4.1ubuntu` - Last observed good kernel: `7.0.0-38-generic` (`7.0.0-38.38`) - First observed bad kernel: `7.0.0-42-generic` (`7.0.0-42.42`) - Current affected kernel: `7.0.0-43-generic` (`7.0.0-43.43`) ## Regression evidence - Six recorded boots with `7.0.0-38-generic`: no global OOM event from this workload. - First boot with `7.0.0-42-generic`: the R9700 reports `Using BOCO for runtime pm`; the first GPU-associated global OOM cascade occurred during that boot. - `7.0.0-43-generic`: BOCO runtime PM remains enabled and the failure remains reproducible. - Mesa/RADV and AMD firmware did not change across the start of the regression. ## Sanitized log excerpts ```text amdgpu 0000:03:00.0: Using BOCO for runtime pm Node 0 ... all_unreclaimable? yes ... gpu_active:11002768kB gpu_reclaim:0kB Out of memory: Killed process ... Node 0 ... all_unreclaimable? yes ... gpu_active:18338004kB gpu_reclaim:0kB Out of memory: Killed process ... systemd-oomd: Killed ... org.gnome.Shell ... due to memory pressure ``` Repeated around affected loads: ```text amdgpu 0000:03:00.0: SMU is resuming... amdgpu 0000:03:00.0: SMU is resumed successfully! ``` ## Reproduction 1. Leave the R9700 runtime-PM policy at its default: ```text /sys/bus/pci/devices/0000:03:00.0/power/control = auto ``` 2. Use RADV/Vulkan to load an approximately 20 GiB workload with full GPU offload and a large GPU-resident context. 3. Observe repeated R9700 runtime resume events and rapidly increasing `gpu_active` in kernel OOM diagnostics. 4. Global memory pressure kills unrelated user processes and can terminate the desktop session. ## Workaround and controlled A/B verification Applying: ```text echo on > /sys/bus/pci/devices/0000:03:00.0/power/control ``` prevents runtime suspend only for the R9700. The identical workload was then tested successfully: - model load and real inference completed successfully - peak R9700 VRAM use: 27.16 GiB - minimum available system RAM: 14.34 GiB - minimum free swap: 7.95 GiB - `runtime_status` remained `active` - no OOM event - no GPU reset, timeout, or SMU resume event during the test This demonstrates that normal RAM/VRAM capacity is sufficient and isolates the failure to the runtime-PM/BOCO path. ## Expected result The R9700 should enter and leave runtime suspend without creating enough unreclaimable memory pressure to trigger global OOM, or runtime PM should be disabled for this device/topology if BOCO is unsafe. ## Actual result Starting with Ubuntu kernel `7.0.0-42`, runtime PM on the headless R9700 can cause large `gpu_active` memory pressure and global OOM kills under Vulkan compute load. Keeping the GPU active prevents the issue entirely. Please correlate the Ubuntu changes between `7.0.0-38.38` and `7.0.0-42.42` with the upstream AMDGPU report and advise whether a test kernel or additional narrowly scoped diagnostics would help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174670/+subscriptions