mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
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 06:42:15 +0300	[thread overview]
Message-ID: <200611130642.18990.arvidjaar@mail.ru> (raw)
In-Reply-To: <20061112145549.GC4371@ucw.cz>

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

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
> > 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.
>

Well, we do have NVRAM do not we?

> Is it notebook?
>

Yes.

> Can you try to unplug system for a few minutes / unplug battery if
> notebook to see if it helps?

No. I unplugged power, removed battery and left it over night. Today morning 
it has shown exactly the same behavior upon resuming (well, upon power-on 
after suspend to disk :))

To recap - this never happens upon simple power off; I do not remember this to 
happen upon suspend to disk until 2.6.19 (I won't claim it never happened, 
just that I do not remember it). This happens consistently in 2.6.19-rc5. I 
am very curious which hardware issue may have such pattern. And in any case 
this does smell like regression (earlier version not triggering this HW issue 
if any)

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

iD8DBQFFV+maR6LMutpd94wRAmhxAKDCZvzoUtqQguQL1+WmdT/wi3Y3RACgnXep
ra/Qr0wUO43MTAZB2qGWiS0=
=pICz
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-11-13  3:42 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 [this message]
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
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=200611130642.18990.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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