mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, 06 Jan 2010 22:46:16 -0700	[thread overview]
Message-ID: <1262843176.27608.2.camel@dc7800.home> (raw)
In-Reply-To: <201001071209.01975.a.brooks@marathon-robotics.com>

On Thu, 2010-01-07 at 12:09 +1100, Alex Brooks wrote:
> > 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.
> 
> I did this on my 2.6.26 kernel (is this current enough or would a later kernel 
> be better?) and attached the dmesg output.

Looks like you got the same errors when accessing config space as
before.

I was hoping for a kernel directly from Linus' git repo, e.g.,
2.6.33-rc3; I don't think the debug output I'm thinking about went in
until after 2.6.32 was released.

Bjorn



  reply	other threads:[~2010-01-07  5:51 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
2010-01-07  1:09     ` Alex Brooks
2010-01-07  5:46       ` Bjorn Helgaas [this message]
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=1262843176.27608.2.camel@dc7800.home \
    --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®