From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Alex Brooks <a.brooks@marathon-robotics.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BAR 0: can't allocate resource
Date: Wed, 6 Jan 2010 13:19:54 -0700 [thread overview]
Message-ID: <201001061319.54436.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <201001061316.21744.a.brooks@marathon-robotics.com>
On Tuesday 05 January 2010 07:16:21 pm Alex Brooks wrote:
> > I don't see any indication that this is a software problem (I know
> > nothing about PC/104, so let me know if you disagree, and why).
>
> I don't have a smoking gun that points at software, it was just my guess
> based on:
> a) all the pieces of hardware work in certain combinations
> b) there's a nasty-looking error message in dmesg
You mentioned two messages. Here's the first:
PCI: BIOS Bug: MCFG area at e0000000 is not reserved in ACPI motherboard resources
PCI: Not using MMCONFIG.
and the second:
PCI: Cannot allocate resource region 0 of device 0000:01:04.0
PCI: Error while updating region 0000:01:04.0/0 (feb00002 != 00000000)
The "Error while updating region" message is because we wrote something
to a BAR, read it back, and they didn't match. I suppose this could be
some kind of config space problem related to the fact that we're not
using MMCONFIG.
Can you try removing the MCFG reservation check, so we do try to use
MMCONFIG? If you do this on a current kernel, we'll also get a little
more debug output about the subsequent resource allocation failure.
Bjorn
next prev parent reply other threads:[~2010-01-06 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201001061305.31635.a.brooks@marathon-robotics.com>
2010-01-06 2:16 ` Alex Brooks
2010-01-06 20:19 ` Bjorn Helgaas [this message]
2010-01-07 1:09 ` Alex Brooks
2010-01-07 5:46 ` Bjorn Helgaas
2010-01-10 3:07 ` Alex Brooks
2010-01-11 21:27 ` Bjorn Helgaas
2010-01-11 21:47 ` Alex Brooks
2010-01-05 9:18 Alex Brooks
2010-01-05 17:33 ` Bjorn Helgaas
2010-01-05 22:19 ` Alex Brooks
2010-01-05 23:00 ` Bjorn Helgaas
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=201001061319.54436.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=a.brooks@marathon-robotics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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
all inboxes | Powered by JetHome®