From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stefan Seyfried <seife@suse.de>
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: Tue, 14 Nov 2006 00:11:09 +0100 [thread overview]
Message-ID: <200611140011.10093.rjw@sisk.pl> (raw)
In-Reply-To: <20061113225500.GF2760@suse.de>
On Monday, 13 November 2006 23:55, Stefan Seyfried wrote:
> On Mon, Nov 13, 2006 at 09:54:38PM +0300, Andrey Borzenkov wrote:
> > Hash: SHA1
> >
> > On Monday 13 November 2006 11:15, Stefan Seyfried wrote:
> > > The most important question:
> > > What filesystem is your /boot on? I'd bet quite some money that it is
> > > reiser or some other journaling FS (not ext3).
> > >
> >
> > there is no /boot, I use single / which is reiser.
>
> ok, so your /boot is on reiser. Q.E.D.
>
> > > I am pretty sure that it will also happen if you do "updatedb &", wait a
> > > minute and then do a _HARD_ power off.
> > >
> > > I am pretty sure that it has nothing to do with the kernel version, just
> > > with the layout of your /boot partition (which of course changes with every
> > > kernel update). In other words: until now, you just have been lucky.
> >
> > The idea is nice; unfortunately it fails to explain the difference
> > between 'poweroff'
>
> filesystem cleanly unmounted
>
> > and 'suspend disk'
>
> filesystem unclean.
>
> > cases. I doubt disk layout is changed
> > between them.
>
> Try the "updatedb &, then _HARD_ poweroff" test described above. It will take
> long to load grub afterwards.
Alternatively, you can use a recent -mm kernel with the bdevs freezing patch
and see if that helps GRUB. ;-)
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-11-13 23:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 11:36 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
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 [this message]
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=200611140011.10093.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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
Powered by JetHome