linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Pavel Machek <pavel@ucw.cz>
Cc: Stefan Seyfried <seife@suse.de>, Zan Lynx <zlynx@acm.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18
Date: Tue, 14 Nov 2006 23:47:27 +0300	[thread overview]
Message-ID: <200611142347.28571.arvidjaar@mail.ru> (raw)
In-Reply-To: <20061114142353.GB2340@elf.ucw.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 14 November 2006 17:23, Pavel Machek wrote:
> Hi!
>
> > > > Maybe its a journal size thing, you could try "sync" before suspend
> > > > and see if it helps.
> > >
> > > We already sync inside the kernel, it does not help here, though.
> > > Blockdev freezing might help.
> >
> > is there patch applicable to vanilla kernel? After repairing reiser
> > several times (due to hard lockups during suspend-to-RAM) that sounds
> > even more interesting.
>
> Could you do the test Stefan asked? I do not think you'll kill
> reiserfs by single forced powerdown.
> 

well, I did it accidentally :) (forgot to plug in power and after 2 hours on 
battery notebook simply switched off) and yes, there was some noticeable 
delay loading grub. I also tried fs freezer without any visible effect. The 
patches from mm I applied to vanilla kernel:

add-include-linux-freezerh-and-move-definitions-from.patch
swsusp-cleanup-whitespace-in-freezer-output.patch
swsusp-freeze-filesystems-during-suspend-rev-2.patch
swsusp-thaw-userspace-and-kernel-space-separately.patch

Do I need some more patches for this to work?

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFWitgR6LMutpd94wRAjh4AKCnGvpzxHuTEj+xKvEP7YhmESkD1wCffCm3
z0ZM59BV8FZUTy/onowVyW8=
=Vt7w
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-11-14 20:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-12 11:36 2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18 Andrey Borzenkov
2006-11-12 12:26 ` Rafael J. Wysocki
2006-11-12 12:34   ` Jan Engelhardt
2006-11-12 12:46   ` Andrey Borzenkov
2006-11-12 13:34     ` Rafael J. Wysocki
2006-11-12 19:13       ` Andrey Borzenkov
2006-11-12 14:55 ` Pavel Machek
2006-11-13  3:42   ` Andrey Borzenkov
2006-11-13  8:15     ` Stefan Seyfried
2006-11-13 18:54       ` Andrey Borzenkov
2006-11-13 22:03         ` Zan Lynx
2006-11-13 22:58           ` Stefan Seyfried
2006-11-14  4:07             ` Andrey Borzenkov
2006-11-14 14:23               ` Pavel Machek
2006-11-14 20:47                 ` Andrey Borzenkov [this message]
2006-11-14 22:57                   ` Pavel Machek
2006-11-15  4:01                     ` Andrey Borzenkov
2006-11-13 23:09           ` Pavel Machek
2006-11-13 22:55         ` Stefan Seyfried
2006-11-13 23:11           ` Rafael J. Wysocki
2006-12-16 19:05 ` Lee Garrett
2007-01-02 10:05   ` Stefan Seyfried
2007-01-02 10:58     ` Xavier Bestel
2007-01-02 12:14       ` Stefan Seyfried

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=200611142347.28571.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=seife@suse.de \
    --cc=zlynx@acm.org \
    /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;
as well as URLs for NNTP newsgroup(s).