Christopher, I did such a test back in March upon request with no response
to my testing results then.  Nor *any* activity, until your recent notes.
Do we have any specific reason or bugfix to believe that this memory issue
has been addressed since then?  Will I get at least a response this time to
my testing results as to next steps?  I ask because this test can take
several days to perform and I will not be able to start it immediately, I
want to make sure its worth our time to do in order to get the most
effective progress on this.

BTW, have you noticed the bug report below?  It seems fairly similar to
what I've been seeing in different kernels/testing as well as has a similar
reproduction method.  In my testing there definitely is the OOM deadlock in
my 2.6 kernel testing while the 3.2 kernel testing seemed to have a
slightly different "deadlock" in believing it had made page freeing
progress when in fact it had not done so.  My upstream kernel testing back
in March had not totally deadlocked, but would "freeze" for long periods of
time.  Here's the kernel.org bug, with no response, that seemed somewhat
similar and could be an indication that me doing upstream testing would not
be all that useful:

https://bugzilla.kernel.org/show_bug.cgi?id=59901


Assuming a positive response for me to still proceed with the upstream
testing you requested, I will first have to reconfirm that my current
testbed can reproduce the issue with the latest 3.2 -51 Ubuntu kernel and
then I will try the upstream kernel you referenced.  So it will be a little
while before I can report on this testing, which took multiple days in the
past.  Nor can I start this testing immediately.  It sure would be nice if
you guys could reproduce this, I thought my info on this score would be
adequate for that.


  -- Marc --



On Fri, Aug 9, 2013 at 7:35 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Marc Hasson, could you please test the latest upstream kernel available
> following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
> additional upstream developers to examine the issue. Please do not test the
> daily folder, but the one all the way at the bottom. Once you've tested the
> upstream kernel, please comment on which kernel version specifically you
> tested. If this bug is fixed in the mainline kernel, please add the
> following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.11-rc4
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> If you are unable to test the mainline kernel, please comment as to why
> specifically you were unable to test it and add the following tags:
> kernel-unable-to-test-upstream
> kernel-unable-to-test-upstream-VERSION-NUMBER
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
>