OK... so I tried three runs of the stress-ng memory test (that has been used successfully on every other system we certify for 16.04) and so far, two of three runs have resulted in the system locking up and a bunch of stack trace data dumped to console.
In both cases, I had to power cycle the system to reboot it into a usable state. All three attempts were 16.04 w/ hwe-edge (4.10) deployed by MAAS. System info: Linux oil-entei 4.10.0-20-generic #22~16.04.1-Ubuntu SMP Thu Apr 20 10:30:58 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux stress-ng: Installed: 0.07.21-1~ppa (We keep an updated version of stress-ng in the cert PPA, it's not modified from Colin's code) I've attached logs (kernel and syslog, other info) in a tarball to this. ** Attachment added: "firestone-stress-ng-failure-logs.tgz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4879180/+files/firestone-stress-ng-failure-logs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
