From: Alex Chiang <achiang@hp.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Subject: Re: hotplug create_slot hang
Date: Sat, 6 Sep 2008 15:50:41 -0600 [thread overview]
Message-ID: <20080906215041.GD27298@ldl.fc.hp.com> (raw)
In-Reply-To: <86802c440809061015v21b6c1eat8718618a6ae25e47@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com>:
> calling pci_hotplug_init+0x0/0x1d
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> initcall pci_hotplug_init+0x0/0x1d returned 0 after 11 msecs
>
> calling acpiphp_init+0x0/0x5f
> acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> decode_hpp: Could not get hotplug parameters. Use defaults
> pci_create_slot: created pci_slot on 0000:07:00
> acpiphp: Slot [1] registered
> decode_hpp: Could not get hotplug parameters. Use defaults
> pci_create_slot: created pci_slot on 0000:0d:00
> acpiphp: Slot [2] registered
> initcall acpiphp_init+0x0/0x5f returned 0 after 105 msecs
Is this the hang?
> calling pcied_init+0x0/0x7b
> pciehp: HPC vendor_id 8086 device_id 340a ss_vid 0 ss_did 0
> pci_create_slot: inc refcount to 2 on 0000:07:00
> pci_destroy_slot: dec refcount to 1 on 0000:07:00
> pciehp: pci_hp_register failed with error -16
> pciehp: pciehp: slot already registered by another hotplug driver
This failure is by design -- we only allow one hotplug driver to
claim a slot now, and it's "first one loaded wins".
Unless you're talking about something else?
Thanks.
/ac
next prev parent reply other threads:[~2008-09-06 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 17:15 hotplug create_slot hang Yinghai Lu
2008-09-06 19:44 ` Andrew Morton
2008-09-06 21:18 ` Yinghai Lu
2008-09-06 21:50 ` Alex Chiang [this message]
2008-09-06 22:18 ` Yinghai Lu
2008-09-07 4:59 ` Alex Chiang
2008-09-08 12:55 ` Kenji Kaneshige
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=20080906215041.GD27298@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.