From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64
Date: Mon, 27 Sep 2004 00:05:04 +0200
User-Agent: KMail/1.6.2
Cc: Stefan Seyfried <seife@suse.de>, Pavel Machek <pavel@suse.cz>,
       Andrew Morton <akpm@osdl.org>
References: <200409251214.28743.rjw@sisk.pl> <200409262125.38271.rjw@sisk.pl> <41572B34.3010209@suse.de>
In-Reply-To: <41572B34.3010209@suse.de>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Message-Id: <200409270005.04458.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1335
Lines: 37

On Sunday 26 of September 2004 22:48, Stefan Seyfried wrote:
> Rafael J. Wysocki wrote:
> 
> >>Try to unload all modules etc, see if it goes away.
> > 
> > I guess it will, but I'll check.
> 
> please try attached patch first. The comments should explain it pretty
> well. It seems to have helped me: without it, sysrq-p during writing
> (even if not that slow) almost always was in pccardd, now it is idling
> in swapper task.
> Maybe i am totally wrong but you may give it a shot.

Does not help, sorry. :-(

> >>If not, fix sysrq  to work for you, and look at backtrace.
> > 
> > This would be more time-consuming. :-)
> 
> maybe you just press wrong keys? On my Dell D600, although SysRQ is in
> blue on PrtSc, no Fn-Key is needed but only ALT-PrtSc.

It is possible, but I have two x86-64 boxes, one of which is a regular PC with 
no Fn-Key whatsoever, and it doesn't work on both, apparently.

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"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/