From: Jiri Slaby <jirislaby@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
linux-pci@atrey.karlin.mff.cuni.cz,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: PCI Failed to allocate mem for PCI ROM
Date: Fri, 11 Jan 2008 10:13:23 +0100 [thread overview]
Message-ID: <47873333.5020202@gmail.com> (raw)
In-Reply-To: <0119CD93-D9F1-42E0-9F6A-A50B2C63B19D@kernel.crashing.org>
On 01/11/2008 10:07 AM, Kumar Gala wrote:
>
> On Jan 11, 2008, at 2:41 AM, Jiri Slaby wrote:
>
>> On 01/11/2008 09:29 AM, 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?
>>
>> Kernel version, please.
>
> Sorry, its 2.6.24-rc7 + some ppc patches queued for 2.6.25
Could you try this patch?
http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=blob_plain;f=pci/pci-remove-default-pci-expansion-rom-memory-allocation.patch
Greg: is this 2.6.25 material, please? We need this for SP2.
thanks,
--
Jiri Slaby
Faculty of Informatics, Masaryk University
Suse Labs
next prev parent reply other threads:[~2008-01-11 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 8:29 PCI Failed to allocate mem for PCI ROM Kumar Gala
2008-01-11 8:41 ` Jiri Slaby
2008-01-11 9:07 ` Kumar Gala
2008-01-11 9:13 ` Jiri Slaby [this message]
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
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=47873333.5020202@gmail.com \
--to=jirislaby@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).