From: Russell King <rmk@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test2: unable to suspend (APM)
Date: Wed, 6 Aug 2003 23:15:19 +0100 [thread overview]
Message-ID: <20030806231519.H16116@flint.arm.linux.org.uk> (raw)
Hi,
I'm trying to test out APM on my laptop (in order to test some PCMCIA
changes), but I'm hitting a brick wall. I've added the device_suspend()
calls for the SAVE_STATE, DISABLE and the corresponding device_resume()
calls into apm's suspend() function. (this is needed so that PCI
devices receive their notifications.)
However, APM is refusing to suspend. I'm seeing the following kernel
messages:
Suspending devices
hdb: start_power_step(step: 0)
hdb: completing PM request, suspend
hda: start_power_step(step: 0)
hda: start_power_step(step: 1)
hda: complete_power_step(step: 1, stat: 50, err: 0)
hda: completing PM request, suspend
Suspending devices
Suspending devices
apm: suspend: Unable to enter requested state
Devices Resumed
hda: Wakeup request inited, waiting for !BSY...
hda: start_power_step(step: 1000)
blk: queue c03a845c, I/O limit 4095Mb (mask 0xffffffff)
hda: completing PM request, resume
hdb: Wakeup request inited, waiting for !BSY...
hdb: start_power_step(step: 1000)
hdb: completing PM request, resume
Devices Resumed
Devices Resumed
The "apm: suspend: Unable to enter requested state" occurs about 20
seconds afterwards.
(Note that APM worked fine with 2.2 and 2.4 kernels.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next reply other threads:[~2003-08-06 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 22:15 Russell King [this message]
2003-08-07 2:46 ` 2.6.0-test2: unable to suspend (APM) Charles Lepple
2003-08-07 10:45 ` Stephen Rothwell
2003-08-07 11:00 ` Russell King
2003-08-07 12:31 ` Charles Lepple
2003-08-07 13:50 ` Alan Cox
2003-08-11 10:14 ` Pavel Machek
2003-08-11 11:31 ` Russell King
2003-08-11 12:50 ` Stephen Rothwell
2003-08-17 16:23 ` Russell King
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=20030806231519.H16116@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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