linux-image-5.15.0-1032-realtime locks up under scheduler test load
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
apparmor (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
New
|
Undecided
|
Unassigned | |||
Kinetic |
New
|
Undecided
|
Unassigned | |||
Lunar |
New
|
Undecided
|
Unassigned | |||
Mantic |
New
|
Undecided
|
Unassigned | |||
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Incomplete
|
Undecided
|
Unassigned | |||
Kinetic |
New
|
Undecided
|
Unassigned | |||
Lunar |
New
|
Undecided
|
Unassigned | |||
Mantic |
Incomplete
|
Low
|
Unassigned |
Bug Description
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
uname -a
Linux jammie-amd64-efi 5.15.0-
x86_64 x86_64 GNU/Linux
free
Mem: 4013888 200984 3439012 1204 373892 3744628
Swap: 4014076 0 4014076
Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake, IBRS):
how to reproduce issue:
git clone https:/
sudo apt-get update
sudo apt-get build-dep stress-ng
sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev libglvnd-dev libgbm-dev
cd stress-ng
make clean
make -j 8
sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m
..wait for all the stressors to get invoked, system becomes unresponsive, can't ^C stress-ng, can't swap consoles on the VM, appears to be hard locked.
Changed in linux (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- linux-image-5.15.0-1032-realtime locksup under scheduler test load + linux-image-5.15.0-1032-realtime locks up under scheduler test load |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2024599
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.