Bug 122094 - Freeze after inserting PCMCIA card
Summary: Freeze after inserting PCMCIA card
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-30 12:43 UTC by Ralf Kleineisel
Modified: 2015-01-04 22:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-16 04:08:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ralf Kleineisel 2004-04-30 12:43:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a)
Gecko/20031103

Description of problem:
When I insert my Cisco Aironet 350 WLAN PCMCAI card into my Dell
Latitude 510 the machine freezes completely. I have to switch the
power off to make it boot.

The last entry in /var/log/messages is:
Apr 29 17:59:59 gimli cardmgr[1053]: socket 0: 350 Series Wireless LAN
Adapter

If the card is in the slot when the machine boots it hangs when it
tries to initialize the PCMCIA.

My other PCMCIA card, a Xircom RealPort Ethernet10/100+Modem, works fine.


Version-Release number of selected component (if applicable):
kernel-2.6.5-1.327

How reproducible:
Always

Steps to Reproduce:
1.Insert card into slot
2.
3.
    

Actual Results:  Freeze.

Expected Results:  Don't freeze.

Additional info:

Comment 1 Dave Jones 2004-12-08 06:16:42 UTC
any better with the current updates ?

Comment 2 Dave Jones 2005-04-16 04:08:30 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.



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