On Thursday 17 December 2009, Alan Stern wrote: > On Wed, 16 Dec 2009, Rafael J. Wysocki wrote: > > > I've just put the first set of data, for the HP nx6325 at: > > http://www.sisk.pl/kernel/data/nx6325/ > > > > The *-dmesg.log files contain full dmesg outputs starting from a cold boot and > > including one suspend-resume cycle in each case, with debug_initcall enabled. > > > > The *-suspend.log files are excerpts from the *-dmesg.log files containing > > the suspend messages only, and analogously for *-resume.log. > > I've just started looking at the sync-suspend.log file. What are all > the '+' characters and " @ 3368" strings after the device names? I think the + is necessary for the Arjan's graph-generating script and the @ number is the value of current (ie. the PID of the calling task). > You didn't print out the parent name for each device, so the tree > structure has been lost. That's because the original Arjan's patch doesn't do that, I'm adding it right now. > Why do those "sd 0:0:0:0 [sda]" messages appear in between two > callbacks? The cache-synchronization and the spin-down commands are > not executed asynchronously. Because the data are incomplete. :-( I've just realized that the Arjan's patch only covers bus types and classes that have been converted to dev_pm_ops already, so I'm extending it to the "legacy" ones at the moment. Rafael -- 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
