Confirmed. 6.19.0-9-generic works fine when installed on an existing
system but the casper initrd of the ISO seems broken. Missing module or
firmware?
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Resolute)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142403
Title:
Ubuntu Resolute Desktop image arm64 - Boot on SC8280XP stalls with
gpi-dma errors
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Resolute:
Confirmed
Bug description:
Booting the https://cdimage.ubuntu.com/daily-live/pending/resolute-desktop-arm64.iso from 02/14/26 and 02/14/21 on The Lenovo Thinkpad X13s or Windows Dev Kit 2023 don't boot. They either reset or stall. Both devices boot nicely with the Ubuntu Concept X1E kernel 6.19.0-6, but on the installed Ubuntu 25.10 from internal SSD.
Digging a bit, I can see these dmesg lines when booting up (after init, shortly after speed-test for RAID6, as it seems after async_tx_init:
gpi 800000.dma-controller: Error with cmd: CH START completion timeout
gpi 800000.dma-controller: Error with cmd: DE ALLOC ret:-5
The WDK resets shortly after that, the X13s stalls. Bouth don't reach
a login.
My guess is its somewhere in the udev rules or init script, as the
same kernel runs fine on 25.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142403/+subscriptions
вторник
[Bug 2143849] [NEW] Kernel NULL pointer dereference in rb_insert_color via hrtimer/runc nanosleep causes CPU soft lockup
Public bug reported:
Kernel panicked with a NULL pointer dereference triggered by runc
(container runtime) during a nanosleep call, leading to a permanent CPU
6 soft lockup. The system became completely unresponsive (no SSH, no
keyboard input) and required a manual hard reboot to recover.
Ubuntu release: Ubuntu 24.04.4 LTS
Kernel: Ubuntu 6.8.0-101.101-generic 6.8.12
Kernel package version: linux-image-6.8.0-101-generic: 6.8.0-101.101
Hardware: OnLogic Helix52X/K52X
BIOS: Z01-0009I102 08/20/2025
Crash time: Mar 09 2026 20:39:54
Initial fault:
BUG: kernel NULL pointer dereference, address: 0000000000000008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 6 PID: 158306 Comm: runc
Call trace:
rb_insert_color+0x14/0x190
timerqueue_add+0x69/0xd0
enqueue_hrtimer+0x4d/0xc0
hrtimer_start_range_ns+0x187/0x2f0
do_nanosleep+0x51/0x150
Secondary lockup (cascading from above):
native_queued_spin_lock_slowpath+0x83/0x300
__raw_spin_lock_irqsave+0x57/0x80
hrtimer_interrupt+0x51/0x250
__sysvec_apic_timer_interrupt+0x4e/0x120
sysvec_apic_timer_interrupt+0x8d/0xd0
After the initial crash, CPU 6 remained deadlocked on a spin lock
indefinitely. RCU stall warnings were logged every 3 minutes for the
remaining uptime (~15 hours) until manual reboot. The system never self-
recovered.
Reproducer: Unknown. The system runs Docker containers continuously. No
specific container action was observed to trigger it. The crash occurred
without any manual intervention.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-101-generic 6.8.0-101.101
ProcVersionSignature: Ubuntu 6.8.0-101.101-generic 6.8.12
Uname: Linux 6.8.0-101-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-101-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Mar 10 12:00:02 2026
InstallationDate: Installed on 2025-11-05 (125 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: OnLogic Helix52X/K52X
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-101-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-101-generic N/A
linux-backports-modules-6.8.0-101-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 08/20/2025
dmi.bios.release: 0.66
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: Z01-0009I102
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Helix52X/K52X
dmi.board.vendor: OnLogic
dmi.board.version: Production
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrZ01-0009I102:bd08/20/2025:br0.66:svnOnLogic:pnHelix52X/K52X:pvrProduction:rvnOnLogic:rnHelix52X/K52X:rvrProduction:cvnChassisManufacturer:ct10:cvrChassisVersion:skuHelix52X_K52X:
dmi.product.family: Helix52X/K52X
dmi.product.name: Helix52X/K52X
dmi.product.sku: Helix52X_K52X
dmi.product.version: Production
dmi.sys.vendor: OnLogic
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/2143849/+attachment/5951221/+files/lspci-vnvn.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143849
Title:
Kernel NULL pointer dereference in rb_insert_color via hrtimer/runc
nanosleep causes CPU soft lockup
Status in linux package in Ubuntu:
New
Bug description:
Kernel panicked with a NULL pointer dereference triggered by runc
(container runtime) during a nanosleep call, leading to a permanent
CPU 6 soft lockup. The system became completely unresponsive (no SSH,
no keyboard input) and required a manual hard reboot to recover.
Ubuntu release: Ubuntu 24.04.4 LTS
Kernel: Ubuntu 6.8.0-101.101-generic 6.8.12
Kernel package version: linux-image-6.8.0-101-generic: 6.8.0-101.101
Hardware: OnLogic Helix52X/K52X
BIOS: Z01-0009I102 08/20/2025
Crash time: Mar 09 2026 20:39:54
Initial fault:
BUG: kernel NULL pointer dereference, address: 0000000000000008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 6 PID: 158306 Comm: runc
Call trace:
rb_insert_color+0x14/0x190
timerqueue_add+0x69/0xd0
enqueue_hrtimer+0x4d/0xc0
hrtimer_start_range_ns+0x187/0x2f0
do_nanosleep+0x51/0x150
Secondary lockup (cascading from above):
native_queued_spin_lock_slowpath+0x83/0x300
__raw_spin_lock_irqsave+0x57/0x80
hrtimer_interrupt+0x51/0x250
__sysvec_apic_timer_interrupt+0x4e/0x120
sysvec_apic_timer_interrupt+0x8d/0xd0
After the initial crash, CPU 6 remained deadlocked on a spin lock
indefinitely. RCU stall warnings were logged every 3 minutes for the
remaining uptime (~15 hours) until manual reboot. The system never
self-recovered.
Reproducer: Unknown. The system runs Docker containers continuously.
No specific container action was observed to trigger it. The crash
occurred without any manual intervention.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-101-generic 6.8.0-101.101
ProcVersionSignature: Ubuntu 6.8.0-101.101-generic 6.8.12
Uname: Linux 6.8.0-101-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-101-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Mar 10 12:00:02 2026
InstallationDate: Installed on 2025-11-05 (125 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: OnLogic Helix52X/K52X
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-101-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-101-generic N/A
linux-backports-modules-6.8.0-101-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 08/20/2025
dmi.bios.release: 0.66
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: Z01-0009I102
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Helix52X/K52X
dmi.board.vendor: OnLogic
dmi.board.version: Production
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrZ01-0009I102:bd08/20/2025:br0.66:svnOnLogic:pnHelix52X/K52X:pvrProduction:rvnOnLogic:rnHelix52X/K52X:rvrProduction:cvnChassisManufacturer:ct10:cvrChassisVersion:skuHelix52X_K52X:
dmi.product.family: Helix52X/K52X
dmi.product.name: Helix52X/K52X
dmi.product.sku: Helix52X_K52X
dmi.product.version: Production
dmi.sys.vendor: OnLogic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143849/+subscriptions
Kernel panicked with a NULL pointer dereference triggered by runc
(container runtime) during a nanosleep call, leading to a permanent CPU
6 soft lockup. The system became completely unresponsive (no SSH, no
keyboard input) and required a manual hard reboot to recover.
Ubuntu release: Ubuntu 24.04.4 LTS
Kernel: Ubuntu 6.8.0-101.101-generic 6.8.12
Kernel package version: linux-image-6.8.0-101-generic: 6.8.0-101.101
Hardware: OnLogic Helix52X/K52X
BIOS: Z01-0009I102 08/20/2025
Crash time: Mar 09 2026 20:39:54
Initial fault:
BUG: kernel NULL pointer dereference, address: 0000000000000008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 6 PID: 158306 Comm: runc
Call trace:
rb_insert_color+0x14/0x190
timerqueue_add+0x69/0xd0
enqueue_hrtimer+0x4d/0xc0
hrtimer_start_range_ns+0x187/0x2f0
do_nanosleep+0x51/0x150
Secondary lockup (cascading from above):
native_queued_spin_lock_slowpath+0x83/0x300
__raw_spin_lock_irqsave+0x57/0x80
hrtimer_interrupt+0x51/0x250
__sysvec_apic_timer_interrupt+0x4e/0x120
sysvec_apic_timer_interrupt+0x8d/0xd0
After the initial crash, CPU 6 remained deadlocked on a spin lock
indefinitely. RCU stall warnings were logged every 3 minutes for the
remaining uptime (~15 hours) until manual reboot. The system never self-
recovered.
Reproducer: Unknown. The system runs Docker containers continuously. No
specific container action was observed to trigger it. The crash occurred
without any manual intervention.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-101-generic 6.8.0-101.101
ProcVersionSignature: Ubuntu 6.8.0-101.101-generic 6.8.12
Uname: Linux 6.8.0-101-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-101-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Mar 10 12:00:02 2026
InstallationDate: Installed on 2025-11-05 (125 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: OnLogic Helix52X/K52X
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-101-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-101-generic N/A
linux-backports-modules-6.8.0-101-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 08/20/2025
dmi.bios.release: 0.66
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: Z01-0009I102
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Helix52X/K52X
dmi.board.vendor: OnLogic
dmi.board.version: Production
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrZ01-0009I102:bd08/20/2025:br0.66:svnOnLogic:pnHelix52X/K52X:pvrProduction:rvnOnLogic:rnHelix52X/K52X:rvrProduction:cvnChassisManufacturer:ct10:cvrChassisVersion:skuHelix52X_K52X:
dmi.product.family: Helix52X/K52X
dmi.product.name: Helix52X/K52X
dmi.product.sku: Helix52X_K52X
dmi.product.version: Production
dmi.sys.vendor: OnLogic
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/bugs/2143849/+attachment/5951221/+files/lspci-vnvn.log
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143849
Title:
Kernel NULL pointer dereference in rb_insert_color via hrtimer/runc
nanosleep causes CPU soft lockup
Status in linux package in Ubuntu:
New
Bug description:
Kernel panicked with a NULL pointer dereference triggered by runc
(container runtime) during a nanosleep call, leading to a permanent
CPU 6 soft lockup. The system became completely unresponsive (no SSH,
no keyboard input) and required a manual hard reboot to recover.
Ubuntu release: Ubuntu 24.04.4 LTS
Kernel: Ubuntu 6.8.0-101.101-generic 6.8.12
Kernel package version: linux-image-6.8.0-101-generic: 6.8.0-101.101
Hardware: OnLogic Helix52X/K52X
BIOS: Z01-0009I102 08/20/2025
Crash time: Mar 09 2026 20:39:54
Initial fault:
BUG: kernel NULL pointer dereference, address: 0000000000000008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 6 PID: 158306 Comm: runc
Call trace:
rb_insert_color+0x14/0x190
timerqueue_add+0x69/0xd0
enqueue_hrtimer+0x4d/0xc0
hrtimer_start_range_ns+0x187/0x2f0
do_nanosleep+0x51/0x150
Secondary lockup (cascading from above):
native_queued_spin_lock_slowpath+0x83/0x300
__raw_spin_lock_irqsave+0x57/0x80
hrtimer_interrupt+0x51/0x250
__sysvec_apic_timer_interrupt+0x4e/0x120
sysvec_apic_timer_interrupt+0x8d/0xd0
After the initial crash, CPU 6 remained deadlocked on a spin lock
indefinitely. RCU stall warnings were logged every 3 minutes for the
remaining uptime (~15 hours) until manual reboot. The system never
self-recovered.
Reproducer: Unknown. The system runs Docker containers continuously.
No specific container action was observed to trigger it. The crash
occurred without any manual intervention.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-101-generic 6.8.0-101.101
ProcVersionSignature: Ubuntu 6.8.0-101.101-generic 6.8.12
Uname: Linux 6.8.0-101-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-101-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Tue Mar 10 12:00:02 2026
InstallationDate: Installed on 2025-11-05 (125 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: OnLogic Helix52X/K52X
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-101-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-101-generic N/A
linux-backports-modules-6.8.0-101-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 08/20/2025
dmi.bios.release: 0.66
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: Z01-0009I102
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Helix52X/K52X
dmi.board.vendor: OnLogic
dmi.board.version: Production
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrZ01-0009I102:bd08/20/2025:br0.66:svnOnLogic:pnHelix52X/K52X:pvrProduction:rvnOnLogic:rnHelix52X/K52X:rvrProduction:cvnChassisManufacturer:ct10:cvrChassisVersion:skuHelix52X_K52X:
dmi.product.family: Helix52X/K52X
dmi.product.name: Helix52X/K52X
dmi.product.sku: Helix52X_K52X
dmi.product.version: Production
dmi.sys.vendor: OnLogic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143849/+subscriptions
[Bug 2143784] Re: Mouse lags at least since previous update (6.17.0-14-generic)
Thanks for the update! Glad we could figure it out. Since this is a
hardware issue with your KVM switch rather than a software bug, the bug
is correctly marked as Invalid.
Replacing the KVM switch should get your mouse working properly. Thanks
for your patience!
--
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:
Invalid
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
hardware issue with your KVM switch rather than a software bug, the bug
is correctly marked as Invalid.
Replacing the KVM switch should get your mouse working properly. Thanks
for your patience!
--
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:
Invalid
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] Re: Mouse lags at least since previous update (6.17.0-14-generic)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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:
Invalid
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
Status: Incomplete => Invalid
--
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:
Invalid
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 2143301] Re: Enable new Intel WCL soundwire support
** Changed in: linux (Ubuntu Noble)
Status: New => Invalid
--
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:
Invalid
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
Status: New => Invalid
--
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:
Invalid
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 2143831] Re: linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
there is no linux-kvm in resolute
** Changed in: linux-kvm (Ubuntu Resolute)
Status: New => Invalid
** Changed in: linux-meta-kvm (Ubuntu Resolute)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143831
Title:
linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
Status in linux package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
Invalid
Status in linux-meta-azure package in Ubuntu:
New
Status in linux-meta-kvm package in Ubuntu:
Invalid
Status in linux source package in Resolute:
New
Status in linux-kvm source package in Resolute:
Invalid
Status in linux-meta-azure source package in Resolute:
New
Status in linux-meta-kvm source package in Resolute:
Invalid
Bug description:
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow
seleced runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline
kho=on is specified, so risk for general purpose usage should be very
minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143831/+subscriptions
** Changed in: linux-kvm (Ubuntu Resolute)
Status: New => Invalid
** Changed in: linux-meta-kvm (Ubuntu Resolute)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143831
Title:
linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
Status in linux package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
Invalid
Status in linux-meta-azure package in Ubuntu:
New
Status in linux-meta-kvm package in Ubuntu:
Invalid
Status in linux source package in Resolute:
New
Status in linux-kvm source package in Resolute:
Invalid
Status in linux-meta-azure source package in Resolute:
New
Status in linux-meta-kvm source package in Resolute:
Invalid
Bug description:
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow
seleced runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline
kho=on is specified, so risk for general purpose usage should be very
minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143831/+subscriptions
[Bug 2143831] [NEW] linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
Public bug reported:
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow seleced
runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline kho=on
is specified, so risk for general purpose usage should be very minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-kvm (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-kvm (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-meta-azure (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-meta-kvm (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-kvm (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/2143831
Title:
linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
Status in linux package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-meta-azure package in Ubuntu:
New
Status in linux-meta-kvm package in Ubuntu:
New
Status in linux source package in Resolute:
New
Status in linux-kvm source package in Resolute:
New
Status in linux-meta-azure source package in Resolute:
New
Status in linux-meta-kvm source package in Resolute:
New
Bug description:
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow
seleced runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline
kho=on is specified, so risk for general purpose usage should be very
minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143831/+subscriptions
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow seleced
runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline kho=on
is specified, so risk for general purpose usage should be very minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-meta-kvm (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-kvm (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-meta-azure (Ubuntu Resolute)
Importance: Undecided
Status: New
** Affects: linux-meta-kvm (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-meta-kvm (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/2143831
Title:
linux-*: please enable CONFIG_KEXEC_HANDOVER and CONFIG_LIVEUPDATE
Status in linux package in Ubuntu:
New
Status in linux-kvm package in Ubuntu:
New
Status in linux-meta-azure package in Ubuntu:
New
Status in linux-meta-kvm package in Ubuntu:
New
Status in linux source package in Resolute:
New
Status in linux-kvm source package in Resolute:
New
Status in linux-meta-azure source package in Resolute:
New
Status in linux-meta-kvm source package in Resolute:
New
Bug description:
Please consider setting:
CONFIG_KEXEC_HANDOVER=y
CONFIG_LIVEUPDATE=y
KHO and LUO are new features available on amd64/arm64 that allow
seleced runtime state to survive a kexec reboot, added in v6.19.
One of the main use cases is letting VMMs quickly resume guests by
having their memory transition from one kernel to the next, but there
are many others planned, so enable the features at build time.
The feature is disabled at runtime by default unless the cmdline
kho=on is specified, so risk for general purpose usage should be very
minimal.
https://docs.kernel.org/next/core-api/kho/index.html
https://docs.kernel.org/next/core-api/liveupdate.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143831/+subscriptions
[Bug 2143030] Re: U26.04 initramfs missing emmc modules
hi Benjamin
Is that any upstream discussion initiated on the dracut to include mmc
driver?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143030
Title:
U26.04 initramfs missing emmc modules
Status in dracut package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in dracut source package in Resolute:
New
Status in linux source package in Resolute:
New
Bug description:
in ubuntu 24.04 , emmc related modules is default available in
initramsfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.17.0-14-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/core/mmc_block.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/cqhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-acpi.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pltfm.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-uhs2.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-xenon-driver.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci_f_sdh30.ko.zst
In ubuntu 26.04, emmc related modules is not available in initramfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.18.0-9-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
user@localhost:~$ echo $?
1
The missing emmc modules in initramfs unfortunately lead to disk image
of ubuntu26.04 failed to boot in emmc.
user@localhost:~$ lsb_release -rd
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2143030/+subscriptions
Is that any upstream discussion initiated on the dracut to include mmc
driver?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143030
Title:
U26.04 initramfs missing emmc modules
Status in dracut package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Status in dracut source package in Resolute:
New
Status in linux source package in Resolute:
New
Bug description:
in ubuntu 24.04 , emmc related modules is default available in
initramsfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.17.0-14-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/core/mmc_block.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/cqhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-acpi.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pltfm.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-uhs2.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-xenon-driver.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci_f_sdh30.ko.zst
In ubuntu 26.04, emmc related modules is not available in initramfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.18.0-9-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
user@localhost:~$ echo $?
1
The missing emmc modules in initramfs unfortunately lead to disk image
of ubuntu26.04 failed to boot in emmc.
user@localhost:~$ lsb_release -rd
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2143030/+subscriptions
[Bug 2143784] Re: Mouse lags at least since previous update (6.17.0-14-generic)
Hi Alex, thank you for your quick analysis. Now I can say the bug can be closed: The bug seems to be caused by hardware - obviously my kvm switch gets old and i need to replace this.
However, your hints are valuable regarding the versions. When I was new to Ubuntu, I had tried to install the graphics card, and then i did some manual work which was not absolutely standard. (probably i'll install ubuntu new again since that graphics is not that new anymore)
Thank you, Stefan
--
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
However, your hints are valuable regarding the versions. When I was new to Ubuntu, I had tried to install the graphics card, and then i did some manual work which was not absolutely standard. (probably i'll install ubuntu new again since that graphics is not that new anymore)
Thank you, Stefan
--
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 2143813] [NEW] Enable CirrusLogic audio solution CS42L45+CS35L63 on more Dell platforms
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
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
Подписаться на:
Комментарии (Atom)