mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Connor Behan <connor.behan@gmail.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	Linux PCI <linux-pci@vger.kernel.org>,
	Gary Hade <garyhade@us.ibm.com>
Subject: Re: Can't allocate resources for PCI video card behind bridge
Date: Tue, 13 Jan 2009 13:35:44 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0901131331330.6528@localhost.localdomain> (raw)
In-Reply-To: <496D0653.3040709@gmail.com>



On Tue, 13 Jan 2009, Connor Behan wrote:
>
> I was about to say that the kernel where this worked once doesn't allow this
> to work again. I downgraded to 2.6.27 and got the same problem. But then I
> also downgraded udev, mkinitcpio, lilo, device-mapper, pciutils and hwdetect
> and reset the defaults on my BIOS and took out pci=assign-busses and then the
> card started working.

Ok, can you now try to upgrade just the kernel? IOW, it would be good to 
try to figure out what it is that triggers this problem.

> dmesg: http://pastebin.com/m68dd0ce
> lspci: http://pastebin.com/m4c01d354

Yes, now I see a new bridge:

	08:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa) (prog-if 00 [Normal decode])

and behind this bridge is this:

	09:00.0 VGA compatible controller: ATI Technologies Inc RV505 [Radeon X1550 Series] (prog-if 00 [VGA controller])
	09:00.1 Display controller: ATI Technologies Inc RV505 [Radeon X1550 Series] (Secondary)

> It's quite a bit different from when I remember it working the other time. The
> errors on BARs 7, 8 and 9 still show up and the card is on bus 09.

Yup. It's all ok. 

> However after I did this I updated all those packages to the newest 
> versions except I did so one at a time not all at once. Now I'm up to 
> date and still have this card working. So I'm sorry to bother you with 
> this, the kernel does not need to be patched for this at all. It's 
> either a BIOS problem or a distro problem caused by updating too many 
> packages at once. Either way it's fixed now. Thanks alot.

Well, your dmesg is now from a 2.6.27 kernel, so I'd like to double-check 
and verify that upgrading the kernel really works now. It does sound like 
some non-kernel-related issue, but still..

		Linus

  reply	other threads:[~2009-01-13 21:37 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
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 [this message]
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=alpine.LFD.2.00.0901131331330.6528@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=connor.behan@gmail.com \
    --cc=garyhade@us.ibm.com \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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