From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Frank <mflt1@micrologica.com.hk>
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: 04 Jun 2003 16:29:20 +0200 [thread overview]
Message-ID: <1054736960.20838.44.camel@gaston> (raw)
In-Reply-To: <200306042210.12468.mflt1@micrologica.com.hk>
> 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)
> 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.
> Call Trace:
> [<c011d958>] schedule+0x40/0x388
> [<c011eb02>] io_schedule+0xe/0x18
> [<c01384d5>] wait_on_page_bit_wq+0xc9/0xe4
> [<c011f320>] autoremove_wake_function+0x0/0x3c
> [<c011f320>] autoremove_wake_function+0x0/0x3c
> [<c01384fa>] wait_on_page_bit+0xa/0x10
> [<c014cc34>] rw_swap_page_sync+0x98/0xc6
> [<c0136afd>] write_suspend_image+0xf1/0x324
> [<c0246bdf>] device_resume+0x7f/0x88
> [<c01370e1>] drivers_unsuspend+0x11/0x18
> [<c013735e>] suspend_save_image+0x12/0x1c
> [<c013753f>] do_magic_suspend_2+0x17/0xa8
> [<c011ba9d>] do_magic+0x4d/0x130
> [<c013763b>] do_software_suspend+0x6b/0x90
> [<c0137695>] software_suspend+0x35/0x3c
> [<c012ba97>] sys_reboot+0x2df/0x36c
> [<c0143830>] unmap_page_range+0x38/0x5c
> [<c0143959>] unmap_vmas+0x105/0x208
> [<c01656e4>] dput+0x1c/0x204
> [<c01656e4>] dput+0x1c/0x204
> [<c015d367>] path_release+0xf/0x30
> [<c014fe69>] sys_chdir+0x5d/0x68
> [<c010af17>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2003-06-04 14:16 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 [this message]
2003-06-04 14:35 ` Michael Frank
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=1054736960.20838.44.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
--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