Bug 6983 - Computer freezes plugging card into yenta slot
Summary: Computer freezes plugging card into yenta slot
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCMCIA (show other bugs)
Hardware: i386 Linux
: P2 blocking
Assignee: linux-pcmcia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-10 09:57 UTC by Cijoml Cijomlovic Cijomlov
Modified: 2007-03-01 11:28 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.17 and higher
Tree: Mainline
Regression: ---


Attachments
photo of the monitor (643.61 KB, image/jpeg)
2006-08-10 10:07 UTC, Cijoml Cijomlovic Cijomlov
Details

Description Cijoml Cijomlovic Cijomlov 2006-08-10 09:57:09 UTC
Most recent kernel where this bug did not occur:
Distribution: Debian testing
Hardware Environment: Acer TravelMate 242
Software Environment: 
Problem Description:

Steps to reproduce:
plug card into slot see dmesg output
Comment 1 Cijoml Cijomlovic Cijomlov 2006-08-10 10:07:10 UTC
Created attachment 8747 [details]
photo of the monitor

photo of the monitor
Comment 2 Larry Finger 2006-08-10 11:36:01 UTC
What is the card? From what I see in the photo, I think it is a wireless card.
If it has a BCM43xx chip, there is an initialization problem in V2.6.17.
Unfortunately, the patch missed the 2.6.18 time window, and the fix will not be
in the mainline code until 2.6.19.
Comment 3 Cijoml Cijomlovic Cijomlov 2006-08-10 12:39:58 UTC
No, it is Hostap driver ZCOM XI-325

ieee80211_crypt: registered algorithm 'NULL'
hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: , irq 3, io 0x3100-0x313f
prism2_hw_init: initialized in 205 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.2
wifi0: registered netdevice wlan0
Comment 4 Cijoml Cijomlovic Cijomlov 2007-03-01 11:28:59 UTC
Looks this problem disappeared in newest kernels

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