public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: Stefan Seyfried <seife@suse.de>, Andrew Morton <akpm@osdl.org>,
	Pavel Machek <pavel@suse.cz>
Subject: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64
Date: Sun, 26 Sep 2004 12:02:34 +0200	[thread overview]
Message-ID: <200409261202.34138.rjw@sisk.pl> (raw)
In-Reply-To: <4155E40D.2020709@suse.de>

On Saturday 25 of September 2004 23:33, Stefan Seyfried wrote:
> Rafael J. Wysocki wrote:
> > Pavel,
> > 
> > I've just tried to suspend my box and I must admit I've given up after 30 
> > minutes (sic!) of waiting when there were only 12% of pages written to 
disk.  
> > Apparently, swsusp slows down to an unacceptable level after saying "PM: 
> > Writing image to disk".
> 
> is this reproducible?

Yes, it is.  100% of the time, AFAICT, though I've tried it for only a couple 
of times.

> can you get sysrq-t / sysrq-p while it is slow 
> writing to disk?

Well, I'll try, but sysrq didn't work for me at all on 2.6.9-rc2-mm1, so I'm 
not sure if I really can.

> I have seen this, too but i cannot nail it down to some specific
> pattern, it just "sometimes" is slow. Sysrq-p shows me it's almost
> always in "pccardd" (where it shouldn't be during suspend, iiuc).
> Unfortunately Pavel does not see this so we have to convince him that
> this is really a problem ;-)
> So if you can reproduce this, it would be a step in the right direction.

It seems that I can. ;-)

Could it be possible to printk time along with the percentage info (for 
debugging purposes only, of course)?

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2004-09-26 10:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25 10:14 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 Rafael J. Wysocki
2004-09-25 21:33 ` Stefan Seyfried
2004-09-26 10:02   ` Rafael J. Wysocki [this message]
2004-09-26 10:10     ` Pavel Machek
2004-09-26 11:45     ` Rafael J. Wysocki
2004-09-26 13:22       ` Pavel Machek
2004-09-26 17:06       ` Rafael J. Wysocki
2004-09-26 18:34         ` Pavel Machek
2004-09-26 19:25           ` Rafael J. Wysocki
2004-09-26 20:48             ` Stefan Seyfried
2004-09-26 22:05               ` Rafael J. Wysocki
2004-09-26 22:41               ` Pavel Machek
2004-09-25 23:40 ` Pavel Machek
2004-09-26 10:08   ` Rafael J. Wysocki
2004-09-26 10:09     ` Pavel Machek
2004-09-26 11:37       ` Rafael J. Wysocki
2004-09-26 13:20         ` Pavel Machek
2004-09-27 23:23           ` 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 (update) Rafael J. Wysocki
2004-09-28  2:03             ` Narayan Desai
2004-09-29 21:58             ` 2.6.9-rc2-mm[2-4]: zaphod-scheduler.patch makes swsusp incredibly slow (was: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64) Rafael J. Wysocki
2004-09-29 22:50               ` Pavel Machek
2004-09-26 21:00         ` 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 Stefan Seyfried
2004-09-26 22:01           ` Rafael J. Wysocki
2004-09-26 22:33             ` Pavel Machek
2004-09-27  9:11               ` 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=200409261202.34138.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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