** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) 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/2158501 Title: linux: enable CONFIG_EROFS_FS_PAGE_CACHE_SHARE Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: [Impact] Currently EROFS already ships CONFIG_EROFS_FS_PAGE_CACHE_SHARE in linux 7.0 as an optional feature. since it's already shipped and users can choose to use it at runtime or not, I hope this feature could be enabled in both Ubuntu 26.10(Stonking Stingray), 26.04(Resolute Raccoon) and future Ubuntu versions. Also, since CONFIG_EROFS_FS_ONDEMAND has been removed in Linux 7.2 cycle (https://git.kernel.org/torvalds/c/c37460cd9b2fc). Since CONFIG_EROFS_FS_ONDEMAND conflicts with CONFIG_EROFS_FS_PAGE_CACHE_SHARE due to CONFIG_EROFS_FS_ONDEMAND deprecation at Linux 7.0. I hope CONFIG_EROFS_FS_ONDEMAND can be disabled in Ubuntu 26.10(Stonking Stingray). [Fix] In short, I hope CONFIG_EROFS_FS_PAGE_CACHE_SHARE=y and CONFIG_EROFS_FS_ONDEMAND is not set [Test plan] Build tested. [Where problems could occur] Very small risk of regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158501/+subscriptions
понедельник
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
** Attachment added: "Ubuntu_24_04_4_dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+attachment/5980567/+files/Ubuntu_24_04_4_dmesg.txt.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
Hi Jeff, Here I update the latest test result, using Ubuntu 24.04.4 updated with the nvidia-64k kernel (6.17.0-1021-nvidia-64k): The issue remains reproducible. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2159937] [NEW] ASUS X411UA hard-freezes after GDM blanks display on i915
Public bug reported: Hardware: - ASUS VivoBook S X411UA - Intel Core i7-8550U - Intel UHD Graphics 620, PCI ID 8086:5917, i915 - BIOS X411UA.310 - Internal 1920×1080 display Software: - Ubuntu 26.04 - Kernel 7.0.0-27-generic - GNOME/GDM using Wayland Steps to reproduce: 1. Boot to the GDM login screen. 2. Leave the machine idle until the display blanks. 3. The machine subsequently becomes completely unresponsive and requires a hard power-off. Moving the cursor delays both display blanking and the freeze. The issue reproduced repeatedly. The journal ends abruptly without a clean shutdown, OOM, storage, or thermal error. Before one freeze, the kernel repeatedly reported: workqueue: output_poll_execute hogged CPU workqueue: i915_hpd_poll_init_work [i915] hogged CPU Testing: - i915.enable_psr=0 alone did not fix the problem. - i915.enable_psr=0 i915.enable_dc=0 has remained stable during stress testing and display blanking so far. Expected result: The display blanks and wakes normally without affecting the system. Actual result: Display blanking leads to a complete system freeze. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Tue Jul 7 16:16:10 2026 InstallationDate: Installed on 2026-07-07 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 13d3:5a07 IMC Networks VGA UVC WebCam Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. X411UA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no username) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=be61cce7-c4dc-42f6-99ea-8d7847981abe ro i915.enable_psr=0 i915.enable_psr=0 i915.enable_dc=0 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UA.310:bd04/16/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX411UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBookS: dmi.product.family: VivoBook S dmi.product.name: X411UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159937 Title: ASUS X411UA hard-freezes after GDM blanks display on i915 Status in linux package in Ubuntu: New Bug description: Hardware: - ASUS VivoBook S X411UA - Intel Core i7-8550U - Intel UHD Graphics 620, PCI ID 8086:5917, i915 - BIOS X411UA.310 - Internal 1920×1080 display Software: - Ubuntu 26.04 - Kernel 7.0.0-27-generic - GNOME/GDM using Wayland Steps to reproduce: 1. Boot to the GDM login screen. 2. Leave the machine idle until the display blanks. 3. The machine subsequently becomes completely unresponsive and requires a hard power-off. Moving the cursor delays both display blanking and the freeze. The issue reproduced repeatedly. The journal ends abruptly without a clean shutdown, OOM, storage, or thermal error. Before one freeze, the kernel repeatedly reported: workqueue: output_poll_execute hogged CPU workqueue: i915_hpd_poll_init_work [i915] hogged CPU Testing: - i915.enable_psr=0 alone did not fix the problem. - i915.enable_psr=0 i915.enable_dc=0 has remained stable during stress testing and display blanking so far. Expected result: The display blanks and wakes normally without affecting the system. Actual result: Display blanking leads to a complete system freeze. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Tue Jul 7 16:16:10 2026 InstallationDate: Installed on 2026-07-07 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 13d3:5a07 IMC Networks VGA UVC WebCam Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. X411UA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no username) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=be61cce7-c4dc-42f6-99ea-8d7847981abe ro i915.enable_psr=0 i915.enable_psr=0 i915.enable_dc=0 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UA.310:bd04/16/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX411UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBookS: dmi.product.family: VivoBook S dmi.product.name: X411UA 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/2159937/+subscriptions
[Bug 2153159] Re: [Ubuntu 26.04] KVM: IBM Test Accelerator for Z (TAZ) not working properly
** Tags removed: verification-needed-resolute-linux ** Tags added: verification-done-resolute-linux ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153159 Title: [Ubuntu 26.04] KVM: IBM Test Accelerator for Z (TAZ) not working properly Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Bug description: [ Impact ] Enable IBM Test Accelerator for Z. [ Fix ] Backport the following patches from upstream: - 2623c96f1172 KVM: s390: only deliver service interrupt with payload - b0ad874d9852 KVM: s390: vsie: Allow non-zarch guests - a9640e2eb711 KVM: s390: vsie: Disable some bits when in ESA mode - c0dcada088ff KVM: s390: vsie: Accommodate ESA prefix pages - 4aebd7d5c72f KVM: s390: Add KVM capability for ESA mode guests [ Test Plan ] Launch a TAZ instance and confirm it can start and run ESA mode nested guests without generating program exceptions in either the TAZ instance or its guests. [ Regression Potential] While the ESA mode enablement is fully opt-in and poses no risk to existing workloads, the prefix bitfield adjustment and the suppression of zero-payload SCLP interrupts are global changes affecting all KVM/s390 guests. Either could impact existing z/Architecture guests. --- On Ubuntu 26.04, the IBM Test Accelerator for Z (TAZ) is not working, i.e. it results in program exceptions within the TAZ instance and/or the guests within it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2153159/+subscriptions
[Bug 2158860] Re: Fix Mic Mute LED no function on HP EliteBook
Verified on GNZA14-PV-SKU2A with linux-oem-6.17/6.17.0-1029.29 kernel, press Fn+F9/F9 to toggle the microphone mute function, when the led is on, the microphone is verified muted. When the LED is off, the microphone is verified unmuted. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158860 Title: Fix Mic Mute LED no function on HP EliteBook Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Audio mic-mute LED does not work on some HP EliteBook laptops. [Fix] Add ALC236_FIXUP_HP_GPIO_LED fixup for affected HP laptops. Upstream commit in v7.2-rc1: 6efb1897209a ("ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2i Laptops") [Test Plan] Press the audio mute key to toggle the mute state. Without patch: Audio mute LED does not light up when muted. With patch: Audio mute LED lights up when muted. [Where problems could occur] Only some particular SSID would be applied for this quirk which is considered low risk of regression To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158860/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-6.8/6.8.0-136.136.2~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-6.8 (6.8.0-136.136.2~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-525-server/unknown (arm64) 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-lowlatency- hwe-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 2158690] Re: [SRU] Export IP discovery even if amdgpu probe fails
** Description changed: [ Impact ] The amdgpu probing sequence can fail for any multitude of reasons (missing firmware, missing NPI support, unexpected hardware response). Ideally; we would have all NPI support in Ubuntu at product launch, but due to kernel schedule this isn't always feasible; particularly for dGPUs. For missing NPI support on dGPU specifically we want to be able to identify the system though so that we can potentially offer DKMS package from amdgpu-install script. To support this need there are changes introduced that will export IP discovery information to userspace even during probe failure. [ Fix ] The major patchsets are: 1. drm/amdgpu: Export ip_discovery sysfs on probe failure[1]: in linux-next 402e04f11ff7 2. drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown[2]: in linux-next 7de02fe95312 3. drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini[3]: in linux-next 26373c719455 And their dependent patches. See additional information. [ Test plan ] On APU/dGPU already supported by Ubuntu out-of-the-box: 1) Remove a GPU firmware from /lib/firmware. 2) Reboot system 3) Verify amdgpu shows probe error 4) Verify that IP discovery info in sysfs 5) Unload amdgpu 6) Restore GPU firmware 7) reload amdgpu 8) Verify works On new APU/dGPU 1) Verify amdgpu shows probe error 2) Verify that IP discovery info in sysfs [ Where problems could occur] - This changes amdgpu module load/unload behaviors, and internal - implementation of some of its sysfs files. Bugs in those implementation - may impact tools actively reading those sysfs files (likely, various - AMD's own tools), or load/unload amdgpu module. + This changes + + Bug in this likely leads to 1) handling of probe failure and 2) module + unload/reload behavior and 3) internal implementation of sysfs files + under ip_discovery. + + For 1), if a probe fails then the gpu drivers is already in the bad + state. This at least leave more postmoterm information that we can + revisit. + + For 2), use cases that need active unload/load the module when system is + up and running may be impacted, which is likely rare. + + For 3), tools relying on those sysfs files may be impacted. [ Additional information ] [1] https://lore.kernel.org/amd-gfx/20260406212442.2321667-1-mario.limonciello@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260616091444.25605-1-geoffrey.mcrae@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260622161914.1648195-1-mario.limonciello@amd.com/ The full patch list to support this on 7.0-based kernel: ``` drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown drm/amdgpu: Export ip_discovery sysfs on probe failure drm/amdgpu: Fix discovery offset check under VF drm/amdgpu: fix IP discovery v0 handling drm/amdgpu: Add size guard before copy discovery binary - drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback + drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback drm/amdgpu: Avoid NULL dereference in discovery topology coredump path v3 drm/amdgpu: fallback to default discovery offset/size in sriov guest drm/amdgpu: New interface to get IP discovery binary v3 drm/amdgpu/discovery: use common function to check discovery table drm/amdgpu/discovery: support new discovery binary header drm/amdgpu: include ip discovery data in devcoredump ``` ** Description changed: + BugLink: https://bugs.launchpad.net/bugs/2158690 + [ Impact ] The amdgpu probing sequence can fail for any multitude of reasons (missing firmware, missing NPI support, unexpected hardware response). Ideally; we would have all NPI support in Ubuntu at product launch, but due to kernel schedule this isn't always feasible; particularly for dGPUs. For missing NPI support on dGPU specifically we want to be able to identify the system though so that we can potentially offer DKMS package from amdgpu-install script. To support this need there are changes introduced that will export IP discovery information to userspace even during probe failure. [ Fix ] The major patchsets are: 1. drm/amdgpu: Export ip_discovery sysfs on probe failure[1]: in linux-next 402e04f11ff7 2. drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown[2]: in linux-next 7de02fe95312 3. drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini[3]: in linux-next 26373c719455 And their dependent patches. See additional information. [ Test plan ] On APU/dGPU already supported by Ubuntu out-of-the-box: 1) Remove a GPU firmware from /lib/firmware. 2) Reboot system 3) Verify amdgpu shows probe error 4) Verify that IP discovery info in sysfs 5) Unload amdgpu 6) Restore GPU firmware 7) reload amdgpu 8) Verify works On new APU/dGPU 1) Verify amdgpu shows probe error 2) Verify that IP discovery info in sysfs [ Where problems could occur] This changes Bug in this likely leads to 1) handling of probe failure and 2) module unload/reload behavior and 3) internal implementation of sysfs files under ip_discovery. For 1), if a probe fails then the gpu drivers is already in the bad state. This at least leave more postmoterm information that we can revisit. For 2), use cases that need active unload/load the module when system is up and running may be impacted, which is likely rare. For 3), tools relying on those sysfs files may be impacted. [ Additional information ] [1] https://lore.kernel.org/amd-gfx/20260406212442.2321667-1-mario.limonciello@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260616091444.25605-1-geoffrey.mcrae@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260622161914.1648195-1-mario.limonciello@amd.com/ The full patch list to support this on 7.0-based kernel: ``` drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown drm/amdgpu: Export ip_discovery sysfs on probe failure drm/amdgpu: Fix discovery offset check under VF drm/amdgpu: fix IP discovery v0 handling drm/amdgpu: Add size guard before copy discovery binary drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback drm/amdgpu: Avoid NULL dereference in discovery topology coredump path v3 drm/amdgpu: fallback to default discovery offset/size in sriov guest drm/amdgpu: New interface to get IP discovery binary v3 drm/amdgpu/discovery: use common function to check discovery table drm/amdgpu/discovery: support new discovery binary header drm/amdgpu: include ip discovery data in devcoredump ``` -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158690 Title: [SRU] Export IP discovery even if amdgpu probe fails Status in linux package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2158690 [ Impact ] The amdgpu probing sequence can fail for any multitude of reasons (missing firmware, missing NPI support, unexpected hardware response). Ideally; we would have all NPI support in Ubuntu at product launch, but due to kernel schedule this isn't always feasible; particularly for dGPUs. For missing NPI support on dGPU specifically we want to be able to identify the system though so that we can potentially offer DKMS package from amdgpu-install script. To support this need there are changes introduced that will export IP discovery information to userspace even during probe failure. [ Fix ] The major patchsets are: 1. drm/amdgpu: Export ip_discovery sysfs on probe failure[1]: in linux-next 402e04f11ff7 2. drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown[2]: in linux-next 7de02fe95312 3. drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini[3]: in linux-next 26373c719455 And their dependent patches. See additional information. [ Test plan ] On APU/dGPU already supported by Ubuntu out-of-the-box: 1) Remove a GPU firmware from /lib/firmware. 2) Reboot system 3) Verify amdgpu shows probe error 4) Verify that IP discovery info in sysfs 5) Unload amdgpu 6) Restore GPU firmware 7) reload amdgpu 8) Verify works On new APU/dGPU 1) Verify amdgpu shows probe error 2) Verify that IP discovery info in sysfs [ Where problems could occur] This changes Bug in this likely leads to 1) handling of probe failure and 2) module unload/reload behavior and 3) internal implementation of sysfs files under ip_discovery. For 1), if a probe fails then the gpu drivers is already in the bad state. This at least leave more postmoterm information that we can revisit. For 2), use cases that need active unload/load the module when system is up and running may be impacted, which is likely rare. For 3), tools relying on those sysfs files may be impacted. [ Additional information ] [1] https://lore.kernel.org/amd-gfx/20260406212442.2321667-1-mario.limonciello@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260616091444.25605-1-geoffrey.mcrae@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260622161914.1648195-1-mario.limonciello@amd.com/ The full patch list to support this on 7.0-based kernel: ``` drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown drm/amdgpu: Export ip_discovery sysfs on probe failure drm/amdgpu: Fix discovery offset check under VF drm/amdgpu: fix IP discovery v0 handling drm/amdgpu: Add size guard before copy discovery binary drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback drm/amdgpu: Avoid NULL dereference in discovery topology coredump path v3 drm/amdgpu: fallback to default discovery offset/size in sriov guest drm/amdgpu: New interface to get IP discovery binary v3 drm/amdgpu/discovery: use common function to check discovery table drm/amdgpu/discovery: support new discovery binary header drm/amdgpu: include ip discovery data in devcoredump ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158690/+subscriptions
[Bug 2158690] Re: [SRU] Export IP discovery even if amdgpu probe fails
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Leo Lin (0xff07) ** Changed in: linux-oem-7.0 (Ubuntu) Assignee: (unassigned) => Leo Lin (0xff07) ** Description changed: [ Impact ] The amdgpu probing sequence can fail for any multitude of reasons (missing firmware, missing NPI support, unexpected hardware response). Ideally; we would have all NPI support in Ubuntu at product launch, but due to kernel schedule this isn't always feasible; particularly for dGPUs. For missing NPI support on dGPU specifically we want to be able to identify the system though so that we can potentially offer DKMS package from amdgpu-install script. To support this need there are changes introduced that will export IP discovery information to userspace even during probe failure. [ Fix ] The major patchsets are: 1. drm/amdgpu: Export ip_discovery sysfs on probe failure[1]: in linux-next 402e04f11ff7 2. drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown[2]: in linux-next 7de02fe95312 3. drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini[3]: in linux-next 26373c719455 And their dependent patches. See additional information. [ Test plan ] On APU/dGPU already supported by Ubuntu out-of-the-box: 1) Remove a GPU firmware from /lib/firmware. 2) Reboot system 3) Verify amdgpu shows probe error 4) Verify that IP discovery info in sysfs 5) Unload amdgpu 6) Restore GPU firmware 7) reload amdgpu 8) Verify works On new APU/dGPU 1) Verify amdgpu shows probe error 2) Verify that IP discovery info in sysfs [ Where problems could occur] This changes amdgpu module load/unload behaviors, and internal implementation of some of its sysfs files. Bugs in those implementation may impact tools actively reading those sysfs files (likely, various AMD's own tools), or load/unload amdgpu module. [ Additional information ] [1] https://lore.kernel.org/amd-gfx/20260406212442.2321667-1-mario.limonciello@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260616091444.25605-1-geoffrey.mcrae@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260622161914.1648195-1-mario.limonciello@amd.com/ The full patch list to support this on 7.0-based kernel: ``` drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown drm/amdgpu: Export ip_discovery sysfs on probe failure drm/amdgpu: Fix discovery offset check under VF drm/amdgpu: fix IP discovery v0 handling + drm/amdgpu: Add size guard before copy discovery binary + drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback drm/amdgpu: Avoid NULL dereference in discovery topology coredump path v3 drm/amdgpu: fallback to default discovery offset/size in sriov guest drm/amdgpu: New interface to get IP discovery binary v3 drm/amdgpu/discovery: use common function to check discovery table drm/amdgpu/discovery: support new discovery binary header drm/amdgpu: include ip discovery data in devcoredump ``` -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158690 Title: [SRU] Export IP discovery even if amdgpu probe fails Status in linux package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Bug description: [ Impact ] The amdgpu probing sequence can fail for any multitude of reasons (missing firmware, missing NPI support, unexpected hardware response). Ideally; we would have all NPI support in Ubuntu at product launch, but due to kernel schedule this isn't always feasible; particularly for dGPUs. For missing NPI support on dGPU specifically we want to be able to identify the system though so that we can potentially offer DKMS package from amdgpu-install script. To support this need there are changes introduced that will export IP discovery information to userspace even during probe failure. [ Fix ] The major patchsets are: 1. drm/amdgpu: Export ip_discovery sysfs on probe failure[1]: in linux-next 402e04f11ff7 2. drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown[2]: in linux-next 7de02fe95312 3. drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini[3]: in linux-next 26373c719455 And their dependent patches. See additional information. [ Test plan ] On APU/dGPU already supported by Ubuntu out-of-the-box: 1) Remove a GPU firmware from /lib/firmware. 2) Reboot system 3) Verify amdgpu shows probe error 4) Verify that IP discovery info in sysfs 5) Unload amdgpu 6) Restore GPU firmware 7) reload amdgpu 8) Verify works On new APU/dGPU 1) Verify amdgpu shows probe error 2) Verify that IP discovery info in sysfs [ Where problems could occur] This changes amdgpu module load/unload behaviors, and internal implementation of some of its sysfs files. Bugs in those implementation may impact tools actively reading those sysfs files (likely, various AMD's own tools), or load/unload amdgpu module. [ Additional information ] [1] https://lore.kernel.org/amd-gfx/20260406212442.2321667-1-mario.limonciello@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260616091444.25605-1-geoffrey.mcrae@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260622161914.1648195-1-mario.limonciello@amd.com/ The full patch list to support this on 7.0-based kernel: ``` drm/amdgpu: don't free standalone ip_discovery sysfs in sysfs_fini drm/amdgpu: clean up discovery and preempt sysfs entries on shutdown drm/amdgpu: Export ip_discovery sysfs on probe failure drm/amdgpu: Fix discovery offset check under VF drm/amdgpu: fix IP discovery v0 handling drm/amdgpu: Add size guard before copy discovery binary drm/amdgpu: use DISCOVERY_TMR_SIZE in ACPI TMR fallback drm/amdgpu: Avoid NULL dereference in discovery topology coredump path v3 drm/amdgpu: fallback to default discovery offset/size in sriov guest drm/amdgpu: New interface to get IP discovery binary v3 drm/amdgpu/discovery: use common function to check discovery table drm/amdgpu/discovery: support new discovery binary header drm/amdgpu: include ip discovery data in devcoredump ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158690/+subscriptions
[Bug 2159608] Re: noble/linux-raspi FTBFS noble-stable-2026-06-16: bcmasp phylib managed-EEE backport missing prerequisites
** Description changed: [ Impact ] - The noble/linux-raspi kernel fails to build from source (FTBFS). - Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport - whose defect is latent in the generic/master kernel — master does not - compile the Broadcom ASP2 driver — but becomes a fatal compile error in - linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi - (not in master)”). + The noble/linux-raspi kernel fails to build from source (FTBFS noble- + stable-2026-06-16). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a + broken stable backport whose defect is latent in the generic/master + kernel — master does not compile the Broadcom ASP2 driver — but becomes + a fatal compile error in linux-raspi, which enables it on arm64 + (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. - [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. - # Revert commit Reverts in-tree Subject - 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 - 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register - 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk - 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 - 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq - 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe - 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 - 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE - 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled + # Revert commit Reverts in-tree Subject + 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 + 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register + 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk + 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 + 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq + 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe + 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 + 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE + 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159608 Title: noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites Status in linux package in Ubuntu: New Bug description: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS noble- stable-2026-06-16). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159608/+subscriptions
[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.
** Attachment added: "video recording" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+attachment/5980353/+files/XCC-7D75-SR650V3A35%20-%20Lenovo%20XClarity%20Controller%202%20-%20Google%20Chrome%202026-06-26%2009-45-33.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions
[Bug 2159608] [NEW] noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites
Public bug reported: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. ** 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/2159608 Title: noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites Status in linux package in Ubuntu: New Bug description: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure (Russell King’s phylib managed-EEE series, ~v6.12) was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159608/+subscriptions
[Bug 2159589] [NEW] Bluetooth turns back on automatically after being turned off in GNOME
Public bug reported: On Ubuntu 26.04 LTS, Bluetooth cannot remain turned off. When I turn Bluetooth off using either GNOME Quick Settings or Settings, it turns off briefly but then automatically turns itself back on. The Bluetooth controller confirms this behavior: immediately after turning it off, bluetoothctl show reports: Powered: no PowerState: off After a short time, without any user action, it changes back to: Powered: yes PowerState: on The Bluetooth adapter is a MediaTek device, USB ID 0e8d:e025, on a Lenovo ThinkPad P16s Gen 4 AMD. The kernel log also showed errors during the Bluetooth power-off sequence, including: Bluetooth: hci0: command 0x2039 tx timeout Bluetooth: hci0: failed to reset (-19) Bluetooth: hci0: Error when powering off device on rfkill (-110) Expected behavior: When Bluetooth is turned off in GNOME Quick Settings or Settings, it should remain off until the user turns it on again. Actual behavior: Bluetooth turns itself back on automatically after being turned off. This occurs consistently after a fresh installation of Ubuntu 26.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:09:07 2026 InstallationDate: Installed on 2026-07-05 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21RX001LGE 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=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2025 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R2XET35W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21RX001LGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrR2XET35W(1.15):bd08/29/2025:br1.15:efr1.8:svnLENOVO:pn21RX001LGE:pvrThinkPadP16sGen4AMD:rvnLENOVO:rn21RX001LGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21RX_BU_Think_FM_ThinkPadP16sGen4AMD:pfaThinkPadP16sGen4AMD: dmi.product.family: ThinkPad P16s Gen 4 AMD dmi.product.name: 21RX001LGE dmi.product.sku: LENOVO_MT_21RX_BU_Think_FM_ThinkPad P16s Gen 4 AMD dmi.product.version: ThinkPad P16s Gen 4 AMD dmi.sys.vendor: LENOVO ** 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/2159589 Title: Bluetooth turns back on automatically after being turned off in GNOME Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 LTS, Bluetooth cannot remain turned off. When I turn Bluetooth off using either GNOME Quick Settings or Settings, it turns off briefly but then automatically turns itself back on. The Bluetooth controller confirms this behavior: immediately after turning it off, bluetoothctl show reports: Powered: no PowerState: off After a short time, without any user action, it changes back to: Powered: yes PowerState: on The Bluetooth adapter is a MediaTek device, USB ID 0e8d:e025, on a Lenovo ThinkPad P16s Gen 4 AMD. The kernel log also showed errors during the Bluetooth power-off sequence, including: Bluetooth: hci0: command 0x2039 tx timeout Bluetooth: hci0: failed to reset (-19) Bluetooth: hci0: Error when powering off device on rfkill (-110) Expected behavior: When Bluetooth is turned off in GNOME Quick Settings or Settings, it should remain off until the user turns it on again. Actual behavior: Bluetooth turns itself back on automatically after being turned off. This occurs consistently after a fresh installation of Ubuntu 26.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:09:07 2026 InstallationDate: Installed on 2026-07-05 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21RX001LGE 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=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2025 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R2XET35W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 21RX001LGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrR2XET35W(1.15):bd08/29/2025:br1.15:efr1.8:svnLENOVO:pn21RX001LGE:pvrThinkPadP16sGen4AMD:rvnLENOVO:rn21RX001LGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21RX_BU_Think_FM_ThinkPadP16sGen4AMD:pfaThinkPadP16sGen4AMD: dmi.product.family: ThinkPad P16s Gen 4 AMD dmi.product.name: 21RX001LGE dmi.product.sku: LENOVO_MT_21RX_BU_Think_FM_ThinkPad P16s Gen 4 AMD dmi.product.version: ThinkPad P16s Gen 4 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159589/+subscriptions