Description of problem: If I shut down my laptop without stopping the pcmcia service the machine enters an infinite loop where the airo driver spews the console with a lot of diagnostics and messages saying it's waiting for the device to become free and that the use count is still 1. I also see the following when doing service pcmcia start/stop: [root@localhost wireless]# service pcmcia stop Shutting down PCMCIA services: ERROR: Module pcmcia_core is in use by yenta_socket done. [root@localhost wireless]# service pcmcia start Starting PCMCIA services: cardmgr[3746]: open_sock(socket 2) failed: Bad file descriptor cardmgr[3746]: watching 2 sockets done. [root@localhost wireless]# [root@localhost wireless]# lsmod |grep airo airo_cs 7237 0 airo 64225 1 airo_cs ds 16965 5 airo_cs pcmcia_core 59913 3 airo_cs,ds,yenta_socket 00:0b.0 CardBus bridge: O2 Micro, Inc. OZ711M1 SmartCardBus MultiMediaBay Controller (rev 20) The card is a Cisco Aironet 350 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** Bug 139710 has been marked as a duplicate of this bug. ***
I saw the Use count = 1 message using madwifi too. Maybe it's a refcounting problem in the pcmcia subsystem itself? Could be that both drivers do the same thing wrong of course...
Latest offender is vmware with a vmnet device spewing these warnings.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
This bug has been automatically closed as part of a mass update. It had been in NEEDINFO state since July 2005. If this bug still exists in current errata kernels, please reopen this bug. There are a large number of inactive bugs in the database, and this is the only way to purge them. Thank you.