From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762222AbZFLHcP (ORCPT ); Fri, 12 Jun 2009 03:32:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757405AbZFLHb7 (ORCPT ); Fri, 12 Jun 2009 03:31:59 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:57110 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753024AbZFLHb7 (ORCPT ); Fri, 12 Jun 2009 03:31:59 -0400 Message-ID: <4A3204CA.8070005@cn.fujitsu.com> Date: Fri, 12 Jun 2009 15:33:30 +0800 From: Li Zefan User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Pekka Enberg CC: Ingo Molnar , Yinghai Lu , Christoph Lameter , Linus Torvalds , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, hannes@cmpxchg.org, mpm@selenic.com, npiggin@suse.de, kamezawa.hiroyu@jp.fujitsu.com Subject: Re: [GIT PULL v3] Early boot SLAB for 2.6.31 References: <84144f020906110706y8df301bhd930dc48f3188d3c@mail.gmail.com> <84144f020906110824g7b3981abmdbcf94ae2f9068de@mail.gmail.com> <4A3143E3.3090705@kernel.org> <20090611214342.GA12762@elte.hu> <20090611220307.GA16180@elte.hu> <20090612071703.GA29679@elte.hu> <1244791788.30512.2.camel@penberg-laptop> In-Reply-To: <1244791788.30512.2.camel@penberg-laptop> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Pekka Enberg wrote: > Hi Ingo, > > On Fri, 2009-06-12 at 09:17 +0200, Ingo Molnar wrote: >> Plus i quickly got this crash too: >> >> [ 0.000000] console [tty0] enabled >> [ 0.000000] allocation of page_cgroup was failed. >> [ 0.000000] please try cgroup_disable=memory boot option >> [ 0.000000] Kernel panic - not syncing: Out of memory >> [ 0.000000] Rebooting in 1 seconds..<1>BUG: unable to handle kernel NULL pointer dereference at 0000004c >> [ 0.000000] IP: [] klist_next+0x10/0x8f >> [ 0.000000] *pdpt = 0000000001a8a001 *pde = 0000000000000000 >> [ 0.000000] Thread overran stack, or stack corrupted > > Hmm, does this patch fix it? Hiroyuki, Li, does the oops look familiar to you? > should be the same bug.