Re: 2.6.19-rc5: grub is much slower resuming from suspend-to-disk than in 2.6.18

From: Andrey Borzenkov
Date: Sun Nov 12 2006 - 14:14:29 EST


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

On Sunday 12 November 2006 16:34, Rafael J. Wysocki wrote:
> On Sunday, 12 November 2006 13:46, Andrey Borzenkov wrote:
> > On Sunday 12 November 2006 15:26, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > On Sunday, 12 November 2006 12:36, Andrey Borzenkov wrote:
> > > > 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 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.
> > >
> > > Can you please see what's in the /sys/power/disk file?
> >
> > {pts/0}% cat /sys/power/disk
> > shutdown
>
> Can you please write "platform" to this file before the suspend and see if
> anything changes?
>

No, nothing changes.

I tested a bit more; I currently have 2.6.18.1, 2.6.18.2 and 2.6.19-rc5
installed. Booting after "poweroff" is OK from within all versions - there is
no delay. Resuming after suspend under 2.6.18.x is mostly OK, at least it is
much less obvious (I had some feeling it may have been "a bit slower" under
2.6.18.2 but may be it is just illusion). Resuming after suspend under
2.6.19-rc5 results in noticeable delay and constantly busy HDD LED during
grub phase.

Yes, it is notebook. I will test Pavel's suggestion later.

regards

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

iD8DBQFFV3J3R6LMutpd94wRAjBoAJ9UBc0KXM4/8ANCwUn17gbHrhTKawCgiJjg
qdsJw+JV4LLL4mP5hz+NYVI=
=Y1of
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/