** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308474
Title:
CPU-intensive processes killed by OS
To manage notifications about this bug go to:
https://b
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308474
Title:
CPU-intensive processes killed by OS
To manage notifications about this bug go to:
https://bug
On 04/16/2014 09:36 PM, Joseph Salisbury wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.15 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'ker
kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308474
Title:
CPU-intensive processes killed by OS
To manage notifications about this bug go to:
https://bugs.launchpad.net
apport information
** Description changed:
When testing some algorithm I ran the test program several times with
different parameters. It was to be expected that each run takes about
four hours, and to utilize the capacities of my computer (4 CPUs) I
started the program 4 times running in
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
apport information
** Tags added: apport-collected
** Description changed:
When testing some algorithm I ran the test program several times with
different parameters. It was to be expected that each run takes about
four hours, and to utilize the capacities of my computer (4 CPUs) I
start
