From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Jani-Matti Hätinen" <jani-matti.hatinen@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lock-up with modprobe sdhci after suspending to ram
Date: Fri, 05 May 2006 22:40:57 +0200 [thread overview]
Message-ID: <445BB859.9030800@drzeus.cx> (raw)
In-Reply-To: <200605040957.30758.jani-matti.hatinen@iki.fi>
Jani-Matti Hätinen wrote:
> I'm not sure if this has any effect on the sdhci issue, but during a normal
> suspend&resume (i.e. when sdhci has been rmmoded earlier) I get the following
> error about the PCMCIA CardBus slot, which is on the same PCI channel as the
> card reader (01:03.0 and 01:03.2 respectively):
>
> May 4 09:37:38 leevi PCMCIA: socket c14d8828: *** DANGER *** unable to remove
> socket power
>
> And the PCMCIA slot doesn't work either after a suspend&resume. I haven't
> tested FireWire yet (which is also on the same PCI channel 01:03.1), but I
> will shortly.
>
>
Sounds like there is something fundamentally broken with your suspend.
It seems like we should hold off on the card reader until the more basic
stuff, like the cardbus slot, works properly after resume.
Rgds
Pierre
next prev parent reply other threads:[~2006-05-05 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 7:33 Lock-up with modprobe sdhci after suspending to ram Jani-Matti Hätinen
2006-04-24 12:29 ` Pierre Ossman
2006-04-25 8:08 ` Jani-Matti Hätinen
2006-04-25 8:42 ` Pierre Ossman
2006-04-25 13:45 ` Jani-Matti Hätinen
2006-04-29 15:25 ` Pierre Ossman
2006-05-04 6:57 ` Jani-Matti Hätinen
2006-05-05 20:40 ` Pierre Ossman [this message]
2006-04-25 10:12 ` Pekka Enberg
2006-04-25 19:11 ` Jani-Matti Hätinen
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=445BB859.9030800@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=jani-matti.hatinen@iki.fi \
--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