linux-kernel - Re: PCI Failed to allocate mem for PCI ROM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1025115-6BE2-46B6-8416-A5ADD506E2ED@kernel.crashing.org>
Date:	Fri, 11 Jan 2008 14:27:16 -0600
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Greg KH <greg@...ah.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linuxppc-dev list <linuxppc-dev@...abs.org>,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: PCI Failed to allocate mem for PCI ROM


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@...00000 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/