Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935459AbZLPXRn (ORCPT ); Wed, 16 Dec 2009 18:17:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S935305AbZLPXRj (ORCPT ); Wed, 16 Dec 2009 18:17:39 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:59622 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935295AbZLPXRh (ORCPT ); Wed, 16 Dec 2009 18:17:37 -0500 From: "Rafael J. Wysocki" To: Alan Stern Subject: Re: Async suspend-resume patch w/ completions (was: Re: Async suspend-resume patch w/ rwsems) Date: Thu, 17 Dec 2009 00:18:05 +0100 User-Agent: KMail/1.12.3 (Linux/2.6.32-rjw; KDE/4.3.3; x86_64; ; ) Cc: Linus Torvalds , Zhang Rui , LKML , ACPI Devel Maling List , pm list References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912170018.05175.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1636 Lines: 40 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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/