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]
Date:	Sat, 6 Sep 2008 15:50:41 -0600
From:	Alex Chiang <achiang@...com>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>
Subject: Re: hotplug create_slot hang

* Yinghai Lu <yhlu.kernel@...il.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

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ