On Wed, 2013-10-30 at 15:13 +0100, Rafael J. Wysocki wrote: > On Wednesday, October 30, 2013 07:57:46 AM Alex Williamson wrote: > > On Wed, 2013-10-30 at 14:40 +0200, Mika Westerberg wrote: > > > Commit 2dc4128 (ACPI / hotplug / PCI: Avoid doing too much for spurious > > > notifies) changed the enable_slot() to check return value of pci_scan_slot() > > > and if it is zero return early from the function. It means that there were > > > no new devices in this particular slot. > > > > > > However, if a device appeared deeper in the hierarchy the code now ignores > > > it causing things like Thunderbolt chaining fail to recognize new devices. > > > > > > The problem with Alex Williamson's machine was solved with commit > > > a47d8c8 (ACPI / hotplug / PCI: Avoid parent bus rescans on spurious device > > > checks) and hence we should be able to restore the original functionality > > > that we always rescan on bus check notification. > > > > > > On a device check notification we still check what acpiphp_rescan_slot() > > > returns and on zero bail out early. > > > > > > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> > > > --- > > > Alex, > > > > > > Are you able to check if your machine still works and doesn't slow down > > > during boot after this patch is applied? > > > > Looks ok to me, no new console output or boot delay. Thanks, > > Great, thanks! > > May I add your Tested-by to it, then? Sure Tested-by: Alex Williamson <alex.williamson@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
