public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Prakash Punnoor <lists@punnoor.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp and kernel 2.6.12-rc4 does not work
Date: Wed, 25 May 2005 17:13:53 +0200	[thread overview]
Message-ID: <20050525151353.GC4375@elf.ucw.cz> (raw)
In-Reply-To: <42949431.7000006@punnoor.de>

Hi!

> >>I haven't treid with an earlier kernel. I am using an Sony Vaio PCG-F8ß07K
> >>notebook and tried to suspend.
> >>
> >>What goes wrong is, that the hd gets shut down before anything is written to it.
> >>
> >>I see (leaving some details out):
> >>
> >>Stopping task:========================|
> >>Freeing memory..done (40502 pages freed)
> >>swsusp: Need to copy 6953 pages
> >>swsusp: critical section/: done (6981 pages copied)
> >>ACPI: PCI Interrupt yadda yadda.. -> IRQ 9
> >>
> >>and there it sits. Is it really just the problem, that the hd gets shut down
> >>too early? Is there an easy way to fix this?
> > 
> > 
> > Disk shutdown is normal, you have other problem. Try again with
> > minimal drivers.
> 
> But shouldn't this happen, *after* memory image is written into swap?
> Otherwiese disk shuts down, spins up, writes image, shuts down, which is not
> too healthy for the hd.

No, it is not too healthy for the hd, and I'll fix it for 2.6.13, but
you'll have to live with it for 2.6.12. See FAQ why.

> I'll try with minimal drivers anyway.

..will not fix disk going down up down, but could fix your other
problem...

								Pavel

      reply	other threads:[~2005-05-25 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 16:19 swsusp and kernel 2.6.12-rc4 does not work Prakash Punnoor
2005-05-25 13:01 ` Pavel Machek
2005-05-25 15:05   ` Prakash Punnoor
2005-05-25 15:13     ` Pavel Machek [this message]

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=20050525151353.GC4375@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@punnoor.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