MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19014.36968.722952.729071@pilspetsen.it.uu.se>
Date: Sat, 27 Jun 2009 23:34:32 +0200
From: Mikael Pettersson <mikpe@it.uu.se>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
       Grant Grundler <grundler@parisc-linux.org>,
       linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [BUG 2.6.31-rc1] HIGHMEM64G causes hang in PCI init on 32-bit
 x86
In-Reply-To: <4A46728B.80301@zytor.com>
References: <200906261559.n5QFxJH8027336@pilspetsen.it.uu.se>
	<19013.29264.623540.275538@pilspetsen.it.uu.se>
	<20090627042556.GA31085@lackof.org>
	<19013.59767.139956.971375@pilspetsen.it.uu.se>
	<4A46728B.80301@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 26

H. Peter Anvin writes:
 > Mikael Pettersson wrote:
 > > 
 > > Sure. This is from 2.6.31-rc1 with the commit commented out and
 > > replaced by a debug printk:
 > > 
 > > identify_cpu: ->x86_phys_bits == 36, would change iomem_resource.end from 0xffffffffffffffff to 0x0000000fffffffff
 > > 
 > > which looks correct for HIGHMEM64G.
 > 
 > OK, I'm going to revert the checkin... however, we still need to figure
 > out what the right answer here is, and why this broke (and why none of
 > my tests showed this failure...)
 > 
 > However, it is clear that the answer is more complex than we originally
 > anticipated.  Mikael, would you be willing to run some experiments over
 > the near future?

Yes

/Mikael
--
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/