mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: PCI Failed to allocate mem for PCI ROM
Date: Fri, 11 Jan 2008 14:27:16 -0600	[thread overview]
Message-ID: <E1025115-6BE2-46B6-8416-A5ADD506E2ED@kernel.crashing.org> (raw)
In-Reply-To: <20080111175039.GB7916@kroah.com>


On Jan 11, 2008, at 11:50 AM, Greg KH wrote:

> On Fri, Jan 11, 2008 at 02:29:28AM -0600, Kumar Gala wrote:
>> Greg,
>>
>> I'm getting the following message from the kernel on an embedded  
>> ppc32
>> system:
>>
>> PCI: Failed to allocate mem resource #9:100000@e0000000 for  
>> 0000:00:00.0
>>
>> The HW setup is a PCIe host controller and an e1000 NIC card.  It  
>> appears
>> that pci_bus_assign_resources() is trying to call  
>> pci_assign_resource() for
>> the ROM and the resource for the ROM is [100000:1fffff] where the  
>> PHB is
>> [c0000000:dfffffff].
>>
>> It seems like the resno that pci_assign_resource is getting called  
>> with is
>> wrong and thus pci_update_resource() doesn't get called.
>>
>> any ideas?
>
> Nope, sorry, any help debugging this is appreciated, pci resource
> allocation is "tricky" :)

I'm happy to debug, is the fact that the resno == 9 ok or does that  
seem wrong?

- k

  reply	other threads:[~2008-01-11 20:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11  8:29 Kumar Gala
2008-01-11  8:41 ` Jiri Slaby
2008-01-11  9:07   ` Kumar Gala
2008-01-11  9:13     ` Jiri Slaby
2008-01-11 15:41       ` Kumar Gala
2008-01-11 16:52         ` Jiri Slaby
2008-01-11 17:49       ` Greg KH
2008-01-11 17:50 ` Greg KH
2008-01-11 20:27   ` Kumar Gala [this message]
2008-01-12  7:27     ` Grant Grundler
2008-01-12 15:12       ` Ivan Kokshaysky

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=E1025115-6BE2-46B6-8416-A5ADD506E2ED@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc-dev@ozlabs.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®