linux-kernel - Re: PCIe hotplug failure

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] [day] [month] [year] [list]

Message-Id: <1271824675.6035.50.camel@dc7800.home>
Date:	Tue, 20 Apr 2010 22:37:55 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Jeff Newbern <jnewbern@...espec.com>
Cc:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: PCIe hotplug failure

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


--
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/