Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759416AbZLOUmZ (ORCPT ); Tue, 15 Dec 2009 15:42:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753608AbZLOUmX (ORCPT ); Tue, 15 Dec 2009 15:42:23 -0500 Received: from 0122700014.0.fullrate.dk ([95.166.99.235]:41617 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752641AbZLOUmW (ORCPT ); Tue, 15 Dec 2009 15:42:22 -0500 Date: Tue, 15 Dec 2009 21:42:21 +0100 From: Jens Axboe To: Yinghai Lu Cc: Jesse Barnes , Linux Kernel , mingo@elte.hu, rdreier@cisco.com, Suresh Siddha , "linux-pci@vger.kernel.org" , "H. Peter Anvin" , Huang Ying Subject: Re: kexec boot regression Message-ID: <20091215204221.GZ28252@kernel.dk> References: <20091215123951.GD28252@kernel.dk> <4B278734.2040704@kernel.org> <20091215141105.GK28252@kernel.dk> <4B27D7E9.4030105@kernel.org> <20091215194319.GT28252@kernel.dk> <4B27E817.6030705@kernel.org> <20091215195111.GV28252@kernel.dk> <4B27EE38.1050103@kernel.org> <20091215201909.GY28252@kernel.dk> <4B27EFC2.1000505@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B27EFC2.1000505@kernel.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1505 Lines: 43 On Tue, Dec 15 2009, Yinghai Lu wrote: > Jens Axboe wrote: > > On Tue, Dec 15 2009, Yinghai Lu wrote: > >> Jens Axboe wrote: > >>> On Tue, Dec 15 2009, Yinghai Lu wrote: > >>>> Jens Axboe wrote: > >>>>> On Tue, Dec 15 2009, Yinghai Lu wrote: > >>>>>> [PATCH] x86/pci: intel ioh bus num reg accessing fix > >>>>>> > >>>>>> it is above 0x100, so if mmconf is not enable, need to skip it > >>>>> This works, it kexecs kernels fine. But since 2.6.32 doesn't have the > >>>>> mmconf problem to begin with, are we now just working around the issue? > >>>>> SRAT still reports issues, numa doesn't work. > >>>> that patch will be bullet proof... we need it. > >>>> > >>>> also still need to figure out why memmap range is not passed properly. > >>>> > >>>> do you mean 2.6.32 kexec 2.6.32 it have worked mmconf and numa in > >>>> second kernel? > >>> Yes, 2.6.32 booted and 2.6.32 kexec'ed works just fine, no SRAT > >>> complaints and NUMA works fine. > >> do you need > >> memmap=62G@4G > >> in this case? > > > > Yes, I've needed that always. > > good, > > can you enable debug option in kexec to see why kexec can not pass > whole 38? range to second kernel? Not getting any output so far, -d doesn't do much. Poking around in the source... -- Jens Axboe -- 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/