[РЕШЕНО] Ошибка № ...

суббота

[Bug 2161289] Re: Kernel 7.0.0-28-generic: system hangs on shutdown/reboot on ThinkPad T14 Gen 2 AMD

Similar issue. System hangs indefinitely during shutdown or reboot, but only when some USB devices are connected (affects gamepads, mounted USB drives, and devices drawing power/charging via USB). So it can be linked to USB subsystem management in kernel 7.0.0-28-generic, like if something blocks USB shutdown or xhci driver. For me the issue is session-dependent: after logging out and shutting down from the login screen (Mint 22.3, Cinnamon 64 bit), shutdown works. Windows 10 on the same hardware shuts down correctly with the same USB devices connected. USB wakeup settings are disabled. Reverting to kernel 6.17.0-40-generic completely resolves the issue. System (after reverting to 6.17.0-40-generic): System: Kernel: 6.17.0-40-generic arch: x86_64 bits: 64 Desktop: Cinnamon v: 6.6.9 Distro: Linux Mint 22.3 Zena Machine: Type: Desktop Mobo: Micro-Star model: MAG B650 TOMAHAWK WIFI (MS-7D75) v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.O0 date: 06/24/2025 CPU: Info: 8-core model: AMD Ryzen 7 7800X3D bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 3457 min/max: 426/5053 cores: 1: 4405 2: 3585 3: 4405 4: 3728 5: 3665 6: 2983 7: 3671 8: 2983 9: 4400 10: 3598 11: 2983 12: 2983 13: 2983 14: 2983 15: 2983 16: 2983 Graphics: Device-1: AMD driver: amdgpu v: kernel Device-2: AMD Raphael driver: amdgpu v: kernel Device-3: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo type: USB Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.8-0ubuntu0.24.04.2 renderer: AMD Radeon RX 9070 (radeonsi gfx1201 LLVM 20.1.2 DRM 3.64 6.17.0-40-generic) API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib Audio: Device-1: AMD driver: snd_hda_intel Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel Device-4: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo type: USB Device-5: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB API: ALSA v: k6.17.0-40-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp14s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e IF: wlp15s0 state: down mac: <filter> Bluetooth: Device-1: MediaTek Wireless_Device driver: btusb type: USB Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 5.4 Drives: Local Storage: total: 3.64 TiB used: 605.18 GiB (16.2%) ID-1: /dev/nvme0n1 vendor: KIOXIA model: EXCERIA PLUS G4 SSD size: 931.51 GiB ID-2: /dev/sda vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB type: USB -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161289 Title: Kernel 7.0.0-28-generic: system hangs on shutdown/reboot on ThinkPad T14 Gen 2 AMD Status in linux package in Ubuntu: Confirmed Bug description: ## Summary On Ubuntu 26.04 LTS, kernel 7.0.0-28-generic fails to shutdown or reboot properly on ThinkPad T14 Gen 2 (Ryzen 5 Pro). System reaches final.target, black screen, but power LED stays on indefinitely. ## Affected Hardware - ThinkPad T14 Gen 2 (Type 20UF) - AMD Ryzen 5 Pro 5650U - Integrated AMD Vega Graphics (amdgpu) ## Affected Kernel - 7.0.0-28-generic: FAILS - 7.0.0-27-generic: WORKS ## Steps to Reproduce 1. Boot kernel 7.0.0-28 2. Attempt shutdown or reboot via UI or CLI 3. System hangs with black screen, power LED remains on 4. Requires force power-off ## Root Cause systemd successfully reaches shutdown.target and final.target (journalctl confirms all services stopped cleanly). System hangs at kernel ACPI power management stage, likely amdgpu driver regression in 7.0.0-28. ## Workaround Downgrade to kernel 7.0.0-27-generic. 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 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 00:18:57 2026 InstallationDate: Installed on 2026-05-08 (72 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20XLS0T500 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=off pci=noaer acpi=debug 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/2026 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET64W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0T500 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.34 dmi.modalias: dmi:bvnLENOVO:bvrR1MET64W(1.34):bd04/16/2026:br1.34:efr1.34:svnLENOVO:pn20XLS0T500:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0T500:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a:pfaThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0T500 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161289/+subscriptions

[Bug 2161359] Re: linux-modules-7.0.0-28-generic breaks backlight control on some laptops

This bug affects me too on Lenovo ThinkPad T480. The brightnes control panel appears, but it has no effect. Additionally, when I suspend the laptop, then when I continue the screen becomes very dim, it's very hard to see anything, and I can't bring its brightness without restarting the laptop. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161359 Title: linux-modules-7.0.0-28-generic breaks backlight control on some laptops Status in linux package in Ubuntu: Confirmed Bug description: linux-modules-7.0.0-28-generic includes changes to backlight control in i915 module. This was supposed to be addressing LP: #2152570 making backlight work on some older laptops. The changes break backlight control on a Samsung 940X laptop with i5-3317 CPU. - drm/i915/backlight: Remove try_vesa_interface https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=40d2f5820951dee818d05c14677277048bd85f9f The previous version of intel_dp_aux_init_backlight_funcs in drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c had a display->params.enable_dpcd_backlight case of INTEL_DP_AUX_BACKLIGHT_AUTO which would only try VESA interface for a panel->vbt.backlight.type of INTEL_BACKLIGHT_VESA_EDP_AUX_INTERFACE or "if (intel_dp->edp_dpcd[0] >= DP_EDP_15)" The new version of intel_dp_aux_init_backlight_funcs tries a VESA interface for all values of panel->vbt.backlight.type including INTEL_BACKLIGHT_PMIC or INTEL_BACKLIGHT_LPSS or INTEL_BACKLIGHT_DSI_DCS or INTEL_BACKLIGHT_PANEL_DRIVER_INTERFACE or INTEL_BACKLIGHT_DISPLAY_DDI even when "(intel_dp->edp_dpcd[0] < DP_EDP_15)". That is overriding funcs that are set in drivers/gpu/drm/i915/display/intel_backlight.c by intel_backlight_init_funcs before it calls intel_dp_aux_init_backlight_funcs. Looking at the output of drm_dbg_kms() calls in i915 driver using kernel boot parameter drm.debug=0x06 shows that the VESA control is used. I added a call to log vbt.backlight.type from intel_bios.c parse_lfp_backlight(). i915 0000:00:02.0: [drm:parse_lfp_backlight [i915]] vbt.backlight.type: INTEL_BACKLIGHT_DISPLAY_DDI That confirmed that vbt.backlight.type is INTEL_BACKLIGHT_DISPLAY_DDI on this laptop. The dmesg output from intel_edp_init_dpcd shows that intel_dp->edp_dpcd[0] is DP_EDP_13, (0x02). i915 0000:00:02.0: [drm:intel_edp_init_dpcd [i915]] eDP DPCD: 02 b7 f6 00 00 Whatever extra tests added in the new check_if_vesa_backlight_possible() function does not spare this laptop. The VESA control is pushed in replacing the working functions previously set by intel_backlight_init_funcs(). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: mike 2707 F.... wireplumber /dev/snd/controlC0: mike 2707 F.... wireplumber /dev/snd/seq: mike 2697 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:43:48 2026 InstallationDate: Installed on 2025-09-10 (313 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940X3G/930X3G 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-28-generic root=UUID=ff2b50fd-2ec0-4e8d-8be8-8d109a2614e9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M drm.debug=0x06 SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-24 (87 days ago) dmi.bios.date: 08/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ACJ.128.140819.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940X3G-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ACJ.128.140819.dg:bd08/19/2014:br4.6:svnSAMSUNGELECTRONICSCO.,LTD.:pn940X3G/930X3G:pvrP05ACJ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940X3G-K04US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:skuSAMSUNGSENSSeries:pfaSAMSUNGSENS: dmi.product.family: SAMSUNG SENS dmi.product.name: 940X3G/930X3G dmi.product.sku: SAMSUNG SENS Series dmi.product.version: P05ACJ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161359/+subscriptions

[Bug 2158978] Re: System freeze on startup: nvidia-modeset/DifrPrefetchEventDeferredWork deadlock with KMS thread (driver 595.71.05, kernel 7.0.0-27)

After upgrading to version 595.84, the issue still persists. Specifically: approximately 1–2 hours after the system suspends, the system completely freezes, and the kernel log still shows the "KMS thread blocked" warning. I have attached the full nvidia-bug- report.log.gz report file for your reference. ** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-595/+bug/2158978/+attachment/5986278/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158978 Title: System freeze on startup: nvidia-modeset/DifrPrefetchEventDeferredWork deadlock with KMS thread (driver 595.71.05, kernel 7.0.0-27) Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-595 package in Ubuntu: Confirmed Bug description: System freezes completely shortly after login. A deadlock occurs between the nvidia-modeset kernel thread and the KMS thread. Requires hard reboot to recover. Hardware: Lenovo 83JM (BIOS PZCN49WW 2025-06-06) GPU: NVIDIA GeForce RTX 5050 laptop (hybrid GPU with Intel i915) Driver: nvidia 595.71.05 (Open Kernel Module) Kernel: 7.0.0-27-generic (Ubuntu 26.04) --- Kernel log (Jul 02 ~03:58) --- INFO: task KMS thread:5195 blocked for more than 122 seconds. task:KMS thread state:D pid:5195 nvkms_ioctl_from_kapi_try_pmlock+0x55/0xd0 [nvidia_modeset] ApplyModeSetConfig+0x357/0xba0 [nvidia_modeset] nv_drm_atomic_apply_modeset_config+0x80b/0x9c0 [nvidia_drm] drm_atomic_commit+0x6c/0xf0 nv_drm_ioctl+0x38/0x3f0 [nvidia_drm] INFO: task KMS thread:5195 blocked on a semaphore likely last held by task nvidia-modeset/:511 task:nvidia-modeset/ state:R (running but stuck) pid:511 RIP: nvWriteGpEntry+0xa4/0x370 [nvidia_modeset] nvPushKickoff+0x28/0x50 [nvidia_modeset] PrefetchHelperSurfaceEvo+0x45c/0x650 [nvidia_modeset] nvDIFRPrefetchSurfaces+0x135/0x1f0 [nvidia_modeset] DifrPrefetchEventDeferredWork+0x16/0x30 [nvidia_modeset] nvkms_kthread_q_callback+0xe9/0x1a0 [nvidia_modeset] (Repeated every ~2 min for 20+ minutes, from 122s to 1228s blocked) --- Additional errors at driver load --- NVRM: NV_ERR_INVALID_DATA from SBIOS for platform power mode and target temperature nvidia_init_module: "Unpatched return thunk in use" (kernel taint OE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158978/+subscriptions

[Bug 2161575] Re: [regression] 7.0.0-28: eDP backlight stays off after resume on ThinkPad T480 (i915 selects DPCD/AUX backlight instead of native PWM)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161575 Title: [regression] 7.0.0-28: eDP backlight stays off after resume on ThinkPad T480 (i915 selects DPCD/AUX backlight instead of native PWM) Status in linux package in Ubuntu: Confirmed Bug description: **Package:** linux-image-generic-hwe-26.04 7.0.0-28.28 **Regression:** yes, 7.0.0-27.27 -> 7.0.0-28.28 **Tags:** `regression-update kernel-bug i915 suspend-resume backlight resolute` ## Summary After upgrading to kernel 7.0.0-28, the internal display backlight does not come on when resuming from suspend. The machine is running after resume (it accepted a blind `sudo reboot` typed at the dark screen), but the backlight stays off. Increasing brightness with the brightness keys does not bring it on. The panel is still driving an image: screen contents are legible under a bright external light. The failure is therefore confined to the backlight, not a modeset or output failure. Booting 7.0.0-27 avoids the problem. Booting 7.0.0-28 with `i915.enable_dpcd_backlight=0` also avoids it. ## Hardware - **Machine:** Lenovo ThinkPad T480, machine type 20L6S0MD00 - **BIOS:** N24ET81W (1.56), 2025-09-06 - **GPU:** Intel Kaby Lake-R GT2 [UHD Graphics 620] `[8086:5917]` rev 07, subsystem `[17aa:225d]` (lspci reports "Lenovo ThinkPad T480 (20L5)") - **Panel:** LG Display LP140WF6-SPB7 on eDP-1 (model string read from EDID) - **OS:** Ubuntu 26.04 LTS (resolute) ## Steps to reproduce 1. Boot 7.0.0-28-generic with stock kernel parameters (`quiet splash`). 2. Suspend. The journal records `PM: suspend entry (deep)`. 3. Resume. **Expected:** display lights up. **Actual:** panel stays dark. Brightness keys do not recover it. ## Observed: max_brightness differs between the two kernels Measured on this machine: | Configuration | `max_brightness` | Resume | |-------------------------------------------|------------------|--------| | 7.0.0-27, stock cmdline | **1515** | works | | 7.0.0-28, stock cmdline | **1023** | backlight off | | 7.0.0-28 + `i915.enable_dpcd_backlight=0` | **1515** | works | `enable_dpcd_backlight` reads `-1` (the default) on 7.0.0-28 when the failure occurs. *Interpretation, not measured:* 1023 is 10-bit full scale and 1515 is not a power-of-two boundary, which suggests the two kernels are driving the backlight through different control paths, and that the parameter selects between them. I have not confirmed from the driver which path is active in either case. That inference rests only on the `max_brightness` values and on the parameter changing the outcome. ## The failure is silent No errors or warnings related to the failure appear in the journal for the affected boots. `PM: suspend exit` completes, and i915 and mei_hdcp rebind. Backlight sysfs during the failure, with the panel dark: ``` /sys/class/backlight/intel_backlight/brightness 1023 /sys/class/backlight/intel_backlight/actual_brightness 1023 /sys/class/backlight/intel_backlight/max_brightness 1023 /sys/class/backlight/intel_backlight/bl_power 0 ``` `/var/lib/systemd/backlight/pci-0000:00:02.0:backlight:intel_backlight` contained `1023`, so the saved brightness value was not lost or zeroed. ## Regression range `linux-image-generic-hwe-26.04` was upgraded 7.0.0-27.27 -> 7.0.0-28.28 on **2026-07-19 18:38 (UTC+1)**, unattended via packagekit (`Commandline: packagekit role='update-packages'` in `/var/log/apt/history.log`). 7.0.0-28 first booted 2026-07-22 15:14. The three-day gap is why the update was not initially suspected. From `journalctl --list-boots` and suspend entries per boot: | Kernel | Boots | Suspends | Outcome | |----------|-------|----------|------------------------------------------| | 7.0.0-27 | 2 | 63 | boots lasted days, spanning many resumes | | 7.0.0-28 | 3 | 4 | restart 39s to 2min after first resume | The short sessions on 7.0.0-28 end because the machine was rebooted blind at a dark screen. ## Workaround Add to `GRUB_CMDLINE_LINUX_DEFAULT` in `/etc/default/grub`, then `update-grub`: ``` i915.enable_dpcd_backlight=0 ``` `max_brightness` returns to 1515 and resume works. Confirmed working after this change. I have not yet run an extended soak of many suspend cycles. ## Checked and excluded - **Not `systemd-backlight` save/restore:** the saved value was intact and sysfs read back at maximum while the panel was dark. - **Not local misconfiguration:** no i915 module parameters set, no backlight-related files in `/etc/modprobe.d`, and the cmdline was stock `quiet splash` before the workaround was added. - **A userspace resume hook did not help:** an `/etc/systemd/system-sleep/` hook that cycled `bl_power` 4 to 0 and rewrote `brightness` on resume did not light the panel. Caveat: I did not independently confirm the hook executed on resume, so this is weaker evidence than the rest of this report. ## Not verified Listing these so they are not read into the report: - Which backlight control path the driver actually selects in either kernel. - The specific upstream commit responsible. I did not bisect, and the shipped `linux-image-7.0.0-28-generic` changelog contains only packaging entries, so I could not identify a candidate change from the package itself. ## Possibly related prior art There is a history of this general symptom with DPCD/AUX backlight on i915. A commit adding a heuristic to choose automatically between AUX and PWM brightness control was reverted upstream after reportedly causing "enabling DPCD backlight leads to a black screen after suspend/resume": https://www.mail-archive.com/intel- gfx@lists.freedesktop.org/msg126115.html That report concerns different and much older hardware (a ThinkPad X1 Carbon 4th Gen and BXT-P), and predates this kernel by many releases. I offer it only as a pointer to a known failure mode in this area, not as a claim about the cause here. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sam 3370 F.... pipewire sam 3389 F.... wireplumber /dev/snd/pcmC0D0p: sam 3370 F...m pipewire /dev/snd/seq: sam 3370 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Jul 22 22:51:57 2026 InstallationDate: Installed on 2026-02-13 (159 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: LENOVO 20L6S0MD00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-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 i915.enable_dpcd_backlight=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-09 (13 days ago) 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: 20L6S0MD00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 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:pn20L6S0MD00:pvrThinkPadT480:rvnLENOVO:rn20L6S0MD00:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S0MD00 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/2161575/+subscriptions

[Bug 2161770] Re: Regression: internal eDP blank after suspend with 7.0.0-28-generic

[Bug 2161780] Re: i915: eDP backlight dead after resume from suspend on Skylake (7.0.0-28 regression)

[Bug 2048183] Re: Don't produce linux--cloud-tools-common, linux--tools-common and linux-*-tools-host binary packages

This bug is awaiting verification that the linux-hwe-6.17/6.17.0-42.42 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-hwe-6.17' to 'verification-done- noble-linux-hwe-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-hwe-6.17' to 'verification-failed- noble-linux-hwe-6.17'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-hwe-6.17-v2 verification-needed-noble-linux-hwe-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/2048183 Title: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages Status in linux package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-iot package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-lowlatency-hwe-5.15 package in Ubuntu: New Status in linux-nvidia package in Ubuntu: New Status in linux-nvidia-6.8 package in Ubuntu: Invalid Status in linux-nvidia-lowlatency package in Ubuntu: Invalid Status in linux-nvidia-tegra package in Ubuntu: Fix Released Status in linux-nvidia-tegra-5.15 package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-xilinx package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Status in linux-hwe-5.15 source package in Focal: New Status in linux-ibm source package in Focal: New Status in linux-intel-iotg-5.15 source package in Focal: New Status in linux-iot source package in Focal: New Status in linux-lowlatency-hwe-5.15 source package in Focal: New Status in linux-hwe-6.5 source package in Jammy: New Status in linux-ibm source package in Jammy: New Status in linux-intel-iotg source package in Jammy: New Status in linux-lowlatency source package in Jammy: New Status in linux-nvidia source package in Jammy: Fix Released Status in linux-nvidia-6.5 source package in Jammy: New Status in linux-nvidia-6.8 source package in Jammy: Fix Released Status in linux-realtime source package in Jammy: New Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Status in linux-ibm source package in Noble: Fix Released Status in linux-lowlatency source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Fix Released Status in linux-nvidia-lowlatency source package in Noble: Fix Released Bug description: [Impact] Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common and/or linux-*-tools-host binary deb packages. That is all wrong, only the primary/main linux source package should produce these. These packages result in install failures of the regular linux-cloud-tools- common, linux-tools-common and linux-tools-host packages. [Test Case] Check list of built binary packages in LP and verify the packages are not built. [Where Problems Could Occur] Already installed packages won't upgrade and become stale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+subscriptions

[Bug 2081030] Re: Clean up packaging bits

пятница

[Bug 2161004] Re: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds

** Changed in: linux (Ubuntu Stonking) Status: Fix Released => 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/2161004 Title: [SRU] HPE: Fix for UBSAN array-index-out-of-bounds Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Resolute: Fix Released Status in linux source package in Stonking: Fix Committed Bug description: [ Impact ] When UBSAN is enabled, multiple array-index-out-of-bounds messages are printed: [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:276:23 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:277:32 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.000000] [ T0] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:282:16 [ 0.000000] [ T0] index 1 is out of range for type '<unknown> [1]' ... [ 0.515850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1344:23 [ 0.519851] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.603850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1345:32 [ 0.607850] [ T1] index 1 is out of range for type '<unknown> [1]' ... [ 0.691850] [ T1] UBSAN: array-index-out-of-bounds in arch/x86/kernel/apic/x2apic_uv_x.c:1353:20 [ 0.695850] [ T1] index 1 is out of range for type '<unknown> [1]' One-element arrays have been deprecated: [ Fix ] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21433d3e3ca14d20f9b0c2237b3d3a1355af7907 [ Test Plan ] [ Where problems could occur ] [ Other Info ] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/ubsan_array_index To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161004/+subscriptions

[Bug 2161739] Re: Backlight brightness no longer works on Fujitsu LIFEBOOK P727 with Intel HD 620 after upgrading to Linux 7.0.0-28

Additional regression testing: Booted Linux 7.0.0-28-generic → brightness keys and KDE brightness slider do not change the LCD backlight. Writing to /sys/class/backlight/intel_backlight/brightness changes both brightness and actual_brightness, but the physical display brightness does not change. Rebooted into 7.0.0-27-generic on the same installation. Brightness keys, KDE brightness slider, and hardware backlight all work normally. This appears to be a regression introduced between 7.0.0-27 and 7.0.0-28. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161739 Title: Backlight brightness no longer works on Fujitsu LIFEBOOK P727 with Intel HD 620 after upgrading to Linux 7.0.0-28 Status in linux package in Ubuntu: New Bug description: After upgrading from Linux 7.0.0-27 to 7.0.0-28, the LCD backlight can no longer be adjusted. Laptop: Fujitsu LIFEBOOK P727 GPU: Intel HD Graphics 620 (Kaby Lake-U) Kubuntu 26.04 LTS /sys/class/backlight/intel_backlight/brightness and actual_brightness both change correctly. The physical display brightness never changes. KDE brightness slider and keyboard brightness keys also stop working. Booting back into Linux 7.0.0-27 immediately restores correct brightness control. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: irfan 1619 F.... wireplumber /dev/snd/seq: irfan 1612 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jul 24 19:38:24 2026 InstallationDate: Installed on 2025-11-19 (247 days ago) InstallationMedia: Kubuntu 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911) MachineType: FUJITSU LIFEBOOK P727 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=5fd1e762-85e1-40ff-98a2-4cd01ee9a8ab ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-06 (48 days ago) dmi.bios.date: 02/10/2025 dmi.bios.release: 1.29 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.29 dmi.board.name: FJNB2A9 dmi.board.vendor: FUJITSU dmi.board.version: G3 dmi.chassis.asset.tag: 3000000989 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P727 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.29:bd02/10/2025:br1.29:svnFUJITSU:pnLIFEBOOKP727:pvr10601736746:rvnFUJITSU:rnFJNB2A9:rvrG3:cvnFUJITSU:ct31:cvrLIFEBOOKP727:skuSK01:pfaLIFEBOOK-FTS: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK P727 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161739/+subscriptions

[Bug 2161739] [NEW] Backlight brightness no longer works on Fujitsu LIFEBOOK P727 with Intel HD 620 after upgrading to Linux 7.0.0-28

Public bug reported: After upgrading from Linux 7.0.0-27 to 7.0.0-28, the LCD backlight can no longer be adjusted. Laptop: Fujitsu LIFEBOOK P727 GPU: Intel HD Graphics 620 (Kaby Lake-U) Kubuntu 26.04 LTS /sys/class/backlight/intel_backlight/brightness and actual_brightness both change correctly. The physical display brightness never changes. KDE brightness slider and keyboard brightness keys also stop working. Booting back into Linux 7.0.0-27 immediately restores correct brightness control. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: irfan 1619 F.... wireplumber /dev/snd/seq: irfan 1612 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jul 24 19:38:24 2026 InstallationDate: Installed on 2025-11-19 (247 days ago) InstallationMedia: Kubuntu 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911) MachineType: FUJITSU LIFEBOOK P727 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=5fd1e762-85e1-40ff-98a2-4cd01ee9a8ab ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-06 (48 days ago) dmi.bios.date: 02/10/2025 dmi.bios.release: 1.29 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.29 dmi.board.name: FJNB2A9 dmi.board.vendor: FUJITSU dmi.board.version: G3 dmi.chassis.asset.tag: 3000000989 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P727 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.29:bd02/10/2025:br1.29:svnFUJITSU:pnLIFEBOOKP727:pvr10601736746:rvnFUJITSU:rnFJNB2A9:rvrG3:cvnFUJITSU:ct31:cvrLIFEBOOKP727:skuSK01:pfaLIFEBOOK-FTS: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK P727 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU ** 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/2161739 Title: Backlight brightness no longer works on Fujitsu LIFEBOOK P727 with Intel HD 620 after upgrading to Linux 7.0.0-28 Status in linux package in Ubuntu: New Bug description: After upgrading from Linux 7.0.0-27 to 7.0.0-28, the LCD backlight can no longer be adjusted. Laptop: Fujitsu LIFEBOOK P727 GPU: Intel HD Graphics 620 (Kaby Lake-U) Kubuntu 26.04 LTS /sys/class/backlight/intel_backlight/brightness and actual_brightness both change correctly. The physical display brightness never changes. KDE brightness slider and keyboard brightness keys also stop working. Booting back into Linux 7.0.0-27 immediately restores correct brightness control. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: irfan 1619 F.... wireplumber /dev/snd/seq: irfan 1612 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jul 24 19:38:24 2026 InstallationDate: Installed on 2025-11-19 (247 days ago) InstallationMedia: Kubuntu 22.04.5 LTS "Jammy Jellyfish" - Release amd64 (20240911) MachineType: FUJITSU LIFEBOOK P727 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=5fd1e762-85e1-40ff-98a2-4cd01ee9a8ab ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-06 (48 days ago) dmi.bios.date: 02/10/2025 dmi.bios.release: 1.29 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.29 dmi.board.name: FJNB2A9 dmi.board.vendor: FUJITSU dmi.board.version: G3 dmi.chassis.asset.tag: 3000000989 dmi.chassis.type: 31 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P727 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.29:bd02/10/2025:br1.29:svnFUJITSU:pnLIFEBOOKP727:pvr10601736746:rvnFUJITSU:rnFJNB2A9:rvrG3:cvnFUJITSU:ct31:cvrLIFEBOOKP727:skuSK01:pfaLIFEBOOK-FTS: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK P727 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161739/+subscriptions

[Bug 2161495] Re: Dell Lattitude 7400 + 7.0.0-28-generic

Amazing. Thanks Krystian. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161495 Title: Dell Lattitude 7400 + 7.0.0-28-generic Status in linux package in Ubuntu: In Progress Bug description: Hello. Running a Dell Latitude 7400. Internal display becomes dim when kernel 7.0.0-28-generic loads, despite backlight being at 100%. Kernel 7.0.0-14-generic works normally. Regression appeared after the first apt upgrade. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: cavalier 3993 F.... wireplumber /dev/snd/seq: cavalier 3976 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:52:29 2026 InstallationDate: Installed on 2026-07-22 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Latitude 7400 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=/vmlinuz-7.0.0-14-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: 03/06/2025 dmi.bios.release: 1.39 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.39.0 dmi.board.name: 07WDVW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.39.0:bd03/06/2025:br1.39:svnDellInc.:pnLatitude7400:pvr:rvnDellInc.:rn07WDVW:rvrA01:cvnDellInc.:ct10:cvr:sku08E1:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7400 dmi.product.sku: 08E1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161495/+subscriptions

[Bug 2161309] Re: Backlight regression

** Also affects: linux-hwe-7.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-7.0 (Ubuntu) Status: New => In Progress ** Changed in: linux-hwe-7.0 (Ubuntu) Importance: Undecided => High ** Changed in: linux-hwe-7.0 (Ubuntu) Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) -- 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: In Progress Status in linux-hwe-7.0 package in Ubuntu: In Progress Bug description: 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