Colin had the hunch that this actually happens if the CPUs do *not* have
anything to do, i. e. want to go into a low freq/power state. We
successfully ran the full stress-ng test suite on the instance without
triggering any of this, but a few minutes after it was done it started
hung processes started to appear again.
We currently run a test whether booting with "nohz=off" works around
that. So far it has survived for some 30 minutes (which is very
promising).
This also has never triggered on a single-CPU instance (m1.small).
** Also affects: auto-package-testing
Importance: Undecided
Status: New
** Changed in: auto-package-testing
Status: New => Triaged
** Changed in: auto-package-testing
Importance: Undecided => Medium
** Changed in: auto-package-testing
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531768
Title:
[arm64] locks up some time after booting
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
