Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757190AbYLaUX7 (ORCPT ); Wed, 31 Dec 2008 15:23:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753498AbYLaUXv (ORCPT ); Wed, 31 Dec 2008 15:23:51 -0500 Received: from fg-out-1718.google.com ([72.14.220.159]:9430 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751784AbYLaUXu (ORCPT ); Wed, 31 Dec 2008 15:23:50 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=s6TvgnrNYdka33KAEL4JD7j5Gb74bMWKkyUtkp+dsUtHuagmn8WhK1ZN7YD9vs0zbK KwRytcOlOsd18Ryr3UWgbof56XuWmpCKliygx0hQtH0F9dkaFc0ZyXBT0pzfSesCxc8B h5Kir+Wh9PeVOZlPxfTnouBnOG+nPojmQ31P8= Date: Wed, 31 Dec 2008 23:23:46 +0300 From: Cyrill Gorcunov To: david@lang.hm Cc: Andi Kleen , linux-kernel Subject: Re: early exception error Message-ID: <20081231202346.GH20882@localhost> References: <87k59hur5f.fsf@basil.nowhere.org> <20081231093803.GA20882@localhost> <20081231183039.GE20882@localhost> <20081231191214.GF20882@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2070 Lines: 61 [david@lang.hm - Wed, Dec 31, 2008 at 01:18:25PM -0800] > On Wed, 31 Dec 2008, Cyrill Gorcunov wrote: > >> [david@lang.hm - Wed, Dec 31, 2008 at 12:07:33PM -0800] >>> On Wed, 31 Dec 2008, Cyrill Gorcunov wrote: >>> >>>> [david@lang.hm - Wed, Dec 31, 2008 at 11:12:12AM -0800] >>>>> On Wed, 31 Dec 2008, Cyrill Gorcunov wrote: >>>>> >>>>>> [david@lang.hm - Tue, Dec 30, 2008 at 05:39:29PM -0800] >>>>>>> >>>>>>> so it looks like this is in alloc_bootmem_core in both cases. >>>>>>> >>>>>>> David Lang >>>>>>> >>>>>> >>>>>> Along with Andi's proposed earlyprintk=vga I think >>>>>> bootmem_debug option could be usefull here too. >>>>> >>>>> adding bootmem_debug creates so much additonal output that the oops >>>>> scrolls off the screen (except the last 'paragraph' of it) >>>>> >>>>> it looks like it's individual items being allocated (trying to scan it as >>>>> it scrolled by) >>>> >>>> on the picture you sent me i noticed the message >>>> "Your memory is not aligned you need to rebuild your >>>> kernel with bigger NODEMAP SIZE shift=20" and then >>>> srat code complains about "No NUMA code hash function found" >>>> which looks a bit scary. Btw, could you post this picture >>>> on some public resource so NUMA people could check it? >>> >>> http://linux.lang.hm/linux/IMG00030.jpg >>> >>> I'll try rebuilding with a bigger nodemap size and let you know >>> >>> David Lang >>> >> >> also you could just pass numa=off and check if it help. >> (even if it help it would not mean that problem are gone >> but become hidden) > > with numa=off the system looks like it gets a bit further > > http://linux.lang.hm/linux/IMG00031.jpg > > this is with framebuffer disabled, earlyprintk=vga bootmem_debug numa=off > > David Lang > Thanks David, if I recognize correctly now it fails at vfs_caches_init. hmm... - Cyrill - -- 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/