Prev: WARNING: at fs/namespace.c:648 commit_tree+0xf1/0x10b()
Next: [PATCH] Use microsecond granularity for taskstats accounting
From: David Rientjes on 1 Jun 2010 17:00
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.
--
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/
First  |  Prev  | 
Pages: 1 2
Prev: WARNING: at fs/namespace.c:648 commit_tree+0xf1/0x10b()
Next: [PATCH] Use microsecond granularity for taskstats accounting