I've seen something very similar to this on this platform and I believe
it's a combination of previous regressions tests and the stress-ng
sysinfo test that triggers this. Running the stress-ng stressor after a
clean boot won't trigger this issue.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856900
Title:
stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856900/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
