Public bug reported:
SRU Justification:
[Impact]
More Dell platforms (Slate 3-piece PTL + Yukon PTL + Slate Max PTL) with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o corresponding firmware bianries.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
bfebfc16a8b3 cirrus: cs35l63: Add firmware for Cirrus CS35L63 for various Dell laptops
21d670224ad1 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Slate 3-piece PTL + Yukon PTL + Slate Max PTL platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63 with particular PCI SSIDs. No regression expected at the current stage.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu Questing)
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Also affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Resolute)
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/2143813
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63 on more Dell
platforms
Status in linux-firmware package in Ubuntu:
New
Status in linux-firmware source package in Noble:
New
Status in linux-firmware source package in Questing:
New
Status in linux-firmware source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
More Dell platforms (Slate 3-piece PTL + Yukon PTL + Slate Max PTL) with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o corresponding firmware bianries.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
bfebfc16a8b3 cirrus: cs35l63: Add firmware for Cirrus CS35L63 for various Dell laptops
21d670224ad1 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Slate 3-piece PTL + Yukon PTL + Slate Max PTL platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63 with particular PCI SSIDs. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2143813/+subscriptions
вторник
[Bug 2143301] Re: Enable new Intel WCL soundwire support
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143301
Title:
Enable new Intel WCL soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
New
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in firmware-sof source package in Resolute:
Fix Released
Status in linux source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
New
Bug description:
[Impact]
New Dell Slate-1-Piece and Congo platform powered by Intel WildcatLake will have no basic audio functions w/o new firmware-sof which has the new DSP firmware and TPLG files
================ kernel ==============================
Realtek on WCL: (Congo WCL)
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/sound/soc/codecs/rt722-sdca.c?id=a27539810e1e61efcfdeb51777ed875dc61e9d49 [git.kernel.org]
CirrusLogic on WCL: (Slate-1-Piece WCL)
https://lore.kernel.org/linux-sound/aYMpbnzi%2FUTO5Fqs@opensource.cirrus.com/T/#t
<=============== firmware-sof ========================
[Fix]
c78aea2df366275fed6c7b090bae3575951de57f Add 2.14.1 signed firmware binaries for Intel MTL+ targets
f3e02da867b54e6061190d7ff1549e4f00bba17c Add 2.14.1 firmware binaries for Intel MTL and newer targets
cdd3c8f9dd879a51dc8ed3c9aa0b7b0a49c108d8 Add 2.14 tools and topology binaries for Intel MTL and newer targets
11fc822288122b83296e634e8508f483c289d565 v2.14.x: add topologies for v2.14.2
e65a0d4f3ffceaf8a01df7f519707ffaf69746ef v2.14.x: add topologies for v2.14.3
[Test Case]
1. Boot up the machine of new Dell Intel WCL Congo and Slate-1-Piece platform powered by Intel WCL
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
5. Test on machines of Intel ARL/LNL/MTL/PTL platforms for possible regression
[Where problems could occur]
Per comment from Intel, the primary requirement is that the topology file (sof-ptl-foo.tplg) and DSP firmware (sof-ptl.ri) are a pair and need to be from the same major version.
If we upgrade of FW for only a single generation (e.g. only for WCL)
This will be problematic. The main problem is that you may have two platforms (let's say
PTL and ARL) using same topology files. If you update FW for only PTL, you should also update the topology
files used by PTL (FW+tplg always a pair!), but then if one of the topology files is used by some ARL
products you may have problems (-> scenario 2 problem on ARL then).
So we need to upgrade the DSP FW and the TPLG both for all MTL+
platforms (include ARL/LNL/MTL/PTL/WCL)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143301/+subscriptions
Importance: Undecided
Status: New
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143301
Title:
Enable new Intel WCL soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
New
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in firmware-sof source package in Resolute:
Fix Released
Status in linux source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
New
Bug description:
[Impact]
New Dell Slate-1-Piece and Congo platform powered by Intel WildcatLake will have no basic audio functions w/o new firmware-sof which has the new DSP firmware and TPLG files
================ kernel ==============================
Realtek on WCL: (Congo WCL)
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/sound/soc/codecs/rt722-sdca.c?id=a27539810e1e61efcfdeb51777ed875dc61e9d49 [git.kernel.org]
CirrusLogic on WCL: (Slate-1-Piece WCL)
https://lore.kernel.org/linux-sound/aYMpbnzi%2FUTO5Fqs@opensource.cirrus.com/T/#t
<=============== firmware-sof ========================
[Fix]
c78aea2df366275fed6c7b090bae3575951de57f Add 2.14.1 signed firmware binaries for Intel MTL+ targets
f3e02da867b54e6061190d7ff1549e4f00bba17c Add 2.14.1 firmware binaries for Intel MTL and newer targets
cdd3c8f9dd879a51dc8ed3c9aa0b7b0a49c108d8 Add 2.14 tools and topology binaries for Intel MTL and newer targets
11fc822288122b83296e634e8508f483c289d565 v2.14.x: add topologies for v2.14.2
e65a0d4f3ffceaf8a01df7f519707ffaf69746ef v2.14.x: add topologies for v2.14.3
[Test Case]
1. Boot up the machine of new Dell Intel WCL Congo and Slate-1-Piece platform powered by Intel WCL
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
5. Test on machines of Intel ARL/LNL/MTL/PTL platforms for possible regression
[Where problems could occur]
Per comment from Intel, the primary requirement is that the topology file (sof-ptl-foo.tplg) and DSP firmware (sof-ptl.ri) are a pair and need to be from the same major version.
If we upgrade of FW for only a single generation (e.g. only for WCL)
This will be problematic. The main problem is that you may have two platforms (let's say
PTL and ARL) using same topology files. If you update FW for only PTL, you should also update the topology
files used by PTL (FW+tplg always a pair!), but then if one of the topology files is used by some ARL
products you may have problems (-> scenario 2 problem on ARL then).
So we need to upgrade the DSP FW and the TPLG both for all MTL+
platforms (include ARL/LNL/MTL/PTL/WCL)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143301/+subscriptions
[Bug 2143294] Re: Ubuntu 24.04: kernel 6.17.0-14-generic causes AMDGPU init failure (MES timeout r=-110) and/or kernel panic; 6.14.0-37 works
Thank you for reporting this and helping make Ubuntu better. This bug
report is missing kernel log files. Please boot into the Ubuntu kernel
and run the following command in a terminal, which will collect
debugging information and attach it to this bug report:
$ sudo apport-collect 2143294
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143294
Title:
Ubuntu 24.04: kernel 6.17.0-14-generic causes AMDGPU init failure (MES
timeout r=-110) and/or kernel panic; 6.14.0-37 works
Status in linux package in Ubuntu:
Confirmed
Bug description:
Product/Package: linux (and possibly linux-meta-oem-6.17 if OEM kernel
was involved)
System:
Laptop: HP Victus 15 (Ryzen 7 7445HS, Radeon 740M iGPU, RTX 4050 dGPU)
Ubuntu 24.04 LTS (dual-boot with Windows 11)
Working kernel: 6.14.0-37-generic (uname -r shows 6.14.0-37-generic)
Candidate HWE kernel on my mirror: linux-generic-hwe-24.04 → 6.17.0-14.14~24.04.1
Problem summary:
After updating to kernel 6.17.0-14-generic, the system failed to boot reliably. I saw either a kernel panic on the "Ubuntu" GRUB entry or a hang/no-graphics during AMDGPU initialization. Booting an older kernel (6.14.0-37-generic) from "Advanced options for Ubuntu" works normally.
Relevant log excerpt (from failed 6.17 boot):
amdgpu: MES failed to respond to msg=SET_HW_RSRC_1
[drm:mes_v11_0_hw_init [amdgpu]] *ERROR* failed ... r=-110
amdgpu: hw_init of IP block <gfx_v11_0> failed -110
amdgpu: Fatal error during GPU init
Followed by warning: amdgpu_irq_put ...
Notes / what fixed it:
Removing/purging the 6.17 kernel and rebuilding grub restored stable
boots on 6.14.
On my system, linux-generic-hwe-24.04 is not installed; it shows candidate 6.17.0-14... so it looks like 6.17 is being offered via updates.
Links to possibly related upstream/Ubuntu issues:
Kernel panic reports for 6.17.0-14-generic are tracked/confirmed in Ubuntu bug #2141203.
Similar AMDGPU "failed to write reg … wait reg …" / init failures reported for the 6.17 OEM line in bug #2132337.
Request:
Please advise whether this is a known regression in 6.17 (AMDGPU MES/GFX init path and/or initramfs generation) affecting AMD iGPU systems, and whether a fixed 6.17 build is planned for noble-updates.
Attachments I can provide:
journalctl -k -b -1 from the failed boot
/var/log/apt/history.log around the kernel upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143294/+subscriptions
report is missing kernel log files. Please boot into the Ubuntu kernel
and run the following command in a terminal, which will collect
debugging information and attach it to this bug report:
$ sudo apport-collect 2143294
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143294
Title:
Ubuntu 24.04: kernel 6.17.0-14-generic causes AMDGPU init failure (MES
timeout r=-110) and/or kernel panic; 6.14.0-37 works
Status in linux package in Ubuntu:
Confirmed
Bug description:
Product/Package: linux (and possibly linux-meta-oem-6.17 if OEM kernel
was involved)
System:
Laptop: HP Victus 15 (Ryzen 7 7445HS, Radeon 740M iGPU, RTX 4050 dGPU)
Ubuntu 24.04 LTS (dual-boot with Windows 11)
Working kernel: 6.14.0-37-generic (uname -r shows 6.14.0-37-generic)
Candidate HWE kernel on my mirror: linux-generic-hwe-24.04 → 6.17.0-14.14~24.04.1
Problem summary:
After updating to kernel 6.17.0-14-generic, the system failed to boot reliably. I saw either a kernel panic on the "Ubuntu" GRUB entry or a hang/no-graphics during AMDGPU initialization. Booting an older kernel (6.14.0-37-generic) from "Advanced options for Ubuntu" works normally.
Relevant log excerpt (from failed 6.17 boot):
amdgpu: MES failed to respond to msg=SET_HW_RSRC_1
[drm:mes_v11_0_hw_init [amdgpu]] *ERROR* failed ... r=-110
amdgpu: hw_init of IP block <gfx_v11_0> failed -110
amdgpu: Fatal error during GPU init
Followed by warning: amdgpu_irq_put ...
Notes / what fixed it:
Removing/purging the 6.17 kernel and rebuilding grub restored stable
boots on 6.14.
On my system, linux-generic-hwe-24.04 is not installed; it shows candidate 6.17.0-14... so it looks like 6.17 is being offered via updates.
Links to possibly related upstream/Ubuntu issues:
Kernel panic reports for 6.17.0-14-generic are tracked/confirmed in Ubuntu bug #2141203.
Similar AMDGPU "failed to write reg … wait reg …" / init failures reported for the 6.17 OEM line in bug #2132337.
Request:
Please advise whether this is a known regression in 6.17 (AMDGPU MES/GFX init path and/or initramfs generation) affecting AMD iGPU systems, and whether a fixed 6.17 build is planned for noble-updates.
Attachments I can provide:
journalctl -k -b -1 from the failed boot
/var/log/apt/history.log around the kernel upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143294/+subscriptions
понедельник
[Bug 2137457] Re: system runs out of memory after loading many corrupt apparmor profiles
** Tags added: questing
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137457
Title:
system runs out of memory after loading many corrupt apparmor profiles
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu questing AMD64, 8GB memory with 6.17.0-8-generic
run stress-ng with AppArmor stressor for ~5-10 mins, system runs out
of memory.
How to reproduce issue:
use latest stress-ng from https://launchpad.net/~colin-
king/+archive/ubuntu/stress-ng
sudo add-apt-repository ppa:colin-king/stress-ng
sudo apt-get update
sudo apt-get install stress-ng
sudo stress-ng --klog-check -v --apparmor 1
after a while one gets:
stress-ng: debug: [1628] invoked with './stress-ng --klog-check -v --apparmor 1' by user 0 'root'
stress-ng: debug: [1628] stress-ng 0.20.00 gf9ac1ba95c22
stress-ng: debug: [1628] system: Linux questing-amd64 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 14 21:44:46 UTC 2025 x86_64, gcc 15.2.0, glibc 2.42, little endian
stress-ng: debug: [1628] RAM total: 7.3G, RAM free: 6.2G, swap free: 2.8G
stress-ng: debug: [1628] temporary file path: '/home/cking/stress-ng', filesystem type: ext4 (892311 blocks available, /dev/dm-0)
stress-ng: debug: [1628] 8 processors online, 8 processors configured
stress-ng: info: [1628] defaulting to a 1 day run per stressor
stress-ng: debug: [1628] CPU data cache: L1: 32K, L2: 4096K, L3: 16384K
stress-ng: debug: [1628] cache allocate: shared cache buffer size: 16384K
stress-ng: info: [1628] dispatching hogs: 1 apparmor
stress-ng: debug: [1628] starting stressor
stress-ng: debug: [1628] 1 stressor started
stress-ng: debug: [1630] apparmor: [1630] started (instance 0 on CPU 4)
stress-ng: info: [1629] klog-check: kernel cmdline: 'BOOT_IMAGE=/vmlinuz-6.17.0-8-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M'
stress-ng: info: [1629] klog-check: warning: [104.610917] 'stress-ng-appar invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-1000'
stress-ng: info: [1629] klog-check: warning: [104.610923] 'CPU: 2 UID: 0 PID: 1634 Comm: stress-ng-appar Not tainted 6.17.0-8-generic #8-Ubuntu PREEMPT(voluntary) '
stress-ng: info: [1629] klog-check: warning: [104.610925] 'Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014'
stress-ng: info: [1629] klog-check: warning: [104.610926] 'Call Trace:'
stress-ng: info: [1629] klog-check: warning: [104.610927] ' <TASK>'
stress-ng: info: [1629] klog-check: warning: [104.610930] ' show_stack+0x49/0x60'
stress-ng: info: [1629] klog-check: warning: [104.610934] ' dump_stack_lvl+0x5f/0x90'
stress-ng: info: [1629] klog-check: warning: [104.610937] ' dump_stack+0x10/0x18'
stress-ng: info: [1629] klog-check: warning: [104.610949] ' dump_header+0x48/0x1be'
stress-ng: info: [1629] klog-check: warning: [104.610950] ' oom_kill_process.cold+0x8/0xac'
stress-ng: info: [1629] klog-check: warning: [104.610951] ' out_of_memory+0xff/0x2b0'
stress-ng: info: [1629] klog-check: warning: [104.610954] ' __alloc_pages_may_oom+0x10a/0x1d0'
stress-ng: info: [1629] klog-check: warning: [104.610956] ' __alloc_pages_slowpath.constprop.0+0x40e/0x990'
stress-ng: info: [1629] klog-check: warning: [104.610957] ' __alloc_frozen_pages_noprof+0x341/0x360'
stress-ng: info: [1629] klog-check: warning: [104.610958] ' alloc_pages_mpol+0x88/0x1b0'
stress-ng: info: [1629] klog-check: warning: [104.610960] ' folio_alloc_mpol_noprof+0x14/0x40'
stress-ng: info: [1629] klog-check: warning: [104.610961] ' __read_swap_cache_async+0x16c/0x260'
stress-ng: info: [1629] klog-check: warning: [104.610963] ' swap_cluster_readahead+0x20a/0x310'
stress-ng: info: [1629] klog-check: warning: [104.610963] ' swapin_readahead+0x75/0x100'
stress-ng: info: [1629] klog-check: warning: [104.610964] ' do_swap_page+0x227/0x1010'
stress-ng: info: [1629] klog-check: warning: [104.610966] ' ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0'
stress-ng: info: [1629] klog-check: warning: [104.610967] ' ? do_syscall_64+0xb9/0xc90'
stress-ng: info: [1629] klog-check: warning: [104.610970] ' ? __pfx_default_wake_function+0x10/0x10'
stress-ng: info: [1629] klog-check: warning: [104.610971] ' handle_pte_fault+0x1b9/0x1f0'
stress-ng: info: [1629] klog-check: warning: [104.610972] ' __handle_mm_fault+0x59d/0x720'
stress-ng: info: [1629] klog-check: warning: [104.610974] ' handle_mm_fault+0xe7/0x2f0'
stress-ng: info: [1629] klog-check: warning: [104.610975] ' do_user_addr_fault+0x22b/0x6c0'
stress-ng: info: [1629] klog-check: warning: [104.610977] ' exc_page_fault+0x7f/0x1b0'
stress-ng: info: [1629] klog-check: warning: [104.610978] ' asm_exc_page_fault+0x27/0x30'
stress-ng: info: [1629] klog-check: warning: [104.610979] 'RIP: 0033:0x750ea1eb137f'
stress-ng: info: [1629] klog-check: warning: [104.610981] 'Code: 9d 38 ee ff ff e9 9c fc ff ff e8 cc 3c 09 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 8b 4f 08 48 89 c8 48 83 e0 f8 48 89 e5 <48> 3b 04 07 0f 85 9e 00 00 00 48 8b 47 10 48 3b 78 18 75 75 48 8b'
stress-ng: info: [1629] klog-check: warning: [104.610981] 'RSP: 002b:00007ffdd4d66fd0 EFLAGS: 00010206'
stress-ng: info: [1629] klog-check: warning: [104.610983] 'RAX: 00000000000002f0 RBX: 0000750ea2034fc0 RCX: 00000000000002f1'
stress-ng: info: [1629] klog-check: warning: [104.610983] 'RDX: 0000750ea2034e00 RSI: 0000000000408000 RDI: 0000596c2fa8fd60'
stress-ng: info: [1629] klog-check: warning: [104.610984] 'RBP: 00007ffdd4d66fd0 R08: 0000000000000118 R09: 0000750ea2034b20'
stress-ng: info: [1629] klog-check: warning: [104.610984] 'R10: 0000000000000120 R11: 0000750ea2034ac0 R12: 00000000000002f0'
Looks like the apparmor profiles being loaded/unloaded eat up memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2137457/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2137457
Title:
system runs out of memory after loading many corrupt apparmor profiles
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu questing AMD64, 8GB memory with 6.17.0-8-generic
run stress-ng with AppArmor stressor for ~5-10 mins, system runs out
of memory.
How to reproduce issue:
use latest stress-ng from https://launchpad.net/~colin-
king/+archive/ubuntu/stress-ng
sudo add-apt-repository ppa:colin-king/stress-ng
sudo apt-get update
sudo apt-get install stress-ng
sudo stress-ng --klog-check -v --apparmor 1
after a while one gets:
stress-ng: debug: [1628] invoked with './stress-ng --klog-check -v --apparmor 1' by user 0 'root'
stress-ng: debug: [1628] stress-ng 0.20.00 gf9ac1ba95c22
stress-ng: debug: [1628] system: Linux questing-amd64 6.17.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 14 21:44:46 UTC 2025 x86_64, gcc 15.2.0, glibc 2.42, little endian
stress-ng: debug: [1628] RAM total: 7.3G, RAM free: 6.2G, swap free: 2.8G
stress-ng: debug: [1628] temporary file path: '/home/cking/stress-ng', filesystem type: ext4 (892311 blocks available, /dev/dm-0)
stress-ng: debug: [1628] 8 processors online, 8 processors configured
stress-ng: info: [1628] defaulting to a 1 day run per stressor
stress-ng: debug: [1628] CPU data cache: L1: 32K, L2: 4096K, L3: 16384K
stress-ng: debug: [1628] cache allocate: shared cache buffer size: 16384K
stress-ng: info: [1628] dispatching hogs: 1 apparmor
stress-ng: debug: [1628] starting stressor
stress-ng: debug: [1628] 1 stressor started
stress-ng: debug: [1630] apparmor: [1630] started (instance 0 on CPU 4)
stress-ng: info: [1629] klog-check: kernel cmdline: 'BOOT_IMAGE=/vmlinuz-6.17.0-8-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M'
stress-ng: info: [1629] klog-check: warning: [104.610917] 'stress-ng-appar invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-1000'
stress-ng: info: [1629] klog-check: warning: [104.610923] 'CPU: 2 UID: 0 PID: 1634 Comm: stress-ng-appar Not tainted 6.17.0-8-generic #8-Ubuntu PREEMPT(voluntary) '
stress-ng: info: [1629] klog-check: warning: [104.610925] 'Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014'
stress-ng: info: [1629] klog-check: warning: [104.610926] 'Call Trace:'
stress-ng: info: [1629] klog-check: warning: [104.610927] ' <TASK>'
stress-ng: info: [1629] klog-check: warning: [104.610930] ' show_stack+0x49/0x60'
stress-ng: info: [1629] klog-check: warning: [104.610934] ' dump_stack_lvl+0x5f/0x90'
stress-ng: info: [1629] klog-check: warning: [104.610937] ' dump_stack+0x10/0x18'
stress-ng: info: [1629] klog-check: warning: [104.610949] ' dump_header+0x48/0x1be'
stress-ng: info: [1629] klog-check: warning: [104.610950] ' oom_kill_process.cold+0x8/0xac'
stress-ng: info: [1629] klog-check: warning: [104.610951] ' out_of_memory+0xff/0x2b0'
stress-ng: info: [1629] klog-check: warning: [104.610954] ' __alloc_pages_may_oom+0x10a/0x1d0'
stress-ng: info: [1629] klog-check: warning: [104.610956] ' __alloc_pages_slowpath.constprop.0+0x40e/0x990'
stress-ng: info: [1629] klog-check: warning: [104.610957] ' __alloc_frozen_pages_noprof+0x341/0x360'
stress-ng: info: [1629] klog-check: warning: [104.610958] ' alloc_pages_mpol+0x88/0x1b0'
stress-ng: info: [1629] klog-check: warning: [104.610960] ' folio_alloc_mpol_noprof+0x14/0x40'
stress-ng: info: [1629] klog-check: warning: [104.610961] ' __read_swap_cache_async+0x16c/0x260'
stress-ng: info: [1629] klog-check: warning: [104.610963] ' swap_cluster_readahead+0x20a/0x310'
stress-ng: info: [1629] klog-check: warning: [104.610963] ' swapin_readahead+0x75/0x100'
stress-ng: info: [1629] klog-check: warning: [104.610964] ' do_swap_page+0x227/0x1010'
stress-ng: info: [1629] klog-check: warning: [104.610966] ' ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0'
stress-ng: info: [1629] klog-check: warning: [104.610967] ' ? do_syscall_64+0xb9/0xc90'
stress-ng: info: [1629] klog-check: warning: [104.610970] ' ? __pfx_default_wake_function+0x10/0x10'
stress-ng: info: [1629] klog-check: warning: [104.610971] ' handle_pte_fault+0x1b9/0x1f0'
stress-ng: info: [1629] klog-check: warning: [104.610972] ' __handle_mm_fault+0x59d/0x720'
stress-ng: info: [1629] klog-check: warning: [104.610974] ' handle_mm_fault+0xe7/0x2f0'
stress-ng: info: [1629] klog-check: warning: [104.610975] ' do_user_addr_fault+0x22b/0x6c0'
stress-ng: info: [1629] klog-check: warning: [104.610977] ' exc_page_fault+0x7f/0x1b0'
stress-ng: info: [1629] klog-check: warning: [104.610978] ' asm_exc_page_fault+0x27/0x30'
stress-ng: info: [1629] klog-check: warning: [104.610979] 'RIP: 0033:0x750ea1eb137f'
stress-ng: info: [1629] klog-check: warning: [104.610981] 'Code: 9d 38 ee ff ff e9 9c fc ff ff e8 cc 3c 09 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 8b 4f 08 48 89 c8 48 83 e0 f8 48 89 e5 <48> 3b 04 07 0f 85 9e 00 00 00 48 8b 47 10 48 3b 78 18 75 75 48 8b'
stress-ng: info: [1629] klog-check: warning: [104.610981] 'RSP: 002b:00007ffdd4d66fd0 EFLAGS: 00010206'
stress-ng: info: [1629] klog-check: warning: [104.610983] 'RAX: 00000000000002f0 RBX: 0000750ea2034fc0 RCX: 00000000000002f1'
stress-ng: info: [1629] klog-check: warning: [104.610983] 'RDX: 0000750ea2034e00 RSI: 0000000000408000 RDI: 0000596c2fa8fd60'
stress-ng: info: [1629] klog-check: warning: [104.610984] 'RBP: 00007ffdd4d66fd0 R08: 0000000000000118 R09: 0000750ea2034b20'
stress-ng: info: [1629] klog-check: warning: [104.610984] 'R10: 0000000000000120 R11: 0000750ea2034ac0 R12: 00000000000002f0'
Looks like the apparmor profiles being loaded/unloaded eat up memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2137457/+subscriptions
[Bug 2143104] Re: Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD platform
** Summary changed:
- Enable CirrusLogic audio solution CS42L45+CS35L63
+ Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD platform
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches https://lore.kernel.org/linux-
sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
still under review.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
- Enable CirrusLogic audio solution CS42L45+CS35L63
+ Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD platform
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches https://lore.kernel.org/linux-
sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
still under review.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
[Bug 1627028] Re: Ubuntu needs a cloud flavour
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1627028
Title:
Ubuntu needs a cloud flavour
Status in linux package in Ubuntu:
Expired
Status in linux source package in Yakkety:
Won't Fix
Status in linux source package in Zesty:
Won't Fix
Bug description:
The virtual flavour cannot be tuned for cloud instances at the level
of changing config options since the virt flavour is actually
constructed from generic. Therefore, a cloud instance will have
separate config settings tuned specifically for virtual guest
instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627028/+subscriptions
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1627028
Title:
Ubuntu needs a cloud flavour
Status in linux package in Ubuntu:
Expired
Status in linux source package in Yakkety:
Won't Fix
Status in linux source package in Zesty:
Won't Fix
Bug description:
The virtual flavour cannot be tuned for cloud instances at the level
of changing config options since the virt flavour is actually
constructed from generic. Therefore, a cloud instance will have
separate config settings tuned specifically for virtual guest
instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627028/+subscriptions
[Bug 2143784] Re: Mouse lags at least since previous update (6.17.0-14-generic)
Hi Stefan,
Thank you for reporting this mouse lag issue. I've investigated your
report and found something important that needs clarification.
You mentioned you're running Ubuntu 24.04.4 LTS with kernel
6.17.0-14-generic. However, according to Ubuntu's official package
repositories, kernel 6.17.0-14 is NOT available for Ubuntu 24.04 (Noble
Numbat) on x86_64 architecture.
Kernel 6.17.0-14 is only available in:
- Ubuntu 25.10 (Questing Quokka) - an interim release
- Ubuntu 26.04 (Resolute Raccoon) - a future LTS release
- riscv64 architecture in Ubuntu 24.04 updates
This discrepancy suggests one of the following:
1. You may have manually installed a kernel from a different Ubuntu release
2. There might be confusion about your Ubuntu version
3. You could be using an unofficial kernel source
Could you please verify:
- Your exact Ubuntu version (run: `lsb_release -a`)
- Your architecture (run: `uname -m`)
- Where the kernel 6.17.0-14 came from (did you install it manually, or did Ubuntu offer it as an update?)
I did find multiple reports online about mouse cursor offset/hotspot
issues specifically with kernel 6.17.0-14 in X11 sessions. If you're
indeed running this kernel, there appears to be a known issue affecting
mouse input handling.
Thank you.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143784
Title:
Mouse lags at least since previous update (6.17.0-14-generic)
Status in linux package in Ubuntu:
Incomplete
Bug description:
I have Ubuntu Ubuntu 24.04.4 LTS with Linux 6.17.0-14-generic now.
Even after a fresh reboot, Ubuntu shows lags in mouse movement. I have no special mouse (gentix 4KCherry). The lags show by stuttering curser (still fast, but slow enough to be seen).
Actions to provoke misbehaviour (no special preconditions, just on Ubuntu desktop)
1. moved my mouse to one direction
2. stopping to move
3. waiting some seconds (optional; no matter how many)
last step:
4. THEN moving to the opposite direction
Seen misbehaviour:
- even during step 1, the mouse stutters
- on step 4, the cursor once appears in the old direction. This is unexcepted and makes no sense for me. The next mouse cursor views follow the direction, still in the same stuttering kind. What could be the issue?
Further info on my environment (partially on proposal by AI, so decide yourself if you need it):
uname -a
Linux a 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I'm using Wayland (no difference on xorg)
No matter which settings in mouse configuration on acceleration and speed
lspci -k | grep -A 2 -i "VGA"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
Subsystem: Sapphire Technology Limited Device a493
Kernel driver in use: amdgpu
sudo libinput list-devices
[...]
Device: Cherry GmbH CHERRY Mouse
Kernel: /dev/input/event4
Group: 4
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
sudo dmesg | grep -i mouse
[ 3.183127] mousedev: PS/2 mouse device common for all mice
[ 5.885578] usb 9-1.2.1.1: Product: CHERRY Mouse
[ 5.996976] input: Cherry GmbH CHERRY Mouse as /devices/pci0000:00/0000:00:08.3/0000:77:00.0/usb9/9-1/9-1.2/9-1.2.1/9-1.2.1.1/9-1.2.1.1:1.0/0003:046A:C094.0004/input/input4
[ 6.013429] hid-generic 0003:046A:C094.0004: input,hidraw3: USB HID v1.11 Mouse [Cherry GmbH CHERRY Mouse] on usb-0000:77:00.0-1.2.1.1/input0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143784/+subscriptions
Thank you for reporting this mouse lag issue. I've investigated your
report and found something important that needs clarification.
You mentioned you're running Ubuntu 24.04.4 LTS with kernel
6.17.0-14-generic. However, according to Ubuntu's official package
repositories, kernel 6.17.0-14 is NOT available for Ubuntu 24.04 (Noble
Numbat) on x86_64 architecture.
Kernel 6.17.0-14 is only available in:
- Ubuntu 25.10 (Questing Quokka) - an interim release
- Ubuntu 26.04 (Resolute Raccoon) - a future LTS release
- riscv64 architecture in Ubuntu 24.04 updates
This discrepancy suggests one of the following:
1. You may have manually installed a kernel from a different Ubuntu release
2. There might be confusion about your Ubuntu version
3. You could be using an unofficial kernel source
Could you please verify:
- Your exact Ubuntu version (run: `lsb_release -a`)
- Your architecture (run: `uname -m`)
- Where the kernel 6.17.0-14 came from (did you install it manually, or did Ubuntu offer it as an update?)
I did find multiple reports online about mouse cursor offset/hotspot
issues specifically with kernel 6.17.0-14 in X11 sessions. If you're
indeed running this kernel, there appears to be a known issue affecting
mouse input handling.
Thank you.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143784
Title:
Mouse lags at least since previous update (6.17.0-14-generic)
Status in linux package in Ubuntu:
Incomplete
Bug description:
I have Ubuntu Ubuntu 24.04.4 LTS with Linux 6.17.0-14-generic now.
Even after a fresh reboot, Ubuntu shows lags in mouse movement. I have no special mouse (gentix 4KCherry). The lags show by stuttering curser (still fast, but slow enough to be seen).
Actions to provoke misbehaviour (no special preconditions, just on Ubuntu desktop)
1. moved my mouse to one direction
2. stopping to move
3. waiting some seconds (optional; no matter how many)
last step:
4. THEN moving to the opposite direction
Seen misbehaviour:
- even during step 1, the mouse stutters
- on step 4, the cursor once appears in the old direction. This is unexcepted and makes no sense for me. The next mouse cursor views follow the direction, still in the same stuttering kind. What could be the issue?
Further info on my environment (partially on proposal by AI, so decide yourself if you need it):
uname -a
Linux a 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I'm using Wayland (no difference on xorg)
No matter which settings in mouse configuration on acceleration and speed
lspci -k | grep -A 2 -i "VGA"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
Subsystem: Sapphire Technology Limited Device a493
Kernel driver in use: amdgpu
sudo libinput list-devices
[...]
Device: Cherry GmbH CHERRY Mouse
Kernel: /dev/input/event4
Group: 4
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
sudo dmesg | grep -i mouse
[ 3.183127] mousedev: PS/2 mouse device common for all mice
[ 5.885578] usb 9-1.2.1.1: Product: CHERRY Mouse
[ 5.996976] input: Cherry GmbH CHERRY Mouse as /devices/pci0000:00/0000:00:08.3/0000:77:00.0/usb9/9-1/9-1.2/9-1.2.1/9-1.2.1.1/9-1.2.1.1:1.0/0003:046A:C094.0004/input/input4
[ 6.013429] hid-generic 0003:046A:C094.0004: input,hidraw3: USB HID v1.11 Mouse [Cherry GmbH CHERRY Mouse] on usb-0000:77:00.0-1.2.1.1/input0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143784/+subscriptions
[Bug 2143784] [NEW] Mouse lags at least since previous update (6.17.0-14-generic)
You have been subscribed to a public bug:
I have Ubuntu Ubuntu 24.04.4 LTS with Linux 6.17.0-14-generic now.
Even after a fresh reboot, Ubuntu shows lags in mouse movement. I have no special mouse (gentix 4KCherry). The lags show by stuttering curser (still fast, but slow enough to be seen).
Actions to provoke misbehaviour (no special preconditions, just on Ubuntu desktop)
1. moved my mouse to one direction
2. stopping to move
3. waiting some seconds (optional; no matter how many)
last step:
4. THEN moving to the opposite direction
Seen misbehaviour:
- even during step 1, the mouse stutters
- on step 4, the cursor once appears in the old direction. This is unexcepted and makes no sense for me. The next mouse cursor views follow the direction, still in the same stuttering kind. What could be the issue?
Further info on my environment (partially on proposal by AI, so decide yourself if you need it):
uname -a
Linux a 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I'm using Wayland (no difference on xorg)
No matter which settings in mouse configuration on acceleration and speed
lspci -k | grep -A 2 -i "VGA"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
Subsystem: Sapphire Technology Limited Device a493
Kernel driver in use: amdgpu
sudo libinput list-devices
[...]
Device: Cherry GmbH CHERRY Mouse
Kernel: /dev/input/event4
Group: 4
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
sudo dmesg | grep -i mouse
[ 3.183127] mousedev: PS/2 mouse device common for all mice
[ 5.885578] usb 9-1.2.1.1: Product: CHERRY Mouse
[ 5.996976] input: Cherry GmbH CHERRY Mouse as /devices/pci0000:00/0000:00:08.3/0000:77:00.0/usb9/9-1/9-1.2/9-1.2.1/9-1.2.1.1/9-1.2.1.1:1.0/0003:046A:C094.0004/input/input4
[ 6.013429] hid-generic 0003:046A:C094.0004: input,hidraw3: USB HID v1.11 Mouse [Cherry GmbH CHERRY Mouse] on usb-0000:77:00.0-1.2.1.1/input0
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: lag mouse
--
Mouse lags at least since previous update (6.17.0-14-generic)
https://bugs.launchpad.net/bugs/2143784
You received this bug notification because you are subscribed to linux in Ubuntu.
I have Ubuntu Ubuntu 24.04.4 LTS with Linux 6.17.0-14-generic now.
Even after a fresh reboot, Ubuntu shows lags in mouse movement. I have no special mouse (gentix 4KCherry). The lags show by stuttering curser (still fast, but slow enough to be seen).
Actions to provoke misbehaviour (no special preconditions, just on Ubuntu desktop)
1. moved my mouse to one direction
2. stopping to move
3. waiting some seconds (optional; no matter how many)
last step:
4. THEN moving to the opposite direction
Seen misbehaviour:
- even during step 1, the mouse stutters
- on step 4, the cursor once appears in the old direction. This is unexcepted and makes no sense for me. The next mouse cursor views follow the direction, still in the same stuttering kind. What could be the issue?
Further info on my environment (partially on proposal by AI, so decide yourself if you need it):
uname -a
Linux a 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I'm using Wayland (no difference on xorg)
No matter which settings in mouse configuration on acceleration and speed
lspci -k | grep -A 2 -i "VGA"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 44 [Radeon RX 9060 XT] (rev c0)
Subsystem: Sapphire Technology Limited Device a493
Kernel driver in use: amdgpu
sudo libinput list-devices
[...]
Device: Cherry GmbH CHERRY Mouse
Kernel: /dev/input/event4
Group: 4
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
sudo dmesg | grep -i mouse
[ 3.183127] mousedev: PS/2 mouse device common for all mice
[ 5.885578] usb 9-1.2.1.1: Product: CHERRY Mouse
[ 5.996976] input: Cherry GmbH CHERRY Mouse as /devices/pci0000:00/0000:00:08.3/0000:77:00.0/usb9/9-1/9-1.2/9-1.2.1/9-1.2.1.1/9-1.2.1.1:1.0/0003:046A:C094.0004/input/input4
[ 6.013429] hid-generic 0003:046A:C094.0004: input,hidraw3: USB HID v1.11 Mouse [Cherry GmbH CHERRY Mouse] on usb-0000:77:00.0-1.2.1.1/input0
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: lag mouse
--
Mouse lags at least since previous update (6.17.0-14-generic)
https://bugs.launchpad.net/bugs/2143784
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2143685] Re: USB-C DisplayPort unstable on Dell Pro Max 14 (Arrow Lake-P 7d51) - xe.force_probe fails, typec_ucsi WARNING
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143685
Title:
USB-C DisplayPort unstable on Dell Pro Max 14 (Arrow Lake-P 7d51) -
xe.force_probe fails, typec_ucsi WARNING
Status in linux package in Ubuntu:
New
Bug description:
# Bug: USB-C DisplayPort alt-mode unstable on Dell Pro Max 14 (Arrow
Lake-P) with xe.force_probe
## Summary
On Dell Pro Max 14 MC14250 with Intel Arrow Lake-P GPU [8086:7d51],
USB-C DisplayPort alt-mode is unstable when using i915 driver on
kernel 6.17.0-14. External monitors connected via USB-C randomly
disconnect and reconnect. Kernel WARNING in
typec_altmode_update_active() triggers repeatedly during cable
plug/unplug events.
Additionally, GRUB was configured with `i915.force_probe=!7d51
xe.force_probe=7d51` (possibly set by an Ubuntu update or installer),
which completely blocked i915 from probing the GPU. The xe driver
failed to load, leaving the system with no functional GPU driver —
only a basic framebuffer, no DP alt-mode, and no external monitors.
Removing these parameters restored i915 functionality.
## System Information
- **Laptop**: Dell Pro Max 14 MC14250
- **OS**: Ubuntu 25.10 (Questing Quokka)
- **Kernel**: 6.17.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC
- **GPU**: Intel Arrow Lake-P [Intel Graphics] [8086:7d51] (rev 03)
- **BIOS**: Dell 1.10.1 (2025-12-11)
- **CPU Microcode**: 0x11b (updated 2026-03-05)
- **Monitors**: 2x 5K (5120x2880) via USB-C, 1x laptop eDP (3072x1920)
## Issues
### Issue 1: xe.force_probe blocks GPU entirely
With `i915.force_probe=!7d51 xe.force_probe=7d51` in GRUB_CMDLINE_LINUX_DEFAULT:
- i915 logs: `I915 probe blocked for Device ID 7d51`
- xe driver does not load (not visible in lsmod)
- GPU falls back to basic framebuffer
- No USB-C DisplayPort alt-mode — external monitors do not work
- Only eDP (laptop screen) works at reduced capability
**Workaround**: Remove both parameters, use plain `quiet splash`
### Issue 2: typec_ucsi WARNING on USB-C hotplug
After restoring i915, external monitors work but are unstable:
- Disconnecting/reconnecting USB-C cables triggers kernel WARNING
- `typec_displayport port1-partner.0: failed to enter mode: -107`
- Multiple WARNINGs at `drivers/usb/typec/class.c:311 typec_altmode_update_active`
- Race condition in `ucsi_unregister_altmodes` / `ucsi_handle_connector_change`
- Monitors sometimes fail to re-establish DP alt-mode after cable movement
### Kernel log excerpts
```
kernel: typec_displayport port1-partner.0: failed to enter mode: -107
kernel: WARNING: CPU: 5 PID: 12 at drivers/usb/typec/class.c:311 typec_altmode_update_active+0x101/0x110 [typec]
kernel: Workqueue: USBC000:00-con2 ucsi_poll_worker [typec_ucsi]
kernel: RIP: 0010:typec_altmode_update_active+0x101/0x110 [typec]
kernel: Workqueue: events ucsi_handle_connector_change [typec_ucsi]
kernel: typec_unregister_altmode+0x3b/0x50 [typec]
kernel: ucsi_unregister_altmodes+0x53/0xb0 [typec_ucsi]
kernel: ucsi_unregister_partner+0x89/0x150 [typec_ucsi]
```
## Steps to Reproduce
1. Boot Dell Pro Max 14 MC14250 with Ubuntu 25.10, kernel 6.17.0-14
2. Connect two 5K monitors via USB-C
3. Observe: monitors may or may not initialize
4. Disconnect and reconnect USB-C cable → kernel WARNING, monitor may not return
## Expected Behavior
- xe driver should work if force_probe is set, OR force_probe should not be set by default
- USB-C DP alt-mode should survive cable reconnection without kernel warnings
## Workaround
Remove `i915.force_probe=!7d51 xe.force_probe=7d51` from GRUB config:
```bash
sudo sed -i 's/quiet splash i915.force_probe=!7d51 xe.force_probe=7d51/quiet splash/' /etc/default/grub
sudo update-grub
```
## Available kernels for bisect
- 6.17.0-12-generic (installed, not yet tested for this issue)
- 6.17.0-14-generic (current, affected)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: subone 3494 F.... pipewire
subone 3533 F.... wireplumber
/dev/snd/seq: subone 3494 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 9 01:42:53 2026
InstallationDate: Installed on 2026-01-15 (52 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Dell Inc. Dell Pro Max 14 MC14250
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=80e678ad-e34e-4c24-bd1a-4f5f157f2400 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2025
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0YJFPY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.22
dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd12/11/2025:br1.10:efr1.22:svnDellInc.:pnDellProMax14MC14250:pvr:rvnDellInc.:rn0YJFPY:rvrA00:cvnDellInc.:ct10:cvr:sku0CF0:
dmi.product.family: Dell Pro Max Laptops
dmi.product.name: Dell Pro Max 14 MC14250
dmi.product.sku: 0CF0
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143685/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143685
Title:
USB-C DisplayPort unstable on Dell Pro Max 14 (Arrow Lake-P 7d51) -
xe.force_probe fails, typec_ucsi WARNING
Status in linux package in Ubuntu:
New
Bug description:
# Bug: USB-C DisplayPort alt-mode unstable on Dell Pro Max 14 (Arrow
Lake-P) with xe.force_probe
## Summary
On Dell Pro Max 14 MC14250 with Intel Arrow Lake-P GPU [8086:7d51],
USB-C DisplayPort alt-mode is unstable when using i915 driver on
kernel 6.17.0-14. External monitors connected via USB-C randomly
disconnect and reconnect. Kernel WARNING in
typec_altmode_update_active() triggers repeatedly during cable
plug/unplug events.
Additionally, GRUB was configured with `i915.force_probe=!7d51
xe.force_probe=7d51` (possibly set by an Ubuntu update or installer),
which completely blocked i915 from probing the GPU. The xe driver
failed to load, leaving the system with no functional GPU driver —
only a basic framebuffer, no DP alt-mode, and no external monitors.
Removing these parameters restored i915 functionality.
## System Information
- **Laptop**: Dell Pro Max 14 MC14250
- **OS**: Ubuntu 25.10 (Questing Quokka)
- **Kernel**: 6.17.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC
- **GPU**: Intel Arrow Lake-P [Intel Graphics] [8086:7d51] (rev 03)
- **BIOS**: Dell 1.10.1 (2025-12-11)
- **CPU Microcode**: 0x11b (updated 2026-03-05)
- **Monitors**: 2x 5K (5120x2880) via USB-C, 1x laptop eDP (3072x1920)
## Issues
### Issue 1: xe.force_probe blocks GPU entirely
With `i915.force_probe=!7d51 xe.force_probe=7d51` in GRUB_CMDLINE_LINUX_DEFAULT:
- i915 logs: `I915 probe blocked for Device ID 7d51`
- xe driver does not load (not visible in lsmod)
- GPU falls back to basic framebuffer
- No USB-C DisplayPort alt-mode — external monitors do not work
- Only eDP (laptop screen) works at reduced capability
**Workaround**: Remove both parameters, use plain `quiet splash`
### Issue 2: typec_ucsi WARNING on USB-C hotplug
After restoring i915, external monitors work but are unstable:
- Disconnecting/reconnecting USB-C cables triggers kernel WARNING
- `typec_displayport port1-partner.0: failed to enter mode: -107`
- Multiple WARNINGs at `drivers/usb/typec/class.c:311 typec_altmode_update_active`
- Race condition in `ucsi_unregister_altmodes` / `ucsi_handle_connector_change`
- Monitors sometimes fail to re-establish DP alt-mode after cable movement
### Kernel log excerpts
```
kernel: typec_displayport port1-partner.0: failed to enter mode: -107
kernel: WARNING: CPU: 5 PID: 12 at drivers/usb/typec/class.c:311 typec_altmode_update_active+0x101/0x110 [typec]
kernel: Workqueue: USBC000:00-con2 ucsi_poll_worker [typec_ucsi]
kernel: RIP: 0010:typec_altmode_update_active+0x101/0x110 [typec]
kernel: Workqueue: events ucsi_handle_connector_change [typec_ucsi]
kernel: typec_unregister_altmode+0x3b/0x50 [typec]
kernel: ucsi_unregister_altmodes+0x53/0xb0 [typec_ucsi]
kernel: ucsi_unregister_partner+0x89/0x150 [typec_ucsi]
```
## Steps to Reproduce
1. Boot Dell Pro Max 14 MC14250 with Ubuntu 25.10, kernel 6.17.0-14
2. Connect two 5K monitors via USB-C
3. Observe: monitors may or may not initialize
4. Disconnect and reconnect USB-C cable → kernel WARNING, monitor may not return
## Expected Behavior
- xe driver should work if force_probe is set, OR force_probe should not be set by default
- USB-C DP alt-mode should survive cable reconnection without kernel warnings
## Workaround
Remove `i915.force_probe=!7d51 xe.force_probe=7d51` from GRUB config:
```bash
sudo sed -i 's/quiet splash i915.force_probe=!7d51 xe.force_probe=7d51/quiet splash/' /etc/default/grub
sudo update-grub
```
## Available kernels for bisect
- 6.17.0-12-generic (installed, not yet tested for this issue)
- 6.17.0-14-generic (current, affected)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-14-generic 6.17.0-14.14
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: subone 3494 F.... pipewire
subone 3533 F.... wireplumber
/dev/snd/seq: subone 3494 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 9 01:42:53 2026
InstallationDate: Installed on 2026-01-15 (52 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Dell Inc. Dell Pro Max 14 MC14250
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=80e678ad-e34e-4c24-bd1a-4f5f157f2400 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2025
dmi.bios.release: 1.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0YJFPY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.22
dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd12/11/2025:br1.10:efr1.22:svnDellInc.:pnDellProMax14MC14250:pvr:rvnDellInc.:rn0YJFPY:rvrA00:cvnDellInc.:ct10:cvr:sku0CF0:
dmi.product.family: Dell Pro Max Laptops
dmi.product.name: Dell Pro Max 14 MC14250
dmi.product.sku: 0CF0
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143685/+subscriptions
[Bug 2143761] [NEW] [linux-nvidia-6.17]: NVFS SGL pool selection overrun, and DMA iterator leak
Public bug reported:
1) For NVFS I/Os, blk_rq_nr_phys_segments() can undercount GPU physical
segments since CPU-side segment contiguity may differ from GPU physical
contiguity. This can undersize the SGL pool causing a buffer overrun.
2) nvfs_blk_rq_dma_map_iter_next() can create DMA mappings that exceed
the number of entries that can be stored or subsequently unmapped.
Fix both issues.
** Affects: linux-nvidia-6.17 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => linux-nvidia-6.17 (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143761
Title:
[linux-nvidia-6.17]: NVFS SGL pool selection overrun, and DMA iterator
leak
Status in linux-nvidia-6.17 package in Ubuntu:
New
Bug description:
1) For NVFS I/Os, blk_rq_nr_phys_segments() can undercount GPU
physical segments since CPU-side segment contiguity may differ from
GPU physical contiguity. This can undersize the SGL pool causing a
buffer overrun.
2) nvfs_blk_rq_dma_map_iter_next() can create DMA mappings that exceed
the number of entries that can be stored or subsequently unmapped.
Fix both issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.17/+bug/2143761/+subscriptions
1) For NVFS I/Os, blk_rq_nr_phys_segments() can undercount GPU physical
segments since CPU-side segment contiguity may differ from GPU physical
contiguity. This can undersize the SGL pool causing a buffer overrun.
2) nvfs_blk_rq_dma_map_iter_next() can create DMA mappings that exceed
the number of entries that can be stored or subsequently unmapped.
Fix both issues.
** Affects: linux-nvidia-6.17 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => linux-nvidia-6.17 (Ubuntu)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143761
Title:
[linux-nvidia-6.17]: NVFS SGL pool selection overrun, and DMA iterator
leak
Status in linux-nvidia-6.17 package in Ubuntu:
New
Bug description:
1) For NVFS I/Os, blk_rq_nr_phys_segments() can undercount GPU
physical segments since CPU-side segment contiguity may differ from
GPU physical contiguity. This can undersize the SGL pool causing a
buffer overrun.
2) nvfs_blk_rq_dma_map_iter_next() can create DMA mappings that exceed
the number of entries that can be stored or subsequently unmapped.
Fix both issues.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.17/+bug/2143761/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
This bug was fixed in the package nvidia-graphics-drivers-570-server -
570.211.01-0ubuntu0.24.04.2
---------------
nvidia-graphics-drivers-570-server (570.211.01-0ubuntu0.24.04.2) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:53:23
-0500
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
570.211.01-0ubuntu0.24.04.2
---------------
nvidia-graphics-drivers-570-server (570.211.01-0ubuntu0.24.04.2) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:53:23
-0500
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
This bug was fixed in the package nvidia-graphics-drivers-570 -
570.211.01-0ubuntu0.24.04.2
---------------
nvidia-graphics-drivers-570 (570.211.01-0ubuntu0.24.04.2) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:59:02
-0500
** Changed in: nvidia-graphics-drivers-570-server (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
570.211.01-0ubuntu0.24.04.2
---------------
nvidia-graphics-drivers-570 (570.211.01-0ubuntu0.24.04.2) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:59:02
-0500
** Changed in: nvidia-graphics-drivers-570-server (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.288.01-0ubuntu0.24.04.3
---------------
nvidia-graphics-drivers-535-server (535.288.01-0ubuntu0.24.04.3) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:49:51
-0500
** Changed in: nvidia-graphics-drivers-570 (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
535.288.01-0ubuntu0.24.04.3
---------------
nvidia-graphics-drivers-535-server (535.288.01-0ubuntu0.24.04.3) noble; urgency=medium
* Blacklist nova driver in modprobe (LP: #2142443)
-- Abdur Rahman <abdur.rahman@canonical.com> Fri, 06 Mar 2026 10:49:51
-0500
** Changed in: nvidia-graphics-drivers-570 (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-570-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Released
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Released
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Подписаться на:
Комментарии (Atom)