[kismac] Re: System freeze after load of WirelessDriver.kext after unload of MACJack.kext

here's my rundown of events and corresponding syslog entries

insert card:
Jun 12 12:07:54 quack mach_kernel: IOPCCard info:   cs: memory probe 
0x90000000-0x9fffffff: clean.
Jun 12 12:07:54 quack mach_kernel: IOPCCard16Device: binding socket 0 function 
0 to card services.
Jun 12 12:07:55 quack mach_kernel: IOPCCard info:   
IOPCCard16Enabler::configure using index 0x01: Vcc 3.3, irq 255, io 
0x0000-0x003f
Jun 12 12:07:55 quack mach_kernel: org_noncontiguous_WirelessDriver: 
_wi_readChipInfos()
Jun 12 12:07:55 quack mach_kernel: org_noncontiguous_WirelessDriver: Firmware 
version: 3-0.8
Jun 12 12:07:55 quack mach_kernel: org_noncontiguous_WirelessDriver: Default 
channel 3
Jun 12 12:07:55 quack mach_kernel: org_noncontiguous_WirelessDriver: Ethernet 
address 00:02:6f:01:bc:21
Jun 12 12:07:55 quack mach_kernel: org_noncontiguous_WirelessDriver: wi_cmd 
error status, val: 121
Jun 12 12:07:56 quack mach_kernel: org_noncontiguous_WirelessDriver: 
wi_get_cur_ssid no record available. Default is: , len: 0


unload of WirelessDriver.kext succeeds, no log entry


kextload /Applications/KisMAC.app/Contents/Resources/MACJack.kext/:
Jun 12 12:11:09 quack mach_kernel: IOPCCard info:   
IOPCCard16Enabler::configure using index 0x01: Vcc 3.3, irq 255, io 
0x0000-0x003f
Jun 12 12:11:09 quack mach_kernel: MACJack: MACJackCard: Firmware vendor 31, 
variant 3, version 0.8


unload of MACJack.kext succeeds, no log entry


now things get icky..
kextload /System/Library/Extensions/WirelessDriver.kext/:
system freeze, no log... have to eject card


card ejection:
system becomes responsive, log entry:

Jun 12 12:13:03 quack mach_kernel:  to read from card after removal!
Jun 12 12:13:03 quack mach_kernel: CSR_READ_2: Attempt to read from card after 
removal!
Jun 12 12:13:03 quack last message repeated 67 times
Jun 12 12:13:03 quack mach_kernel: org_noncontiguous_WirelessDriver: wi_cmd 
timeout 2, val: 21
Jun 12 12:13:03 quack mach_kernel: org_noncontiguous_WirelessDriver: wi_cmd 
failed
Jun 12 12:13:03 quack mach_kernel: org_noncontiguous_WirelessDriver: Error 5 
reading ethernet address
Jun 12 12:13:03 quack mach_kernel: 
org_noncontiguous_WirelessDriver::start(provider=0x2ae8900, this=0x2ad2000) ** 
ABORTING! **
Jun 12 12:13:11 quack mach_kernel: IOPCCard: socket 0 did not terminate 
cleanly, state = 0x4.
Jun 12 12:13:11 quack mach_kernel: IOPCCard16Device: releasing socket 0 
function 0 from card services.


card insertion:
Jun 12 12:15:49 quack mach_kernel: IOPCCard16Device: binding socket 0 function 
0 to card services.
Jun 12 12:15:49 quack mach_kernel: IOPCCard info:   
IOPCCard16Enabler::configure using index 0x01: Vcc 3.3, irq 255, io 
0x0000-0x003f
Jun 12 12:15:49 quack mach_kernel: org_noncontiguous_WirelessDriver: 
_wi_readChipInfos()
Jun 12 12:15:49 quack mach_kernel: org_noncontiguous_WirelessDriver: Firmware 
version: 3-0.8
Jun 12 12:15:49 quack mach_kernel: org_noncontiguous_WirelessDriver: Default 
channel 3
Jun 12 12:15:49 quack mach_kernel: org_noncontiguous_WirelessDriver: Ethernet 
address 00:02:6f:01:bc:21
Jun 12 12:15:49 quack mach_kernel: org_noncontiguous_WirelessDriver: wi_cmd 
error status, val: 121
Jun 12 12:15:50 quack mach_kernel: org_noncontiguous_WirelessDriver: 
wi_get_cur_ssid no record available. Default is: , len: 0

now attempt to unload WirelessDriver.kext fails:
kextunload /System/Library/Extensions/WirelessDriver.kext/
unload kext /System/Library/Extensions/WirelessDriver.kext/ failed (result code 
0xdc004002)

system log:
Jun 12 12:17:28 quack mach_kernel: Can't unload 
org.noncontiguous.WirelessDriver due to -
Jun 12 12:17:28 quack mach_kernel: org.noncontiguous.WirelessDriver: 
org_noncontiguous_WirelessDriver has 1 instance(s)

I should note that i can load and unload the WirelessDriver all day and night, 
it only
breaks when I try loading after unload of MACJack.kext

Let me know if you need any more info

Thanks

-dave

On Thu, Jun 12, 2003 at 12:55:00PM +0200, Michael Rossberg wrote:
> >> I have the same situation, as I reported earlier.  The problem with
> >> this bug is that it requires looking both at the Wireless Driver and
> >> MacJack.  I suppose the first step is to compile  debugging drivers
> >> that write to the system.log.  I'm a professor, and this week is the
> >> one of final exams, so I won't have time to work on it for a while.
> >> Mick has been very responsive to previous bug reports though.  Perhaps
> >> he will be able to quickly squash this bug as well.
> 
> i played a little bit around, and i only ran into one bug. when i 
> reload the wireless driver and have a client running (such as the pref 
> pane) then the system will crash, when trying to goto sleep. this is 
> definitely a problem of wireless.kext, and it seems to be a tricky one. 
> at least i could not find anything.
> i cannot reproduce the problem with the system crash. do you have some 
> errors in your system.log?
> 
> mick

Other related posts: