From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wedgwood Date: Fri, 17 Feb 2006 08:46:05 +0000 Subject: Re: Problems with MSI-X on ia64 Message-Id: <20060217084605.GG4523@taniwha.stupidest.org> List-Id: References: <20060217075829.GB22451@esmail.cup.hp.com> In-Reply-To: <20060217075829.GB22451@esmail.cup.hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Grant Grundler Cc: Greg KH , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, linux-ia64@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, "Miller, Mike (OS Dev)" , Jesse Barnes On Thu, Feb 16, 2006 at 11:58:29PM -0800, Grant Grundler wrote: > The root cause is the use of u32 to describe a PCI resource "start". > phys_addr needs to be "unsigned long". More details in Log entry > below. That won't always suffice. I have machines at work that will place some PCI resources above the 4GB boundary even when booting in '32-bit OS' mode (there is a BIOS option for this but no matter the setting some resources always end up above 4GB). I've heard from others they've also been hit by this (with 64-bit kernels it's fine). I guess it could be argued that it's a BIOS bug, I'm not entirely sure what to thing, Windows seems to deal with it.