[lkml]   [2009]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: OOM kernel behaviour
On 12/07/2009 08:29 PM, Mel Gorman wrote:
> On Mon, Dec 07, 2009 at 11:04:24AM +0530, David John wrote:
>> On 12/02/2009 09:25 PM, Mel Gorman wrote:
>>> On Tue, Dec 01, 2009 at 11:26:37AM -0600, Christoph Lameter wrote:
>>>> On Tue, 1 Dec 2009, David John wrote:
>>>>> Here are three logs from three days. Log3.txt is today's log and the OOM
>>>>> killer murdered Thunderbird as I was attempting to write this message.
>>>>> The kernel config is also attached.
>>>> Hmmm... This is all caused by the HIGHMEM zone freecount going beyond min
>>>> which then triggers reclaim which for some reason fails (should not there
>>>> is sufficient material there to reclaim). There is enough memory in the
>>>> NORMAL zone. Wonder if something broke in 2.6.31 in reclaim? Mel?
>>> I'm not aware of breakage of that level, nor do I believe the page
>>> allocator problems are related to this bug.
>>> However, I just took a look at the logs from the three days and I see
>>> things like
>>> Nov 25 23:58:53 avalanche kernel: Free swap = 0kB
>>> Nov 25 23:58:53 avalanche kernel: Total swap = 2048248kB
>>> Something on that system is leaking badly. Do something like
>>> ps aux --sort vsz
>>> and see what process has gone mental and is consuming all of swap. It's
>>> possible that the OOM killer is triggering too easily but it's possible
>>> that a delayed triggering of the OOM killer would have been just that -
>>> a delay. Eventually all memory and all swap would be used.
>> It is a leak in Compiz. Killing and restarting Compiz frees up the swap.
>> The issue is better in 2.6.32 for some reason. The funny thing is I've
>> been using Compiz with 2.6.31 for a couple of months now, with no
>> updates to either, so I'm not sure what triggered this problem.
> This is a total stab in the dark. Is it possible there was a change in
> DRM between 2.6.31 and 2.6.32 that means resources (like textures) are
> no longer been freed properly? This might be particularly the case if
> you were not using KMS before but you are now.
> If something like that has changed, it should probably be brought to the
> attention of David Airlie.
> If nothing in that regard has changed, I don't have a better alternative
> theory as to why it's leaking now.

No, I've had KMS enabled from before 2.6.31. There aren't any major
changes like that from 2.6.31 to 32. It's basically the same config.
Note that the same leak is present on 32, it's just that it takes
much longer to trigger the OOM killer.

I'm guessing it's an internal Compiz problem that I triggered while
changing some Compiz configuration, or it could be a leak in one of the


 \ /
  Last update: 2009-12-08 04:43    [W:0.067 / U:4.708 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site