On Fri, 18 Dec 2009, Rafael J. Wysocki wrote: > I didn't manage to do that, but I was able to mark sd and i8042 as async and > see the impact of this. Apparently this didn't do what you wanted. In the nx6325 sd+i8042+async+extra log, the 0:0:0:0 device (which is a SCSI disk) was suspended by the main thread instead of an async thread. There's an important point I neglected to mention before. Your logs don't show anything for devices with no suspend callbacks at all. Nevertheless, these devices sit on the device list and prevent other devices from suspending or resuming as soon as they could. For example, the fingerprint sensor (3-1) took the most time to resume. But other devices were delayed until after it finished because it had children with no callbacks, and they delayed the devices following them in the list. What would happen if you completed these devices immediately, as part of the first pass? Alan Stern -- 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
