[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061113225500.GF2760@suse.de>
Date: Mon, 13 Nov 2006 23:55:00 +0100
From: Stefan Seyfried <seife@...e.de>
To: Andrey Borzenkov <arvidjaar@...l.ru>
Cc: linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>
Subject: Re: 2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18
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.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists