Re: Problems with MSI-X on ia64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux