2013/4/25 Yinghai Lu <yinghai@xxxxxxxxxx> > > On Wed, Apr 24, 2013 at 6:20 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > > On Wed, Apr 24, 2013 at 3:55 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > >> On Wednesday, April 24, 2013 02:03:04 PM Bjorn Helgaas wrote: > >>> > >>> We install a notify handler on PCI0 in find_root_bridges(), and that > >>> notify handler leads to _handle_hotplug_event_root(), which assumes > >>> this is a host bridge hotplug event. But I would expect the notify > >>> for a host bridge hot-add would go to the *parent* of the host bridge, > >>> not to the host bridge itself, so something seems wrong here. > >>> > >>> Maybe the ACPI & hotplug experts can comment on this. > >> > >> I think it may (ie. won't be against the spec) go both ways, so it may go > >> to the parent or the host bridge object itself. We should be handling both > >> cases IMO. > > > > Yes, we missed that path. > > > > Attached patch should fix the problem. > > > > Gavin, > > > > Can you please check that on top of pci/next? > > updated -v2. Hi Yinghai, I tested the first version of your patch and it can't work. Now, I'm testing the v2 of your patch. Please wait a minute. Gavin Guo -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
