--- Comment From balb...@au1.ibm.com 2016-12-20 22:55 EDT---
Could the Ubuntu team check if this is still an issue with the 4.8 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
--- Comment From balb...@au1.ibm.com 2016-12-20 22:55 EDT---
Could the Ubuntu team check if this is still an issue with the 4.8 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From balb...@au1.ibm.com 2016-07-13 23:04 EDT---
I also added af8e15cc85a253155fdcea707588bf6ddfc0be2e to my diff, just FYI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
--- Comment From balb...@au1.ibm.com 2016-07-12 04:14 EDT---
I backported the oom-reaper changes from v4.5 and I've had good runs so far (2
runs with machine returning to console)
I took aac453635549699c13a84ea1456d5b0e574ef855 + next 7 patches and
removed unsupported bits. I also took
--- Comment From balb...@au1.ibm.com 2016-07-11 00:59 EDT---
Can you please provide links to the sources as well, just to do a quick diff
against the 4.5 working git?
Have we made further progress on bisect?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
--- Comment From balb...@au1.ibm.com 2016-07-10 23:00 EDT---
No luck with the new build shared (just 1 run, I'll try more runs).. More
debugging in progress as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--- Comment From balb...@au1.ibm.com 2016-07-06 20:56 EDT---
>From what I can see the following is the root cause of the issue
cgroup_threadgroup_rwsem almost serializes accesses on the system
1. stress-ng-brk has cgroup_threadgroup_rwsem held in read mode via
copy_process() and does a
--- Comment From balb...@au1.ibm.com 2016-07-01 02:36 EDT---
What is the criteria for forward progress of the stress?
I did a quick check for what processes are OOM'd
In new kernel
2 apport
1 cron
1 dhclient
1 gmain
2 in:imklog
1 (journald)
1 kworker/u160:4
1 rs:main
1 stress-ng
972
--- Comment From heji...@cn.ibm.com 2016-05-27 03:40 EDT---
Hi, where could I get the src/binary of memory_stress_ng. I will try to
reproduce it in local power servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20 matches
Mail list logo
