From: Chris Wedgwood <cw@f00f.org>
To: Grant Grundler <iod00d@hp.com>
Cc: Greg KH <gregkh@suse.de>,
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)" <Mike.Miller@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Problems with MSI-X on ia64
Date: Fri, 17 Feb 2006 00:46:05 -0800 [thread overview]
Message-ID: <20060217084605.GG4523@taniwha.stupidest.org> (raw)
In-Reply-To: <20060217075829.GB22451@esmail.cup.hp.com>
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.
next prev parent reply other threads:[~2006-02-17 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:14 Problems with MSI-X on ia64 Miller, Mike (OS Dev)
2006-01-26 17:24 ` Mark Maule
2006-01-26 20:24 ` Grant Grundler
2006-02-17 7:58 ` Grant Grundler
2006-02-17 8:46 ` Chris Wedgwood [this message]
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 16:36 ` Grant Grundler
2006-02-17 19:10 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 20:37 Miller, Mike (OS Dev)
2006-01-27 4:37 ` Greg KH
2006-01-27 15:34 Miller, Mike (OS Dev)
2006-02-17 19:52 Luck, Tony
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:21 ` Roland Dreier
2006-02-21 20:21 Miller, Mike (OS Dev)
2006-02-25 16:23 ` Grant Grundler
2006-02-27 18:36 Miller, Mike (OS Dev)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060217084605.GG4523@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=Mike.Miller@hp.com \
--cc=gregkh@suse.de \
--cc=iod00d@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox