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: Mon, 27 Sep 2004 11:11:42 +0200 [thread overview]
Message-ID: <200409271111.42812.rjw@sisk.pl> (raw)
In-Reply-To: <20040926223351.GO28810@elf.ucw.cz>
Hi,
On Monday 27 of September 2004 00:33, Pavel Machek wrote:
[-- snip --]
> > I've got two logs (attached), one of which is taken from the system with
all
> > modules loaded (swsusp.log), and the other comes from the system with no
> > modules except for ipv6 (swsusp-nomod.log). As you can see from the first
> > log, the system with all modules loaded slows down significantly after
> > pci_device_resume() is called for the device having vendor id = 0x10de
> > (NVidia) and device id = 0x00d7 (no idea). The system without modules is
>
> lspci, and take a look?
albercik:~ # lspci -n
[ ... ]
0000:00:02.0 Class 0c03: 10de:00d7 (rev a5)
0000:00:02.1 Class 0c03: 10de:00d7 (rev a5)
0000:00:02.2 Class 0c03: 10de:00d8 (rev a2)
[ ... ]
albercik:~ # lspci
[ ... ]
0000:00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
0000:00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
[ ... ]
So, it's the USB 1.1 controller (OHCI).
> > capable of writing 80-83% of pages to the swap _before_ slows down too and
I
> > have to wait for 1/2 h for the remaining ~20%.
>
> Strange, *very* strange.
Yes, it is.
> > I'm afraid I can't get any more info until I sort out the sysrq
> > problem.
>
> This should remap magic key to both-shifts-both-alts-key. Worked for
> me once...
Thanks a lot, but it turned out to be much simpler: sysrq was disabled by an
initscript (shame on me, shame, shame). I'll get the traces as soon as I can
get something to attach to the serial console. In the meantime, I'll try to
look at the USB stuff.
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"
prev parent reply other threads:[~2004-09-27 9:11 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
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 [this message]
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=200409271111.42812.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