From: Russell King <rmk@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues)
Date: Sun, 5 Oct 2003 17:10:55 +0100 [thread overview]
Message-ID: <20031005171055.A21478@flint.arm.linux.org.uk> (raw)
On Sun, Aug 17, 2003 at 05:23:10PM +0100, Russell King wrote:
> On Wed, Aug 06, 2003 at 11:15:19PM +0100, Russell King wrote:
> > 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:
>
> I've just been doing further testing.
>
> The kernel test setup consists of booting a kernel with init=/bin/sh,
> and after the shell prompt appears, hitting the BIOS-magic "suspend to
> RAM" key combination.
I've just re-tested this with 2.6.0-test6, and the problem persists.
Red Hat 2.4.20-20.7smp works fine.
I'm booting both 2.4 and 2.6 kernels with: init=/bin/sh apm=debug
without starting any daemons, or having any PCMCIA socket drivers
loaded. apm debug messages appear to be identical between 2.4 and
2.6 kernels.
On Mon, Aug 11, 2003 at 10:50:39PM +1000, Stephen Rothwell wrote:
> The error logged by the apm driver indicates an error from the BIOS. So
> the BIOS thinks the machine is in a state that it cannot suspend from.
If that is so, how do we go about debugging this type of problem?
I've tried the obvious of disabling virtually all drivers, and this
doesn't appear to make any difference what so ever. I'm guessing
that something in the core i386 architecture code is causing the
problem.
--
Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next reply other threads:[~2003-10-05 16:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 16:10 Russell King [this message]
2003-12-28 17:46 ` 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues) Russell King
2003-12-28 18:25 ` Russell King
2003-12-28 20:49 ` Linus Torvalds
2003-12-30 11:43 ` Russell King
2003-12-30 16:50 ` Russell King
2003-12-30 18:17 ` Russell King
2003-12-30 18:47 ` Linus Torvalds
2003-12-30 19:40 ` Russell King
2003-12-30 19:53 ` Russell King
2003-12-30 23:00 ` Vojtech Pavlik
2003-12-31 1:45 ` Dmitry Torokhov
2003-12-31 12:40 ` Vojtech Pavlik
2004-01-03 3:43 ` Rusty Russell
2004-01-03 18:28 ` Pavel Machek
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=20031005171055.A21478@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