Re: IDE Power Management (Was: software suspend in 2.5.70-mm3)

Michael Frank (mflt1@micrologica.com.hk)
Wed, 4 Jun 2003 22:35:41 +0800


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/

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/