linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Zan Lynx <zlynx@acm.org>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: 2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18
Date: Mon, 13 Nov 2006 23:58:18 +0100	[thread overview]
Message-ID: <20061113225818.GG2760@suse.de> (raw)
In-Reply-To: <1163455396.9482.38.camel@localhost>

On Mon, Nov 13, 2006 at 03:03:16PM -0700, Zan Lynx wrote:

> I have not checked if this is true, but it is a possible explanation:
> 
> Perhaps the filesystem is not properly unmounted during a suspend?  That

Of course not.

> would mean GRUB is reading from a incoherent filesystem on resume.

Exactly.

> GRUB's filesystem drivers are not very fancy.  It could be it does
> something silly like check the journal before returning each block.

GRUB must not write to the fs, so it probably plays back the journal in
memory only and it does this for every file it reads (at least that's how
it feels :-)
 
> 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.

> Another thing would be to create /boot as a separate partition.

Yes, that's what i always advise: /boot on separate ext2 partition. Then
GRUB resumes fast.
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

  reply	other threads:[~2006-11-13 22:59 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 [this message]
2006-11-14  4:07             ` Andrey Borzenkov
2006-11-14 14:23               ` Pavel Machek
2006-11-14 20:47                 ` Andrey Borzenkov
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=20061113225818.GG2760@suse.de \
    --to=seife@suse.de \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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).