From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id 6EB948D003B for ; Tue, 19 Apr 2011 13:11:32 -0400 (EDT) Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards From: James Bottomley In-Reply-To: References: <20110415135144.GE8828@tiehlicka.suse.cz> <20110418100131.GD8925@tiehlicka.suse.cz> <20110418135637.5baac204.akpm@linux-foundation.org> <20110419111004.GE21689@tiehlicka.suse.cz> <1303228009.3171.18.camel@mulgrave.site> Content-Type: text/plain; charset="UTF-8" Date: Tue, 19 Apr 2011 12:11:28 -0500 Message-ID: <1303233088.3171.26.camel@mulgrave.site> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Pekka Enberg Cc: Michal Hocko , Andrew Morton , Hugh Dickins , linux-mm@kvack.org, LKML , linux-parisc@vger.kernel.org, Christoph Lameter , David Rientjes On Tue, 2011-04-19 at 20:05 +0300, Pekka Enberg wrote: > > It seems to be a random intermittent mm crash because the next reboot > > crashed with the same trace but after the fsck had completed and the > > third came up to the login prompt. > > Looks like a genuine SLUB problem on parisc. Christoph? Looking through the slub code, it seems to be making invalid assumptions. All of the node stuff is dependent on CONFIG_NUMA. However, we're CONFIG_DISCONTIGMEM (with CONFIG_NUMA not set): on the machines I and Dave Anglin have, our physical memory ranges are 0-1GB and 64-65GB, so I think slub crashes when we get a page from the high memory range ... because it's not expecting a non-zero node number. James -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org