Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754043AbZLAR1Q (ORCPT ); Tue, 1 Dec 2009 12:27:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753785AbZLAR1O (ORCPT ); Tue, 1 Dec 2009 12:27:14 -0500 Received: from nlpi157.sbcis.sbc.com ([207.115.36.171]:60623 "EHLO nlpi157.prodigy.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752553AbZLAR1D (ORCPT ); Tue, 1 Dec 2009 12:27:03 -0500 Date: Tue, 1 Dec 2009 11:26:37 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@router.home To: Mel Gorman cc: David John , linux-kernel@vger.kernel.org, Jonathan Miles , Pekka Enberg Subject: Re: OOM kernel behaviour In-Reply-To: <4B154E10.7050300@xenontk.org> Message-ID: References: <4B1402FC.80307@cybus.co.uk> <4B1537CA.7020107@xenontk.org> <4B154E10.7050300@xenontk.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 758 Lines: 16 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/