From: Kyle Rose <krose@krose.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: "PCI: Cannot allocate resource region" error misleading (with patch)
Date: Sat, 15 Nov 2003 14:44:56 -0500 [thread overview]
Message-ID: <87llqhs9fr.fsf@nausicaa.krose.org> (raw)
It turns out that this error typically indicates that the resource is
being remapped elsewhere, but no indication is given of the remapping,
leading the naive user (e.g., me) to believe no memory was mapped at
all. Perhaps a reasonable patch would be:
--- linux-2.6.0-test9/arch/i386/pci/i386.c.orig 2003-11-15 14:17:30.000000000 -0500
+++ linux-2.6.0-test9/arch/i386/pci/i386.c 2003-11-15 14:22:45.000000000 -0500
@@ -143,7 +143,7 @@
r->start, r->end, r->flags, disabled, pass);
pr = pci_find_parent_resource(dev, r);
if (!pr || request_resource(pr, r) < 0) {
- printk(KERN_ERR "PCI: Cannot allocate resource region %d of device %s\n", idx, pci_name(dev));
+ printk(KERN_ERR "PCI: Cannot allocate resource region %d of device %s (requested %08lx-%08lx); deferring reassignment\n", idx, pci_name(dev), r->start, r->end);
/* We'll assign a new address later */
r->end -= r->start;
r->start = 0;
@@ -192,8 +192,11 @@
* the BIOS forgot to do so or because we have decided the old
* address was unusable for some reason.
*/
- if (!r->start && r->end)
- pci_assign_resource(dev, idx);
+ if (!r->start && r->end) {
+ if (!pci_assign_resource(dev, idx)) {
+ printk(KERN_ERR "PCI: Reassigned region %d of device %s to %08lx-%08lx\n", idx, pci_name(dev), r->start, r->end);
+ }
+ }
}
if (pci_probe & PCI_ASSIGN_ROMS) {
Of course, I haven't come up with a solution to my original problem,
but I'm inclined the believe it originates with the nVidia
closed-source driver instead of with the kernel, since the open source
nv XFree86 driver doesn't exhibit the same set of problems (e.g., DVD
playback is fine), although its set of problems is likely to be at
least as large. If anyone has any leads or can offer any insight, it
would be greatly appreciated.
Cheers,
Kyle
reply other threads:[~2003-11-15 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87llqhs9fr.fsf@nausicaa.krose.org \
--to=krose@krose.org \
--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
all inboxes | Powered by JetHome®