From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [QUESTION] 440EPx with PCI to PCIe bridge error
Date: Tue, 06 Jan 2009 08:18:38 +1100 [thread overview]
Message-ID: <1231190318.14860.17.camel@pasglop> (raw)
In-Reply-To: <496268E7.5090907@harris.com>
On Mon, 2009-01-05 at 15:09 -0500, Steven A. Falco wrote:
> I have a Sequoia board (440EPx) with kernel 2.6.27.9. I've recently
> plugged in a PLX adapter board to convert one of the PCI connectors
> on the Sequoia to PCIe.
>
> When the kernel boots, I get the following error messages regarding
> mem resource allocation. Device 0000:00:0c.0 is the PCI<->PCIe bridge,
> and device 0000:01:00.0 is an FPGA PCIe evaluation board.
Please enable DEBUG in arch/powerpc/kernel/pci-common.c and pci_32.c and
send us a full log. It might also be useful to do that on top of 2.6.28
in case some of the changes that went in after .27 make a difference.
I think I'll turn those DEBUG into something that can be enabled from
the kernel command line one of these days :-)
Cheers,
Ben.
> PCI host bridge /plb/pci@1ec000000 (primary) ranges:
> MEM 0x0000000180000000..0x000000018fffffff -> 0x0000000080000000
> IO 0x00000001e8000000..0x00000001e80fffff -> 0x0000000000000000
> 4xx PCI DMA offset set to 0x00000000
> PCI: Probing PCI hardware
> PCI: Hiding 4xx host bridge resources 0000:00:00.0
> pci 0000:00:0c.0: PME# supported from D0 D1 D3hot
> pci 0000:00:0c.0: PME# disabled
> pci 0000:00:0c.0: BAR 8: can't allocate mem resource [0x180000000-0x18fffffff]
> pci 0000:01:00.0: BAR 1: can't allocate mem resource [0x1f0000000-0x1ffffffff]
> pci 0000:01:00.0: BAR 0: can't allocate mem resource [0x180000000-0x18007ffff]
> pci 0000:00:0c.0: PCI bridge, secondary bus 0000:01
> pci 0000:00:0c.0: IO window: disabled
> pci 0000:00:0c.0: MEM window: disabled
> pci 0000:00:0c.0: PREFETCH window: disabled
>
> Plain PCI cards plugged directly into the Sequoia work fine. Is there
> something I have to add to the .dts file to represent the PCI<->PCIe
> bridge?
>
> Thanks,
> Steve
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2009-01-05 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:09 [QUESTION] 440EPx with PCI to PCIe bridge error Steven A. Falco
2009-01-05 21:18 ` Benjamin Herrenschmidt [this message]
2009-01-05 21:35 ` Steven A. Falco
2009-01-06 6:33 ` Benjamin Herrenschmidt
2009-01-06 14:44 ` Steven A. Falco
2009-01-06 18:33 ` Steven A. Falco
2009-01-06 20:41 ` Steven A. Falco
2009-01-06 21:38 ` Steven A. Falco
2009-01-06 22:02 ` Benjamin Herrenschmidt
2009-01-06 22:22 ` Steven A. Falco
2009-01-06 23:13 ` Benjamin Herrenschmidt
2009-01-07 14:45 ` Steven A. Falco
2009-01-07 20:52 ` Benjamin Herrenschmidt
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=1231190318.14860.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfalco@harris.com \
/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).