[Bug 2161223] DpkgList.txt

apport information ** Attachment added: "DpkgList.txt" https://bugs.launchpad.net/bugs/2161223/+attachment/5984645/+files/DpkgList.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161223 Title: Touchpad (ELAN0718) not working on HP Pavilion Gaming Laptop 15 with kernel 7.0.0 (Ubuntu 26.04) Status in linux package in Ubuntu: Incomplete Bug description: HP Pavilion Gaming Laptop 15 (Ryzen 5 4600H, AMD Raven/Picasso platform) Touchpad ACPI ID: ELAN0718 (I2C HID device), also enumerated as legacy PS/2 (ETPS/2 Elantech) via psmouse psmouse/elantech driver loads without errors and creates input device, but produces zero events (confirmed via evtest and raw /dev/input/eventX read) ACPI device ELAN0718:01 exists on i2c bus (i2c-ELAN0718:01) but has no driver bound, i2c_hid_acpi shows 0 usage No physical I2C controller PCI device found matching this bus (only i2c_piix4 SMBus for RAM SPD) Touchpad works fine under Windows on same hardware Tested: i8042 params, psmouse.elantech_smbus=0, manual driver bind attempts — none resolved it Kernel: 7.0.0-28-generic, Ubuntu 26.04 "resolute" --- ProblemType: Bug ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: n7 2083 F.... wireplumber /dev/snd/controlC0: n7 2083 F.... wireplumber /dev/snd/seq: n7 2061 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-07-18 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=2c0e3d76-a9b9-4ca3-a4bb-edc2abae6c60 ro quiet splash i8042.reset i8042.nomux i8042.nopnp ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Tags: resolute wayland-session Uname: Linux 7.0.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users _MarkForUpload: True dmi.bios.date: 03/03/2022 dmi.bios.release: 15.13 dmi.bios.vendor: AMI dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86D5 dmi.board.vendor: HP dmi.board.version: 96.45 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.45 dmi.modalias: dmi:bvnAMI:bvrF.13:bd03/03/2022:br15.13:efr96.45:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D5:rvr96.45:cvnHP:ct10:cvrChassisVersion:sku8UD79EA#AB8:pfa103C_5335KVHPPavilion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx dmi.product.sku: 8UD79EA#AB8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161223/+subscriptions

[Bug 2160752] Re: uvcvideo: unkillable deadlock in status-event/PM path wedges USB stack (RealSense D405)

** Changed in: linux (Ubuntu Resolute) Status: Triaged => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160752 Title: uvcvideo: unkillable deadlock in status-event/PM path wedges USB stack (RealSense D405) Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: # uvcvideo: unkillable deadlock in status-event / PM path (kernel 7.0) Draft for: Launchpad (`ubuntu-bug linux`, tag `regression-update`) and linux-media@vger.kernel.org (CC uvcvideo maintainer + granular-PM series author). Status: draft, 2026-07-15. Traces: `uvcvideo-deadlock-traces.txt` (same directory). ## Summary Control access to an Intel RealSense D405 (USB 8086:0b5b) reliably wedges the whole USB host stack on Ubuntu kernel 7.0.0-27-generic (also present, by code inspection, in upstream v7.0.6 and current mainline). The triggering process enters uninterruptible sleep (unkillable, survives SIGKILL), and the device's USB disconnect path then deadlocks the hub workqueue (`usb_hub_wq` in D state), after which no device on that hub can enumerate. Only a reboot recovers. ## Root cause (source analysis, drivers/media/usb/uvc) `uvc_ctrl_set_handle()` takes a PM reference (`uvc_pm_get`) for a pending async control, released by `uvc_ctrl_clear_handle()` -> `uvc_pm_put()` when the control-change status event arrives. That release runs inside `uvc_ctrl_status_event()`, which is invoked from two contexts where dropping the LAST status user deadlocks: 1. From the async worker `uvc_ctrl_status_event_work()`: `uvc_pm_put` -> `uvc_status_put` (takes `status_lock`) -> `uvc_status_stop` -> `cancel_work_sync(&dev->async_ctrl.work)` — cancelling the work item it is currently executing in. Waits for itself forever, holding `status_lock`. 2. From `uvc_status_stop()` itself (the synchronous flush, `if (cancel_work_sync(&w->work)) uvc_ctrl_status_event(...)`): the same put chain then re-acquires `status_lock`, which the caller (`uvc_status_put`/`uvc_status_suspend`) already holds. Self-deadlock on a non-recursive mutex. Every subsequent open/ioctl blocks in `uvc_status_get()` on `status_lock` (observed hung tasks), and `uvc_status_unregister()` -> `uvc_status_suspend()` blocks the USB disconnect path, freezing the hub workqueue. ## Observed impact (hardware reproduction) - Machine: omen rig, Ubuntu resolute, kernel 7.0.0-27-generic, 2x Intel RealSense D405 + 1x D435 on the same bus. - One D405 unit hits the race nearly every time on XU control access (its firmware emits the status event at the fatal moment); the other unit survives identical commands. Reproduced via librealsense enumeration AND via minimal raw UVCIOC_CTRL_QUERY ioctls; also right after a clean boot. - Hung-task stacks captured in `uvcvideo-deadlock-traces.txt` show both sides: `uvc_v4l2_unlocked_ioctl -> uvc_status_get` blocked, and `Workqueue: events uvc_ctrl_status_event_work -> uvc_ctrl_status_event -> uvc_pm_put -> uvc_status_put -> uvc_status_stop` blocked. - No uvcvideo changes between Ubuntu 7.0.0-14 and -27 (changelog); not an Ubuntu-local regression. `uvc_status.c` identical in mainline as of 2026-07-15; no fix or report found on linux-media/patchwork. ## Suggested direction for a fix Dropping the pending-async-control PM reference must not synchronously stop the status URB from the event-delivery contexts. Options: defer the final `uvc_status_stop()` to a separate work item when called from the async worker (`current_work() == &dev->async_ctrl.work`), or drop the reference outside `status_lock` / outside the worker. The synchronous-flush path (2) additionally must not re-enter `uvc_status_put` under `status_lock`. ## Verification (2026-07-15, same machine) - Firmware dependence of the trigger: on camera FW 5.15.1.55 one D405 unit wedged nearly every XU control access and the other rarely; after updating both cameras to FW 5.17.3.10 the deadlock became DETERMINISTIC on both units (first control-change sequence wedges both cameras, reproduced immediately after a clean boot). Newer firmware appears to deliver the async control-change status event more reliably, hitting the race window every time. - Workaround validation: with the patched module (status endpoint never armed, see below), the identical control sequences complete with zero hangs across repeated apply/hammer cycles on both FW versions' event behavior. Side effect observed: async controls (AE/exposure) remain "pending" forever (GET returns EBUSY) since the confirmation event never arrives — consistent with uvc_ctrl_set_handle never being cleared, and benign for operation (SETs land; streaming unaffected). ## Local mitigation deployed on this machine Out-of-tree build of uvcvideo 7.0.0-27 with a `disable_status` module parameter that skips `uvc_status_init()` URB arming entirely (no status events -> no worker -> no deadlock; costs async control-change notifications and camera-button events). Installed under `/lib/modules/7.0.0-27-generic/updates/`, enabled via `/etc/modprobe.d/uvcvideo-rig.conf`. 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/controlC2: robocurve 5721 F.... wireplumber /dev/snd/controlC0: robocurve 5721 F.... wireplumber /dev/snd/controlC1: robocurve 5721 F.... wireplumber /dev/snd/seq: robocurve 5703 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 00:03:18 2026 InstallationDate: Installed on 2026-06-29 (16 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: HP OMEN by HP 45L Gaming Desktop GT22-3xxx ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1639853a-6154-4c17-954d-08761337d8ae 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: 11/13/2025 dmi.bios.release: 15.32 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.name: 8D2C dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 36.15 dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/13/2025:br15.32:efr36.15:svnHP:pnOMENbyHP45LGamingDesktopGT22-3xxx:pvr:rvnHP:rn8D2C:rvr00:cvnHP:ct3:cvr:skuB91WJAA#ABA:pfa103C_5331M5HPOMEN: dmi.product.family: 103C_5331M5 HP OMEN dmi.product.name: OMEN by HP 45L Gaming Desktop GT22-3xxx dmi.product.sku: B91WJAA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160752/+subscriptions

[Bug 2161093] Re: Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580

I would like to add some background information that may or may not be related to this issue. Since my very first Linux installation (about six months ago), I have always needed to boot with the kernel parameter: amdgpu.dc=0 Even before installing Linux, the installer would only start in Safe Graphics mode. Without amdgpu.dc=0, I can see the KDE neon splash screen during boot. Immediately after the splash screen disappears, the screen turns completely black, and the graphical desktop never appears. Because of this, I have been using the amdgpu.dc=0 kernel parameter ever since I started using Linux. I don't know whether this is related to the current kernel issue, but I thought this background information might be useful. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161093 Title: Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580 Status in linux package in Ubuntu: New Bug description: After installing the latest system updates on KDE neon, my system no longer boots into the graphical desktop when using kernel 7.0.0-28-generic. Hardware: - CPU: AMD Ryzen 5 1600 - GPU: AMD Radeon RX 580 8 GB (Polaris) Symptoms: - GRUB loads normally. - The boot logo is displayed. - After that the screen becomes completely black. - Ctrl+Alt+F1...F6 do not switch to a TTY. - Ctrl+Alt+Del reboots the computer. Booting the previous kernel (6.17.0-40-generic) on the same installation works normally. The issue started immediately after installing system updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161093/+subscriptions

[Bug 2161312] [NEW] System hangs on suspend (s2idle) with kernel 7.0.0-28-generic, works fine on 7.0.0-27

Public bug reported: Hello Here is a bug occurring on my laptop. The analysis is from claude code. I hope it is relevant & complete. Thanks for your help. Summary System hangs permanently when entering suspend (s2idle) on kernel 7.0.0-28-generic; requires a hard power-off to recover. The exact same hardware suspended and resumed reliably dozens of times over 8 days on kernel 7.0.0-27-generic. The regression appeared immediately after the machine booted 7.0.0-28 for the first time — first suspend attempt on the new kernel already failed, and it failed again on the next boot. Hardware Machine: Dell Inspiron 14 5425 CPU: AMD Ryzen 7 5825U with Radeon Graphics GPU: AMD/ATI Barcelo iGPU (integrated, PCI 04:00.0) BIOS: 1.19.0 (2024-09-10) Sleep mode: only s2idle is offered by the platform (/sys/power/mem_sleep → [s2idle], no deep/S3 option available) Software Ubuntu 25.10 (Questing Quokka), KDE Plasma 6.5, Wayland session (kwin_wayland) Working kernel: linux-image-7.0.0-27-generic (7.0.0-27.27) Broken kernel: linux-image-7.0.0-28-generic (7.0.0-28.28) Steps to reproduce Boot into 7.0.0-28-generic. Trigger suspend (via systemd Suspend action / closing lid / GUI power menu). System freezes during or immediately after suspend entry: keyboard backlight stays lit, no reaction to any key or the power button short-press, screen never turns back on. Only recovery is holding the power button for a hard shutdown. Expected behavior System suspends and resumes normally, as it did consistently on 7.0.0-27-generic. Actual behavior System never comes back from suspend. journalctl shows the boot ending abruptly right after suspend entry, with no PM: suspend exit line and no orderly shutdown sequence — consistent with a full system hang, not a clean poweroff. Evidence from journalctl Working kernel (7.0.0-27), representative sample out of ~40 successful cycles between 2026-07-09 and 2026-07-17: juil. 16 19:31:46 kernel: PM: suspend entry (s2idle) juil. 17 14:48:21 kernel: PM: suspend exit Failing kernel (7.0.0-28), first attempt, boot ends here with no further log lines at all: juil. 20 10:42:38 root[18433]: Dell wakeup sources disabled - ALL including dock disconnect juil. 20 10:42:38 systemd-sleep[18388]: Performing sleep operation 'suspend'... juil. 20 10:42:38 kernel: PM: suspend entry (s2idle) [-- nothing further; next boot is a cold boot, not a resume --] Failing kernel (7.0.0-28), second attempt on a fresh boot, same pattern: juil. 20 12:32:59 systemd-sleep[26074]: Performing sleep operation 'suspend'... juil. 20 12:32:59 kernel: PM: suspend entry (s2idle) [-- nothing further --] Both failing boots are followed by a fresh cold boot (new boot ID in journalctl --list-boots), confirming the machine was hard power-cycled rather than resuming. Workaround Pinning the system to linux-image-7.0.0-27-generic (apt-mark hold) restores reliable suspend/resume. Additional notes A local dell-suspend-fix.service (disables PCI/USB/BT/WMI wakeup sources before sleep, standard workaround for this laptop's dock/eSATA wake-on-disconnect quirk) is present and unchanged across both the working and failing kernel — ruling it out as the cause. Not the known 7.0.0-28.28 AMDGPU/HMM ROCm performance regression (that one is a slowdown in compute workloads, not a hang) — this appears to be a separate, undocumented issue in the same kernel build. 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 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 20 14:19:25 2026 InstallationDate: Installed on 2025-07-09 (376 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) IwDevWlp3s0Link: Not connected. MachineType: Dell Inc. Inspiron 14 5425 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=b239c123-a9a4-4924-bfc7-38c39f92e79b ro quiet splash acpi_backlight=native resume=UUID=871f8b5f-e842-4660-9c64-7661287c3695 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 (11 days ago) dmi.bios.date: 09/10/2024 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0J9C2M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.19.0 dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/10/2024:br1.19:svnDellInc.:pnInspiron145425:pvr1.19.0:rvnDellInc.:rn0J9C2M:rvrA00:cvnDellInc.:ct10:cvr1.19.0:sku0B46:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5425 dmi.product.sku: 0B46 dmi.product.version: 1.19.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161312 Title: System hangs on suspend (s2idle) with kernel 7.0.0-28-generic, works fine on 7.0.0-27 Status in linux package in Ubuntu: New Bug description: Hello Here is a bug occurring on my laptop. The analysis is from claude code. I hope it is relevant & complete. Thanks for your help. Summary System hangs permanently when entering suspend (s2idle) on kernel 7.0.0-28-generic; requires a hard power-off to recover. The exact same hardware suspended and resumed reliably dozens of times over 8 days on kernel 7.0.0-27-generic. The regression appeared immediately after the machine booted 7.0.0-28 for the first time — first suspend attempt on the new kernel already failed, and it failed again on the next boot. Hardware Machine: Dell Inspiron 14 5425 CPU: AMD Ryzen 7 5825U with Radeon Graphics GPU: AMD/ATI Barcelo iGPU (integrated, PCI 04:00.0) BIOS: 1.19.0 (2024-09-10) Sleep mode: only s2idle is offered by the platform (/sys/power/mem_sleep → [s2idle], no deep/S3 option available) Software Ubuntu 25.10 (Questing Quokka), KDE Plasma 6.5, Wayland session (kwin_wayland) Working kernel: linux-image-7.0.0-27-generic (7.0.0-27.27) Broken kernel: linux-image-7.0.0-28-generic (7.0.0-28.28) Steps to reproduce Boot into 7.0.0-28-generic. Trigger suspend (via systemd Suspend action / closing lid / GUI power menu). System freezes during or immediately after suspend entry: keyboard backlight stays lit, no reaction to any key or the power button short-press, screen never turns back on. Only recovery is holding the power button for a hard shutdown. Expected behavior System suspends and resumes normally, as it did consistently on 7.0.0-27-generic. Actual behavior System never comes back from suspend. journalctl shows the boot ending abruptly right after suspend entry, with no PM: suspend exit line and no orderly shutdown sequence — consistent with a full system hang, not a clean poweroff. Evidence from journalctl Working kernel (7.0.0-27), representative sample out of ~40 successful cycles between 2026-07-09 and 2026-07-17: juil. 16 19:31:46 kernel: PM: suspend entry (s2idle) juil. 17 14:48:21 kernel: PM: suspend exit Failing kernel (7.0.0-28), first attempt, boot ends here with no further log lines at all: juil. 20 10:42:38 root[18433]: Dell wakeup sources disabled - ALL including dock disconnect juil. 20 10:42:38 systemd-sleep[18388]: Performing sleep operation 'suspend'... juil. 20 10:42:38 kernel: PM: suspend entry (s2idle) [-- nothing further; next boot is a cold boot, not a resume --] Failing kernel (7.0.0-28), second attempt on a fresh boot, same pattern: juil. 20 12:32:59 systemd-sleep[26074]: Performing sleep operation 'suspend'... juil. 20 12:32:59 kernel: PM: suspend entry (s2idle) [-- nothing further --] Both failing boots are followed by a fresh cold boot (new boot ID in journalctl --list-boots), confirming the machine was hard power-cycled rather than resuming. Workaround Pinning the system to linux-image-7.0.0-27-generic (apt-mark hold) restores reliable suspend/resume. Additional notes A local dell-suspend-fix.service (disables PCI/USB/BT/WMI wakeup sources before sleep, standard workaround for this laptop's dock/eSATA wake-on-disconnect quirk) is present and unchanged across both the working and failing kernel — ruling it out as the cause. Not the known 7.0.0-28.28 AMDGPU/HMM ROCm performance regression (that one is a slowdown in compute workloads, not a hang) — this appears to be a separate, undocumented issue in the same kernel build. 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 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 20 14:19:25 2026 InstallationDate: Installed on 2025-07-09 (376 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) IwDevWlp3s0Link: Not connected. MachineType: Dell Inc. Inspiron 14 5425 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=b239c123-a9a4-4924-bfc7-38c39f92e79b ro quiet splash acpi_backlight=native resume=UUID=871f8b5f-e842-4660-9c64-7661287c3695 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 (11 days ago) dmi.bios.date: 09/10/2024 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0J9C2M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.19.0 dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd09/10/2024:br1.19:svnDellInc.:pnInspiron145425:pvr1.19.0:rvnDellInc.:rn0J9C2M:rvrA00:cvnDellInc.:ct10:cvr1.19.0:sku0B46:pfaInspiron: dmi.product.family: Inspiron dmi.product.name: Inspiron 14 5425 dmi.product.sku: 0B46 dmi.product.version: 1.19.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161312/+subscriptions

[Bug 2161309] Re: Backlight regression

To clarify - the bug is in .28 rather than .27 that was running when I ran the bug report. -- 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: New 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

[Bug 2161223] Re: Touchpad (ELAN0718) not working on HP Pavilion Gaming Laptop 15 with kernel 7.0.0 (Ubuntu 26.04)

Thank you for taking the time to report this issue and help improve Ubuntu. The information you provided is useful. To continue investigating the problem, we need a few additional details. Could you please provide the following? - Attach a complete `dmesg` log from a boot where the problem occurred, preferably after a fresh power cycle. - While running an affected Ubuntu kernel, run `apport-collect 2161223` in a terminal. This will add the diagnostic information directly to this report. I did a little digging and found out a potential workaround: https://bbs.archlinux.org/viewtopic.php?pid=1979370#p1979370, so maybe you could give it a try as another diagnostic step after getting the logs. Thanks! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161223 Title: Touchpad (ELAN0718) not working on HP Pavilion Gaming Laptop 15 with kernel 7.0.0 (Ubuntu 26.04) Status in linux package in Ubuntu: Incomplete Bug description: HP Pavilion Gaming Laptop 15 (Ryzen 5 4600H, AMD Raven/Picasso platform) Touchpad ACPI ID: ELAN0718 (I2C HID device), also enumerated as legacy PS/2 (ETPS/2 Elantech) via psmouse psmouse/elantech driver loads without errors and creates input device, but produces zero events (confirmed via evtest and raw /dev/input/eventX read) ACPI device ELAN0718:01 exists on i2c bus (i2c-ELAN0718:01) but has no driver bound, i2c_hid_acpi shows 0 usage No physical I2C controller PCI device found matching this bus (only i2c_piix4 SMBus for RAM SPD) Touchpad works fine under Windows on same hardware Tested: i8042 params, psmouse.elantech_smbus=0, manual driver bind attempts — none resolved it Kernel: 7.0.0-28-generic, Ubuntu 26.04 "resolute" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161223/+subscriptions

[Bug 2161223] Re: Touchpad (ELAN0718) not working on HP Pavilion Gaming Laptop 15 with kernel 7.0.0 (Ubuntu 26.04)

** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (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/2161223 Title: Touchpad (ELAN0718) not working on HP Pavilion Gaming Laptop 15 with kernel 7.0.0 (Ubuntu 26.04) Status in linux package in Ubuntu: Incomplete Bug description: HP Pavilion Gaming Laptop 15 (Ryzen 5 4600H, AMD Raven/Picasso platform) Touchpad ACPI ID: ELAN0718 (I2C HID device), also enumerated as legacy PS/2 (ETPS/2 Elantech) via psmouse psmouse/elantech driver loads without errors and creates input device, but produces zero events (confirmed via evtest and raw /dev/input/eventX read) ACPI device ELAN0718:01 exists on i2c bus (i2c-ELAN0718:01) but has no driver bound, i2c_hid_acpi shows 0 usage No physical I2C controller PCI device found matching this bus (only i2c_piix4 SMBus for RAM SPD) Touchpad works fine under Windows on same hardware Tested: i8042 params, psmouse.elantech_smbus=0, manual driver bind attempts — none resolved it Kernel: 7.0.0-28-generic, Ubuntu 26.04 "resolute" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161223/+subscriptions

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

Additional official distribution-config evidence for this existing report: I independently reached the same configuration question while comparing current x86_64 distribution kernel configs. I am adding the evidence here instead of opening a duplicate bug. The following official Ubuntu release configurations all contain: # CONFIG_MITIGATION_GDS is not set Observed releases: * Ubuntu 24.04 Noble HWE, 6.17.0-35-generic * Ubuntu 25.10 Questing, 6.17.0-40-generic * Ubuntu 26.04 Resolute, 7.0.0-27-generic The current Resolute configuration therefore shows that the setting persists on the 7.0 kernel line rather than being limited to one older HWE build. In a dependency-aware comparison, all 12 independent current x86_64 peer configuration sources with a known value enable CONFIG_MITIGATION_GDS. Ubuntu/Mint, Debian/Kali, and Alma/Rocky were each collapsed to one vote where they share an effective configuration source, so related distributions were not allowed to inflate the majority. One symbol-history detail may be useful when reviewing the policy. The older CONFIG_MITIGATION_GDS_FORCE=n only avoided force-disabling AVX on systems without suitable microcode. The newer CONFIG_MITIGATION_GDS=n is the top-level mitigation switch itself. Linux v7.0 describes the latter as a default-y option that enables mitigation for Gather Data Sampling: https://github.com/torvalds/linux/blob/v7.0/arch/x86/Kconfig#L2566-L2574 This comment does not add a new hardware reproduction; the original report already contains stronger machine-level evidence, including the result with gather_data_sampling=force. It only adds release persistence, cross-distribution context, and the distinction between the old FORCE option and the current top-level option. Could the Ubuntu kernel team confirm whether CONFIG_MITIGATION_GDS=n on the current Resolute kernel is intentional, and whether the older AVX compatibility rationale is intended to apply to this newer top-level switch? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154728 Title: GDS mitigation not enabled in Ubuntu kernel Status in linux package in Ubuntu: Confirmed Bug description: TL;DR: Gather Data Sampling (GDS) vulnerability is not being mitigated in Ubuntu kernel because the config option CONFIG_MITIGATION_GDS is not enabled. This option is necessary so the microcode mitigation be enabled. I have an Intel CPU, and GDS should be mitigated by microcode, but since this config option is not enabled, I don't know if it's because performance or other reason, the mitigation in the microcode doesn't work. I'm comparing with my other kernel, the Liquorix, which has this config option enabled. With it I got: cat /sys/devices/system/cpu/vulnerabilities/gather_data_sampling Mitigation: Microcode Also, with the same kernel I got: sudo rdmsr 291 -a [sudo: authenticate] Password: CPU 0: 0 CPU 1: 0 CPU 2: 0 CPU 3: 0 CPU 4: 0 CPU 5: 0 CPU 6: 0 CPU 7: 0 CPU 8: 0 CPU 9: 0 CPU 10: 0 CPU 11: 0 CPU 12: 0 CPU 13: 0 CPU 14: 0 CPU 15: 0 0 is the correct value accordingly the Intel documentation. Without this option, the result for the command is 10, which means the mitigation is not being applied. How can we change that so the mitigation be put in place? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154728/+subscriptions

[Bug 2161181] Re: [Regression] LUKS root passphrase rejected on kernel 7.0.0-28, works on 7.0.0-27

Also affects Ubuntu 26.04 on a Dell Latitude 5550. Root filesystem is a LUKS2 volume on an external Samsung 990 Pro NVMe connected through Thunderbolt 4. Kernel 7.0.0-27 boots correctly; 7.0.0-28 fails at systemd-cryptsetup after entering the correct passphrase. thunderbolt.host_reset=0 is present. Reinstalling the kernel and regenerating the dracut initramfs did not help. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161181 Title: [Regression] LUKS root passphrase rejected on kernel 7.0.0-28, works on 7.0.0-27 Status in linux package in Ubuntu: New Bug description: LUKS root volume fails to unlock with kernel 7.0.0-28-generic, but works with 7.0.0-27-generic. After upgrading from 7.0.0-27.27 to 7.0.0-28.28, the Plymouth LUKS prompt rejects the correct passphrase with: cryptsetup: ERROR: dm_crypt-0: cryptsetup failed, bad password or options? The same passphrase and the same LUKS2 volume work correctly when booting 7.0.0-27-generic and when opening the volume from an Ubuntu Live system using cryptsetup. I recreated the initramfs for 7.0.0-28-generic: sudo update-initramfs -c -k 7.0.0-28-generic sudo update-grub Both commands completed without errors, but the issue persists. Affected kernel: 7.0.0-28-generic Working kernel: 7.0.0-27-generic LUKS device: /dev/nvme0n1p3 LUKS version: LUKS2 The crypttab UUID matches the actual LUKS UUID. 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/controlC2: gpad 4459 F.... wireplumber /dev/snd/controlC1: gpad 4459 F.... wireplumber /dev/snd/controlC0: gpad 4459 F.... wireplumber /dev/snd/seq: gpad 4436 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 18 12:01:56 2026 InstallationDate: Installed on 2025-08-20 (332 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: SANTECH PCX0DX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-04 (44 days ago) dmi.bios.date: 05/20/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03TSAS dmi.board.asset.tag: Tag 12345 dmi.board.name: PCX0DX dmi.board.vendor: SANTECH dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SANTECH dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03TSAS:bd05/20/2020:br7.3:efr7.2:svnSANTECH:pnPCX0DX:pvrNotApplicable:rvnSANTECH:rnPCX0DX:rvrNotApplicable:cvnSANTECH:ct10:cvrN/A:skuNotApplicable:pfaNotApplicable: dmi.product.family: Not Applicable dmi.product.name: PCX0DX dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SANTECH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161181/+subscriptions

[Bug 2160975] Re: Regression: Bluetooth HFP profile broken on RTL8723BU (Boat Airdopes 280 ANC) in Ubuntu 26.04

Thanks. The WirePlumber log shows the HFP/SCO transport being set up with the MSBC codec and no error, so the failure is after SCO bring-up. To pin it down more, please can you do all of the following in one sitting (so the timestamps line up) and attach the results: 0. The log names the device "Boat Rockerz 525", but the report says "Boat Airdopes 280 ANC". Are these captures from the same headset? 1. CVSD test: in Settings > Sound (profile dropdown), pick the headset profile labelled "Headset Head Unit (HSP/HFP, codec CVSD)", then test speaker and mic. Does audio works in CVSD? 2. Link-level capture (needs root; note: this file contains Bluetooth MAC addresses): sudo btmon -w hci.btsnoop Leave it running, switch to HFP, try speaker + mic for ~10s, then Ctrl-C. 3. PipeWire debug across the same switch: wpctl set-log-level 4 journalctl --user -u pipewire -f > pw.log switch to HFP, try speaker + mic, Ctrl-C. Run wpctl set-log-level 0 afterwards to stop the logging. Attach hci.btsnoop and pw.log, and post the CVSD result + headset confirmation as a comment. The HFP/SCO datapath was changed a lot between your affected versions upstream. ** Changed in: pipewire (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/2160975 Title: Regression: Bluetooth HFP profile broken on RTL8723BU (Boat Airdopes 280 ANC) in Ubuntu 26.04 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Status in pipewire package in Ubuntu: Incomplete Bug description: Summary Bluetooth HFP/HSP profile is broken on Ubuntu 26.04. Hardware Computer: Intel 2nd Generation Core platform Bluetooth controller: Realtek RTL8723BU Headset: Boat Airdopes 280 ANC Problem A2DP playback works correctly. When switching to the Hands-Free Profile (HFP/HSP): - Speaker stops working. - Microphone stops working. - Audio applications cannot use the headset for calls. Expected result Speaker and microphone should both work in HFP mode. Actual result Both speaker and microphone stop functioning after switching to HFP. Regression testing Windows: ✓ Speaker works ✓ Microphone works Ubuntu 25.04 Live USB: ✓ Speaker works ✓ Microphone works Ubuntu 26.04 Live USB: ✗ Speaker does not work in HFP ✗ Microphone does not work in HFP Ubuntu 26.04 fresh installation: Same issue. Additional information This issue is reproducible on a clean installation and also on the Ubuntu 26.04 Live USB, so it is not caused by user configuration. The issue does not occur on Ubuntu 25.04 using the same hardware. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: bluez 5.85-4ubuntu0.1 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 16:18:38 2026 InstallationDate: Installed on 2026-07-11 (5 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ZEBRONICS H61 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=913bbcc0-7ffa-4947-b9a7-bd0343f2b273 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2025 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: ZEBRONICS dmi.board.version: V1.3 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/21/2025:br4.6:svnZEBRONICS:pnH61:pvrTobefilledbyO.E.M.:rvnZEBRONICS:rnH61:rvrV1.3:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H61 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ZEBRONICS hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:1F:05:78:76:8B ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1494 acl:0 sco:0 events:163 errors:0 TX bytes:28311 acl:0 sco:0 commands:164 errors:0 modified.conffile..etc.bluetooth.main.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2160975/+subscriptions

[Bug 2161298] [NEW] Quirk in amdgpu driver for the Apple studio displays

Public bug reported: [ Impact ] During testing, we found problems with both the 2022 and 2026 Apple Studio displays on AMD platforms. We have a quirk that we are upstreaming that (ideally) should be brought into the OEM kernel. [ Fix ] Backport the following quirk: - drm/amd/display: hide Apple Studio Display secondary tile[1] [ Test ] 1. Boot into the kernel with the quirk. 2. Connect the Apple Studio monitor. It should function normally. [ Where the problems could occur ] This quirk matches those displays specifically, so it shouldn't take effects on other displays. That said, this quirk's dependencies make it very unlikely to bring it to 7.0-based kernel. See below. [ Additional information ] Backporting this cleanly depends on a massive file rearrangement patchset[2], which depends on various other patchsets (e.g. the HDMI FRL patchset[3]), making the backport unlikely to happen on 7.0-based kernels. That said, still open a public bug in case other users bump into this, and we can point them to this. The file arrangement patches will likely land in 7.3, and that'll be a more suitable timing to revisit this. [1] https://lore.kernel.org/amd-gfx/20260715134432.1975118-65-Wayne.Lin@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260610094639.1965367-12-chen-yu.chen@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260520202929.555119-1-harry.wentland@amd.com/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: [ Impact ] During testing, we found problems with both the 2022 and 2026 Apple Studio displays on AMD platforms. We have a quirk that we are upstreaming that (ideally) should be brought into the OEM kernel. - [ Fix ] Backport the following quirk: - drm/amd/display: hide Apple Studio Display secondary tile[1] - [ Test ] 1. Boot into the kernel with the quirk. 2. Connect the Apple Studio monitor. It should function normally. - [ Where the problems could occur ] This quirk matches those displays specifically, so it shouldn't take effects on other displays. That said, this quirk's dependencies make it very unlikely to bring it to 7.0-based kernel. See below. - [ Additional information ] Backporting this cleanly depends on a massive file rearrangement patchset[2], which depends on various other patchsets (e.g. the HDMI FRL - patchset[3]), making the backport unlikely to happens on 7.0-based + patchset[3]), making the backport unlikely to happen on 7.0-based kernels. That said, still open a public bug in case other users bump into this, and we can point them to this. The file arrangement patches will likely land in 7.3, and that'll be a more suitable timing to revisit this. [1] https://lore.kernel.org/amd-gfx/20260715134432.1975118-65-Wayne.Lin@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260610094639.1965367-12-chen-yu.chen@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260520202929.555119-1-harry.wentland@amd.com/ -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161298 Title: Quirk in amdgpu driver for the Apple studio displays Status in linux package in Ubuntu: New Bug description: [ Impact ] During testing, we found problems with both the 2022 and 2026 Apple Studio displays on AMD platforms. We have a quirk that we are upstreaming that (ideally) should be brought into the OEM kernel. [ Fix ] Backport the following quirk: - drm/amd/display: hide Apple Studio Display secondary tile[1] [ Test ] 1. Boot into the kernel with the quirk. 2. Connect the Apple Studio monitor. It should function normally. [ Where the problems could occur ] This quirk matches those displays specifically, so it shouldn't take effects on other displays. That said, this quirk's dependencies make it very unlikely to bring it to 7.0-based kernel. See below. [ Additional information ] Backporting this cleanly depends on a massive file rearrangement patchset[2], which depends on various other patchsets (e.g. the HDMI FRL patchset[3]), making the backport unlikely to happen on 7.0-based kernels. That said, still open a public bug in case other users bump into this, and we can point them to this. The file arrangement patches will likely land in 7.3, and that'll be a more suitable timing to revisit this. [1] https://lore.kernel.org/amd-gfx/20260715134432.1975118-65-Wayne.Lin@amd.com/ [2] https://lore.kernel.org/amd-gfx/20260610094639.1965367-12-chen-yu.chen@amd.com/ [3] https://lore.kernel.org/amd-gfx/20260520202929.555119-1-harry.wentland@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161298/+subscriptions

[Bug 2161234] Re: Touchpad Unusable and Random Screen Freeze After Installing Linux

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161234 Title: Touchpad Unusable and Random Screen Freeze After Installing Linux Status in linux package in Ubuntu: New Bug description: OS: Linux Mint 22.3 (based on Ubuntu 24.04 LTS) Kernel: 7.0.0-28-generic (Ubuntu HWE kernel) DE: Cinnamon Hardware: Laptop: LENOVO 21Q4 ThinkBook 14 G7+ ASP CPU: AMD Ryzen AI 9 H 365 w/ Radeon 880M (12 cores) GPU: AMD/ATI Device 150e (Radeon 880M iGPU) Touchpad: GXTP5100:00 27C6:01E9 (Goodix) The touchpad uses the I2C-HID protocol. Issue 1: Touchpad completely unresponsive Symptoms: The touchpad is detected by the system (xinput and dmesg show the device), but it does not respond to any touch or movement at the login screen and remains non-functional after login. This issue has occured when installing & using the OS. Issue 2: Random UI freezes Symptoms: After a random period (1 to 10 hours) of normal use, the UI freezes completely. The mouse cursor can still be moved using an external USB mouse, but clicking and keyboard shortcuts (e.g. Alt+F2) does not respond. Audio plays normally. Temporary Solution: Pressing Ctrl+Alt+Backspace to restart the UI session restores functionality temporarily. Steps to Reproduce: Install Linux Mint 22 (or any Ubuntu 24.04 based distro with kernel 6.8+, note that ALL kernels provided doesn't provide the solution to the problem). Boot into the system. The touchpad will not work from the login screen onwards. Use the system normally; the UI will freeze within 1-10 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161234/+subscriptions

[Bug 2161247] Re: linux kernel 7.0.0-28 purple kernel panic screen

Have you tried booting into the previous kernel, or is this a fresh install? ** 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/2161247 Title: linux kernel 7.0.0-28 purple kernel panic screen Status in linux package in Ubuntu: Incomplete Bug description: Won't boot. I get a purple kernel panic screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161247/+subscriptions