public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, 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 00:33:51 +0200	[thread overview]
Message-ID: <20040926223351.GO28810@elf.ucw.cz> (raw)
In-Reply-To: <200409270001.09311.rjw@sisk.pl>

Hi!

> --- pci-driver.c	2004-09-26 23:35:32.701574416 +0200
> +++ pci-driver.c.rjw	2004-09-26 23:35:18.441742240 +0200
> @@ -328,6 +328,7 @@
>   */
>  static void pci_default_resume(struct pci_dev *pci_dev)
>  {
> +	printk("pci_default_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
> pci_dev->device, jiffies/HZ);
>  	/* restore the PCI config space */
>  	pci_restore_state(pci_dev, pci_dev->saved_config_space);
>  	/* if the device was enabled before suspend, reenable */
> @@ -343,6 +344,7 @@
>  	struct pci_dev * pci_dev = to_pci_dev(dev);
>  	struct pci_driver * drv = pci_dev->driver;
>  
> +	printk("pci_device_resume (0x%04x, 0x%04x): %ld\n", pci_dev->vendor, 
> pci_dev->device, jiffies/HZ);
>  	if (drv && drv->resume)
>  		drv->resume(pci_dev);
>  	else
> 
> in order to identify the offending device.  I'm now almost sure that the 
> NVidia chipset is to blame but I don't know which part of it exactly.
> 
> 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?

> 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.

> 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...
								Pavel

--- clean-mm/drivers/char/keyboard.c	2004-09-26 01:34:24.000000000 +0200
+++ linux-mm/drivers/char/keyboard.c	2004-09-26 01:42:24.000000000 +0200
@@ -1079,6 +1079,23 @@
 		sysrq_down = down;
 		return;
 	}
+	if (test_bit(KEY_LEFTALT, key_down) &&
+	    test_bit(KEY_RIGHTALT, key_down) &&
+	    test_bit(KEY_LEFTSHIFT, key_down) &&
+	    test_bit(KEY_RIGHTSHIFT, key_down) &&
+		down && !rep) {
+		handle_sysrq(kbd_sysrq_xlate[keycode], regs, tty);
+#ifdef CONFIG_KGDB_SYSRQ
+                sysrq_down = 0;        /* in case we miss the "up" event */
+#endif
+		return;
+	}
+
+	if (down)
+		set_bit(keycode, key_down);
+	else
+		clear_bit(keycode, key_down);
+
 	if (sysrq_down && down && !rep) {
 		handle_sysrq(kbd_sysrq_xlate[keycode], regs, tty);
 #ifdef CONFIG_KGDB_SYSRQ
@@ -1114,11 +1131,6 @@
 		raw_mode = 1;
 	}
 
-	if (down)
-		set_bit(keycode, key_down);
-	else
-		clear_bit(keycode, key_down);
-
 	if (rep && (!vc_kbd_mode(kbd, VC_REPEAT) || (tty && 
 		(!L_ECHO(tty) && tty->driver->chars_in_buffer(tty))))) {
 		/*

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-09-26 22:34 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 [this message]
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=20040926223351.GO28810@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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