From: dave b on
On 2 June 2010 06:52, David Rientjes <rientjes(a)google.com> wrote:
> On Thu, 27 May 2010, dave b wrote:
>
>> That was just a simple test case with dd. That test case might be
>> invalid - but it is trying to trigger out of memory - doing this any
>> other way still causes the problem. I note that playing with some bios
>> settings I was actually able to trigger what appeared to be graphics
>> corruption issues when I launched kde applications ... nothing shows
>> up in dmesg so this might just be a conflict between xorg and the
>> kernel with those bios settings...
>>
>> Anyway, This is no longer a 'problem' for me since I disabled
>> overcommit and altered the values for dirty_ratio and
>> dirty_background_ratio - and I cannot trigger it.
>>
>
> Disabling overcommit should always do it, but I'd be interested to know if
> restoring dirty_ratio to 40 would help your usecase.
>
Actually it turns out on 2.6.34.1 I can trigger this issue. What it
really is, is that linux doesn't invoke the oom killer when it should
and kill something off. This is *really* annoying.

I used the follow script - (on 2.6.34.1)
cat ./scripts/disable_over_commit
#!/bin/bash
echo 2 > /proc/sys/vm/overcommit_memory
echo 40 > /proc/sys/vm/dirty_ratio
echo 5 > /proc/sys/vm/dirty_background_ratio

And I was still able to reproduce this bug.
Here is some c code to trigger the condition I am talking about.


#include <stdlib.h>
#include <stdio.h>

int main(void)
{
while(1)
{
malloc(1000);
}

return 0;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: David Rientjes on
On Tue, 27 Jul 2010, dave b wrote:

> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
> really is, is that linux doesn't invoke the oom killer when it should
> and kill something off. This is *really* annoying.
>

I'm not exactly sure what you're referring to, it's been two months and
you're using a new kernel and now you're saying that the oom killer isn't
being utilized when the original problem statement was that it was killing
things inappropriately?

> I used the follow script - (on 2.6.34.1)
> cat ./scripts/disable_over_commit
> #!/bin/bash
> echo 2 > /proc/sys/vm/overcommit_memory
> echo 40 > /proc/sys/vm/dirty_ratio
> echo 5 > /proc/sys/vm/dirty_background_ratio
>
> And I was still able to reproduce this bug.
> Here is some c code to trigger the condition I am talking about.
>
>
> #include <stdlib.h>
> #include <stdio.h>
>
> int main(void)
> {
> while(1)
> {
> malloc(1000);
> }
>
> return 0;
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: dave b on
On 27 July 2010 08:12, David Rientjes <rientjes(a)google.com> wrote:
> On Tue, 27 Jul 2010, dave b wrote:
>
>> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
>> really is, is that linux doesn't invoke the oom killer when it should
>> and kill something off. This is *really* annoying.
>>
>
> I'm not exactly sure what you're referring to, it's been two months and
> you're using a new kernel and now you're saying that the oom killer isn't
> being utilized when the original problem statement was that it was killing
> things inappropriately?

Sorry about the timespan :(
Well actually it is the same issue. Originally the oom killer wasn't
being invoked and now the problem is still it isn't invoked - it
doesn't come and kill things - my desktop just sits :)
I have since replaced the hard disk - which I thought could be the
issue. I am thinking that because I have shared graphics not using KMS
- with intel graphics - this may be the root of the cause.

--
All things that are, are with more spirit chased than enjoyed. --
Shakespeare, "Merchant of Venice"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: KOSAKI Motohiro on
> On 27 July 2010 08:12, David Rientjes <rientjes(a)google.com> wrote:
> > On Tue, 27 Jul 2010, dave b wrote:
> >
> >> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
> >> really is, is that linux doesn't invoke the oom killer when it should
> >> and kill something off. This is *really* annoying.
> >>
> >
> > I'm not exactly sure what you're referring to, it's been two months and
> > you're using a new kernel and now you're saying that the oom killer isn't
> > being utilized when the original problem statement was that it was killing
> > things inappropriately?
>
> Sorry about the timespan :(
> Well actually it is the same issue. Originally the oom killer wasn't
> being invoked and now the problem is still it isn't invoked - it
> doesn't come and kill things - my desktop just sits :)
> I have since replaced the hard disk - which I thought could be the
> issue. I am thinking that because I have shared graphics not using KMS
> - with intel graphics - this may be the root of the cause.

Do you mean the issue will be gone if disabling intel graphics?
if so, we need intel graphics driver folks help. sorry, linux-mm folks don't
know intel graphics detail.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: dave b on
On 27 July 2010 14:46, KOSAKI Motohiro <kosaki.motohiro(a)jp.fujitsu.com> wrote:
>> On 27 July 2010 08:12, David Rientjes <rientjes(a)google.com> wrote:
>> > On Tue, 27 Jul 2010, dave b wrote:
>> >
>> >> Actually it turns out on 2.6.34.1 I can trigger this issue. What it
>> >> really is, is that linux doesn't invoke the oom killer when it should
>> >> and kill something off. This is *really* annoying.
>> >>
>> >
>> > I'm not exactly sure what you're referring to, it's been two months and
>> > you're using a new kernel and now you're saying that the oom killer isn't
>> > being utilized when the original problem statement was that it was killing
>> > things inappropriately?
>>
>> Sorry about the timespan :(
>> Well actually it is the same issue. Originally the oom killer wasn't
>> being invoked and now the problem is still it isn't invoked - it
>> doesn't come and kill things - my desktop just sits :)
>> I have since replaced the hard disk - which I thought could be the
>> issue. I am thinking that because I have shared graphics not using KMS
>> - with intel graphics - this may be the root of the cause.
>
> Do you mean the issue will be gone if disabling intel graphics?
> if so, we need intel graphics driver folks help. sorry, linux-mm folks don't
> know intel graphics detail.

Well the only other system I have running the 2.6.34.1 kernel atm is
an arm based system.
I originally sent this to the kernel list and was told I should
probably forward it to the mm list.
It may be a general issue or it could just be specific :)

--
"Not Hercules could have knock'd out his brains, for he had none." --
Shakespeare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/