journalctl -b | grep -E "sof[-_]|cs(35|42)l"
Jul 05 19:44:40 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: enabling device (0004 -> 0006)
Jul 05 19:44:40 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
Jul 05 19:44:40 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [xe])
Jul 05 19:44:40 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: use msi interrupt mode
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: hda codecs found, mask 4
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: NHLT device BT(0) detected, ssp_mask 0x4
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: BT link detected in NHLT tables: 0x4
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: DMICs detected in NHLT tables: 2
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Firmware paths/files for ipc type 1:
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Firmware file: intel/sof-ipc4/lnl/sof-lnl.ri
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/lnl
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Topology file: intel/sof-ipc4-tplg/sof-lnl-cs42l43-l0-cs35l56-l3-2ch.tplg
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.12.0.1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: supply vdd-p not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: supply vdd-d not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: supply vdd-a not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: supply vdd-io not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: supply vdd-cp not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_P not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_IO not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:0: supply VDD_A not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:0: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0)
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:0: Slave 2 state check1: UNATTACHED, status was 1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_P not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_IO not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:1: supply VDD_A not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43 sdw:0:0:01fa:4243:01: Slave 6 state check1: UNATTACHED, status was 1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:1: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0)
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs35l56 sdw:0:3:01fa:3556:01:1: Slave 1 state check1: UNATTACHED, status was 1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Booted firmware version: 2.12.0.1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: cs42l43-codec cs42l43-codec: supply vdd-amp not found, using dummy regulator
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof_sdw sof_sdw: ASoC: physical link dmic01 (id 4) not exist
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof_sdw sof_sdw: ASoC: topology: could not load header: -22
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: error: tplg component load failed -22
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: error: failed to load DSP topology -22
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof-audio-pci-intel-lnl 0000:00:1f.3: ASoC error (-22): at snd_soc_component_probe() on 0000:00:1f.3
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof_sdw sof_sdw: ASoC: failed to instantiate card -22
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof_sdw sof_sdw: error -EINVAL: snd_soc_register_card failed -22
Jul 05 19:44:41 ThinkPad-X9-14-Gen-1 kernel: sof_sdw sof_sdw: probe with driver sof_sdw failed with error -22
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116011
Title:
Mainline kernel 6.15.4: snd_soc_intel_soundwire_sof_mach.ko missing
despite CONFIG enabled
Status in linux package in Ubuntu:
New
Bug description:
On Ubuntu Mainline Kernel 6.15.4-061504-generic, the kernel
configuration contains:
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
However, the compiled kernel module
`snd_soc_intel_soundwire_sof_mach.ko` is missing from the installed
package:
linux-modules-6.15.4-061504-generic
This module is required for audio functionality on Intel platforms
using SOF + SoundWire (e.g. Lunar Lake, Meteor Lake), including:
- Intel Lunar Lake SoC
- CS42L43/CS35L56 codec combinations
- ThinkPad X9 Gen 1 and similar hardware
Without this module, affected systems have no audio devices except
"Dummy Output".
---
**Expected behavior**:
- The module should be included in the package and available under:
/lib/modules/6.15.4-061504-generic/kernel/sound/soc/intel/boards/
**Actual behavior**:
- The module is missing.
- `modinfo` fails with:
modinfo: ERROR: Module snd_soc_intel_soundwire_sof_mach not found.
---
**Steps to reproduce**:
1. Install 6.15.4 from https://kernel.ubuntu.com/mainline/v6.15.4/
2. Reboot into kernel 6.15.4-061504-generic
3. Run:
modinfo snd_soc_intel_soundwire_sof_mach
---
**Impact**:
This module is required for proper SOF SoundWire audio support on modern Intel hardware. Several distributions (Fedora, Arch) include this module by default. Without it, mainline kernels are incomplete for current-generation laptops and embedded devices.
Please include the compiled module
`snd_soc_intel_soundwire_sof_mach.ko` in future linux-modules-*
packages when CONFIG is set to `=m`.
Tested system:
Kernel: 6.15.4-061504-generic
GCC: 14.2.0
Arch: amd64
Device: Lenovo ThinkPad X9 14 Gen 1 (Intel Lunar Lake)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2116011/+subscriptions
суббота
[Bug 2112439] Re: [Dell XPS 15 9570] F4 key action repeats even when not held down
Had the same issue on my laptop. Resolved by switching the state of the
Fn key.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112439
Title:
[Dell XPS 15 9570] F4 key action repeats even when not held down
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
Opinion
Bug description:
### Affected version
- Device: Laptop Dell Inc. XPS 15 9570
- OS: Ubuntu 24.04.2
- Gnome Shell: 46
- Windowing system: Wayland
- Issue happens without extensions: Maybe? Is hard to reproduce, more details later.
### Bug summary
At times when focusing a [Brave browser](https://brave.com) or [Ungoogled Chormium](https://github.com/ungoogled-software/ungoogled-chromium), the `ctrl` and `alt` keys behave weirdly:
- Hitting `ctrl` causes the current tab to close
- Hitting `alt` causes the whole window to close, if multiple tabs are open the dialog to close multiple tabs show up.
VSCode can also behave weirdly, if the console is active it may print
the `^[OS` control character.
Important things to point out
- The behavior happens after an initial unknown trigger and then switching the focus of a window via the Activities view.
- Hitting `tab` fixed the issue, until you switch focus again via the Activities view.
- It happens only in the laptop keyboard, external keyboards do not show this behavior.
- Disabling "Repeat Keys" makes the issue go away, until it gets reenabled.
### Steps to reproduce
1. An unknown trigger that I haven't been able to nail down
2. Open a terminal window via a a custom keyboard shortcut
3. Switch to workspace 2 via keyboard shortcuts
4. Open a terminal window via a a custom keyboard shortcut
5. Switch back to workspace 1 via keyboard shortcuts
6. Focus Brave browser
7. Hit `ctrl` or `alt` keys
### What happened
The `ctrl` or `alt` keys do not behave as expected
### What did you expect to happen
For the `ctrl` and `alt` keys to not change behavior
### Relevant logs, screenshots, screencasts etc.
- [Gnome Shell issue](https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8443)
- [Bug opened with the Brave team](https://community.brave.com/t/brave-on-linux-sometimes-closes-windows-with-alt-and-tabs-with-ctrl/620892/11)
- [Very similar issue on Mutter](https://gitlab.gnome.org/GNOME/mutter/-/issues/1066)
- [Reddit thread](https://www.reddit.com/r/Ubuntu/comments/14tsrur/pressing_ctrl_closes_browser_tab_in_ubuntu_2304/)
- [This comment is the exact same issue](https://www.reddit.com/r/Ubuntu/comments/14tsrur/comment/kpiiiye/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
- [Thread on AskUbuntu with the disable "Repeat Keys" workaround](https://askubuntu.com/questions/1497058/ubuntu-23-10-pressing-alt-key-closes-window-abruptly/1532813)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu6~24.04.9
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 4 00:16:22 2025
DisplayManager: gdm3
InstallationDate: Installed on 2023-03-06 (821 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.8
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-09-02 (275 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2112439/+subscriptions
Fn key.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112439
Title:
[Dell XPS 15 9570] F4 key action repeats even when not held down
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
Opinion
Bug description:
### Affected version
- Device: Laptop Dell Inc. XPS 15 9570
- OS: Ubuntu 24.04.2
- Gnome Shell: 46
- Windowing system: Wayland
- Issue happens without extensions: Maybe? Is hard to reproduce, more details later.
### Bug summary
At times when focusing a [Brave browser](https://brave.com) or [Ungoogled Chormium](https://github.com/ungoogled-software/ungoogled-chromium), the `ctrl` and `alt` keys behave weirdly:
- Hitting `ctrl` causes the current tab to close
- Hitting `alt` causes the whole window to close, if multiple tabs are open the dialog to close multiple tabs show up.
VSCode can also behave weirdly, if the console is active it may print
the `^[OS` control character.
Important things to point out
- The behavior happens after an initial unknown trigger and then switching the focus of a window via the Activities view.
- Hitting `tab` fixed the issue, until you switch focus again via the Activities view.
- It happens only in the laptop keyboard, external keyboards do not show this behavior.
- Disabling "Repeat Keys" makes the issue go away, until it gets reenabled.
### Steps to reproduce
1. An unknown trigger that I haven't been able to nail down
2. Open a terminal window via a a custom keyboard shortcut
3. Switch to workspace 2 via keyboard shortcuts
4. Open a terminal window via a a custom keyboard shortcut
5. Switch back to workspace 1 via keyboard shortcuts
6. Focus Brave browser
7. Hit `ctrl` or `alt` keys
### What happened
The `ctrl` or `alt` keys do not behave as expected
### What did you expect to happen
For the `ctrl` and `alt` keys to not change behavior
### Relevant logs, screenshots, screencasts etc.
- [Gnome Shell issue](https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8443)
- [Bug opened with the Brave team](https://community.brave.com/t/brave-on-linux-sometimes-closes-windows-with-alt-and-tabs-with-ctrl/620892/11)
- [Very similar issue on Mutter](https://gitlab.gnome.org/GNOME/mutter/-/issues/1066)
- [Reddit thread](https://www.reddit.com/r/Ubuntu/comments/14tsrur/pressing_ctrl_closes_browser_tab_in_ubuntu_2304/)
- [This comment is the exact same issue](https://www.reddit.com/r/Ubuntu/comments/14tsrur/comment/kpiiiye/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
- [Thread on AskUbuntu with the disable "Repeat Keys" workaround](https://askubuntu.com/questions/1497058/ubuntu-23-10-pressing-alt-key-closes-window-abruptly/1532813)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu6~24.04.9
ProcVersionSignature: Ubuntu 6.8.0-60.63-generic 6.8.12
Uname: Linux 6.8.0-60-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 4 00:16:22 2025
DisplayManager: gdm3
InstallationDate: Installed on 2023-03-06 (821 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.8
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-09-02 (275 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2112439/+subscriptions
[Bug 2105402] Re: Plucky fails to boot on (older) Macs
Works on iMac14,2
Linux iMac 6.14.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15
11:18:07 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
using
linux-headers-6.14.0-24_6.14.0-24.24_all.deb
linux-headers-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-modules-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-modules-extra-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-image-6.14.0-24-generic_6.14.0-24.24_amd64.deb
from https://launchpad.net/ubuntu/+source/linux/6.14.0-24.24
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2105402
Title:
Plucky fails to boot on (older) Macs
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
MacBookAir7,1 (i5-5250U)
MacBookPro12,1 (i5-5287U)
iMac14,1 (i5-4570R)
With three older Macs I am trying Plucky versions from the past two
weeks or so fail to boot.
The built-in displays stay blank but the backlight is visible until I
force the computers to power off. External video doesn't show
anything.
I have tried both installed (more below) and live images. With the
live image the GRUB menu with "Try or install" does show up.
All three do boot normally to 24.10 live images. The iMac has 24.10
installed which also boots fine.
The two MacBooks have Plucky installed, one upgraded from an earlier
version and one installed several weeks ago. Plucky booted fine until
around 2025-03-16 when this boot issue started, both with the
installed version and the live image. I know this because it caused me
to set these aside until now when I had a chance to look closer and
find a non-Mac computer that I installed on that date.
[Test Case]
Boot on above mentioned Macs.
[Fix]
Enable efi hack only on arm64.
[Where Problems Could Occur]
Non-arm64 machines that need this fix (highly unlikely) might not
boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105402/+subscriptions
Linux iMac 6.14.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15
11:18:07 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
using
linux-headers-6.14.0-24_6.14.0-24.24_all.deb
linux-headers-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-modules-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-modules-extra-6.14.0-24-generic_6.14.0-24.24_amd64.deb
linux-image-6.14.0-24-generic_6.14.0-24.24_amd64.deb
from https://launchpad.net/ubuntu/+source/linux/6.14.0-24.24
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2105402
Title:
Plucky fails to boot on (older) Macs
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
MacBookAir7,1 (i5-5250U)
MacBookPro12,1 (i5-5287U)
iMac14,1 (i5-4570R)
With three older Macs I am trying Plucky versions from the past two
weeks or so fail to boot.
The built-in displays stay blank but the backlight is visible until I
force the computers to power off. External video doesn't show
anything.
I have tried both installed (more below) and live images. With the
live image the GRUB menu with "Try or install" does show up.
All three do boot normally to 24.10 live images. The iMac has 24.10
installed which also boots fine.
The two MacBooks have Plucky installed, one upgraded from an earlier
version and one installed several weeks ago. Plucky booted fine until
around 2025-03-16 when this boot issue started, both with the
installed version and the live image. I know this because it caused me
to set these aside until now when I had a chance to look closer and
find a non-Mac computer that I installed on that date.
[Test Case]
Boot on above mentioned Macs.
[Fix]
Enable efi hack only on arm64.
[Where Problems Could Occur]
Non-arm64 machines that need this fix (highly unlikely) might not
boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105402/+subscriptions
[Bug 2116011] [NEW] Mainline kernel 6.15.4: snd_soc_intel_soundwire_sof_mach.ko missing despite CONFIG enabled
Public bug reported:
On Ubuntu Mainline Kernel 6.15.4-061504-generic, the kernel
configuration contains:
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
However, the compiled kernel module
`snd_soc_intel_soundwire_sof_mach.ko` is missing from the installed
package:
linux-modules-6.15.4-061504-generic
This module is required for audio functionality on Intel platforms using
SOF + SoundWire (e.g. Lunar Lake, Meteor Lake), including:
- Intel Lunar Lake SoC
- CS42L43/CS35L56 codec combinations
- ThinkPad X9 Gen 1 and similar hardware
Without this module, affected systems have no audio devices except
"Dummy Output".
---
**Expected behavior**:
- The module should be included in the package and available under:
/lib/modules/6.15.4-061504-generic/kernel/sound/soc/intel/boards/
**Actual behavior**:
- The module is missing.
- `modinfo` fails with:
modinfo: ERROR: Module snd_soc_intel_soundwire_sof_mach not found.
---
**Steps to reproduce**:
1. Install 6.15.4 from https://kernel.ubuntu.com/mainline/v6.15.4/
2. Reboot into kernel 6.15.4-061504-generic
3. Run:
modinfo snd_soc_intel_soundwire_sof_mach
---
**Impact**:
This module is required for proper SOF SoundWire audio support on modern Intel hardware. Several distributions (Fedora, Arch) include this module by default. Without it, mainline kernels are incomplete for current-generation laptops and embedded devices.
Please include the compiled module `snd_soc_intel_soundwire_sof_mach.ko`
in future linux-modules-* packages when CONFIG is set to `=m`.
Tested system:
Kernel: 6.15.4-061504-generic
GCC: 14.2.0
Arch: amd64
Device: Lenovo ThinkPad X9 14 Gen 1 (Intel Lunar Lake)
** 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/2116011
Title:
Mainline kernel 6.15.4: snd_soc_intel_soundwire_sof_mach.ko missing
despite CONFIG enabled
Status in linux package in Ubuntu:
New
Bug description:
On Ubuntu Mainline Kernel 6.15.4-061504-generic, the kernel
configuration contains:
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
However, the compiled kernel module
`snd_soc_intel_soundwire_sof_mach.ko` is missing from the installed
package:
linux-modules-6.15.4-061504-generic
This module is required for audio functionality on Intel platforms
using SOF + SoundWire (e.g. Lunar Lake, Meteor Lake), including:
- Intel Lunar Lake SoC
- CS42L43/CS35L56 codec combinations
- ThinkPad X9 Gen 1 and similar hardware
Without this module, affected systems have no audio devices except
"Dummy Output".
---
**Expected behavior**:
- The module should be included in the package and available under:
/lib/modules/6.15.4-061504-generic/kernel/sound/soc/intel/boards/
**Actual behavior**:
- The module is missing.
- `modinfo` fails with:
modinfo: ERROR: Module snd_soc_intel_soundwire_sof_mach not found.
---
**Steps to reproduce**:
1. Install 6.15.4 from https://kernel.ubuntu.com/mainline/v6.15.4/
2. Reboot into kernel 6.15.4-061504-generic
3. Run:
modinfo snd_soc_intel_soundwire_sof_mach
---
**Impact**:
This module is required for proper SOF SoundWire audio support on modern Intel hardware. Several distributions (Fedora, Arch) include this module by default. Without it, mainline kernels are incomplete for current-generation laptops and embedded devices.
Please include the compiled module
`snd_soc_intel_soundwire_sof_mach.ko` in future linux-modules-*
packages when CONFIG is set to `=m`.
Tested system:
Kernel: 6.15.4-061504-generic
GCC: 14.2.0
Arch: amd64
Device: Lenovo ThinkPad X9 14 Gen 1 (Intel Lunar Lake)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2116011/+subscriptions
On Ubuntu Mainline Kernel 6.15.4-061504-generic, the kernel
configuration contains:
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
However, the compiled kernel module
`snd_soc_intel_soundwire_sof_mach.ko` is missing from the installed
package:
linux-modules-6.15.4-061504-generic
This module is required for audio functionality on Intel platforms using
SOF + SoundWire (e.g. Lunar Lake, Meteor Lake), including:
- Intel Lunar Lake SoC
- CS42L43/CS35L56 codec combinations
- ThinkPad X9 Gen 1 and similar hardware
Without this module, affected systems have no audio devices except
"Dummy Output".
---
**Expected behavior**:
- The module should be included in the package and available under:
/lib/modules/6.15.4-061504-generic/kernel/sound/soc/intel/boards/
**Actual behavior**:
- The module is missing.
- `modinfo` fails with:
modinfo: ERROR: Module snd_soc_intel_soundwire_sof_mach not found.
---
**Steps to reproduce**:
1. Install 6.15.4 from https://kernel.ubuntu.com/mainline/v6.15.4/
2. Reboot into kernel 6.15.4-061504-generic
3. Run:
modinfo snd_soc_intel_soundwire_sof_mach
---
**Impact**:
This module is required for proper SOF SoundWire audio support on modern Intel hardware. Several distributions (Fedora, Arch) include this module by default. Without it, mainline kernels are incomplete for current-generation laptops and embedded devices.
Please include the compiled module `snd_soc_intel_soundwire_sof_mach.ko`
in future linux-modules-* packages when CONFIG is set to `=m`.
Tested system:
Kernel: 6.15.4-061504-generic
GCC: 14.2.0
Arch: amd64
Device: Lenovo ThinkPad X9 14 Gen 1 (Intel Lunar Lake)
** 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/2116011
Title:
Mainline kernel 6.15.4: snd_soc_intel_soundwire_sof_mach.ko missing
despite CONFIG enabled
Status in linux package in Ubuntu:
New
Bug description:
On Ubuntu Mainline Kernel 6.15.4-061504-generic, the kernel
configuration contains:
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
However, the compiled kernel module
`snd_soc_intel_soundwire_sof_mach.ko` is missing from the installed
package:
linux-modules-6.15.4-061504-generic
This module is required for audio functionality on Intel platforms
using SOF + SoundWire (e.g. Lunar Lake, Meteor Lake), including:
- Intel Lunar Lake SoC
- CS42L43/CS35L56 codec combinations
- ThinkPad X9 Gen 1 and similar hardware
Without this module, affected systems have no audio devices except
"Dummy Output".
---
**Expected behavior**:
- The module should be included in the package and available under:
/lib/modules/6.15.4-061504-generic/kernel/sound/soc/intel/boards/
**Actual behavior**:
- The module is missing.
- `modinfo` fails with:
modinfo: ERROR: Module snd_soc_intel_soundwire_sof_mach not found.
---
**Steps to reproduce**:
1. Install 6.15.4 from https://kernel.ubuntu.com/mainline/v6.15.4/
2. Reboot into kernel 6.15.4-061504-generic
3. Run:
modinfo snd_soc_intel_soundwire_sof_mach
---
**Impact**:
This module is required for proper SOF SoundWire audio support on modern Intel hardware. Several distributions (Fedora, Arch) include this module by default. Without it, mainline kernels are incomplete for current-generation laptops and embedded devices.
Please include the compiled module
`snd_soc_intel_soundwire_sof_mach.ko` in future linux-modules-*
packages when CONFIG is set to `=m`.
Tested system:
Kernel: 6.15.4-061504-generic
GCC: 14.2.0
Arch: amd64
Device: Lenovo ThinkPad X9 14 Gen 1 (Intel Lunar Lake)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2116011/+subscriptions
[Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
Works on my computer if I add 'intel_iommu=igfx_off' to the kernel
command line.
Using latest 6.11 kernel with Ubuntu 24.04.2.
Intel UHD Graphics 620 GPU.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
Linux 6.8
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-hwe-6.8 source package in Oracular:
Fix Released
Bug description:
SRU Justification
[Impact]
The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area.
Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
The problem persists in the latest drm tip.
[Fix]
As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue.
This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs.
[Test]
1. Boot up to desktop with 6.8.0-x kernels
2. Moving cursor around the desktop
3. There should be no flicker while cursor is moving
[Where problems could occur]
For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency.
Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal.
===========
After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random.
It happens after a moderate to heavy on screen activity like window switching, scrolling etc.
It never happens when playing video or when there is no interaction using keyboard/pointer.
It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region.
Around the same time the following appears in kernel log:
kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Happens on both X11 and Wayland on both KDE plasma and Mate (though
less).
I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
Kernels 6.6, 6.5, 6.1 and older did not have that issue.
Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520]
Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
Attaching kernel log for 6.8.0-28
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
command line.
Using latest 6.11 kernel with Ubuntu 24.04.2.
Intel UHD Graphics 620 GPU.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
Linux 6.8
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-hwe-6.8 source package in Oracular:
Fix Released
Bug description:
SRU Justification
[Impact]
The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area.
Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
The problem persists in the latest drm tip.
[Fix]
As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue.
This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs.
[Test]
1. Boot up to desktop with 6.8.0-x kernels
2. Moving cursor around the desktop
3. There should be no flicker while cursor is moving
[Where problems could occur]
For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency.
Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal.
===========
After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random.
It happens after a moderate to heavy on screen activity like window switching, scrolling etc.
It never happens when playing video or when there is no interaction using keyboard/pointer.
It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region.
Around the same time the following appears in kernel log:
kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Happens on both X11 and Wayland on both KDE plasma and Mate (though
less).
I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
Kernels 6.6, 6.5, 6.1 and older did not have that issue.
Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520]
Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
Attaching kernel log for 6.8.0-28
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
пятница
Re: [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8
I had the same issue on my Dell computer and after editing GRUB it still
persisted. I decided to go back to 22.04. When 24.10 came out I installed
it and the problem disappeared for me. But I'm pretty sure 24.10 was using
kernel 6.11 at that time and didn't go to kernel 6.13 until 2025. You might
try a test install of 24.10 or 25.04 on your computer to see what happens
with a newer version of the kernel.
Douglas.
On Fri, Jul 4, 2025 at 8:45 AM Leo Vleeshouwers <2062951@bugs.launchpad.net>
wrote:
> I am experiencing this bug for more than one year now.
> It annoys me to death tbh.
> None of the suggested workarounds were successful.
> Apparently a fix has been released, but if so it does not work for me.
> I quit.
> Fortunately I have dual boot and there is still Windows.
>
> Ubuntu 24.04 LTS
> $ uname -r
> 6.11.0-29-generic
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2080588).
> https://bugs.launchpad.net/bugs/2062951
>
> Title:
> Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
> Linux 6.8
>
> Status in Linux:
> New
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux-hwe-6.8 package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Confirmed
> Status in linux-hwe-6.8 source package in Jammy:
> Fix Released
> Status in linux source package in Noble:
> Fix Released
> Status in linux-hwe-6.8 source package in Noble:
> Fix Released
> Status in linux source package in Oracular:
> Fix Released
> Status in linux-hwe-6.8 source package in Oracular:
> Fix Released
>
> Bug description:
> SRU Justification
>
> [Impact]
> The flickering predominantly occurs when the mouse cursor is in the
> bottom quarter of the screen and stops when the cursor leaves this area.
> Extensive testing across various kernel versions revealed that the issue
> became apparent from kernel version 6.8.0 onward, correlating with the
> mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and
> CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
> The problem persists in the latest drm tip.
>
> [Fix]
> As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel
> command line has been found to effectively eliminate the flickering issue.
> This patch proposes the same behavior as 'intel_iommu=igfx_off' and
> apply the rule to all Intel SKL GPU IDs.
>
> [Test]
> 1. Boot up to desktop with 6.8.0-x kernels
> 2. Moving cursor around the desktop
> 3. There should be no flicker while cursor is moving
>
> [Where problems could occur]
> For virtualized environments using hardware-assisted virtualization for
> graphics (such as VFIO or mediated pass-through), disabling IOMMU for
> graphics could either disable these features or reduce their security and
> efficiency.
> Usually, users pass the 'intel_iommu=on' by themselves when they are
> using related features. So, the impact of this change is minimal.
>
> ===========
>
> After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing
> heavy flickering at random.
> It happens after a moderate to heavy on screen activity like window
> switching, scrolling etc.
> It never happens when playing video or when there is no interaction
> using keyboard/pointer.
>
> It tend to happen when the mouse cursor is in the bottom quarter of the
> screen and stops immediately when the cursor leaves that screen region.
> Around the same time the following appears in kernel log:
> kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
>
> Happens on both X11 and Wayland on both KDE plasma and Mate (though
> less).
>
> I first encountered the issue with Linux 6.8.0-11 and it still happens
> with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
> Kernels 6.6, 6.5, 6.1 and older did not have that issue.
>
> Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD
> Graphics 520]
> Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
>
> Attaching kernel log for 6.8.0-28
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
>
>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
Linux 6.8
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-hwe-6.8 source package in Oracular:
Fix Released
Bug description:
SRU Justification
[Impact]
The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area.
Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
The problem persists in the latest drm tip.
[Fix]
As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue.
This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs.
[Test]
1. Boot up to desktop with 6.8.0-x kernels
2. Moving cursor around the desktop
3. There should be no flicker while cursor is moving
[Where problems could occur]
For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency.
Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal.
===========
After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random.
It happens after a moderate to heavy on screen activity like window switching, scrolling etc.
It never happens when playing video or when there is no interaction using keyboard/pointer.
It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region.
Around the same time the following appears in kernel log:
kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Happens on both X11 and Wayland on both KDE plasma and Mate (though
less).
I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
Kernels 6.6, 6.5, 6.1 and older did not have that issue.
Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520]
Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
Attaching kernel log for 6.8.0-28
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
persisted. I decided to go back to 22.04. When 24.10 came out I installed
it and the problem disappeared for me. But I'm pretty sure 24.10 was using
kernel 6.11 at that time and didn't go to kernel 6.13 until 2025. You might
try a test install of 24.10 or 25.04 on your computer to see what happens
with a newer version of the kernel.
Douglas.
On Fri, Jul 4, 2025 at 8:45 AM Leo Vleeshouwers <2062951@bugs.launchpad.net>
wrote:
> I am experiencing this bug for more than one year now.
> It annoys me to death tbh.
> None of the suggested workarounds were successful.
> Apparently a fix has been released, but if so it does not work for me.
> I quit.
> Fortunately I have dual boot and there is still Windows.
>
> Ubuntu 24.04 LTS
> $ uname -r
> 6.11.0-29-generic
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2080588).
> https://bugs.launchpad.net/bugs/2062951
>
> Title:
> Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
> Linux 6.8
>
> Status in Linux:
> New
> Status in linux package in Ubuntu:
> Fix Released
> Status in linux-hwe-6.8 package in Ubuntu:
> Fix Released
> Status in linux source package in Jammy:
> Confirmed
> Status in linux-hwe-6.8 source package in Jammy:
> Fix Released
> Status in linux source package in Noble:
> Fix Released
> Status in linux-hwe-6.8 source package in Noble:
> Fix Released
> Status in linux source package in Oracular:
> Fix Released
> Status in linux-hwe-6.8 source package in Oracular:
> Fix Released
>
> Bug description:
> SRU Justification
>
> [Impact]
> The flickering predominantly occurs when the mouse cursor is in the
> bottom quarter of the screen and stops when the cursor leaves this area.
> Extensive testing across various kernel versions revealed that the issue
> became apparent from kernel version 6.8.0 onward, correlating with the
> mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and
> CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
> The problem persists in the latest drm tip.
>
> [Fix]
> As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel
> command line has been found to effectively eliminate the flickering issue.
> This patch proposes the same behavior as 'intel_iommu=igfx_off' and
> apply the rule to all Intel SKL GPU IDs.
>
> [Test]
> 1. Boot up to desktop with 6.8.0-x kernels
> 2. Moving cursor around the desktop
> 3. There should be no flicker while cursor is moving
>
> [Where problems could occur]
> For virtualized environments using hardware-assisted virtualization for
> graphics (such as VFIO or mediated pass-through), disabling IOMMU for
> graphics could either disable these features or reduce their security and
> efficiency.
> Usually, users pass the 'intel_iommu=on' by themselves when they are
> using related features. So, the impact of this change is minimal.
>
> ===========
>
> After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing
> heavy flickering at random.
> It happens after a moderate to heavy on screen activity like window
> switching, scrolling etc.
> It never happens when playing video or when there is no interaction
> using keyboard/pointer.
>
> It tend to happen when the mouse cursor is in the bottom quarter of the
> screen and stops immediately when the cursor leaves that screen region.
> Around the same time the following appears in kernel log:
> kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
>
> Happens on both X11 and Wayland on both KDE plasma and Mate (though
> less).
>
> I first encountered the issue with Linux 6.8.0-11 and it still happens
> with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
> Kernels 6.6, 6.5, 6.1 and older did not have that issue.
>
> Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD
> Graphics 520]
> Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
>
> Attaching kernel log for 6.8.0-28
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
>
>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
Linux 6.8
Status in Linux:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Fix Released
Status in linux source package in Oracular:
Fix Released
Status in linux-hwe-6.8 source package in Oracular:
Fix Released
Bug description:
SRU Justification
[Impact]
The flickering predominantly occurs when the mouse cursor is in the bottom quarter of the screen and stops when the cursor leaves this area.
Extensive testing across various kernel versions revealed that the issue became apparent from kernel version 6.8.0 onward, correlating with the mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
The problem persists in the latest drm tip.
[Fix]
As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel command line has been found to effectively eliminate the flickering issue.
This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the rule to all Intel SKL GPU IDs.
[Test]
1. Boot up to desktop with 6.8.0-x kernels
2. Moving cursor around the desktop
3. There should be no flicker while cursor is moving
[Where problems could occur]
For virtualized environments using hardware-assisted virtualization for graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics could either disable these features or reduce their security and efficiency.
Usually, users pass the 'intel_iommu=on' by themselves when they are using related features. So, the impact of this change is minimal.
===========
After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random.
It happens after a moderate to heavy on screen activity like window switching, scrolling etc.
It never happens when playing video or when there is no interaction using keyboard/pointer.
It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region.
Around the same time the following appears in kernel log:
kernel: i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Happens on both X11 and Wayland on both KDE plasma and Mate (though
less).
I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7.
Kernels 6.6, 6.5, 6.1 and older did not have that issue.
Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520]
Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26
Attaching kernel log for 6.8.0-28
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+subscriptions
[Bug 2105402] Re: Plucky fails to boot on (older) Macs
Works in uname -a :
Linux aritrade 6.14.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Wed Jun 25
17:16:34 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-plucky-linux-intel
** Tags added: verification-done-plucky-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2105402
Title:
Plucky fails to boot on (older) Macs
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
MacBookAir7,1 (i5-5250U)
MacBookPro12,1 (i5-5287U)
iMac14,1 (i5-4570R)
With three older Macs I am trying Plucky versions from the past two
weeks or so fail to boot.
The built-in displays stay blank but the backlight is visible until I
force the computers to power off. External video doesn't show
anything.
I have tried both installed (more below) and live images. With the
live image the GRUB menu with "Try or install" does show up.
All three do boot normally to 24.10 live images. The iMac has 24.10
installed which also boots fine.
The two MacBooks have Plucky installed, one upgraded from an earlier
version and one installed several weeks ago. Plucky booted fine until
around 2025-03-16 when this boot issue started, both with the
installed version and the live image. I know this because it caused me
to set these aside until now when I had a chance to look closer and
find a non-Mac computer that I installed on that date.
[Test Case]
Boot on above mentioned Macs.
[Fix]
Enable efi hack only on arm64.
[Where Problems Could Occur]
Non-arm64 machines that need this fix (highly unlikely) might not
boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105402/+subscriptions
Linux aritrade 6.14.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Wed Jun 25
17:16:34 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-plucky-linux-intel
** Tags added: verification-done-plucky-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2105402
Title:
Plucky fails to boot on (older) Macs
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
MacBookAir7,1 (i5-5250U)
MacBookPro12,1 (i5-5287U)
iMac14,1 (i5-4570R)
With three older Macs I am trying Plucky versions from the past two
weeks or so fail to boot.
The built-in displays stay blank but the backlight is visible until I
force the computers to power off. External video doesn't show
anything.
I have tried both installed (more below) and live images. With the
live image the GRUB menu with "Try or install" does show up.
All three do boot normally to 24.10 live images. The iMac has 24.10
installed which also boots fine.
The two MacBooks have Plucky installed, one upgraded from an earlier
version and one installed several weeks ago. Plucky booted fine until
around 2025-03-16 when this boot issue started, both with the
installed version and the live image. I know this because it caused me
to set these aside until now when I had a chance to look closer and
find a non-Mac computer that I installed on that date.
[Test Case]
Boot on above mentioned Macs.
[Fix]
Enable efi hack only on arm64.
[Where Problems Could Occur]
Non-arm64 machines that need this fix (highly unlikely) might not
boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105402/+subscriptions
[Bug 2115512] Re: MacBook Pro USB 3.0 Devices Unrecognized
See kernel-log-sandisk-inserted-after-pooweron.txt with the usb-
storage.quirks=0781:55a9:u kernel argument (that matches a SanDisk USB
3.2 thumb drive). I can't see any activity in the kernel log when I
plugged in that thumb drive.
Then I powercycled the MacBook Pro with the SanDisk drive left in the
slot; when the computer booted the drive showed up as expected. See the
attached kernel-log-sandisk-inserted-after-poweron.txt file for that
log; note that the quirks command line wasn't required.
Unplugging the SanDisk drive and re-connecting it fails, again without
any kernel messages at all. I also tried another USB 3 thumb drive
without result.
** Attachment added: "kernel-log-sandisk-inserted-at-poweron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+attachment/5888053/+files/kernel-log-sandisk-inserted-at-poweron.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
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-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
storage.quirks=0781:55a9:u kernel argument (that matches a SanDisk USB
3.2 thumb drive). I can't see any activity in the kernel log when I
plugged in that thumb drive.
Then I powercycled the MacBook Pro with the SanDisk drive left in the
slot; when the computer booted the drive showed up as expected. See the
attached kernel-log-sandisk-inserted-after-poweron.txt file for that
log; note that the quirks command line wasn't required.
Unplugging the SanDisk drive and re-connecting it fails, again without
any kernel messages at all. I also tried another USB 3 thumb drive
without result.
** Attachment added: "kernel-log-sandisk-inserted-at-poweron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+attachment/5888053/+files/kernel-log-sandisk-inserted-at-poweron.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
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-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
[Bug 2115512] Re: MacBook Pro USB 3.0 Devices Unrecognized
** Attachment added: "kernel-log-sandisk-inserted-after-poweron.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+attachment/5888052/+files/kernel-log-sandisk-inserted-after-poweron.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
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-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+attachment/5888052/+files/kernel-log-sandisk-inserted-after-poweron.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
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-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
[Bug 2107976] Re: Apple spi keyboard/trackpad not working 25.04
Works in uname -a :
Linux aritrade 6.14.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Wed Jun 25
17:16:34 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-plucky-linux-intel
** Tags added: verification-done-plucky-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2107976
Title:
Apple spi keyboard/trackpad not working 25.04
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
2 Ubuntu users reported that the spi keyboard/trackpad doesn't work anymore with
Ubuntu Plucky kernel, it works well with Oracular kernel. Through investigation,
I found the root cause is the change on iommu/intel introduced from v6.12-rc1,
from v6.12-rc, the keyboard/trackpad stops working. I checked the linux-next,
there is a fix for this issue already.
This issue only exists for Plucky kernel and onwards, Q is unstable atm, the fix
will be in Q automatically.
[Fix]
cherry-pick one patch from upstream.
[Test]
I patched a Plucky kernel and built it, then shared the deb to
bug reporters, they tested with the patched kernel, the spi keyboard/trackpad
could work well with this kernel.
[Where problems could occur]
The change impacts context entry setup order for aliased devices, if there is
regression, it will be on intel pci/pcie aliased devices, but the regression
chance is very low, since this patch just resotres to the original setup order
for aliased devices, it should be safe. And they tested the patched kernel,
no new issues were found.
Following upgrade to 25.04 the spi keyboard and trackpad are not working on my macbook 10,1. No mouse shows up on screen. applespi shows up still but dmesg logs show corrupt packets and timeouts. I have also tried running afresh from a live USB but same problem occurs.
---
ProblemType: Bug
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: eoin 2838 F.... wireplumber
/dev/snd/seq: eoin 2834 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
DistroRelease: Ubuntu 25.04
InstallationDate: Installed on 2025-03-12 (69 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: Apple Inc. MacBook10,1
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-15-generic root=UUID=411324ce-3c68-482a-a959-e1181945ef27 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-15.15-generic 6.14.0
RelatedPackageVersions:
linux-restricted-modules-6.14.0-15-generic N/A
linux-backports-modules-6.14.0-15-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
Tags: plucky wayland-session
Uname: Linux 6.14.0-15-generic x86_64
UpgradeStatus: Upgraded to plucky on 2025-05-15 (5 days ago)
UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 06/23/2024
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 529.140.2.0.0
dmi.board.name: Mac-EE2EBD4B90B839A8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBook10,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-EE2EBD4B90B839A8
dmi.modalias: dmi:bvnAppleInc.:bvr529.140.2.0.0:bd06/23/2024:br0.1:svnAppleInc.:pnMacBook10,1:pvr1.0:rvnAppleInc.:rnMac-EE2EBD4B90B839A8:rvrMacBook10,1:cvnAppleInc.:ct9:cvrMac-EE2EBD4B90B839A8:sku:
dmi.product.family: MacBook
dmi.product.name: MacBook10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2107976/+subscriptions
Linux aritrade 6.14.0-1006-realtime #6-Ubuntu SMP PREEMPT_RT Wed Jun 25
17:16:34 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-plucky-linux-intel
** Tags added: verification-done-plucky-linux-intel
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2107976
Title:
Apple spi keyboard/trackpad not working 25.04
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[Impact]
2 Ubuntu users reported that the spi keyboard/trackpad doesn't work anymore with
Ubuntu Plucky kernel, it works well with Oracular kernel. Through investigation,
I found the root cause is the change on iommu/intel introduced from v6.12-rc1,
from v6.12-rc, the keyboard/trackpad stops working. I checked the linux-next,
there is a fix for this issue already.
This issue only exists for Plucky kernel and onwards, Q is unstable atm, the fix
will be in Q automatically.
[Fix]
cherry-pick one patch from upstream.
[Test]
I patched a Plucky kernel and built it, then shared the deb to
bug reporters, they tested with the patched kernel, the spi keyboard/trackpad
could work well with this kernel.
[Where problems could occur]
The change impacts context entry setup order for aliased devices, if there is
regression, it will be on intel pci/pcie aliased devices, but the regression
chance is very low, since this patch just resotres to the original setup order
for aliased devices, it should be safe. And they tested the patched kernel,
no new issues were found.
Following upgrade to 25.04 the spi keyboard and trackpad are not working on my macbook 10,1. No mouse shows up on screen. applespi shows up still but dmesg logs show corrupt packets and timeouts. I have also tried running afresh from a live USB but same problem occurs.
---
ProblemType: Bug
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: eoin 2838 F.... wireplumber
/dev/snd/seq: eoin 2834 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
DistroRelease: Ubuntu 25.04
InstallationDate: Installed on 2025-03-12 (69 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
MachineType: Apple Inc. MacBook10,1
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-15-generic root=UUID=411324ce-3c68-482a-a959-e1181945ef27 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-15.15-generic 6.14.0
RelatedPackageVersions:
linux-restricted-modules-6.14.0-15-generic N/A
linux-backports-modules-6.14.0-15-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
Tags: plucky wayland-session
Uname: Linux 6.14.0-15-generic x86_64
UpgradeStatus: Upgraded to plucky on 2025-05-15 (5 days ago)
UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
_MarkForUpload: True
dmi.bios.date: 06/23/2024
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 529.140.2.0.0
dmi.board.name: Mac-EE2EBD4B90B839A8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBook10,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-EE2EBD4B90B839A8
dmi.modalias: dmi:bvnAppleInc.:bvr529.140.2.0.0:bd06/23/2024:br0.1:svnAppleInc.:pnMacBook10,1:pvr1.0:rvnAppleInc.:rnMac-EE2EBD4B90B839A8:rvrMacBook10,1:cvnAppleInc.:ct9:cvrMac-EE2EBD4B90B839A8:sku:
dmi.product.family: MacBook
dmi.product.name: MacBook10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2107976/+subscriptions
[Bug 2112578] Re: riscv64: KVM does not release harts
I built upstream kernel 6.14.9 with above matches. They solve my
problem.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112578
Title:
riscv64: KVM does not release harts
Status in linux package in Ubuntu:
New
Status in qemu package in Ubuntu:
Invalid
Bug description:
In the 6.14.0-13-generic kernel there seems to be a problem with KVM.
On my amd64 machine I am running a riscv64 machine using QEMU 10 with
16 cores. Inside the VM I spin up a further machine with 2 cores. Once
KVM emulation is started the load of my amd64 machine rises to > 14/16
cores for qemu-system-riscv64. KVM seems not to release cores that
were ever used. Top in 1st VM shows 0.25 cores used for 2nd VM.
The usage on my amd64 machine only drops when unloading the kvm module in the first VM.
---
ProblemType: Bug
ApportVersion: 2.32.0-0ubuntu5
Architecture: riscv64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: zfsdt 2105 F.... wireplumber
/dev/snd/seq: zfsdt 2103 F.... pipewire
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-03-17 (80 days ago)
InstallationMedia: Ubuntu-Server 25.04 "Plucky Puffin" - Daily riscv64 (20250316)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: QEMU QEMU Virtual Machine
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=af336ba2-ea81-4dd5-bada-b3e8e7fb1c58 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
ProcVersionSignature: Ubuntu 6.14.0-13.13.2-generic 6.14.0
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.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
Tags: questing
Uname: Linux 6.14.0-13-generic riscv64
UpgradeStatus: Upgraded to questing on 2025-05-17 (19 days ago)
UserGroups: N/A
_MarkForUpload: True
acpidump:
dmi.bios.date: 05/13/2025
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2025.02-8
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: virt
dmi.modalias: dmi:bvnUbuntudistributionofEDKII:bvr2025.02-8:bd05/13/2025:br0.0:svnQEMU:pnQEMUVirtualMachine:pvrvirt:cvnQEMU:ct1:cvrvirt:sku:
dmi.product.name: QEMU Virtual Machine
dmi.product.version: virt
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2112578/+subscriptions
problem.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112578
Title:
riscv64: KVM does not release harts
Status in linux package in Ubuntu:
New
Status in qemu package in Ubuntu:
Invalid
Bug description:
In the 6.14.0-13-generic kernel there seems to be a problem with KVM.
On my amd64 machine I am running a riscv64 machine using QEMU 10 with
16 cores. Inside the VM I spin up a further machine with 2 cores. Once
KVM emulation is started the load of my amd64 machine rises to > 14/16
cores for qemu-system-riscv64. KVM seems not to release cores that
were ever used. Top in 1st VM shows 0.25 cores used for 2nd VM.
The usage on my amd64 machine only drops when unloading the kvm module in the first VM.
---
ProblemType: Bug
ApportVersion: 2.32.0-0ubuntu5
Architecture: riscv64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: zfsdt 2105 F.... wireplumber
/dev/snd/seq: zfsdt 2103 F.... pipewire
CasperMD5json:
{
"result": "skip"
}
CurrentDesktop: XFCE
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2025-03-17 (80 days ago)
InstallationMedia: Ubuntu-Server 25.04 "Plucky Puffin" - Daily riscv64 (20250316)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: QEMU QEMU Virtual Machine
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-13-generic root=UUID=af336ba2-ea81-4dd5-bada-b3e8e7fb1c58 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
ProcVersionSignature: Ubuntu 6.14.0-13.13.2-generic 6.14.0
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.14.0-13-generic N/A
linux-backports-modules-6.14.0-13-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
Tags: questing
Uname: Linux 6.14.0-13-generic riscv64
UpgradeStatus: Upgraded to questing on 2025-05-17 (19 days ago)
UserGroups: N/A
_MarkForUpload: True
acpidump:
dmi.bios.date: 05/13/2025
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2025.02-8
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: virt
dmi.modalias: dmi:bvnUbuntudistributionofEDKII:bvr2025.02-8:bd05/13/2025:br0.0:svnQEMU:pnQEMUVirtualMachine:pvrvirt:cvnQEMU:ct1:cvrvirt:sku:
dmi.product.name: QEMU Virtual Machine
dmi.product.version: virt
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2112578/+subscriptions
[Bug 2115209] Re: NVMe namespace ID mismatch on repeated map/unmap
I'm marking Oracular as Won't Fix, as it's going to be EOL before the
next kernel cycle completes.
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Questing)
Importance: Medium
Status: Fix Released
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Plucky)
Status: New => Fix Released
** Changed in: linux (Ubuntu Plucky)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Oracular)
Status: New => Won't Fix
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115209
Title:
NVMe namespace ID mismatch on repeated map/unmap
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Won't Fix
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Fix Released
Bug description:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
9546ad1a9bda nvme: requeue namespace scan on missed AENs
62baf70c3274 nvme: re-read ANA log page after ns scan completes
26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115209/+subscriptions
next kernel cycle completes.
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Questing)
Importance: Medium
Status: Fix Released
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Plucky)
Status: New => Fix Released
** Changed in: linux (Ubuntu Plucky)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Oracular)
Status: New => Won't Fix
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115209
Title:
NVMe namespace ID mismatch on repeated map/unmap
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Won't Fix
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Fix Released
Bug description:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
9546ad1a9bda nvme: requeue namespace scan on missed AENs
62baf70c3274 nvme: re-read ANA log page after ns scan completes
26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115209/+subscriptions
[Bug 2115209] Re: NVMe namespace ID mismatch on repeated map/unmap
** Description changed:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
- 9546ad1a9bda nvme: requeue namespace scan on missed AENs
- 62baf70c3274 nvme: re-read ANA log page after ns scan completes
- 26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
+ 9546ad1a9bda nvme: requeue namespace scan on missed AENs
+ 62baf70c3274 nvme: re-read ANA log page after ns scan completes
+ 26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
- The attached ns-stress.ng script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
+ The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115209
Title:
NVMe namespace ID mismatch on repeated map/unmap
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Bug description:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
9546ad1a9bda nvme: requeue namespace scan on missed AENs
62baf70c3274 nvme: re-read ANA log page after ns scan completes
26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115209/+subscriptions
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
- 9546ad1a9bda nvme: requeue namespace scan on missed AENs
- 62baf70c3274 nvme: re-read ANA log page after ns scan completes
- 26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
+ 9546ad1a9bda nvme: requeue namespace scan on missed AENs
+ 62baf70c3274 nvme: re-read ANA log page after ns scan completes
+ 26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
- The attached ns-stress.ng script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
+ The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115209
Title:
NVMe namespace ID mismatch on repeated map/unmap
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Bug description:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr changed AENs) where new NSs get mapped reusing the old NSID, one occasionally sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where the respective NVMe block device (i.e. /dev/nvmeXnY) is available, but not the corresponding NVMe generic char device (i.e. /dev/ngXnY). This issue is not seen if the same NS is remapped on the same NSID, but only hit when a new NS is mapped reusing the same NSID which was previously used by some other NS.
The following error entries are seen in the messages file during this
device inconsistency scenario:
...
kernel: [267011.744167][ T2016] nvme nvme6: rescanning namespaces.
kernel: [267011.744347][T46805] nvme nvme2: rescanning namespaces.
kernel: [267011.750418][ T7876] nvme nvme1: rescanning namespaces.
kernel: [267011.784466][ T2016] nvme nvme6: IDs don't match for shared namespace 1
kernel: [267011.784791][T46805] nvme nvme2: IDs don't match for shared namespace 1
kernel: [267011.790843][ T7876] nvme nvme1: IDs don't match for shared namespace 1
kernel: [267011.804852][ T2016] nvme nvme6: IDs don't match for shared namespace 2
kernel: [267011.804867][T46805] nvme nvme2: IDs don't match for shared namespace 2
kernel: [267011.810788][ T7876] nvme nvme1: IDs don't match for shared namespace 2
kernel: [267011.824600][ T2016] nvme nvme6: IDs don't match for shared namespace 3
kernel: [267011.825114][T46805] nvme nvme2: IDs don't match for shared namespace 3
kernel: [267011.830982][ T7876] nvme nvme1: IDs don't match for shared namespace 3
kernel: [267011.844712][ T2016] nvme nvme6: duplicate IDs in subsystem for nsid 4
kernel: [267011.845161][T46805] nvme nvme2: duplicate IDs in subsystem for nsid 4
kernel: [267011.851060][ T7876] nvme nvme1: duplicate IDs in subsystem for nsid 4
[Fix]
The following upstream commits are required:
9546ad1a9bda nvme: requeue namespace scan on missed AENs
62baf70c3274 nvme: re-read ANA log page after ns scan completes
26d7fb4fd4ca nvme: fixup scan failure for non-ANA multipath controllers
$ git describe --contains 9546ad1a9bda 62baf70c3274 26d7fb4fd4ca
v6.15-rc2~11^2~1^2~11
v6.15-rc2~11^2~1^2~10
v6.15-rc3~27^2^2~5
These are already included in the Plucky tree and the Questing kernel
seems to be based on v6.15 already, so only Noble needs the cherry-
picks.
[Test Case]
The ns-stress.sh script should be able to reproduce this. It repeatedly creates and deletes NVMe namespaces mapped to the same ID. An example run from an affected system will look like the one below:
# ./ns-stress.sh /dev/nvme2
Starting test with parameters:
Controller: /dev/nvme2
NSID: 1
Iterations: 100
Size1: 0x200000
Size2: 0x400000
Iteration 1/100
create-ns: Success, created nsid:1
attach-ns: Success, nsid:1
❌ Char device missing after first attach
[Where Problems Could Occur]
The fix requeues controller scans if there are any pending/missed AEN events. This can introduce delays when managing NVMe namespaces, so we should look out for any delays or hangs with such operations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115209/+subscriptions
Подписаться на:
Сообщения (Atom)