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: Pavel Machek <pavel@suse.cz>, Stefan Seyfried <seife@suse.de>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64
Date: Sun, 26 Sep 2004 21:25:38 +0200	[thread overview]
Message-ID: <200409262125.38271.rjw@sisk.pl> (raw)
In-Reply-To: <20040926183449.GA28810@elf.ucw.cz>

On Sunday 26 of September 2004 20:34, Pavel Machek wrote:
> Hi!
> 
> > [-- snip --]
> > >  swsusp: Image: 11145 Pages
> > >  swsusp: Pagedir: 0 Pages
> > > Writing data to swap (11145 pages)...   0%
> > > 
> > > Here I have to press the red button unless I want to wait for a couple 
of 
> > > hours.  I'll send you more info when there's more.
> > 
> > I figured out that the slowdown occurs in device_resume(), so I put a 
printk() 
> > in dpm_resume(), like this:
> 
> When you hit "writing data to swap", device_resume should be no longer
> happening.

It isn't.  Still, device_resume() is called explicitly by swsusp_write() and 
IMO what happens is that the resume() function of one of the drivers does 
something that causes the system to slow down, which affects the writing 
operation (please note that the clock seems to be unaffected, though).  I'll 
try to narrow it.

> Try to unload all modules etc, see if it goes away.

I guess it will, but I'll check.

> If not, fix sysrq  to work for you, and look at backtrace.

This would be more time-consuming. :-)

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 19:24 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
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 [this message]
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=200409262125.38271.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