Bug 139710 - airo_cs: infinite loop on shutdown
Summary: airo_cs: infinite loop on shutdown
Keywords:
Status: CLOSED DUPLICATE of bug 139709
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-17 17:41 UTC by Kjartan Maraas
Modified: 2015-01-04 22:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kjartan Maraas 2004-11-17 17:41:26 UTC
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:

Comment 1 Bill Nottingham 2004-11-18 08:42:15 UTC

*** This bug has been marked as a duplicate of 139709 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:07:05 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.