From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: System Design Works <wsherman@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: PCI device problem - MMCONFIG, cannot allocate resource region, resource collisions
Date: Mon, 21 May 2007 19:03:46 -0700 [thread overview]
Message-ID: <200705211903.46678.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <46524A6D.5050601@gmail.com>
On Monday, May 21, 2007, System Design Works wrote:
> The kernel has a problem allocating resources for my PCI NIC. Here is
> what the kernel is reporting:
>
> # uname -a
> Linux wopr 2.6.20-gentoo-r8 #7 SMP Sun May 20 20:56:56 PDT 2007 i686 AMD
> Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
>
> # dmesg
> ...
> PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
This is actually an unrelated problem. We're a little too conservative
about using MCFG space (though this turns out to be a good thing on some
of my machines), but shouldn't affect the rest of your PCI resource
assignment.
> ...
> PCI: Cannot allocate resource region 0 of device 0000:02:02.0
> ...
> PCI: Device 0000:02:02.0 not available because of resource collisions
> skge: 0000:02:02.0 cannot enable PCI device
> skge: probe of 0000:02:02.0 failed with error -22
> ...
>
> I have seen other posts reporting similar error messages. I would like
> to help resolve this problem, and I can do some testing if needed. More
> info:
>
> Kernel boot params: pci=nomsi
There's a recent thread about PCI resource assignment (sounds like your
BIOS might be buggy btw, or you're somehow running out of space), search
for the title "PCI bridge range sizing bug". You may need the kernel to
reassign the resource for your NIC before you can use it. I think Ivan
has some test patches along these lines.
If you can find out what resource it's colliding with, that might give you
a clue.
Jesse
next prev parent reply other threads:[~2007-05-22 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 1:42 System Design Works
2007-05-22 2:03 ` Jesse Barnes [this message]
2007-05-22 2:36 ` Wayne Sherman
2007-05-22 15:58 ` Jesse Barnes
2007-05-22 23:21 ` Wayne Sherman
2007-05-22 23:31 ` Jesse Barnes
2007-05-23 9:26 ` Ivan Kokshaysky
2007-05-24 0:20 ` Wayne Sherman
2007-05-24 3:08 ` Jesse Barnes
2007-05-24 3:10 ` Jesse Barnes
2007-05-24 10:09 ` Ivan Kokshaysky
2007-05-25 0:27 ` Wayne Sherman
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=200705211903.46678.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=wsherman@gmail.com \
/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
Powered by JetHome