From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932392AbYDOVI0 (ORCPT ); Tue, 15 Apr 2008 17:08:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754217AbYDOVIR (ORCPT ); Tue, 15 Apr 2008 17:08:17 -0400 Received: from relay2.sgi.com ([192.48.171.30]:32937 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753855AbYDOVIR (ORCPT ); Tue, 15 Apr 2008 17:08:17 -0400 Date: Tue, 15 Apr 2008 14:08:14 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Ingo Molnar cc: Linus Torvalds , Pekka Enberg , linux-kernel@vger.kernel.org, Mel Gorman , Nick Piggin , Andrew Morton , "Rafael J. Wysocki" , Yinghai.Lu@sun.com, apw@shadowen.org, travis@sgi.com, KAMEZAWA Hiroyuki Subject: Re: [bug] SLUB + mm/slab.c boot crash in -rc9 In-Reply-To: <20080415205820.GC31645@elte.hu> Message-ID: References: <20080415161532.GA15088@elte.hu> <20080415195430.GA23015@elte.hu> <20080415201734.GA25628@elte.hu> <20080415202805.GA26880@elte.hu> <20080415203405.GA27958@elte.hu> <20080415204208.GA30432@elte.hu> <20080415205820.GC31645@elte.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 15 Apr 2008, Ingo Molnar wrote: > and the bug pattern seems to be memory corruption - not memory > exhaustion. SLUB does not do a memory allocation where it fails here but simply accesses per cpu information that is expected to be already zeroed. > i.e. we allocated RAM but it got corrupted after allocation. In some situations we are screwing up the per cpu data handling on 32 bit x86? Adding Mike. This looks like the per cpu area overlaps with something else?