** Tags removed: blocks-hwcert-server
--
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
** Tags added: cscc
--
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:
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => Fix Released
--
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
** Changed in: plainbox-provider-checkbox
Milestone: future => 0.40.0
--
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
** Changed in: plainbox-provider-checkbox
Status: Confirmed => Fix Committed
--
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
resetting all the tasks to confirmed, rather than Incomplete as I've
tested and am still waiting for a resolution or whatever.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux
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
OK, I have a Firestone available, so I'm re-trying this with a cycle of
10 runs to see what happens. Currently using 16.04 w/ HWE-Edge (4.10)
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: plainbox-provider-checkbox
Milestone:
** Changed in: plainbox-provider-checkbox
Status: Fix Released => Confirmed
** Changed in: plainbox-provider-checkbox
Assignee: Mike Rushton (leftyfb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue, or similar symptoms doesn't seem to be fixed. This is with
stock kernel, stock stress-ng but with the suggested changes to the
memory_stress_ng test script. The machine locks up completely maybe 1
out of 5-10 runs. See attached dmesg for errors.
Kernel: 4.4.0-64-generic-85-Ubuntu
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => Fix Released
--
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
** Changed in: plainbox-provider-checkbox
Milestone: 0.36.0 => 0.35.0
--
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
Ok, so we're now using stress-ng 0.07.21 which resolved a lot of issues
and have also adopted Colin's suggestions into our wrapper script to
modify how stress-ng is being called and culled.
This seems to resolve the problems that led to this.
** Also affects: plainbox-provider-checkbox
** Merge proposal linked:
https://code.launchpad.net/~leftyfb/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/318977
--
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:
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Xenial)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Yakkety)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
**
We're getting zombies here which aren't being reaped:
130428 ?Z 0:00 [stress-ng-brk]
130432 ?Z 0:00 [stress-ng-brk]
130434 ?Z 0:00 [stress-ng-brk]
130436 ?Z 0:00 [stress-ng-brk]
The reason for this is that memory stressors like brk have a
output of stress_ng test running on Power 8 Tuleta LPAR
** Attachment added: "3.19.0-15-generic-15-Ubuntu.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788536/+files/3.19.0-15-generic-15-Ubuntu.log
--
You received this bug notification because you are a
dmesg output while stress_ng test was running on Power 8 Tuleta LPAR
** Attachment added: "dmesg2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788537/+files/dmesg2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
`ps -ax` output while stress_ng test was running on Power 8 Tuleta LPAR
** Attachment added: "ps2.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788538/+files/ps2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Balibir, the v4.8 final kernel is now available and can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
The latest upstream stable 4.4 kernel is also avaiable from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.23
--
You received this bug notification because you
FYI, I think the patch made it to 4.4 stable as well
--
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
Sure, we can wait for 4.8-rc7. It should be available on Monday. I'll
post a link to the download location once it's available.
--
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:
Can we build the latest 4.8, may be we should wait for 4.8-rc7. I've got
all the fixes upstream, with the latest being
135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Balbir, Kalpana,
I can build the kernel for you. Can you post a list of all the patches
you would like included? That way we ensure they are all included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1. Can we get the configurations of the machines.
XML files for all 4 machines with hardware information from the
certification process will be attached in the next few comments
2. The first column is the number of times the test ran?
Yes
4. Did any of the tests result in system hang? Can we
** Attachment added: "tuleta.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740354/+files/tuleta.xml
--
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:
** Attachment added: "gulpin.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740353/+files/gulpin.xml
--
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:
** Attachment added: "alpine.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740352/+files/alpine.xml
--
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:
Can we please get answers to 1, 2 and 4 for comment #128. Also Kalpana
has a request for a new kernel build.
Thanks,
--
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
** Tags removed: kernel-key
--
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:
Sorry, I should have taken out the 4.4.0-31 tests. That test was not
using stress-ng but our original memory stress test.
--
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:
Thank you for the excellent summary. Questions
1. Can we get the configurations of the machines.
2. The first column is the number of times the test ran?
3. I see that 4.4.0-31-generic-50-Ubuntu passed on all machines across several
runs, is that true?
4. Did any of the tests result in system
Attached is the cultivation of all the kernel testing we have done.
** Attachment added: "Power Testing Result.pdf"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4732427/+files/Power%20Testing%20Result.pdf
--
You received this bug notification because you are a
Joseph: Is it possible for you to post test kernel with Balbir's patches ?
and place them at earlier location -
http://kernel.ubuntu.com/~jsalisbury/lp1573062/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just posted another patch @ http://www.mail-archive.com/linux-
ker...@vger.kernel.org/msg1219903.html, I am testing this patch at the
moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
This comment is to inform you that mirroring has been disabled between
Launchpad bug 1573062 and LTC bug 141723 due to the size of this LP bug
attachments.
If you want to make this LP bug bridgeable again, I suggest you to
remove unwanted attachments or perhaps to compress some of the existing
** Tags removed: performing-bisect
** Tags added: kernel-key
--
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
Thanks Jeff. I see that the ARM64 might have failed -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610320
Can we know the git commit id that fixed the ARM64 failure in mainline?
BTW, could you please share the full machine configurations -
threads+RAM+swap for each of the other
Just an additional data point, I ran this test (using Mike's script in a
loop) on other architectures:
amd64 bare metal: 30 times 4.4.0, no failures
amd64 virtual machine: 30 times, 4.4.0, no failures
s390 4GB RAM: 40 times on both 4.4.0-31 and 4.7.0, no failures
s390 20GB RAM: 40 times on both
** Summary changed:
- memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
+ memory_stress_ng failing for Power architecture for 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
40 matches
Mail list logo
