Following a suggestion in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695182#513
I tested older kernels: seems that PAE was always (or at least back to
karmic 2.6.31) prone to OOM under the sleep test.
Curiously I found that non-PAE kernels of that vintage might also OOM,
maybe depending on
Should a CVE be assigned, seeing how this issue causes a DoS?
And then a USN/DSA should be issued when eventually solved.
Should it be reported to SecurityFocus and obtain a BID?
Could the Status be changed to something better than Expired?
Would some kind soul confirm and explicitly state that
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098961
Title:
PAE regression: OOM with just a few sleeps
To manage notifications about this bug go to:
Now at Ubuntu VERSION=14.04.1 LTS, Trusty Tahr seems that the
one-and-only x86 kernel offered is with PAE, so I cannot easily
demonstrate the difference between PAE and non-PAE kernels.
With the PAE kernel, my machine produces an OOM crash with the
test command
bash -c 'n=0; while [ $n -lt
Expired? That is weird... how come it did not expire between comments#18
and comments#19, between 16Jan and 6Aug?
Anyway the bug is alive... as anyone could easily test, with a simple
bash -c 'n=0; while [ $n -lt 33000 ]; do sleep 600 ((n=n+1));
((m=n%500)); if [ $m -lt 1 ]; then echo -n $n -
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098961
Dear Christopher,
About testing the latest kernel (with a development Ubuntu, which may be
unrelated to the kernel bug): would not it be better for you to test?
The feedback to you would be more immediate, allowing you to test kernel
tuneables, or maybe tweak/fix/patch the kernel sources.
Paul Szabo, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal
Dear Christopher,
... test the latest upstream kernel ...
Did not I do that already in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098961/comments/18
? Is there really a need to re-test? (Yes I know that the kernel now is
different
from what I tested... but unless you know that
Paul Szabo, as per
http://www.dell.com/support/drivers/us/en/19/driverdetails?driverid=R157196
an update is available for your BIOS (2.4.0). If you update to this,
does it change anything?
If not, could you please both specify what happened, and provide the output of
the following terminal
Tested latest upstream kernel: the mainline kernel does NOT fix the bug.
Tag 'kernel-bug-exists-upstream' added, bug marked as 'Confirmed'.
More verbose blurb below.
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.8 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
apport information
** Tags added: apport-collected
** Description changed:
There is a spurious OOM issue with PAE kernel: it will suffer an OOM
crash just by running a few processes.
Please see also
http://bugs.debian.org/695182
and discussion on linux...@kvack.org e.g.
13 matches
Mail list logo
