mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Connor Behan <connor.behan@gmail.com>,
	linux-kernel@vger.kernel.org,
	Linux PCI <linux-pci@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Can't allocate resources for PCI video card behind bridge
Date: Thu, 8 Jan 2009 12:26:38 -0800	[thread overview]
Message-ID: <200901081226.38909.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200901082057.00170.rjw@sisk.pl>

On Thursday, January 8, 2009 11:56 am Rafael J. Wysocki wrote:
> Cc-ing linux-pci and Jesse.
>
> On Thursday 08 January 2009, Connor Behan wrote:
> > Hello, I am trying to use two video cards. One is the built in ATI Rage
> > Mobility M3 AGP card which drives the screen of my laptop (Thinkpad a22m
> > 2628-S1U if that matters), the other is the ATI Radeon X1550 PCI card in
> > the Thinkpad Dock II which is supposed to drive an external monitor.
> > X1550 is a PCI-E chipset but my card is a PCI card with an onboard PCI
> > to PCI-E bridge. I first tried this with kernel 2.6.27 as packaged by
> > Archlinux and got the following startup errors:
> >
> > pci 0000:00:04.0: BAR 7: can't allocate resource
> > pci 0000:00:04.0: BAR 8: can't allocate resource
> > pci 0000:00:04.0: BAR 9: can't allocate resource
> >
> > I've seen this problem discussed in the archives and couldn't find what
> > looked like a fix. I WAS able to fix this by loading dock, pci_slot,
> > pci_hotplug and acpiphp and appending pci=assign-busses. However since
> > then I have run a package update to kernel 2.6.27.10 and I am once again
> > getting the same problem even with the same modules and parameters. I
> > have since tried appending irqpoll, pci=bios, pci=routeirq and acpi=off
> > with no success. I have even rolled back my kernel to 2.6.27 (and the
> > headers and a few other packages) setup my system the way it was setup
> > before to the best of my knowledge but I still can't get the PCI card
> > working again. Another subtle change must be responsible.
> >
> > Certain PCI devices in the dock are working such as the Cardbus slots...
> > but I could care less about them... is there a way I could tell the
> > kernel to prioritize the video card and sacrifice Cardbus slots first if
> > it can't allocate enough resources? Also my lspci output shows a large
> > gap 01:00.0 to 06:00.0 so some part of my system must have expected
> > other devices in that range. When I had the video card working it was
> > 02:00.0. I have tried changing the four IRQ numbers in the BIOS but this
> > is pointless at best and sometimes causes my soundcard to be disabled.
> > My dmesg, lspci and (trimmed) kernel config are pasted:
> >
> > dmesg: http://pastebin.com/f3ae15a58
> > lspci: http://pastebin.com/f5d7dee6e
> > .config: http://pastebin.com/fb925760
> >
> > I'm hoping for a solution that doesn't require recompiling the kernel
> > but I definitely would if that's necessary. In any event I'll be much
> > more vigilant about system updates if I get this working again.
> > Thank-you very much for your time.

Can you post the output of lspci -vvv somewhere as well after trying 2.6.28?  
It may be that we want the "don't allocate resources for transparent bridges" 
patch after all:

diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
index ea979f2..586451c 100644
--- a/drivers/pci/setup-bus.c
+++ b/drivers/pci/setup-bus.c
@@ -467,8 +467,12 @@ void __ref pci_bus_size_bridges(struct pci_bus *bus)
                }
        }
 
-       /* The root bus? */
-       if (!bus->self)
+       /*
+        * We don't need to allocate PCI bridging windows
+        * for a root bus (everything bridged) or for a
+        * transparent one.
+        */
+       if (!bus->self || bus->self->transparent)
                return;
 
        switch (bus->self->class >> 8) {


Since in your case it looks like it's incorrectly causing some of your other 
resources to be disabled:

pnp 00:02: io resource (0x22-0x22) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), 
disabling
pnp 00:02: io resource (0x92-0x92) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), 
disabling
pnp 00:02: io resource (0xb2-0xb3) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), 
disabling
pnp 00:0a: io resource (0x2e-0x2f) overlaps 0000:00:04.0 BAR 7 (0x0-0xfff), 
disabling

Sorry but you might have to build a few kernels to help us fix this one. :)

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-01-08 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 19:31 Connor Behan
2009-01-08 19:56 ` Rafael J. Wysocki
2009-01-08 20:26   ` Jesse Barnes [this message]
2009-01-09  0:08     ` Gary Hade
2009-01-09  0:39       ` Connor Behan
2009-01-09 22:30     ` Bjorn Helgaas
2009-01-10 20:09       ` Grant Grundler
2009-01-13  2:42         ` Connor Behan
2009-01-13  3:05           ` Linus Torvalds
2009-01-13 21:23             ` Connor Behan
2009-01-13 21:35               ` Linus Torvalds
2009-01-14  0:14                 ` Connor Behan

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=200901081226.38909.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=connor.behan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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

Powered by JetHome