Messages in this thread | | | Date | Wed, 4 Jun 2003 21:46:59 +0200 | From | Pavel Machek <> | Subject | Re: IDE Power Management (Was: software suspend in 2.5.70-mm3) |
| |
Hi!
> > ............ > > [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)
Why? Suspending then resuming it may take long but seems correct to me.
> > 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.
Yes, it looks so. Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - 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/
| |