From: Michael Frank <mflt1@micrologica.com.hk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: hugang <hugang@soulinfo.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE Power Management (Was: software suspend in 2.5.70-mm3)
Date: Wed, 4 Jun 2003 22:35:41 +0800 [thread overview]
Message-ID: <200306042235.41326.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <1054736960.20838.44.camel@gaston>
On Wednesday 04 June 2003 22:29, Benjamin Herrenschmidt wrote:
> > hda: start_power_step(susp: 1, step: 0)
> > hda: start_power_step(susp: 1, step: 1)
> > hda: start_power_step(susp: 1, step: 2)
> > hda: complete_power_step(susp: 1, step: 2, stat: 50, err: 0)
> > hda: completing PM request, suspend: 1
> > Suspending devices
> > /critical section: Counting pages to copy[nosave c03f7000] (pages needed:
> > 2273+512=2785 free: 14110) Alloc pagedir
> > ............
> > [nosave c03f7000]critical section/: done (2273 pages copied)
> > hda: Wakeup request inited, waiting for !BSY...
> > hda: start_power_step(susp: 0, step: 0)
> > hda: start_power_step(susp: 0, step: 101)
> > hda: completing PM request, suspend: 0
> > Devices Resumed
> > Devices Resumed
>
> Hrm... the joy if swsusp putting your disk to sleep just to wake it up
> right away... I need to check if I can differenciate suspend-to-disk
> from suspend-to-ram here to just not put the drive in STANDBY mode
> on suspend-to-disk (just freeze the queues)
It did this also in 2.4 until Nigel Cunningham fixed it.
>
> > Writing data to swap (2273 pages): .<3>bad: scheduling while atomic!
>
> Here's the real one. However, it doesn't look related to my sleep code,
> though I cannot guarantee this for sure right now, it _seems_ it's
> a swsusp bug you are hitting.
Well, awaiting the next patch...
Regards
Michael
--
Powered by linux-2.5.70-mm3
My current linux related activities in rough order of priority:
- Testing of 2.4/2.5 kernel interactivity
- Testing of Swsusp for 2.4
- Testing of Opera 7.11 emphasizing interactivity
- Research of NFS i/o errors during transfer 2.4>2.5
- Learning 2.5 series kernel debugging with kgdb - it's in the -mm tree
- Studying 2.5 series serial and ide drivers, ACPI, S3
* Input and feedback is always welcome *
Joke of the day: http://lwn.net/Articles/34848/
next prev parent reply other threads:[~2003-06-04 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 13:11 software suspend in 2.5.70-mm3 hugang
2003-06-03 13:22 ` Alan Cox
2003-06-03 14:35 ` hugang
2003-06-03 14:08 ` Alan Cox
2003-06-03 17:04 ` Benjamin Herrenschmidt
2003-06-04 13:14 ` IDE Power Management (Was: software suspend in 2.5.70-mm3) Benjamin Herrenschmidt
2003-06-04 13:51 ` Michael Frank
2003-06-04 13:58 ` Benjamin Herrenschmidt
2003-06-04 14:10 ` Michael Frank
2003-06-04 14:29 ` Benjamin Herrenschmidt
2003-06-04 14:35 ` Michael Frank [this message]
2003-06-04 19:46 ` Pavel Machek
2003-06-04 20:16 ` Pavel Machek
2003-06-03 18:55 ` software suspend in 2.5.70-mm3 Pavel Machek
2003-06-08 2:26 ` hugang
2003-06-08 18:29 ` Pavel Machek
2003-06-08 2:27 ` hugang
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=200306042235.41326.mflt1@micrologica.com.hk \
--to=mflt1@micrologica.com.hk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=benh@kernel.crashing.org \
--cc=hugang@soulinfo.com \
--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