PCMCIA breaks suspend-to-(disk|ram) with 2.6.11

Dominik Brodowski linux at dominikbrodowski.net
Wed Mar 2 17:21:05 EST 2005

[moving this to linux-pcmcia list where it is better suited]

On Wed, Mar 02, 2005 at 07:24:37PM +0100, Sebastian Kügler wrote:
> Unloading orincoco_cs and then yenta_socket hangs rmmod in D state.
Does issuing a "cardctl eject" in between help? Or do you do this before?
I'd think orinoco_cs has usage count 1 during normal use (even with
interface down).

> If I then 
> send the machine to S3 it will hang on resume, right after having switched 
> the display back on, leaving me with funny colors and a not-responding system 
> (no SYSRQ, no reaction on CAPS lock, whatsoever).

I might assume this is caused by rmmod in D.

> Both, S3 and S4 work fine without the PCMCIA adapter inserted. My suspend 
> scripts unload PCMCIA and related stuff and are supposed to stop cardmgr. (I 
> have problems resuming without the PCMCIA card plugged in when I suspended 
> with it inserted, making swsusp hang about at the end of resuming with 
> "orinoco_lock() called with hw_unavailable (dev=de08f800)".)

Is this a regression, too?

> I am getting this oops if I try to rmmod -f orinoco_cs while the card is 
> inserted, the problem seems to boil down to that (This oops obviously renders 
> the PCMCIA card unusable until I reboot):

cardctl eject or

echo "42" > /sys/class/pcmcia_socket/pcmcia_socket%n/card_eject

should allow you to rmmod orinoco_cs and then yenta_socket. Actually, you
won't need to rmmod orinoco_cs then as the kernel will behave as if there
were no card inserted to the socket then.

On a sidenote, I intend to allow to do a "rmmod MODULE" when a matching card
is inserted in a few weeks, but only after some more cleanups have gone in.
Currently, it'd mean nasty little races.

> On a different note, is there a split out version of the PCMCIA hotplug stuff 
> recently merged into -mm? I'd like to try it and see if it fixes my issues, 
> but I'd rather not introduce too much new deltas.

everything is at
[actually, it isn't yet, but should appear there any minute]

and patches are applied in the order of the numbering [-02b- after -02-].
However, I don't think these patches change anything with regard to the
problems you're experiencing with PCMCIA. Nonetheless, these patches enjoy
being tested ;)


More information about the linux-pcmcia mailing list