public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Len Brown <len.brown@intel.com>,
	linux-pm@lists.linux-foundation.org,
	Jack Steiner <steiner@sgi.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [linux-pm] Resume from Memory very slow on 2.6.37+
Date: Wed, 19 Jan 2011 02:38:18 +0100	[thread overview]
Message-ID: <201101190238.18529.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTikay6g5rOyDnv_ocz49GvUcQN+OkrusrbcRPB0K@mail.gmail.com>

On Wednesday, January 19, 2011, Jeff Chua wrote:
> On Wed, Jan 19, 2011 at 4:20 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > Please apply the appended patch (without the previous one) and post a dmesg
> > log containing a suspend-resume cycle with the delay.  I wonder where exactly
> > the delay occurs.
> > +       pr_info("%s: synchronize_rcu()\n", __func__);
> >        synchronize_rcu();
> > +       pr_info("%s: iounmap(%p), physaddr: %llx, size: %u\n", __func__,
> > +               map->virt, map->phys, map->size);
> 
> Rafael,
> 
> The 30 seconds is due to this ...
> 
> PM: Syncing filesystems ... done.
> Freezing user space processes ... _memory: synchronize_rcu()
> acpi_os_unmap_memory: iounmap(ffffc90001c22000), physaddr: bb398000, size: 4096
> acpi_os_unmap_memory: synchronize_rcu()
> acpi_os_unmap_memory: iounmap(ffffc90001c26000), physaddr: bb399000, size: 4096
> acpi_os_unmap_memory: synchronize_rcu()
> acpi_os_unmap_memory: iounmap(ffffc90001c2a000), physaddr: bb39a000, size: 4096
> acpi_os_unmap_memory: synchronize_rcu()
> acpi_os_unmap_memory: iounmap(ffffc90001c2e000), physaddr: bb39b000, size: 4096
> <repeat till ...>
> acpi_os_unmap_memory: iounmap(ffffc90003538000), physaddr: bb79d000, size: 4096
> acpi_os_unmap_memory: synchronize_rcu()
> acpi_os_unmap_memory: iounmap(ffffc9000353c000), physaddr: bb79e000, size: 4096
> Restarting tasks ... done.
> 
> After this, I see my X windows.

Are you able to say whether the synchronize_rcu() or the iounmap() calls block?

Rafael

  reply	other threads:[~2011-01-19  1:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimBEnKTuR5aQyXvpZX8grQPw1eCaVgP-k9yBXhv@mail.gmail.com>
2011-01-17 18:55 ` Resume from Memory very slow on 2.6.37+ Brown, Len
2011-01-17 22:49 ` Rafael J. Wysocki
2011-01-18  0:14   ` [linux-pm] " Rafael J. Wysocki
2011-01-18  1:14     ` Jeff Chua
2011-01-18  1:35       ` Rafael J. Wysocki
2011-01-18  5:19         ` Jeff Chua
2011-01-18 20:20           ` Rafael J. Wysocki
2011-01-19  1:20             ` Jeff Chua
2011-01-19  1:38               ` Rafael J. Wysocki [this message]
2011-01-19 14:13                 ` Jeff Chua
2011-01-19 21:19                   ` Rafael J. Wysocki
2011-01-19 21:27                     ` [1/2] ACPI: Introduce acpi_os_ioremap() Rafael J. Wysocki
2011-01-19 21:27                     ` [2/2] ACPI / PM: Call suspend_nvs_free() earlier during resume Rafael J. Wysocki
2011-01-20  1:21                     ` [linux-pm] Resume from Memory very slow on 2.6.37+ Jeff Chua
2011-01-20  1:50                       ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201101190238.18529.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jeff.chua.linux@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=steiner@sgi.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox