From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jeff Newbern <jnewbern@bluespec.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: PCIe hotplug failure
Date: Tue, 20 Apr 2010 22:37:55 -0600 [thread overview]
Message-ID: <1271824675.6035.50.camel@dc7800.home> (raw)
In-Reply-To: <g2z3c10cdd31004200910y322fd94fn65c548d329104f30@mail.gmail.com>
On Tue, 2010-04-20 at 12:10 -0400, Jeff Newbern wrote:
> Kernel: Ubuntu 9.10 (Karmic) 2.6.31-20-generic
>
> The pciehp driver is built into the kernel.
>
> I am connecting a custom FPGA device with a PCIe endpoint through the
> ExpressCard slot on a Lenovo T61 laptop.
>
> lspci -vv shows HotPlug+ and Surpise+ capabilities for the ExpressCard
> controller.
>
> I'm running the kernel with pciehp.pciehp_debug=1, and this is the
> dmesg output when I bring up the FPGA device:
>
> [ 3346.553917] pciehp 0000:00:1c.3:pcie04: pcie_isr: intr_loc 8
> [ 3346.553925] pciehp 0000:00:1c.3:pcie04: Presence/Notify input change
> [ 3346.553934] pciehp 0000:00:1c.3:pcie04: Card present on Slot(5)
> [ 3346.553951] pciehp 0000:00:1c.3:pcie04: Surprise Removal
> [ 3346.553960] pciehp 0000:00:1c.3:pcie04: hpc_get_power_status:
> SLOTCTRL 58 value read 38
> [ 3346.553969] pciehp 0000:00:1c.3:pcie04: hpc_get_attention_status:
> SLOTCTRL 58, value read 38
> [ 3346.554030] pciehp 0000:00:1c.3:pcie04: board_added: slot device,
> slot offset, hp slot = 0, 0, 0
> [ 3347.122566] pciehp 0000:00:1c.3:pcie04: hpc_check_lnk_status:
> lnk_status = 3011
> [ 3347.122685] pci 0000:05:00.0: reg 10 32bit mmio: [0x000000-0x7fffff]
> [ 3347.122708] pci 0000:05:00.0: reg 14 32bit mmio: [0x000000-0x7fffff]
> [ 3347.122743] pci 0000:05:00.0: reg 18 64bit mmio: [0x000000-0x1ffffff]
> [ 3347.122795] pci 0000:05:00.0: reg 30 32bit mmio: [0x000000-0x0fffff]
> [ 3347.122884] pci 0000:05:00.0: PME# supported from D0
> [ 3347.122898] pci 0000:05:00.0: PME# disabled
> [ 3347.122974] pciehp: Could not get hotplug parameters
> [ 3347.123004] pci 0000:05:00.0: BAR 0: can't allocate mem resource
> [0xd6000000-0xd5ffffff]
> [ 3347.123012] pci 0000:05:00.0: BAR 1: can't allocate mem resource
> [0xd6000000-0xd5ffffff]
> [ 3347.123249] pciehp 0000:00:1c.3:pcie04: hpc_get_power_status:
> SLOTCTRL 58 value read 38
> [ 3347.123259] pciehp 0000:00:1c.3:pcie04: hpc_get_attention_status:
> SLOTCTRL 58, value read 38
>
> The BAR types and sizes look correct in the initial pci lines, but are
> non-sensical in the "can't allocate mem resource" error messages that
> follow the "Could not get hotplug parameters" message.
I added linux-pci, which is more pertinent than lkml. If you can try a
current upstream kernel and post the entire dmesg log, that would be
useful. There have been a number of recent changes related to PCI
resource allocation.
Bjorn
prev parent reply other threads:[~2010-04-21 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 16:10 Jeff Newbern
2010-04-21 4:37 ` Bjorn Helgaas [this message]
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=1271824675.6035.50.camel@dc7800.home \
--to=bjorn.helgaas@hp.com \
--cc=jnewbern@bluespec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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®