From: Robert Hancock <hancockr@shaw.ca>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Karl Bellve <Karl.Bellve@umassmed.edu>,
linux-kernel@vger.kernel.org
Subject: Re: PCI: Unable to reserve mem region problem
Date: Mon, 10 Sep 2007 19:44:32 -0600 [thread overview]
Message-ID: <46E5F300.20602@shaw.ca> (raw)
In-Reply-To: <fa.xf8XcHy8Nla3C3Q0MmArV00z04k@ifi.uio.no>
Chuck Ebbert wrote:
> On 09/05/2007 08:31 PM, Alan Cox wrote:
>> On Wed, 05 Sep 2007 10:32:38 -0400
>> "Karl Bellve" <Karl.Bellve@umassmed.edu> wrote:
>>
>>> Please CC any response. Thanks.
>>>
>>> I am having an issue with a Supermicro h8dce motherboard and failure to
>>> recognize a 5th SATA drive after upgrading to Fedora 7.
>> Can you send me an lspci -vvxxx so that I can look into this. Might be a
>> few days with the kernel summit but it should give a clue and may be
>> linked to ADMA mode
>
> It's in RH bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=280641
The last BAR on the nForce4 ADMA controllers on this board are at
0xdfefe000 and 0xdfefd000. But it looks like PnP ACPI is also reserving
those memory ranges:
Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
0xdfefd000-0xdfefd3ff has been reserved
Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range
0xdfefe000-0xdfefe3ff has been reserved
Which I very much doubt it should be doing, the BIOS doesn't need to
reserve PCI BAR ranges in the ACPI tables. This sounds like a BIOS bug.
You might want to check for an update from Supermicro.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-09-11 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.kIR1dSmxlPM+uRVmi9kPkHkX/W8@ifi.uio.no>
[not found] ` <fa.mWCFmDlYQmMO/aBFdKFbo8OVII4@ifi.uio.no>
[not found] ` <fa.xf8XcHy8Nla3C3Q0MmArV00z04k@ifi.uio.no>
2007-09-11 1:44 ` Robert Hancock [this message]
2007-09-11 10:16 ` PCI: Unable to reserve mem region problem Alan Cox
2007-09-05 14:32 Karl Bellve
2007-09-05 17:35 ` Chuck Ebbert
2007-09-06 0:31 ` Alan Cox
2007-09-07 14:56 ` Chuck Ebbert
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=46E5F300.20602@shaw.ca \
--to=hancockr@shaw.ca \
--cc=Karl.Bellve@umassmed.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=linux-kernel@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