This patch is targeting 7.3-oem kernel, but the proper package page hasn't shown up on LP, so file it against the "linux" pcakage for now. Will target to 7.3-oem once it shows up. ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/2169534 + BugLink: [ Impact ] To enable NPU on Gorgon Halo, a new ID needs to be added to the revision list in the driver. Otherwise the amdxdna driver would show the following error message: [ 2.996014] test kernel: amdxdna 0000:c5:00.1: [drm] *ERROR* aie2_get_dev_revision: Unknown device revision: 9 (raw fuse: 0x10170) [ Fix ] - Cherry-pick the following patch to the 7.3-oem kernel: + Cherry-pick the following patch: - [PATCH V2] accel/amdxdna: Add support for AIE2 revision 9[1] - This patch is currently in the drm-misc tree commit - 63e91c1997898f32f68a5dbf68195d68b8e58443. + This patch is currently in the linux-next tree as commit + 63e91c1997898f32f68a5dbf68195d68b8e58443 since next-20260930 [ Test plan ] Boot the kernel. The driver should recognize the NPU, showing the following message instead: [ 3.130089] test kernel: [drm] Initialized amdxdna_accel_driver 0.10.0 for 0000:c5:00.1 on minor 0 [ Where problems could occur ] Unless there are conflicts in the IDs, this only makes the driver bind to a superset of already-supported hardware, so this shouldn't impact existing hardware support. [ Additional information ] [1] https://lore.kernel.org/dri- devel/20260929181459.928468-1-lizhi.hou@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/2169534 Title: [SRU] Fix NPU errors on Gorgon Halo Status in linux package in Ubuntu: New Bug description: BugLink: [ Impact ] To enable NPU on Gorgon Halo, a new ID needs to be added to the revision list in the driver. Otherwise the amdxdna driver would show the following error message: [ 2.996014] test kernel: amdxdna 0000:c5:00.1: [drm] *ERROR* aie2_get_dev_revision: Unknown device revision: 9 (raw fuse: 0x10170) [ Fix ] Cherry-pick the following patch: - [PATCH V2] accel/amdxdna: Add support for AIE2 revision 9[1] This patch is currently in the linux-next tree as commit 63e91c1997898f32f68a5dbf68195d68b8e58443 since next-20260930 [ Test plan ] Boot the kernel. The driver should recognize the NPU, showing the following message instead: [ 3.130089] test kernel: [drm] Initialized amdxdna_accel_driver 0.10.0 for 0000:c5:00.1 on minor 0 [ Where problems could occur ] Unless there are conflicts in the IDs, this only makes the driver bind to a superset of already-supported hardware, so this shouldn't impact existing hardware support. [ Additional information ] [1] https://lore.kernel.org/dri- devel/20260929181459.928468-1-lizhi.hou@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169534/+subscriptions
воскресенье
[Bug 2169534] [NEW] [SRU] Fix NPU errors on Gorgon Halo
Public bug reported: BugLink: [ Impact ] To enable NPU on Gorgon Halo, a new ID needs to be added to the revision list in the driver. Otherwise the amdxdna driver would show the following error message: [ 2.996014] test kernel: amdxdna 0000:c5:00.1: [drm] *ERROR* aie2_get_dev_revision: Unknown device revision: 9 (raw fuse: 0x10170) [ Fix ] Cherry-pick the following patch: - [PATCH V2] accel/amdxdna: Add support for AIE2 revision 9[1] This patch is currently in the linux-next tree as commit 63e91c1997898f32f68a5dbf68195d68b8e58443 since next-20260930 [ Test plan ] Boot the kernel. The driver should recognize the NPU, showing the following message instead: [ 3.130089] test kernel: [drm] Initialized amdxdna_accel_driver 0.10.0 for 0000:c5:00.1 on minor 0 [ Where problems could occur ] Unless there are conflicts in the IDs, this only makes the driver bind to a superset of already-supported hardware, so this shouldn't impact existing hardware support. [ Additional information ] [1] https://lore.kernel.org/dri- devel/20260929181459.928468-1-lizhi.hou@amd.com/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - BugLink: + BugLink: https://bugs.launchpad.net/bugs/2169534 [ Impact ] To enable NPU on Gorgon Halo, a new ID needs to be added to the revision list in the driver. Otherwise the amdxdna driver would show the following error message: [ 2.996014] test kernel: amdxdna 0000:c5:00.1: [drm] *ERROR* aie2_get_dev_revision: Unknown device revision: 9 (raw fuse: 0x10170) - [ Fix ] - Cherry-pick the following patch: + Cherry-pick the following patch to the 7.3-oem kernel: - [PATCH V2] accel/amdxdna: Add support for AIE2 revision 9[1] This patch is currently in the drm-misc tree commit 63e91c1997898f32f68a5dbf68195d68b8e58443. - [ Test plan ] Boot the kernel. The driver should recognize the NPU, showing the following message instead: [ 3.130089] test kernel: [drm] Initialized amdxdna_accel_driver 0.10.0 for 0000:c5:00.1 on minor 0 - [ Where problems could occur ] Unless there are conflicts in the IDs, this only makes the driver bind to a superset of already-supported hardware, so this shouldn't impact existing hardware support. - [ Additional information ] [1] https://lore.kernel.org/dri- devel/20260929181459.928468-1-lizhi.hou@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/2169534 Title: [SRU] Fix NPU errors on Gorgon Halo Status in linux package in Ubuntu: New Bug description: BugLink: [ Impact ] To enable NPU on Gorgon Halo, a new ID needs to be added to the revision list in the driver. Otherwise the amdxdna driver would show the following error message: [ 2.996014] test kernel: amdxdna 0000:c5:00.1: [drm] *ERROR* aie2_get_dev_revision: Unknown device revision: 9 (raw fuse: 0x10170) [ Fix ] Cherry-pick the following patch: - [PATCH V2] accel/amdxdna: Add support for AIE2 revision 9[1] This patch is currently in the linux-next tree as commit 63e91c1997898f32f68a5dbf68195d68b8e58443 since next-20260930 [ Test plan ] Boot the kernel. The driver should recognize the NPU, showing the following message instead: [ 3.130089] test kernel: [drm] Initialized amdxdna_accel_driver 0.10.0 for 0000:c5:00.1 on minor 0 [ Where problems could occur ] Unless there are conflicts in the IDs, this only makes the driver bind to a superset of already-supported hardware, so this shouldn't impact existing hardware support. [ Additional information ] [1] https://lore.kernel.org/dri- devel/20260929181459.928468-1-lizhi.hou@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169534/+subscriptions
[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060
I can also verify that the "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us" messages do not occur with the previous kernel version I had installed (7.0.0-31-generic), and the bug does not occur. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior: Random pixels/artifacts briefly flicker in the background from time to time. This issue was NOT present in kernel 7.0.0-34. The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 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: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181/+subscriptions
[Bug 2169505] Re: NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169505 Title: NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0 Status in linux package in Ubuntu: New Bug description: Dell XPS 15 9530, hybrid Intel Iris Xe + RTX 4070 Laptop (AD106M), Ubuntu 26.10, nvidia 615.71.09 (open, from the archive), GNOME/Wayland, PRIME on-demand, display on the iGPU. Same driver, same DKMS build, same config, only the kernel differs: 7.3.0-8-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Not supported Video Memory: Active power/runtime_status = active power/runtime_suspended_time = 0 (across full uptime, every boot) 7.0.0-38-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Enabled (fine-grained) Video Memory: Off power/runtime_status = suspended power/runtime_suspended_time = 24769 Every documented RTD3 requirement is satisfied on both kernels: - Ada GPU (newer than the Turing minimum) - CONFIG_PM=y, CONFIG_PCIE_PME=y - ACPI _PR3 present: \_SB_.PC00.PEG1.PG01 "New power resource"; power_resources_D3hot present on the parent bridge 0000:00:01.0 - d3cold_allowed=1 on bridge and GPU - NVreg_DynamicPowerManagement=0x02, set by Ubuntu's own /usr/lib/modprobe.d/nvidia-runtimepm.conf - no displays on the dGPU (no card2-* connectors) - platform ships a dedicated RTD3 ACPI table: ACPI: SSDT (v02 DELL DellRtd3 00001000 INTL 20200717) So on 7.3 the driver declines RTD3 on a platform that meets every requirement and that demonstrably works on 7.0. Impact: the dGPU is pinned in D0 permanently — constant idle power draw and heat on battery. Likely the same regression as CachyOS/linux-cachyos#1053, where 7.2.6 reported "Enabled (fine-grained)" and 7.3.0-rc3 reported "Not supported". That reporter believed it was CachyOS-specific; this reproduces on Ubuntu's own 7.3.0-8-generic, so it is not. Combining both data points puts the regression window at 7.2.6 -> 7.3.0-rc3. Not reproducible on 7.0.0-38-generic. I have no 7.1/7.2 kernels installed to narrow it further locally, but can test builds on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169505/+subscriptions
[Bug 2169490] Re: [Regression] snd_hda_intel fails to initialize on Intel 5-series (Ibex Peak) HDA: "CORB reset timeout#2, CORBRP = 65535" / "no codecs initialized" — works on 6.8.0-31, broken on 6.8.0-139
** 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/2169490 Title: [Regression] snd_hda_intel fails to initialize on Intel 5-series (Ibex Peak) HDA: "CORB reset timeout#2, CORBRP = 65535" / "no codecs initialized" — works on 6.8.0-31, broken on 6.8.0-139 Status in linux package in Ubuntu: New Bug description: ## Description After a kernel update within the 6.8.x series, the Intel onboard HDA audio controller stopped working: the snd_hda_intel driver fails to communicate with the codec at boot, so no sound card (other than the GPU HDMI audio) is exposed to ALSA, and PipeWire falls back to a "Dummy Output". This is a kernel regression, bisected upstream to commit: 4d4c10f763d7 "PCI: Explicitly put devices into D0 when initializing" which is tracked as an upstream regression on lists.linux.dev for the same hardware (Intel 5-series PCH "Ibex Peak" HDA controller 8086:3b56 + Realtek ALC269VB). See regressions@lists.linux.dev thread "[REGRESSION][BISECTED] HDA controller MMIO...". On these old chipsets, after this commit the HDA controller MMIO registers read 0xFFFF, causing CORB timeouts and codec enumeration failure. ## Hardware - Machine: [Acer model, e.g. Acer Aspire — DMI: `sudo dmidecode -s system-product-name`] - HDA controller: 00:1b.0 [8086:3b56] rev 05 (Intel 5 Series/3400 Series, Ibex Peak) - Codec: Realtek ALC269VB (Subsystem Id: 0x10250359) - GPU: AMD Radeon HD 5000 series (HDMI audio on card 1 works fine) - OS: Ubuntu 24.04 LTS, GNOME, PipeWire 1.0.5 ## Working / broken kernel versions - WORKS: 6.8.0-31-generic (original 24.04 kernel) - BROKEN: 6.8.0-139-generic (+several previous versions) - Also verified working on the same machine with Linux Mint / kernel 6.1.0-49-amd64 - Neither a cold boot (full shutdown, battery removed, several minutes) nor module options (probe_only=1, probe_mask=1, single_cmd=1, power_save=0) work around the issue. ## Steps to reproduce 1. Boot Ubuntu 24.04 with kernel >= 6.8.0-139 2. Run: aplay -l -> Only "card 1: HDMI [HDA ATI HDMI]" is listed; the analog HDA card is missing. 3. Run: wpctl status -> Only sink available: "Dummy Output". ## Relevant dmesg output [ 7.236527] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002) [ 7.238138] snd_hda_intel 0000:00:1b.0: number of I/O streams is 30, forcing separate stream tags [ 7.342564] snd_hda_intel 0000:00:1b.0: CORB reset timeout#2, CORBRP = 65535 [ 7.342733] hdaudio hdaudioC0D0: no AFG or MFG node found [ 7.342751] hdaudio hdaudioC0D1: no AFG or MFG node found [ 7.342763] hdaudio hdaudioC0D2: no AFG or MFG node found [ 7.342778] hdaudio hdaudioC0D3: no AFG or MFG node found [ 7.342781] snd_hda_intel 0000:00:1b.0: no codecs initialized ## Expected behavior The ALC269VB codec is enumerated and the analog sound card appears as "card 0: MID [HDA Intel MID], device 0: ALC269VB Analog", as it does with kernel 6.8.0-31 and with kernel 6.1.0-49-amd64 on the same machine. ## Additional context The upstream regression was bisected to commit 4d4c10f763d7 ("PCI: Explicitly put devices into D0 when initializing"), first appearing in v6.16 upstream and still present as of recent mainline rc kernels. If this commit (or its backport) was pulled into the Ubuntu 6.8.x stable updates, that would explain the breakage starting with 6.8.0-[xx]. A revert or a quirk for the 5-series HDA controller (8086:3b56) would restore audio for this hardware family. ## Workaround Staying on linux-image-unsigned-6.8.0-31-generic restores audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169490/+subscriptions
[Bug 2169181] Re: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060
I can reproduce this pretty easily by starting a game and switching workspaces (I use the desktop cube plugin if that matters). But it manifests in a multitude of different ways. Playing a video in my web browser will cause corruption. I've attached my (mildly censored) dmesg log as requested. There's some obvious clues at the end of it. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181/+attachment/6005723/+files/dmesg.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169181 Title: Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing intermittent pixel corruption and flickering artifacts in the background/desktop UI after updating to kernel version 7.0.0-38. Behavior: Random pixels/artifacts briefly flicker in the background from time to time. This issue was NOT present in kernel 7.0.0-34. The issue started immediately after updating to kernel 7.0.0-38. CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz GPU: AMD Radeon RX 9060 XT 16 GB[Discrete] P.S. I was planning to upgrade to the 26.10 beta this weekend, but I will stay on Resolute to help resolve this issue with any testing you might need. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:29:50 2026 InstallationDate: Installed on 2026-08-31 (31 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=1bdfa414-371c-4c93-9288-8cdc845cb610 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: 02/25/2026 dmi.bios.release: 38.41 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3841 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3841:bd02/25/2026:br38.41:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUSWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181/+subscriptions
[Bug 2169505] Re: NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0
** Package changed: compiz-plugins-main (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169505 Title: NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0 Status in linux package in Ubuntu: New Bug description: Dell XPS 15 9530, hybrid Intel Iris Xe + RTX 4070 Laptop (AD106M), Ubuntu 26.10, nvidia 615.71.09 (open, from the archive), GNOME/Wayland, PRIME on-demand, display on the iGPU. Same driver, same DKMS build, same config, only the kernel differs: 7.3.0-8-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Not supported Video Memory: Active power/runtime_status = active power/runtime_suspended_time = 0 (across full uptime, every boot) 7.0.0-38-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Enabled (fine-grained) Video Memory: Off power/runtime_status = suspended power/runtime_suspended_time = 24769 Every documented RTD3 requirement is satisfied on both kernels: - Ada GPU (newer than the Turing minimum) - CONFIG_PM=y, CONFIG_PCIE_PME=y - ACPI _PR3 present: \_SB_.PC00.PEG1.PG01 "New power resource"; power_resources_D3hot present on the parent bridge 0000:00:01.0 - d3cold_allowed=1 on bridge and GPU - NVreg_DynamicPowerManagement=0x02, set by Ubuntu's own /usr/lib/modprobe.d/nvidia-runtimepm.conf - no displays on the dGPU (no card2-* connectors) - platform ships a dedicated RTD3 ACPI table: ACPI: SSDT (v02 DELL DellRtd3 00001000 INTL 20200717) So on 7.3 the driver declines RTD3 on a platform that meets every requirement and that demonstrably works on 7.0. Impact: the dGPU is pinned in D0 permanently — constant idle power draw and heat on battery. Likely the same regression as CachyOS/linux-cachyos#1053, where 7.2.6 reported "Enabled (fine-grained)" and 7.3.0-rc3 reported "Not supported". That reporter believed it was CachyOS-specific; this reproduces on Ubuntu's own 7.3.0-8-generic, so it is not. Combining both data points puts the regression window at 7.2.6 -> 7.3.0-rc3. Not reproducible on 7.0.0-38-generic. I have no 7.1/7.2 kernels installed to narrow it further locally, but can test builds on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169505/+subscriptions
[Bug 2169505] [NEW] NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0
You have been subscribed to a public bug: Dell XPS 15 9530, hybrid Intel Iris Xe + RTX 4070 Laptop (AD106M), Ubuntu 26.10, nvidia 615.71.09 (open, from the archive), GNOME/Wayland, PRIME on-demand, display on the iGPU. Same driver, same DKMS build, same config, only the kernel differs: 7.3.0-8-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Not supported Video Memory: Active power/runtime_status = active power/runtime_suspended_time = 0 (across full uptime, every boot) 7.0.0-38-generic: /proc/driver/nvidia/gpus/0000:01:00.0/power Runtime D3 status: Enabled (fine-grained) Video Memory: Off power/runtime_status = suspended power/runtime_suspended_time = 24769 Every documented RTD3 requirement is satisfied on both kernels: - Ada GPU (newer than the Turing minimum) - CONFIG_PM=y, CONFIG_PCIE_PME=y - ACPI _PR3 present: \_SB_.PC00.PEG1.PG01 "New power resource"; power_resources_D3hot present on the parent bridge 0000:00:01.0 - d3cold_allowed=1 on bridge and GPU - NVreg_DynamicPowerManagement=0x02, set by Ubuntu's own /usr/lib/modprobe.d/nvidia-runtimepm.conf - no displays on the dGPU (no card2-* connectors) - platform ships a dedicated RTD3 ACPI table: ACPI: SSDT (v02 DELL DellRtd3 00001000 INTL 20200717) So on 7.3 the driver declines RTD3 on a platform that meets every requirement and that demonstrably works on 7.0. Impact: the dGPU is pinned in D0 permanently — constant idle power draw and heat on battery. Likely the same regression as CachyOS/linux-cachyos#1053, where 7.2.6 reported "Enabled (fine-grained)" and 7.3.0-rc3 reported "Not supported". That reporter believed it was CachyOS-specific; this reproduces on Ubuntu's own 7.3.0-8-generic, so it is not. Combining both data points puts the regression window at 7.2.6 -> 7.3.0-rc3. Not reproducible on 7.0.0-38-generic. I have no 7.1/7.2 kernels installed to narrow it further locally, but can test builds on request. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- NVIDIA dGPU never enters RTD3 on kernel 7.3.0; works on 7.0.0 https://bugs.launchpad.net/bugs/2169505 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2167549] Re: ThinkPad P1 Gen 7 Meteor Lake — i915 PHY/DPLL failure after s2idle resume
Relevant patch is included in 7.0.0-38 - drm/i915/mtl+: Enable PPS before PLL ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167549 Title: ThinkPad P1 Gen 7 Meteor Lake — i915 PHY/DPLL failure after s2idle resume Status in linux package in Ubuntu: Fix Released Bug description: After resuming from an s2idle suspend of 30+ minutes, the i915 driver fails to re-enable the display. According to logs, the C10 PHY becomes completely unresponsive because its internal registers are inaccessible and this causes the entire display pipeline to remain stuck, sometimes for ~60 seconds or sometimes indefinitely (requiring a hard reset). GNOME Shell and input handling remain functional throughout; keystrokes typed during the black screen appear in the password box if/when the display eventually recovers. Short-duration suspends (<~2 minutes) resume cleanly without errors. The failure apparently correlates with suspend duration: during long s2idle, the display power well fully shuts down, and on resume the C10 PHY cold-start sequence fails. The bug does NOT reproduce on Windows (on the same laptop), suggesting this is an i915 driver bug, not a hardware or BIOS issue. ## My setup - Laptop: Lenovo ThinkPad P1 Gen 7 (model 21KV0025UK) - BIOS: N48ET34W (1.21), dated 2026-05-11 (current; no LVFS updates available) - iGPU: Intel Meteor Lake-P [Intel Arc Graphics] — PCI 8086:7d55 (rev 08) - Kernel driver: i915 - Panel: eDP-1, 3840x2400 (16:10), 4 lanes, C10 PLL at 540 MHz port clock - dGPU: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] — PCI 10de:28a0 - Driver: nvidia 580.173.02 (open kernel module), nvidia-drm modeset=1 - NOTE: bug reproduces with and without nvidia loaded — not a factor - suspend mode: s2idle (platform supports only s2idle; no "deep"/S3 available) ## Software - OS: Ubuntu 24.04.5 LTS (Noble Numbat) - Kernel: 7.0.0-31-generic (#31~24.04.1-Ubuntu PREEMPT_DYNAMIC) (also reproduces on 7.0.0-30-generic) - Desktop: GNOME 46.0 on Wayland (GDM) - linux-firmware: 20240318.git3b128b60.0ubuntu3.1 - i915 firmware loaded: - DMC: i915/mtl_dmc.bin v2.21 - GuC: i915/mtl_guc_70.bin v70.36.0 (kernel recommends v70.53.0 but only 70.36.0 available — may or may not be related) - HuC: i915/mtl_huc_gsc.bin v8.5.4 ## To reproduce 1. Boot the system (any kernel 7.0.0-30 or 7.0.0-31) 2. Suspend (lid close or `systemctl suspend`) 3. Leave suspended for 30+ minutes (short suspends <2 min do NOT trigger it) 4. Resume (open lid / press key) 5. Observe: screen stays black for ~60 seconds (or never recovers and needs a hard reset) 6. Kernel log shows the error burst (see below) Suspend duration correlation: - Short suspends (1-2 min): 0 DRM errors, prompt in ~2s - Long suspends (30+ min): 19-97 DRM errors, 60s+ delay or hard reset ## What does NOT work I tried quite a few things, none of which succeeded: - Kernel update 7.0.0-30 → 7.0.0-31: no effect - i915.enable_psr=0 (PSR disabled): no effect - i915.enable_dc=0 (display C-states disabled): no effect - i915.enable_dsb=0 (Display State Buffer disabled): no effect (DSB timeouts disappeared from logs, but core PHY failure remained) - i915.disable_power_well=0 (keep power wells always on): no effect - NVIDIA driver loaded vs unloaded: no effect - nvidia_drm modeset=0 / modeset=1: no effect ## What DOES work - Hibernation: bypasses s2idle entirely (full boot from hibernation image re-initializes display from scratch). Zero DRM errors on resume. Confirmed working across multiple hibernate cycles. - Windows Modern Standby: does NOT reproduce the bug. ## What was NOT testable - xe driver: my laptop would not boot (apparently because the xe driver does not work in my kernel version. It refuses to probe even with xe.force_probe=7d55, requiring both xe.force_probe=7d55 AND i915.force_probe=!7d55. When loaded on 7.0.0-30, it registered only a generic card0-Unknown-1 connector with no eDP display output. Not a viable alternative without a newer kernel with proper MTL display support in xe. ## Root cause (from logs) On resume from long s2idle, the C10 PHY cold-start sequence fails at the hardware register level: 1. `Failed to bring PHY A to idle` PHY A cannot reach idle state 2. `PHY A Read 0c70 failed after 3 retries` PHY register 0c70 is completely inaccessible (returns no data) 3. `PHY A Write 0c70 failed after 3 retries` writes to the PHY also fail 4. `Timeout waiting for DDI BUF A to get active` DDI buffer never enables (depends on PHY being up) 5. `Timed out waiting for DP idle patterns` DP link training cannot proceed 6. C10 PLL state mismatch: expected clock 540000 (540 MHz), found 61440 (61.44 MHz = the idle/standby clock; PLL never re-enabled at full rate) All PLL registers found as 0x00 (zeroed/idle state) 7. `flip_done timed out` repeating every ~10s all atomic commits fail 8. `vblank wait timed out on crtc 0` pipe is dead, no vblanks The C10 PHY's control register interface (offset 0c70) is completely dead after long s2idle. No i915 kernel parameter that I tried can fix this. The PHY itself is in an inaccessible state. Since Windows handles the same hardware correctly, the i915 driver is missing a step in its PHY re-initialization sequence that the Windows Intel driver performs. From: journalctl -b 0 -k (With i915.enable_dc=0, i915.enable_dsb=0, i915.disable_power_well=0 all active) Code: Select all Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate (expected 572010, found 65082) Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* expected: Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 540000, fracen: yes, Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* quot: 40960, rem: 0, den: 1, multiplier: 140, tx_clk_div: 0. Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: tx: 0x10, cmn: 0x21 Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0xf4, pll[1] = 0x0, pll[2] = 0xf8, pll[3] = 0x0 Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[16] = 0x84, pll[17] = 0x4f, pll[18] = 0xe5, pll[19] = 0x23 Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* found: Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, multiplier: 16, tx_clk_div: 0. Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: tx: 0x0, cmn: 0x0 Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* pll[0-19] = 0x0 (all zeros) Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in hw.pipe_mode.crtc_clock (expected 572010, found 65082) Sep 14 13:06:35 kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in port_clock (expected 540000, found 61440) Sep 14 13:06:35 kernel: i915 0000:00.0: [drm] pipe state doesn't match! Sep 14 13:06:35 kernel: WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x51b/0x6c0 [i915] Sep 14 13:06:35 kernel: intel_modeset_verify_crtc+0x70/0xb0 [i915] Sep 14 13:06:35 kernel: intel_atomic_commit_tail+0x8bb/0xc80 [i915] Sep 14 13:06:35 kernel: intel_atomic_commit+0x2c0/0x310 [i915] Sep 14 13:06:35 kernel: drm_atomic_commit+0xaf/0xf0 Sep 14 13:06:35 kernel: WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state+0x6c7/0x7e0 [i915] Sep 14 13:06:35 kernel: intel_modeset_verify_crtc+0x7b/0xb0 [i915] (flip_done timeouts repeat every ~10s:) Sep 14 13:06:45 i915 *ERROR* flip_done timed out Sep 14 13:06:45 i915 *ERROR* [CRTC:150:pipe A] commit wait timed out Sep 14 13:06:55 i915 *ERROR* flip_done timed out Sep 14 13:06:55 i915 *ERROR* [CONNECTOR:507:eDP-1] commit wait timed out Sep 14 13:07:06 i915 *ERROR* flip_done timed out Sep 14 13:07:06 i915 *ERROR* [PLANE:34:plane 1A] commit wait timed out ... Sep 14 13:07:57 i915 *ERROR* [CRTC:150:pipe A] flip_done timed out Sep 14 13:07:58 i915: vblank wait timed out on crtc 0 Sep 14 13:07:58 WARNING: drivers/gpu/drm/drm_vblank.c:1320 at drm_crtc_wait_one_vblank+0x18c/0x200 Sep 14 13:07:58 drm_client_modeset_wait_for_vblank+0x61/0x80 Sep 14 13:07:58 drm_fb_helper_damage_work+0x8c/0x1a0 (PM: suspend exit at 13:07:57, ~90s after the first PHY error at 13:06:35) Sep 14 13:07:57 kernel: PM: suspend exit Seems like it needs a kernel patch in the i915 display PHY resume code (drivers/gpu/drm/i915/display/intel_cx0_phy.c or similar), potentially adding a forced PHY reset or an alternative re-initialization sequence for the post-s2idle cold-start case. ## Workaround Hibernation works. I had to fiddle around with swap space and resume paramters to make this work but then `systemctl hibernate` works reliably with zero DRM errors on resume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167549/+subscriptions
суббота
[Bug 2168920] Re: LTS update fails on mysql_native_password check
** Information type changed from Private Security to Public Security -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168920 Title: LTS update fails on mysql_native_password check Status in linux package in Ubuntu: New Bug description: LTS update suggests changing mysql_native_password to caching_sha2_password then fails. After setting default_authentication_plugin=caching_sha2_password AND changing old users to caching_sha2_password, flush privileges AND restarting mysql two mysql built in users remain stuck with mysql_native_password. Users mysql.session and mysql.sys which are locked by mysql, mysql documentation say they will migrate when mysql is updated. Unfortunately the LTS update is blocked because of the check fo any mysql user still on mysql_native_password.... Mysql and net searches provide no means of manually changing those to caching_sha2_password. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-142-generic 6.8.0-142.142 ProcVersionSignature: Ubuntu 6.8.0-142.142-generic 6.8.12 Uname: Linux 6.8.0-142-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: atuttle 3946 F.... wireplumber /dev/snd/controlC0: atuttle 3946 F.... wireplumber /dev/snd/seq: atuttle 3942 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 29 15:53:15 2026 HibernationDevice: RESUME=/dev/nvme0n1p3 InstallationDate: Installed on 2018-11-17 (2873 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lo no wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-142-generic root=UUID=01736369-094d-46a1-bdf5-ea9657dbb6ef ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-142-generic N/A linux-backports-modules-6.8.0-142-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to noble on 2026-09-29 (0 days ago) dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F67 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF67:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B450 MB dmi.product.name: B450 AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168920/+subscriptions
[Bug 2165873] Re: Bluetooth fails to initialize due to a kernel NULL pointer error
I'm no longer having this issue on build: 6.8.0-146-generic #146-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 3 16:12:30 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165873 Title: Bluetooth fails to initialize due to a kernel NULL pointer error Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: In Progress Bug description: SRU Justification [Impact] Bluetooth fails to start on HP systems with a MediaTek MT7922 controller (CID: 202401-33402) running 6.8.0-139.139~22.04.1. The kernel oopses during Bluetooth power-on. The worker thread dies, so hci0 stays in DOWN INIT and its BD address is all zeros. Bluetooth is unusable. rfkill unblock and hciconfig do not help. Error log: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231120183620 BUG: kernel NULL pointer dereference, address: 0000000000000219 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 9 PID: 340 Comm: kworker/u33:1 Not tainted 6.8.0-139-generic Workqueue: hci0 hci_power_on [bluetooth] RIP: 0010:__pm_runtime_resume+0x1b/0x80 Call Trace: <TASK> usb_autopm_get_interface+0x1d/0x60 btmtk_usb_hci_wmt_sync+0xb9/0x340 [btmtk] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] btusb_mtk_setup+0x2d6/0x610 [btusb] hci_dev_setup_sync+0x6c/0x440 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0x8b/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] Hits 3 out of 3 boots. 6.8.0-138.138~22.04.1 is fine. This breaks these checkbox tests: com.canonical.certification::bluetooth/detect-output com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 This is not limited to the reporting machine. Any MediaTek MT766x or MT79xx USB Bluetooth controller takes the same path and hits the same oops on 6.8.0-139. [Fix] 6.8.0-139 picked up d019930b0049 ("Bluetooth: btmtk: move btusb_mtk_hci_wmt_sync to btmtk.c", v6.11) as a stable dependency of the urb->setup_packet leak fix. That commit moves the WMT command path into btmtk.c, where it reads intf, udev and ctrl_anchor out of struct btmtk_data. The commit that fills those three fields in is the next one in the same upstream series, and it was not picked: 5c5e8c52e3ca Bluetooth: btmtk: move btusb_mtk_[setup, shutdown] to btmtk.c (v6.11) So the pointers stay NULL. The first WMT command calls usb_autopm_get_interface(NULL) and oopses. The fix is to backport 5c5e8c52e3ca so the series is complete again. It adds the missing assignments in btusb_mtk_setup(): btmtk_data->drv_name = btusb_driver.name; btmtk_data->intf = data->intf; btmtk_data->udev = data->udev; btmtk_data->ctrl_anchor = &data->ctrl_anchor; btmtk_data->reset_sync = btusb_mtk_reset; udev and ctrl_anchor are just as NULL as intf, and are used by the WMT receive URB, so all of them are needed. A NULL check on intf alone would only move the oops. [Test Plan] On a machine with a MediaTek MT7922 Bluetooth controller. Boot the machine, then check for the oops: $ dmesg | grep -A20 'NULL pointer' $ journalctl -b -0 -k | grep btmtk Check the controller came up: $ sudo rfkill unblock bluetooth $ hciconfig -a $ hcitool dev Without patch: dmesg shows the NULL pointer oops in __pm_runtime_resume with btmtk_usb_hci_wmt_sync in the call trace. hciconfig shows hci0 DOWN INIT with BD Address 00:00:00:00:00:00. hcitool dev lists no device. With patch: no oops in dmesg. hciconfig shows hci0 UP RUNNING with a real BD address. hcitool dev lists hci0. Then run the two failing tests: $ checkbox-cli run com.canonical.certification::bluetooth/detect-output $ checkbox-cli run com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 Both pass with the patch, both fail without it. [Where problems could occur] Could break the btusb and btmtk drivers for all MediaTek Bluetooth controllers. This is not a small patch. It moves btusb_mtk_setup() and btusb_mtk_shutdown() and their helpers out of btusb.c into btmtk.c, so the whole MediaTek setup path is touched. If the move dropped or changed something, MediaTek Bluetooth would fail to set up. That would show up as "Failed to set up firmware" or "Failed to send wmt func ctrl" in dmesg, or as a timeout during hci0 power-on, and Bluetooth would stay down. The device reset path also moves (btusb_mtk_subsys_reset becomes btmtk_usb_subsys_reset). If that is wrong, chip recovery after a firmware crash would fail and the controller would need a reboot to come back. Nothing outside drivers/bluetooth is touched. Other Bluetooth vendors (Intel, Realtek, Qualcomm, Broadcom) are not affected, because btusb only calls this code for MediaTek devices. [Other Info] The patch is upstream in v6.11. It is the second half of a two-commit series; the first half is already in 6.8.0-139, which is what caused the regression. The backport needed manual conflict resolution in drivers/bluetooth/btusb.c. 6.8 is missing the intermediate commits that added fw_flavor handling and the BTMTK_FIRMWARE_LOADED flag, so the old copies of btusb_mtk_func_query(), btusb_mtk_uhw_reg_*(), btusb_mtk_reg_read(), btusb_mtk_id_get(), btusb_mtk_reset_done(), btusb_mtk_subsys_reset() and the open-coded btusb_mtk_setup() body all conflicted. Those are exactly the functions this commit deletes, so the upstream side was taken. The resulting btusb_mtk_setup() is identical to upstream at 5c5e8c52e3ca. =========================== The Bluetooth controller fails to initialize on kernel 6.8.0-139.139~22.04.1. During hci_power_on, the MediaTek btmtk driver hits a kernel NULL pointer dereference, the handling kworker dies with IRQs disabled, and hci0 is left stuck in DOWN INIT with an all-zero BD address. The previous kernel 6.8.0-138.138~22.04.1 is unaffected, with identical linux-firmware(20220329.git681281e4-0ubuntu3.42) and bluez(5.64-0ubuntu1.4), this seems to be a kernel regression. This failure affects the following checkbox tests: - com.canonical.certification::bluetooth/detect-output - com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 Machines: - https://certification.canonical.com/hardware/202401-33402/ Steps to reproduce: 1. Boot the machine with kernel 6.8.0-139.139~22.04.1. 2. Checkbox dmesg for crash, null pointer appears in btmtk_usb_hci_wmt_sync during hci power on. 3. run `sudo rfkill unblock bluetooth; hciconfig -a; hcitool dev` to check the controller state. 4. reboot into 6.8.0-138.138~22.04.1 and repeat steps 2-3. Fail rate: 3/3 on 6.8.0.139 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-139.139~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1307 F.... pulseaudio /dev/snd/controlC0: ubuntu 1307 F.... pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail Date: Mon Aug 31 13:19:26 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20240408-800 InstallationDate: Installed on 2026-08-28 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20240408-800 MachineType: HP HP ZBook Power 16 inch G11 A Mobile Workstation PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=6006e56e-4c1e-49e1-8a56-4c55eea6d70d ro automatic-oem-config quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.42 SourcePackage: linux-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W85 Ver. 01.01.01 dmi.board.name: 8C95 dmi.board.vendor: HP dmi.board.version: KBC Version 08.40.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 8.64 dmi.modalias: dmi:bvnHP:bvrW85Ver.01.01.01:bd03/21/2024:br1.1:efr8.64:svnHP:pnHPZBookPower16inchG11AMobileWorkstationPC:pvrSBKPF:rvnHP:rn8C95:rvrKBCVersion08.40.00:cvnHP:ct10:cvr:skuXW8SKU3#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 16 inch G11 A Mobile Workstation PC dmi.product.sku: XW8SKU3#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165873/+subscriptions
[Bug 2169402] Re: Kernel 7.0.0-38 regression: screen corruption flashes on RX 7600 XT (Wayland, VRR), 7.0.0-34 unaffected
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/2169402 Title: Kernel 7.0.0-38 regression: screen corruption flashes on RX 7600 XT (Wayland, VRR), 7.0.0-34 unaffected Status in linux package in Ubuntu: Confirmed Bug description: After the update from 7.0.0-34-generic to 7.0.0-38-generic (Oct 2, 2026), I get short flashes of screen corruption on my desktop. When you move around windows or sometimes random, blocks of colored noise appear. Regression: - 7.0.0-34-generic: no corruption - 7.0.0-38-generic: corruption, intermittent - Windows 11 on the same machine (dual boot): no corruption, so hardware seems fine Trigger: - Launching VS Code (Electron/Chromium) triggerd it. - Otherwise it is intermittent and can disappear for a while. System: - Kubuntu 26.04, Plasma 6.6.6, Wayland session - Mesa 26.0.8-1ubuntu0.3 - GPU: AMD Radeon RX 7600 XT [1002:7480], DCN 3.2.1 - CPU: Ryzen 5 7600, integrated GPU [1002:164e] enabled but no display connected - DP-1: LG UltraGear 1920x1080 @ 179.96 Hz, VRR Automatic, 10 bpc - DP-2: Dell U2419H 1920x1080 @ 60 Hz, VRR incapable Kernel log on 7.0.0-38 (no GPU resets or ring timeouts): workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 131 times, consider switching to WQ_UNBOUND Tried on 7.0.0-38 (brief tests only, since the issue is intermittent): VRR set to Never, 8 bpc, tearing disabled, 144 Hz. None clearly fixed it. Workaround: booting 7.0.0-34-generic. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 3 12:21:30 2026 InstallationDate: Installed on 2024-10-20 (712 days ago) InstallationMedia: Kubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.6) MachineType: Micro-Star International Co., Ltd. MS-7E26 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-34-generic root=UUID=634abc01-8b3c-4d75-baeb-4749e779b55f 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-05-15 (141 days ago) dmi.bios.date: 12/27/2024 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B650 GAMING PLUS WIFI (MS-7E26) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.I0:bd12/27/2024:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E26:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB650GAMINGPLUSWIFI(MS-7E26):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E26 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169402/+subscriptions
[Bug 2169442] [NEW] Use-after-free in AppArmor prompting: audit_cache_work_function delayed work queued on freed memory → panic in __run_timers
Public bug reported: Kernel: 7.0.0-38-generic (also reproduced on 7.0.0-34-generic), Ubuntu 26.04 snapd: 2.77.1 with experimental.apparmor-prompting=true Hardware: Lenovo 21KV0018US (Meteor Lake), BIOS N48ET34W 1.21 Reproducible kernel panic within ~15-20s of launching the Thunderbird snap (157.0-2, rev 1279) when snapd AppArmor prompting is enabled. Happened 4 times in one evening. Setting experimental.apparmor-prompting=false makes it stop completely. Sequence: 1. Repeated: WARNING: kernel/workqueue.c:2351 at __queue_work.part.0+0x190/0x390 from delayed_work_timer_fn (timer softirq, idle CPU) 2. Oops: general protection fault, probably for non-canonical address 0xdead00000000012a, RIP: __run_timers+0x1e0/0x2c0 3. Kernel panic - not syncing: Fatal exception in interrupt A bpftrace kprobe on delayed_work_timer_fn caught the bad work items: in every case the delayed_work had func=audit_cache_work_function and work.entry.next == NULL (the memory was freed or zeroed). Each one was armed by snapd from this path: __queue_delayed_work knotif_update_from_uresp_perm+258 aa_listener_unotif_response+304 notify_user_response+288 listener_ioctl+699 __x64_sys_ioctl do_syscall_64 So when snapd responds to a prompt notification, the kernel queues audit_cache_work_function on a delayed_work whose containing object has already been freed (or was never initialized). The timer then fires on corrupted memory. Workaround: snap set system experimental.apparmor-prompting=false ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tau 11619 F.... pipewire tau 11637 F.... wireplumber /dev/snd/seq: tau 11619 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 23:30:58 2026 InstallationDate: Installed on 2026-05-16 (141 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21KV0018US 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-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash nvidia.NVreg_PreserveVideoMemoryAllocations=1 nvidia-drm.modeset=1 acpi.ec_no_wakeup=1 nmi_watchdog=0 snd_hda_intel.power_save=1 i915.enable_psr=0 crash_kexec_post_notifiers panic=10 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2026 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET34W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KV0018US dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET34W(1.21):bd05/11/2026:br1.21:efr1.15:svnLENOVO:pn21KV0018US:pvrThinkPadP1Gen7:rvnLENOVO:rn21KV0018US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KV_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KV0018US dmi.product.sku: LENOVO_MT_21KV_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169442 Title: Use-after-free in AppArmor prompting: audit_cache_work_function delayed work queued on freed memory → panic in __run_timers Status in linux package in Ubuntu: New Bug description: Kernel: 7.0.0-38-generic (also reproduced on 7.0.0-34-generic), Ubuntu 26.04 snapd: 2.77.1 with experimental.apparmor-prompting=true Hardware: Lenovo 21KV0018US (Meteor Lake), BIOS N48ET34W 1.21 Reproducible kernel panic within ~15-20s of launching the Thunderbird snap (157.0-2, rev 1279) when snapd AppArmor prompting is enabled. Happened 4 times in one evening. Setting experimental.apparmor-prompting=false makes it stop completely. Sequence: 1. Repeated: WARNING: kernel/workqueue.c:2351 at __queue_work.part.0+0x190/0x390 from delayed_work_timer_fn (timer softirq, idle CPU) 2. Oops: general protection fault, probably for non-canonical address 0xdead00000000012a, RIP: __run_timers+0x1e0/0x2c0 3. Kernel panic - not syncing: Fatal exception in interrupt A bpftrace kprobe on delayed_work_timer_fn caught the bad work items: in every case the delayed_work had func=audit_cache_work_function and work.entry.next == NULL (the memory was freed or zeroed). Each one was armed by snapd from this path: __queue_delayed_work knotif_update_from_uresp_perm+258 aa_listener_unotif_response+304 notify_user_response+288 listener_ioctl+699 __x64_sys_ioctl do_syscall_64 So when snapd responds to a prompt notification, the kernel queues audit_cache_work_function on a delayed_work whose containing object has already been freed (or was never initialized). The timer then fires on corrupted memory. Workaround: snap set system experimental.apparmor-prompting=false ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tau 11619 F.... pipewire tau 11637 F.... wireplumber /dev/snd/seq: tau 11619 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 23:30:58 2026 InstallationDate: Installed on 2026-05-16 (141 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21KV0018US 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-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash nvidia.NVreg_PreserveVideoMemoryAllocations=1 nvidia-drm.modeset=1 acpi.ec_no_wakeup=1 nmi_watchdog=0 snd_hda_intel.power_save=1 i915.enable_psr=0 crash_kexec_post_notifiers panic=10 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2026 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET34W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KV0018US dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET34W(1.21):bd05/11/2026:br1.21:efr1.15:svnLENOVO:pn21KV0018US:pvrThinkPadP1Gen7:rvnLENOVO:rn21KV0018US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KV_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KV0018US dmi.product.sku: LENOVO_MT_21KV_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169442/+subscriptions