From: Russell King <rmk+lkml@arm.linux.org.uk>
To: pZa1x <pZa1x@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM Suspend Problem
Date: Sat, 29 Nov 2003 08:22:00 +0000 [thread overview]
Message-ID: <20031129082200.A30476@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3FC7F2E3.8080109@rogers.com>; from pZa1x@rogers.com on Sat, Nov 29, 2003 at 01:14:11AM +0000
On Sat, Nov 29, 2003 at 01:14:11AM +0000, pZa1x wrote:
> A follow-up
>
> by shutting down PCMCIA and rmmod'ing all the related modules ie ide_cs,
> ds, yenta_socket, pcmcia_core the suspend works on AC again.
>
> So, I add them back one by one:
> pcmcia_core -> still works
> yenta_socket -> FAILS!
> rmmod yenta_socket -> works again!
>
> Summary: suspend works on my Thinkpad T21
> (a) with no apm module or apmd but with all PCMCIA (ie. hardware
> suspend- close lid etc);
> (b) with apm & apmd and all PCMCIA but no AC power
> (c) with apm & apmd but no yenta_socket and the rest but with AC power
>
> The problem is a combination of apm, yenta_socket and AC power.
The output of:
lspci -vvxxxx
both with and without yenta_socket inserted would be a useful starting
point.
--
Russell King
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 prev parent reply other threads:[~2003-11-29 8:22 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 1:02 APM Suspend Problem pZa1x
2003-11-29 1:14 ` pZa1x
2003-11-29 8:22 ` Russell King [this message]
2003-11-29 11:26 ` pZa1x
2003-12-01 21:07 ` Russell King
2003-12-06 21:46 ` pZa1x
2003-12-07 17:06 ` Russell King
2003-12-08 2:06 ` pcmcia yenta no devices " Bob
2003-12-08 9:43 ` Russell King
[not found] <15Eea-Id-23@gated-at.bofh.it>
[not found] ` <15Eea-Id-25@gated-at.bofh.it>
[not found] ` <15Eea-Id-27@gated-at.bofh.it>
[not found] ` <15Eea-Id-21@gated-at.bofh.it>
2003-12-25 19:17 ` Michael Schierl
[not found] <WnPi.57n.5@gated-at.bofh.it>
[not found] ` <WsPg.Xi.35@gated-at.bofh.it>
[not found] ` <WAWd.BP.7@gated-at.bofh.it>
2003-11-28 21:12 ` Michael Schierl
-- strict thread matches above, loose matches on Subject: below --
2003-11-27 6:20 Misha Nasledov
2003-11-27 11:46 ` Felipe Alfaro Solana
2003-11-27 20:22 ` Misha Nasledov
2003-11-27 22:58 ` Benjamin Herrenschmidt
2003-11-27 23:33 ` Misha Nasledov
2003-11-28 21:28 ` William Lee Irwin III
2003-11-28 21:50 ` Misha Nasledov
2003-11-28 21:50 ` William Lee Irwin III
2003-11-28 22:27 ` Nigel Cunningham
2003-11-28 22:49 ` William Lee Irwin III
2003-11-29 2:17 ` Misha Nasledov
2003-11-29 2:20 ` William Lee Irwin III
2003-11-29 2:35 ` Nigel Cunningham
2003-11-29 5:38 ` Shawn Willden
2003-11-29 5:46 ` William Lee Irwin III
2003-11-29 9:57 ` Misha Nasledov
2003-11-29 7:36 ` Misha Nasledov
2003-12-01 20:24 ` Pavel Machek
2003-12-02 21:44 ` john stultz
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=20031129082200.A30476@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pZa1x@rogers.com \
/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