All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, 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 23:00:53 +0200	[thread overview]
Message-ID: <41572E05.9030406@suse.de> (raw)
In-Reply-To: <200409261337.53298.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Sunday 26 of September 2004 12:09, Pavel Machek wrote:

>>>>We have seen something similar after hdparm was used on specific
>>>>machines. Are you using hdparm?

Pavel, i am pretty sure the issue with hdparm and 32-bit disk access was
just a symptom, not the cause. Rafael, please try the patch i posted in
the other mail, i believe this is the right thing to do.

>>>Not explicitly, but it's used by SuSE initscripts to set IDE DMA, AFAICS.  
>>>However, the problem did not occur on 2.6.9-rc2-mm1 with the same 
>>>initscripts.
>>
>>Okay, so try what happens without the initscripts
> 
> I turned the stuff off but of course it didn't change anything. :-)

That's what i expected.

>>and try to locate change that breaks it...

> Well, I'm a bit confused:
> 
> --- linux-2.6.9-rc2-mm1/kernel/power/swsusp.c   2004-09-16 14:06:56.000000000 
> +0200
> +++ linux-2.6.9-rc2-mm3/kernel/power/swsusp.c   2004-09-24 11:35:18.000000000 
> +0200
> @@ -862,8 +862,8 @@
>         error = swsusp_arch_suspend();
>         /* Restore control flow magically appears here */
>         restore_processor_state();
> -       local_irq_enable();
>         restore_highmem();
> +       local_irq_enable();
>         return error;
>  }

without this one is needed or highmem will break "sometimes". Was really
nasty. You did have highmem-resume problems, didn't you?

    Stefan

  parent reply	other threads:[~2004-09-26 21: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
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         ` Stefan Seyfried [this message]
2004-09-26 22:01           ` 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 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=41572E05.9030406@suse.de \
    --to=seife@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.