All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Stefan Seyfried <seife@suse.de>
Cc: 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 21:54:38 +0300	[thread overview]
Message-ID: <200611132154.38644.arvidjaar@mail.ru> (raw)
In-Reply-To: <20061113081528.GB18022@suse.de>

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

On Monday 13 November 2006 11:15, Stefan Seyfried wrote:
> Hi,
>
> On Mon, Nov 13, 2006 at 06:42:15AM +0300, Andrey Borzenkov wrote:
> > On Sunday 12 November 2006 17:55, Pavel Machek wrote:
> > > On Sun 12-11-06 14:36:41, Andrey Borzenkov wrote:
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > This is rather funny; in 2.6.19-rc5 grub is *really* slow loading
> > > > kernel when I switch on the system after suspend to disk. Actually,
> > > > after kernel has been loaded, the whole resuming (up to the point I
> > > > have usable
>
> 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.

> > > > desktop again) takes about three time less than the process of
> > > > loading kernel + initrd. During loading disk LED is constantly lit.
> > > > This almost looks like kernel leaves HDD in some strange state,
> > > > although I always assumed HDD/IDE is completely reinitialized in this
> > > > case.
> > >
> > > Seems like broken hw, really. No state should survive machine
> > > poweroff.
>
> No. Broken FS / crappy GRUB.
>
> > To recap - this never happens upon simple power off; I do not remember
> > this to
>
> 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' and 'suspend disk' cases. I doubt disk layout is changed 
between them.

regards

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

iD8DBQFFWL9uR6LMutpd94wRAh0NAJ4o2hU4E/BsMOJXPxqX8OSH8OR/nwCfdLPz
DWHM1gAFYTvc9WtyNv+qq08=
=EaDe
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-11-13 18:54 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 [this message]
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
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=200611132154.38644.arvidjaar@mail.ru \
    --to=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 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.