[Bug 2156312] Re: Internal display black screen on Intel Lunar Lake with eDP panel

This bug is awaiting verification that the linux- realtime-7.0/7.0.0-31.31.1~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux- realtime-7.0' to 'verification-done-noble-linux-realtime-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux- realtime-7.0' to 'verification-failed-noble-linux-realtime-7.0'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-realtime-7.0-v2 verification-needed-noble-linux-realtime-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156312 Title: Internal display black screen on Intel Lunar Lake with eDP panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Internal display goes black after login on Intel Lunar Lake systems with an eDP panel. The external monitor works. The internal display shows as disabled in display settings and cannot be enabled. Hits 100% on affected hardware (3 units, 15/15 attempts). The bug is caused by LOBF (Link Off Between Frames) being enabled on platforms that use the legacy VRR timing generator. Those platforms do not meet the bspec requirement for LOBF (Always-on VRR TG with fixed refresh rate mode). Enabling LOBF incorrectly causes the display to go dark. [Fix] Replace the raw vmin/vmax/flipline comparison with the proper bspec checks: - intel_vrr_always_use_vrr_tg() to gate LOBF on platforms with Always-on VRR TG - intel_vrr_is_fixed_rr() to confirm fixed refresh rate mode Backported from upstream commit 8a517b1e6d8b, merged in v7.1-rc1. [Test Plan] Boot on affected Intel Lunar Lake hardware with an eDP panel. Without patch: internal display is black after login; shows as disabled in display settings. With patch: internal display works normally after login. [Where problems could occur] Could affect intel_alpm.c LOBF configuration logic in the i915 driver. If intel_vrr_always_use_vrr_tg() or intel_vrr_is_fixed_rr() return wrong results on a platform, LOBF would be incorrectly blocked, and Panel Replay power savings would be lost on those machines. The display would still work — it would just not enter LOBF mode. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156312/+subscriptions

[Bug 2156556] Re: Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier

This bug is awaiting verification that the linux- realtime-7.0/7.0.0-31.31.1~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux- realtime-7.0' to 'verification-done-noble-linux-realtime-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux- realtime-7.0' to 'verification-failed-noble-linux-realtime-7.0'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-realtime-7.0-v2 verification-needed-noble-linux-realtime-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156556 Title: Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier 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: New Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: New Bug description: [Impact] The TI TAS2781 smart amp fails to initialize when connected over SPI on the new HP HP ZBook. The right built-in speaker will fail to output after reboot [Fix] Two changes in one commit: 1. Always run the software reset sequence for the amp, not just in the no-gpio path. This resets device-0 even when its hardware reset pin has no effect. 2. Ignore -EXDEV during block processing when the device is on SPI. The driver keeps iterating through the blocks and adds up the total block size correctly. Upstream commit (in tiwai/sound for-next, not yet in a released tag): 513480da5e9c ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing https://patch.msgid.link/20260609105253.19510-1-baojun.xu@ti.com [Test Plan] On HP Zbook with a TAS2781 amp connected over SPI: $ dmesg | grep -i tas2781 Play audio: $ speaker-test -c 2 -t wav Without patch: dmesg shows "dev sw-reset fail" or "process_block: single write error" / "bulk_write error". No sound from the TAS2781 speakers. With patch: no reset or block errors in dmesg. Speakers play sound. [Where problems could occur] The reset change now runs the software reset on every path, including the gpio reset path. If the software reset is wrong for some amp, the device could fail to come up and stay silent. Both changes are amp init only, so a regression would show up as no sound on TAS2781 SPI systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156556/+subscriptions

[Bug 2158229] Re: MT7925 wifi is hard blocked on Dell's machine

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158229 Title: MT7925 wifi is hard blocked on Dell's machine Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] The Wi-Fi is hard blocked on Dell systems (CIDs: 202505-36757, 202501-36195, 202501-36253) and HP systems with Mediatek MT7925 cards. The wireless connection cannot be used. The rfkill state shows: $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Fix] We revert the hardware rfkill polling feature for Mediatek MT7925 cards. This polling feature was introduced upstream in v6.16. We also revert the local DMI quirk for HP systems since polling is now disabled. Reverted commits: • Revert "wifi: mt76: mt7925: add rfkill_poll for hardware rfkill" (reverts upstream commit e54b870212c079bef4ff61238f8c1278a14d1863 from v6.16) • Revert local DMI quirk commit for HP systems (reverts local commit 20c9b07dcea9d49c876c9532a48a6dc88f43d0f9) [Test Plan] Check the rfkill state on affected hardware: $ rfkill list Without the patches: The Wireless LAN interface shows "Hard blocked: yes". The Wi-Fi connection does not work. With the patches: The Wireless LAN interface shows "Hard blocked: no". The Wi-Fi connection works. [Where problems could occur] This change affects the mt76 Mediatek wireless driver. If a system has a physical wireless switch that needs software polling, the switch will stop working. Toggling the physical switch would not change the Wi-Fi block state. ========================================================= [Impact] The wifi is hard blocked and can't be used randomly. [Test] 1. Boot up Machine 2. Run `rfkill list` to check wlan0 block state Wireless: Mediatek Inc. - 14c3:7925 ubuntu@localhost:~$ rfkill list 0: hci0: Bluetooth  Soft blocked: no  Hard blocked: no 1: phy0: Wireless LAN  Soft blocked: no  Hard blocked: yes [Affected Machines] 202505-36757 202501-36195 202501-36253 [Similar Issue] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2127044 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1020-oem 6.17.0-1020.20 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 Uname: Linux 6.17.0-1020-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: ubuntu 1918 F.... pipewire                       ubuntu 1922 F.... wireplumber  /dev/snd/controlC0: ubuntu 1922 F.... wireplumber  /dev/snd/seq: ubuntu 1918 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jun 25 05:43:16 2026 DistributionChannelDescriptor:  # This is the distribution channel descriptor for Ubuntu 24.04 for Dell  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor  canonical-oem-somerville-noble-oem-24.04b-proposed-20250604-520 InstallationDate: Installed on 2026-05-07 (49 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) IwConfig:  lo no wireless extensions.  enp195s0f0 no wireless extensions.  wlp194s0 no wireless extensions. MachineType: Dell Inc. Dell Pro Max 14 MC14255 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=881d0e73-6adc-444d-90b2-9491672e82b1 ro quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.17.0-1020-oem N/A  linux-backports-modules-6.17.0-1020-oem N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2025 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0WT010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd09/09/2025:br1.4:efr1.3:svnDellInc.:pnDellProMax14MC14255:pvr:rvnDellInc.:rn0WT010:rvrD01:cvnDellInc.:ct10:cvr:sku0D80: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 MC14255 dmi.product.sku: 0D80 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158229/+subscriptions

[Bug 2158462] Re: Malformed HV_LINUX_VENDOR_ID breaks VM Availability Metric on Azure

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158462 Title: Malformed HV_LINUX_VENDOR_ID breaks VM Availability Metric on Azure Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: Won't Fix Status in linux source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2158462 SRU Justification [Impact] Commit 56f727d2cc7a ("UBUNTU: SAUCE: (no-up) hv: Supply vendor ID and package ABI") introduced a regression that breaks the VM Availability Metric functionality on Azure due to a malformed HV_LINUX_VENDOR_ID being reported to Hyper-V. This impacts customers that rely on that metric to assess if their VMs are in a healthy state or not. [Fix] The HV_LINUX_VENDOR_ID should be 0x8180 rather than 0x80; this issue can be fixed by adjusting the value of the constant in all generic kernels affected by this. [Test Plan] Compile and boot tested; verified that the metric works on an Azure VM running a kernel with the fix. Microsoft is to perform validation on their side as well. [Regression Potential] Low regression potential, but could impact the identification of Ubuntu guests on Azure. [Other Info] SF: #00439544 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158462/+subscriptions

[Bug 2158605] Re: The screen will show garbages by running glxgears fullscreen.

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158605 Title: The screen will show garbages by running glxgears fullscreen. Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid 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 Released Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2158605 [Impact] Screen garbage can show when running glxgears fullscreen on affected Intel graphics systems. The Launchpad report says it happens about 1 in 3 runs. [Fix] Skip the SCANOUT flag and VM_BIND checks for external dma-buf imports in the xe display framebuffer setup and pin paths. For imported sg buffers, CPU caching is controlled by the exporter. The patch keeps the existing checks for local buffers. This patch is from upstream Patchwork, not yet merged: https://patchwork.freedesktop.org/patch/732636/ [Test Plan] Run the fullscreen glxgears test 10 times: $ glxgears -fullscreen Or run the matching checkbox test for the affected GPU: $ checkbox-cli run graphics/2_valid_glxgears_fullscreen_PCI_ID_<affected-gpu> Without patch: screen shows garbage during the fullscreen glxgears test. With patch: fullscreen glxgears completes without screen garbage. [Where problems could occur] Could break external dma-buf framebuffer setup in the xe display driver. If the sg-buffer exception is wrong, imported framebuffers could be accepted when they should be rejected. This could show as display corruption, failed framebuffer creation, or xe framebuffer pinning warnings. [Other Info] SRU target: linux-oem-6.17. The patch is not in an upstream kernel release yet. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2158605/+subscriptions

[Bug 2160302] Re: Drop DEP-8 tests from kernel packages

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160302 Title: Drop DEP-8 tests from kernel packages Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Triaged Status in linux source package in Noble: Triaged Status in linux source package in Resolute: Triaged Status in linux source package in Stonking: Fix Committed Bug description: == SRU Justification == Impact: We added DEP-8 tests to the kernel package when there was no other testing. Today we do much more thorough regression testing internally (RT is a superset of kernel ADT). Given that generally ADT is already struggling to cope and we literally get no added value from running the same tests in ADT and RT lets drop the tests from ADT. This does not change the fact that the tests of other packages with relations to the kernel get run in ADT for each new kernel (DKMS, snapd, systemd, glibc, ...). Fix: Delete debian/tests from the kernel source package. Testcase: The kernel package stops showing as separate test run on ADT. Other packages get still triggered for new kernel uploads. Regression Potential: Possibly the missing test gets flagged on the first modified upload and has to be accepted. Otherwise nothing should hard rely on those tests to be run in ADT. And they still run for RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160302/+subscriptions

[Bug 2161309] Re: Backlight regression

Installed the following on LG Gram: linux-image-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed] linux-modules-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed,automatic] linux-modules-nvidia-580-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed] linux-nvidia-tools-7.0.0-1018/resolute-proposed,now 7.0.0-1018.18 amd64 [installed] linux-objects-nvidia-580-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed,automatic] linux-signatures-nvidia-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed,automatic] linux-tools-7.0.0-1018-nvidia/resolute-proposed,now 7.0.0-1018.18 amd64 [installed] brightness still stuck on max changed tag to verification failed. let me know if i failed the verification. ** Tags removed: verification-needed-resolute-linux-nvidia ** Tags added: resolute-linux-nvidia verification-failed- -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Fix Committed Bug description: ----------------------------- Possible workaround until 7.0.0-31 kernel is released Boot with i915.enable_dpcd_backlight=0 parameter ----------------------------- ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not 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:  USER PID ACCESS COMMAND  /dev/snd/controlC0: neal 3608 F.... wireplumber  /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native 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: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions

[Bug 2161757] Re: Resolute real-time patchset: 7.0.1-rt2

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161757 Title: Resolute real-time patchset: 7.0.1-rt2 Status in ubuntu-realtime: In Progress Status in linux package in Ubuntu: In Progress Status in linux-realtime package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux-realtime source package in Resolute: In Progress Bug description: [Impact] Starting in resolute, the patches from the PREEMPT_RT patchset are applied to generic so they can be inherited by derivative kernels and flavors that need real-time. PREEMPT_RT 7.0-rc1-rt1 patchset was previously applied ( https://bugs.launchpad.net/ubuntu- realtime/+bug/2143181 ). The patches have been updated with patchset 7.0.1-rt2. This set of patches will be filtered to only ones that apply where we support real-time, including amd64 and arm64. Of those, only two have changed. They were previously dropped due to conflicts, so this effort will reapply the new versions of the patches. [Fix] For kernel 7.0, the upstream PREEMPT_RT patchset 7.0.1-rt2 has been released. https://cdn.kernel.org/pub/linux/kernel/projects/rt/7.0/ The following patches were previously applied and have not changed: UBUNTU: SAUCE: sysfs: Add /sys/kernel/realtime entry UBUNTU: SAUCE: Revert "drm/i915: Depend on !PREEMPT_RT." UBUNTU: SAUCE: drm/i915: Consider RCU read section as atomic. UBUNTU: SAUCE: drm/i915/guc: Consider also RCU depth in busy loop. UBUNTU: SAUCE: drm/i915: Drop the irqs_disabled() check UBUNTU: SAUCE: drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() + spin_lock() UBUNTU: SAUCE: drm/i915: Disable tracing points on PREEMPT_RT UBUNTU: SAUCE: drm/i915: Don't disable interrupts on PREEMPT_RT during atomic updates UBUNTU: SAUCE: drm/i915: Use preempt_disable/enable_rt() where recommended These patches have been updated and will be applied as part of this patchset: UBUNTU: SAUCE: Reapply "serial: 8250: Revert "drop lockdep annotation from serial8250_clear_IER()"" UBUNTU: SAUCE: Reapply "serial: 8250: Switch to nbcon console" [Test Case] Compile and boot test [Where things could go wrong] These patches primarily apply to the 8250 serial driver, so they may cause minor performance differences in these drivers even when PREEMPT_RT is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/2161757/+subscriptions

[Bug 2162917] Re: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios"

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162917 Title: Backport: "mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios" Status in linux package in Ubuntu: New Status in linux-nvidia-7.0 package in Ubuntu: New Status in linux source package in Resolute: New Status in linux-nvidia-7.0 source package in Resolute: New Bug description: Clean cherry-pick from linux-next: ``` (cherry picked from commit ae75e88d8c258fd849de594e7d468b5263e7b3e3 linux-next) ``` John Hubbard, Acked-by David Hildenbrand, applied by Andrew Morton. [Lore thread](https://lore.kernel.org/all/20260708005745.164928-1-jhubbard@nvidia.com/). ## Problem `f002882ca369` (present on this branch) made `gup_fast_folio_allowed()` bail to the slow path for *any* order-0 folio with a NULL `->mapping` when `CONFIG_SECRETMEM=y`. Pages from `alloc_page()` + `vm_insert_page()` legitimately have a NULL mapping, so every `pin_user_pages_fast()` over such a range misses the fast path — nvidia-fs (GPUDirect Storage) allocates its shadow buffers exactly this way. The NULL check was meant to catch truncated file-backed pages, not secretmem. Secretmem folios are published via `filemap_add_folio()`, which always sets `->mapping`, so a NULL mapping proves the folio is *not* secretmem. Returning `!reject_file_backed` keeps long-term writable pins on the slow path and restores the fast path otherwise — exactly the pre-`f002882ca369` behaviour. `CONFIG_SECRETMEM=y` on amd64 and arm64, so this is live on every flavour we ship. ## Measurement (GH200, 288 cores) A module reproducing the nvidia-fs pattern (`alloc_page` + `vm_insert_page`, then `pin_user_pages_fast(..., FOLL_WRITE, ...)`), with an anonymous-memory control the patch cannot affect. `get_user_pages_fast_only()` gives the GUP-fast verdict directly: **0/N unpatched, N/N patched**. Median ns/page, 512 pages/thread, 5 reps: | threads | 4K unpatched → patched | 64K unpatched → patched | |--------:|-----------------------:|------------------------:| | 1 | 34 → 34 (1.0x) | 33 → 30 (1.1x) | | 8 | 74 → 33 (**2.2x**) | 1920 → 31 (**62x**) | | 32 | 95 → 33 (**2.9x**) | 4792 → 33 (**145x**) | | 128 | 500 → 218 (noisy) | 16673 → 76 (**219x**) | The anon control held at 30-35 ns/page across all four kernels, so only the affected range moved. Stock `7.0.0-1015-nvidia-64k` independently reproduces the unpatched 64K numbers (8 threads: 1176 vs 37), so this isn't a test-config artefact. Single-threaded it's a wash; the win is under concurrency. `perf` on the unpatched 64K kernel shows the slow path is ~90% lock contention (`queued_spin_lock_slowpath` 72%), gone entirely once patched — contention that scales with thread count, not a fixed per-page cost. ## Risk Low. One line in a static function with three callers, all in GUP-fast. Only `reject_file_backed == false && check_secretmem && mapping == NULL` changes behaviour; long-term writable pins are untouched. A secretmem folio caught mid-truncate can't happen here: `secretmem_setattr()` refuses to shrink, there's no `.fallocate` (so no punch-hole), and `secretmem_migrate_folio()` returns `-EBUSY`. Only inode eviction remains, which requires every VMA gone — no VMA, no PTE for GUP-fast to walk. Raised by David Hildenbrand on v1 and resolved before he Acked. ## Testing Applies cleanly; built arm64 4K/64K and x86_64, no new warnings; verified in the binary (unpatched `mov w0, #0x0` vs patched `eor w0, w0, #0x1`); benchmarked as above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162917/+subscriptions

[Bug 2161309] Re: Backlight regression

** Tags added: noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Fix Committed Bug description: ----------------------------- Possible workaround until 7.0.0-31 kernel is released Boot with i915.enable_dpcd_backlight=0 parameter ----------------------------- ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not 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:  USER PID ACCESS COMMAND  /dev/snd/controlC0: neal 3608 F.... wireplumber  /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native 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: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions

[Bug 2162952] Re: i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35

Probably bug 2161309 I'd suggest trying the 7.0.0-31 kernel in -proposed ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162952 Title: i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35 Status in linux package in Ubuntu: Incomplete Bug description: # i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35 ## Summary On resume from S3 (`mem_sleep=deep`), the internal eDP panel is permanently dark. It is **unpowered, not merely unlit**. No userspace action recovers it — only a reboot. Regression: **6.17.0-35-generic works, 7.0.0-28-generic fails.** The bug is **specific to the S3/deep path** — `s2idle` on the same kernel resumes correctly. ## Test matrix | Kernel | mem_sleep | Panel on resume | |---|---|---| | 6.17.0-35-generic | deep (S3) | OK — 39 suspend cycles over 25 days, no failures | | 7.0.0-28-generic | deep (S3) | **FAIL** — dark, reboot-only recovery | | 7.0.0-28-generic | s2idle | OK — verified over a 32.5 min suspend | ## Key diagnostic detail After the failed resume, every software indicator reports a healthy display. A dead panel is indistinguishable from a live one via sysfs/xrandr: - `/sys/class/drm/card1-eDP-1/status` = `connected`, `enabled` = `enabled` - `xrandr` reports the output enabled, `link-status: Good`, `dpms On` - X is genuinely compositing live content into the panel's region (confirmed by sampling root-window pixels — real window content present) - `intel_backlight`: `actual_brightness` = 1023/1023, `bl_power` = 0; writes are accepted and read back correctly, but a full 0 -> max PWM sweep produces **zero** physical response - A full modeset (`xrandr --output eDP-1 --off` then `--mode ... `) does **not** relight it - **No eDP link-training errors or drm errors in the kernel log** — the resume path logs clean (GuC/HuC reload, mei_hdcp/mei_pxp rebind, nothing else) This points at panel power-sequencing (PPS) state not being restored on the S3 resume path, rather than a link, mode, or backlight-value problem. ## Hardware - Chassis: Elimina Pro V 16 (Clevo/Kapok barebone, subsystem 2564) - iGPU: Intel i915 `0000:00:02.0`, alderlake_p/raptorlake_p, device ID a7a8, integrated display version 13.00 stepping E0 - dGPU: NVIDIA `0000:01:00.0`, driver 595, hybrid/PRIME (external via HDMI-1-0 reverse-prime) - Panel: AUO B160QANAA.H, 2560x1600@165Hz, eDP-1, vrr_capable - Firmware default sleep state: `deep` (nothing forcing it on the kernel cmdline) - Ubuntu 24.04, GNOME on X11, systemd 255 ## Reproducer 1. Boot 7.0.0-28-generic with default `mem_sleep=deep` 2. Confirm the internal panel is lit 3. `systemctl suspend` 4. Wake via power button Internal panel stays dark. External displays are unaffected and continue working. ## Workaround Boot 6.17.0-35-generic. `mem_sleep_default=s2idle` also avoids the bug, but is **not usable on this platform**: S0ix never engages (`/sys/kernel/debug/pmc_core/slp_s0_residency_usec` stayed at **0** across a 32.5-minute suspend), giving 4.67 W average draw vs ~0.3-0.8 W for working S3 (9.2 %/hour battery drain). That may be a separate platform issue worth its own report. Sysinfo: === version === uname -a: Linux aidan-dunphy-Elimina-Pro-V-16 7.0.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 15:50:57 UTC 2 x86_64 x86_64 x86_64 GNU/Linux /proc/version_signature: Ubuntu 7.0.0-28.28~24.04.1-generic 7.0.12 lsb_release: Ubuntu 24.04.4 LTS installed kernel pkg: linux-image-7.0.0-28-generic 7.0.0-28.28~24.04.1 fallback kernel pkg: linux-image-6.17.0-35-generic 6.17.0-35.35~24.04.1 cmdline: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=a06770dc-b95b-4687-8825-6650f2d58f13 ro quiet splash mem_sleep_default=s2idle vt.handoff=7 mem_sleep: [s2idle] deep === display hardware === 00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04) 00:06.2 PCI bridge [0604]: Intel Corporation Device [8086:a73d] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2d18] (rev a1) === drm connectors === card1-DP-1 disconnected enabled=disabled card1-DP-2 disconnected enabled=disabled card1-DP-3 disconnected enabled=disabled card1-DP-4 disconnected enabled=disabled card1-DP-5 disconnected enabled=disabled card1-eDP-1 connected enabled=enabled card1-HDMI-A-1 disconnected enabled=disabled card2-eDP-2 disconnected enabled=disabled card2-HDMI-A-2 connected enabled=disabled === panel EDID (eDP-1, base block) === 00ffffffffffff0006afb58100000000 17220104b5221678038235a5534a9e26 0f505400000001010101010101010101 0101010101011f6f00a0a0408f603020 aa0058d7100000180000000f00000000 00000000000000000020000000fd0c30 a522224e010a202020202020000000fc 004231363051414e41412e48200a0264 === nvidia driver === nvidia-driver-590-open 590.48.01-0ubuntu0.24.04.5 nvidia-driver-595-open 595.84-0ubuntu0.24.04.1 === i915 messages, current boot === Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Found alderlake_p/raptorlake_p (device ID a7a8) integrated display version 13.00 stepping E0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Registered 4 planes with drm panic Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: fbcon: i915drmfb (fb0) is primary device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915]) Aug 06 12:15:28 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162952/+subscriptions

[Bug 2163019] Re: Screen brightness control completely broken on kernel 7.0.0-28 and 7.0.0-29; works perfectly on 7.0.0-22. Dell Inspiron 15 3511, Intel Tiger Lake Iris Xe.

*** This bug is a duplicate of bug 2161309 *** https://bugs.launchpad.net/bugs/2161309 ** This bug has been marked a duplicate of bug 2161309 Backlight regression -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163019 Title: Screen brightness control completely broken on kernel 7.0.0-28 and 7.0.0-29; works perfectly on 7.0.0-22. Dell Inspiron 15 3511, Intel Tiger Lake Iris Xe. Status in linux package in Ubuntu: New Bug description: Summary: Backlight brightness control regressed between kernel 7.0.0-22 and 7.0.0-28 on a Dell Inspiron 15 3511 with Intel Tiger Lake-LP GT2 [Iris Xe Graphics]. The physical brightness keys are detected (on-screen slider moves), but the actual screen backlight does not change at all. Completely broken on 7.0.0-28 and 7.0.0-29. Works perfectly on 7.0.0-22. Hardware: Laptop: Dell Inspiron 15 3511 CPU/GPU: Intel Tiger Lake-LP GT2 [Iris Xe Graphics] (device ID 9a49) OS: Ubuntu 26.04 (resolute), dual boot with Windows Backlight interface: /sys/class/backlight/intel_backlight DMC firmware: i915/tgl_dmc_ver2_12.bin (v2.12) Regression window: ✅ Works: 7.0.0-22-generic ❌ Broken: 7.0.0-28-generic ❌ Broken: 7.0.0-29-generic The jump from 7.0.0-22 to 7.0.0-28 was introduced by an unattended upgrade on 2026-08-02. What was ruled out (extensive testing): Not a hardware fault — brightness works perfectly in Windows on the same machine (dual boot), and works in a live Ubuntu session from the original install ISO (kernel 7.0.0-14). Not a BIOS/firmware issue — booting the same hardware from a clean live USB with kernel 7.0.0-14 restored full brightness control, confirming the BIOS behaves correctly. The BIOS was also updated to the latest available version — no change. Not a firmware package regression — downgraded linux-firmware-intel-graphics from 0ubuntu2.1 back to 0ubuntu2 and confirmed the DMC firmware blob is identical between the working live session and the installed system (md5: de018e9fa626be8cf8d388c0bf767410). Brightness still broken on 7.0.0-28/29 with the old firmware package. Not a software/daemon interference — tested from a bare virtual terminal (Ctrl+Alt+F3, no desktop session, no extensions, no daemons running). Still broken. ACPI/SMI chain verified firing correctly — dumped and disassembled the DSDT. The _BCM brightness method routes through GENS → SMBF → ASMI(), which writes 0xE0 to I/O port 0xB2 (a genuine SMI trigger). Verified via the CPU's IA32_SMI_COUNT MSR (register 0x34, msr-tools) that the SMI counter increments by exactly 1 on every write to /sys/class/backlight/acpi_video0/brightness — the ACPI method and SMI are firing correctly. This was tested on the broken kernel (7.0.0-29); the issue is that the result is ignored. Kernel isolated as the sole cause — with the firmware package held at the old version, switching between 7.0.0-22 (works) and 7.0.0-28 (broken) is the only variable that changes the outcome. Kernel parameters tested (none fixed it on 7.0.0-28/29): acpi_backlight=native acpi_backlight=vendor acpi_backlight=video i915.enable_dpcd_backlight=1 i915.enable_dpcd_backlight=2 i915.enable_psr=0 i915.invert_brightness=1 Blacklisted xe module, ensured i915 has exclusive control Current workaround: Pinned to 7.0.0-22-generic via apt-mark hold. Brightness fully functional on that kernel. Reproduces on: Dell Inspiron 15 3511, Tiger Lake Iris Xe, Ubuntu 26.04, kernel ≥ 7.0.0-28. Happy to provide full dmesg output, ACPI DSDT dump, or any other diagnostics from either the working (7.0.0-22) or broken (7.0.0-29) kernel on request. This bug were spotted by a human and this report was generated with the assist of an AI after giving it all of the context. Thank you for making linux available for the community ❤️. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC0: mohammed 4163 F.... wireplumber  /dev/snd/seq: mohammed 4147 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 7 11:37:32 2026 InstallationDate: Installed on 2026-05-19 (80 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Inspiron 15 3511 ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=af9f8c53-fb0e-4c6a-951d-7f651c38ed30 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: 05/27/2026 dmi.bios.release: 1.47 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.47.0 dmi.board.name: 0042CN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.47.0:bd05/27/2026:br1.47:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0042CN:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163019/+subscriptions

[Bug 2163204] Re: Regression: Acer Nitro AN515-55 internal eDP display/backlight fails to resume from S3 since 7.0.0-28; 7.0.0-27 works

*** This bug is a duplicate of bug 2161309 *** https://bugs.launchpad.net/bugs/2161309 ** This bug has been marked a duplicate of bug 2161309 Backlight regression -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163204 Title: Regression: Acer Nitro AN515-55 internal eDP display/backlight fails to resume from S3 since 7.0.0-28; 7.0.0-27 works Status in linux package in Ubuntu: New Bug description: After upgrading the Ubuntu 26.04 kernel from 7.0.0-27-generic to 7.0.0-28-generic, my Acer Nitro AN515-55 no longer restores the internal display after suspend-to-RAM (S3/deep). The problem is also present in 7.0.0-29-generic. The computer itself successfully resumes. I can connect to the machine over SSH after the failed resume, networking works, and kernel logs reach PM: suspend exit. The failure appears limited to restoration of the internal Intel-driven eDP display/backlight. Regression testing: 7.0.0-27-generic: WORKS 7.0.0-28-generic: FAILS 7.0.0-29-generic: FAILS I tested 7.0.0-27 with the same NVIDIA 595.84 open driver currently used on the newer kernels, and suspend/resume works normally. Hardware: Acer Nitro AN515-55 Intel CometLake-H GT2 UHD Graphics (i915) NVIDIA GeForce RTX 3050 Mobile Internal 1920x1080 eDP panel BIOS V2.06 Failure behavior: Boot 7.0.0-28 or 7.0.0-29. Suspend using systemctl suspend or normal desktop suspend. Wake the computer. Computer resumes and remains accessible via SSH, but the internal laptop display remains completely black. During the failed state: /sys/class/drm/card1-eDP-1/status reports connected. i915_display_info reports Pipe A enabled and active and eDP-1 connected. The framebuffer is reported visible. /sys/class/backlight/intel_backlight/brightness accepts nonzero values. /sys/class/backlight/intel_backlight/actual_brightness remains 0. Writing brightness values manually does not restore the display. Switching virtual terminals does not restore it. Restarting GDM does not restore it. Additional testing performed: pm_test=devices: passes pm_test=platform: passes pm_test=core: passes PRIME Intel-only mode: still fails on affected kernels i915.enable_psr=0: no change intel_iommu=off: no change pcie_aspm=off: no fix 60 Hz instead of 144 Hz: no change s2idle: does not behave correctly on this hardware S3/deep is the normal sleep mode (s2idle [deep]) The regression therefore appears to have been introduced between Ubuntu kernels 7.0.0-27 and 7.0.0-28, possibly affecting restoration of the Intel i915/eDP panel or backlight following a real S3 transition. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leo 3546 F.... wireplumber /dev/snd/controlC1: leo 3546 F.... wireplumber /dev/snd/seq: leo 3525 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 15:02:21 2026 InstallationDate: Installed on 2025-10-13 (301 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More&Better] Bus 001 Device 003: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Acer Nitro AN515-55 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=21d24b70-7c3c-4b62-8c0c-b0018d627618 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/20/2021 dmi.bios.release: 2.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stonic_CMS dmi.board.vendor: CML dmi.board.version: V2.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.06 dmi.ec.firmware.release: 2.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd08/20/2021:br2.6:efr2.5:svnAcer:pnNitroAN515-55:pvrV2.06:rvnCML:rnStonic_CMS:rvrV2.06:cvnAcer:ct10:cvrV2.06:sku0000000000000000:pfaNitro5: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-55 dmi.product.sku: 0000000000000000 dmi.product.version: V2.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163204/+subscriptions