Public bug reported: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec ** 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/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: New Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
пятница
[Bug 2156629] [NEW] Jammy update: v5.15.207 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release Ported from the following upstream stable releases: v5.15.204, v5.15.205, v5.15.206, v5.15.207 from git://git.kernel.org/ Buffer overflow in drivers/xen/sys-hypervisor.c xen/privcmd: fix double free via VMA splitting Linux 5.15.204 Linux 5.15.205 Linux 5.15.206 x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Noah Wager (nwager) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Noah Wager (nwager) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release + + Ported from the following upstream stable releases: + v5.15.204, v5.15.205, v5.15.206, v5.15.207 + from git://git.kernel.org/ - + Buffer overflow in drivers/xen/sys-hypervisor.c + xen/privcmd: fix double free via VMA splitting + Linux 5.15.204 + Linux 5.15.205 + Linux 5.15.206 + x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 - x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache - x86/CPU/AMD: Add X86_FEATURE_ZEN1 - x86/CPU/AMD: Rename init_amd_zn() to init_amd_zen_common() - x86/CPU/AMD: Call the spectral chicken in the Zen2 init function - x86/CPU/AMD: Add ZenX generations flags - ptrace: slightly saner 'get_dumpable()' logic + UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156629 Title: Jammy update: v5.15.207 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.207 upstream stable release Ported from the following upstream stable releases: v5.15.204, v5.15.205, v5.15.206, v5.15.207 from git://git.kernel.org/ Buffer overflow in drivers/xen/sys-hypervisor.c xen/privcmd: fix double free via VMA splitting Linux 5.15.204 Linux 5.15.205 Linux 5.15.206 x86/CPU/AMD: Prevent improper isolation of shared resources in Zen2's op cache Linux 5.15.207 UBUNTU: Upstream stable to v5.15.204, v5.15.205, v5.15.206, v5.15.207 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156629/+subscriptions
четверг
[Bug 1767324] Re: Extreme regression in battery autonomy with kernel 4.15
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1767324 Title: Extreme regression in battery autonomy with kernel 4.15 Status in linux package in Ubuntu: Expired Bug description: Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts less than one hour on a fully charged battery. On Ubuntu 17.10 with kernel 4.13, the autonomy was typically in excess of 5 hours. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-lowlatency 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jzimm 3538 F.... pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:10:02 2018 InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-20-lowlatency root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-lowlatency N/A linux-backports-modules-4.15.0-20-lowlatency N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767324/+subscriptions
[Bug 2156553] Re: Kernel Panic when download Gemini text
** Package changed: 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/2156553 Title: Kernel Panic when download Gemini text Status in linux package in Ubuntu: New Bug description: Gemini (Pro) provided some code, which I tried to download using the "down" button. System showed downloaded files dialog box, but soon cursor froze, and I got a screen saying "Kernel Panic" "Please Reboot" "Fatal Exception in Interrupt". No stack trace. Repeatable. Browser is Firefox 151.0.4; acceleration is disabled. journal did not show an clear signs of a crash. Ubuntu 7.0.0-22.22-generic 7.0.0 1 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: george 4498 F.... wireplumber /dev/snd/seq: george 4477 F.... pipewire CasperMD5CheckResult: unknown Date: Thu Jun 11 21:06:23 2026 InstallationDate: Installed on 2026-04-01 (71 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=771d63ca-1644-4fb4-aa72-a91bc92b8c80 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 (8 days ago) dmi.bios.date: 02/13/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd02/13/2020:br1.14:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA00:cvnDellInc.:ct9:cvr:sku06E4:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156553/+subscriptions
[Bug 2156553] [NEW] Kernel Panic when download Gemini text
You have been subscribed to a public bug: Gemini (Pro) provided some code, which I tried to download using the "down" button. System showed downloaded files dialog box, but soon cursor froze, and I got a screen saying "Kernel Panic" "Please Reboot" "Fatal Exception in Interrupt". No stack trace. Repeatable. Browser is Firefox 151.0.4; acceleration is disabled. journal did not show an clear signs of a crash. Ubuntu 7.0.0-22.22-generic 7.0.0 1 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: george 4498 F.... wireplumber /dev/snd/seq: george 4477 F.... pipewire CasperMD5CheckResult: unknown Date: Thu Jun 11 21:06:23 2026 InstallationDate: Installed on 2026-04-01 (71 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=771d63ca-1644-4fb4-aa72-a91bc92b8c80 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 (8 days ago) dmi.bios.date: 02/13/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0Y9N5X dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd02/13/2020:br1.14:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA00:cvnDellInc.:ct9:cvr:sku06E4:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- Kernel Panic when download Gemini text https://bugs.launchpad.net/bugs/2156553 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2156312] Re: Internal display black screen on Intel Lunar Lake with eDP panel
** Changed in: linux (Ubuntu Resolute) Status: New => 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/2156312 Title: Internal display black screen on Intel Lunar Lake with eDP panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Internal display goes black after login on Intel Lunar Lake systems with an eDP panel. The external monitor works. The internal display shows as disabled in display settings and cannot be enabled. Hits 100% on affected hardware (3 units, 15/15 attempts). The bug is caused by LOBF (Link Off Between Frames) being enabled on platforms that use the legacy VRR timing generator. Those platforms do not meet the bspec requirement for LOBF (Always-on VRR TG with fixed refresh rate mode). Enabling LOBF incorrectly causes the display to go dark. [Fix] Replace the raw vmin/vmax/flipline comparison with the proper bspec checks: - intel_vrr_always_use_vrr_tg() to gate LOBF on platforms with Always-on VRR TG - intel_vrr_is_fixed_rr() to confirm fixed refresh rate mode Backported from upstream commit 8a517b1e6d8b, merged in v7.1-rc1. [Test Plan] Boot on affected Intel Lunar Lake hardware with an eDP panel. Without patch: internal display is black after login; shows as disabled in display settings. With patch: internal display works normally after login. [Where problems could occur] Could affect intel_alpm.c LOBF configuration logic in the i915 driver. If intel_vrr_always_use_vrr_tg() or intel_vrr_is_fixed_rr() return wrong results on a platform, LOBF would be incorrectly blocked, and Panel Replay power savings would be lost on those machines. The display would still work — it would just not enter LOBF mode. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156312/+subscriptions
[Bug 2156559] Re: Fix no sound output device on Dell GhostRider PTL no camera SKU
** Changed in: linux (Ubuntu Resolute) Status: New => 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/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions
[Bug 2156559] [NEW] Fix no sound output device on Dell GhostRider PTL no camera SKU
Public bug reported: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: In Progress ** Tags: jira-wtn-416 oem-priority wtn ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Tags added: jira-wtn-416 oem-priority wtn -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions
среда
[Bug 2148538] Re: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350
Set verification-done due to positive test result from user. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148538 Title: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350 Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: I have a Lenovo ThinkPad P14s Gen 6 AMD Ryzen AI 7 pro 350 I have installed - 24.04 LTS - 6.17.0-1017-oem - linux-image-6.17.0-1017-oem 6.17.0-1017.17 Regularly (at this point, seems to happen once per day), the kernel locks up (actually, let me amend that; I just noticed that the key combination I thought would go into terminal mode doesn't do that, so I don't know if the kernel has locked up or gnome has frozen). I haven't been able to identify particular workloads that are causing this behavior. At any given instance, I am running firefox, brave, mattermost, vs code, multiple terminal sessions, obsidian, perhaps some qemu vms (no GUI). Looking at the journal, after one recent lockup, I saw the following: amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. workqueue: amdgpu_tlb_fence_work [amdgpu] hogged CPU for >13333us 35 times, consider switching to WQ_UNBOUND amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. INFO: task kworker/7:0:37823 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/7:0 state:D stack:0 pid:37823 tgid:37823 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:0:39916 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:0 state:D stack:0 pid:39916 tgid:39916 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/12:4:40454 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/12:4 state:D stack:0 pid:40454 tgid:40454 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/5:4:40750 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/5:4 state:D stack:0 pid:40750 tgid:40750 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:3:40825 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:3 state:D stack:0 pid:40825 tgid:40825 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:8:40844 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:8 state:D stack:0 pid:40844 tgid:40844 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:9:40845 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:9 state:D stack:0 pid:40845 tgid:40845 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:2:41419 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:2 state:D stack:0 pid:41419 tgid:41419 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:0:41524 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:0 state:D stack:0 pid:41524 tgid:41524 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:0:42116 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:0 state:D stack:0 pid:42116 tgid:42116 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. Supervising 9 threads of 6 processes of 1 users. Supervising 9 threads of 6 processes of 1 users. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. kauditd_printk_skb: 4 callbacks suppressed SRU Justification: [ Impact ] On Lenovo ThinkPad P14s Gen 6 systems with AMD Ryzen AI 7 PRO 350, the system can lock up under graphical workloads. Kernel logs show the AMDGPU MES ring buffer becoming full and hung task reports involving amdgpu_tlb_fence_work. The issue is caused by commit f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update") which attaches TLB fences too broadly and can flood KIQ/MES TLB invalidation work. [ Fix ] Backport upstream fixes: - d967509651601 ("drm/amdgpu: make sure userqs are enabled in userq IOCTLs") - 9163fe4d790f (Revert "drm/amdgpu: don't attach the tlb fence for SI") - e9f58ff991dd ("drm/amdgpu: rework how we handle TLB fences") [ Test Plan ] 1. Boot the affected Lenovo P14s Gen 6 AMD Ryzen AI 7 PRO 350 system. 2. Exercise the graphical workload that previously reproduced the lockup. 3. Verify the system remains responsive and dmesg does not show MES ring buffer full or amdgpu_tlb_fence_work hung task messages. A test kernel with this fix series ran for 12 hours on the affected system without reproducing the lockup (LP #2148538 comment #29). [ Where problems could occur ] Regressions could appear as GPU hangs, failed VM updates, TLB flush failures, or user queue/KFD workload failures on AMD GPUs. [ Other Info ] Noble linux is not affected (offending commit absent). Resolute linux is not affected (fixes already present). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148538/+subscriptions
[Bug 2156421] [NEW] bug on keyboard keys kernel 7
Public bug reported: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156421 Title: bug on keyboard keys kernel 7 Status in linux package in Ubuntu: New Bug description: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156421/+subscriptions
[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.
Hi Shieh, I will analyze the log soon, a little busy now. And I suggest you keep the current setup to reproduce the issue in case there will more test. Thank you very much. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions
[Bug 2155195] Re: [Panther Lake/xe] DisplayPort-over-Thunderbolt external monitor not detected at cold boot (regression in linux 7.0.0-22)
expecting to be fixed on 7.0.0-26. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155195 Title: [Panther Lake/xe] DisplayPort-over-Thunderbolt external monitor not detected at cold boot (regression in linux 7.0.0-22) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu release: Ubuntu 26.04 LTS (resolute) [lsb_release -rd] Kernel package: linux-image-7.0.0-22-generic 7.0.0-22.22 version_signature: Ubuntu 7.0.0-22.22-generic 7.0.0 What I expected: On boot, an external monitor connected via a Dell Thunderbolt 4 dock (DisplayPort output) should be detected and lit, as it was on kernel 7.0.0-15-generic. What happened instead: After updating to 7.0.0-22-generic, the external monitor is not detected on a cold boot. All other dock functions work normally (USB keyboard/mouse, YubiKey, Gigabit Ethernet), and the same dock + cable + monitor work in Windows on the same machine. The internal panel (eDP-1) works. All /sys/class/drm/card1-DP-*/status read "disconnected"; only eDP-1 is connected. Root cause (boot-time ordering race in DisplayPort-over-Thunderbolt tunneling): The Thunderbolt connection manager sets up and tears down the DP tunnel ~83s BEFORE the xe display driver finishes loading, so the tunnel is destroyed and never recreated. Kernel log (monotonic boot offsets): [ 4.97s] thunderbolt 0-1: new device found ... Dell Thunderbolt 4 Dock [ 17.72s] thunderbolt 0000:00:0d.2: 0:5 <-> 1:14 (DP): not active, tearing down [101.11s] xe 0000:00:02.0: [drm] Found pantherlake (device ID b080) integrated display [102.46s] [drm] Initialized xe 1.1.0 for 0000:00:02.0 The late xe load correlates with a stalled udev coldplug: `systemd- analyze blame` shows a cluster of device units (dev-rfkill, tpm0, ttyS0-3, ...) all settling at ~1min 39s, i.e. udev is wedged ~99s and only modprobes xe afterward. This ~99s stall does not occur on 7.0.0-15-generic. Recovery (confirms HW is fine): unplugging/replugging the single Thunderbolt cable AFTER boot (xe now loaded) immediately re- establishes the DP tunnel and DP-7 goes "connected" and the monitor lights up. The failure is purely the cold-boot ordering race. Hardware: - Dell XPS 16 (product_name "XPS 16 DA16260", board 0TVXV7), BIOS 1.5.1 (2026-04-01) - GPU: Intel Panther Lake [Arc B390] [8086:b080] (rev 04), driver: xe - Dock: Dell Thunderbolt 4 Dock (USB4, links at 40 Gb/s) -> DisplayPort -> external monitor - Session: Wayland (GNOME/mutter) Workarounds: replug the Thunderbolt cable after boot; or boot 7.0.0-15-generic. See also (same teardown signature, different distro/HW): https://github.com/basecamp/omarchy/issues/3906 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kgapos 6304 F.... pipewire kgapos 6325 F.... wireplumber /dev/snd/seq: kgapos 6304 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:48:43 2026 InstallationDate: Installed on 2026-05-28 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 16 DA16260 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-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 StagingDrivers: intel_ipu7_isys intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2026 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0TVXV7 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd04/01/2026:br1.5:efr1.2:svnDellInc.:pnXPS16DA16260:pvr:rvnDellInc.:rn0TVXV7:rvrA02:cvnDellInc.:ct10:cvr:sku0DBA:pfaDellLaptops: dmi.product.family: Dell Laptops dmi.product.name: XPS 16 DA16260 dmi.product.sku: 0DBA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155195/+subscriptions
[Bug 2155161] Re: Jabra Evolve 2 85 headset keeps reconnecting via usb
Hi Alexander Thank you for your information. BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155161 Title: Jabra Evolve 2 85 headset keeps reconnecting via usb Status in linux package in Ubuntu: New Bug description: As soon as i want to use any kind of usb connection with the headset the usb connects and reconnects over and over again. I made sure its not an issue of cable used or the usb hub in the docking station. by connecting it directly to the laptop. Although i could use usb with this headset on ubuntu lts 24 without any issues since i reinstalled with kubuntu 26 this occurs (guess it would happen in ubuntu 26 too) I gladly provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 3 16:10:16 2026 InstallationDate: Installed on 2026-05-12 (22 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. Precision 3581 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=UUID=e1d7f812-2942-4efe-80f9-510636bb0378 ro quiet cryptdevice=UUID=24e90ca6-128d-41d3-be29-328e50acf97d:luks-24e90ca6-128d-41d3-be29-328e50acf97d root=/dev/mapper/luks-24e90ca6-128d-41d3-be29-328e50acf97d splash nvidia-drm.modeset=1 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: 12/12/2025 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0V8YXF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd12/12/2025:br1.27:efr1.25:svnDellInc.:pnPrecision3581:pvr:rvnDellInc.:rn0V8YXF:rvrA00:cvnDellInc.:ct10:cvr:sku0C07:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3581 dmi.product.sku: 0C07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155161/+subscriptions