libertas module cant remove then insert again

[xie jiangbo]

Hi,all

I do the following steps:

[root at FriendlyARM plg]# insmod libertas.ko 
[root at FriendlyARM plg]# insmod libertas_sdio.ko 
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas: e0:2a:82:71:61:e3, fw 9.70.3p36, cap 0x00000303
cfg80211: Calling CRDA for country: JP
libertas: wlan0: Marvell WLAN 802.11 adapter
[root at FriendlyARM plg]# 
[root at FriendlyARM plg]# iwconfig
lo        no wireless extensions.
eth0      no wireless extensions.
wlan0     IEEE 802.11bg  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          
[root at FriendlyARM plg]# lsmod
libertas_sdio 8093 0 - Live 0xbf013000
libertas 44440 1 libertas_sdio, Live 0xbf000000
[root at FriendlyARM plg]# rmmod libertas_sdio
[root at FriendlyARM plg]# lsmod
[root at FriendlyARM plg]# 
[root at FriendlyARM plg]# insmod libertas.ko 
[root at FriendlyARM plg]# insmod libertas_sdio.ko 
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas: failed to load helper firmware
libertas_sdio: probe of mmc0:0001:1 failed with error -110

my platform is samsung 6410,linux 2.6.36,wifi chip is marvel8686 with  sdio.

android system offen remove and insert the driver. it will faild in the second insert.

so,any suggestion to this question ?




2011-04-21 



谢江波
深圳岭义科技有限公司
地址：深圳市罗湖区嘉宾路4051号金威大厦1913室
0755-25586481
xiejb at lingyitech.com




发件人： libertas-dev-request 
发送时间： 2011-04-21  00:01:03 
收件人： libertas-dev 
抄送： 
主题： libertas-dev Digest, Vol 58, Issue 11 
 
Send libertas-dev mailing list submissions to
libertas-dev at lists.infradead.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.infradead.org/mailman/listinfo/libertas-dev
or, via email, send a message with subject or body 'help' to
libertas-dev-request at lists.infradead.org
You can reach the person managing the list at
libertas-dev-owner at lists.infradead.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of libertas-dev digest..."
Today's Topics:
   1. tx watch dog timeout on resume kills device (Daniel Drake)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Apr 2011 19:19:57 +0100
From: Daniel Drake <dsd at laptop.org>
To: libertas-dev at lists.infradead.org
Subject: tx watch dog timeout on resume kills device
Message-ID: <BANLkTiktbaVmHhww8CY_R8sw+vZtu8tUEQ at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
At http://dev.laptop.org/ticket/10748 we're seeing libertas sd8686
dying occasionally during resume.
[  885.737199] Restarting tasks ... done.
[  891.020099] libertas: tx watch dog timeout
[  894.030042] libertas: command 0x000b timed out
[  894.034676] libertas: Timeout submitting command 0x000b
[  894.040554] libertas: PREP_CMD: command 0x000b failed: -11
[  896.010255] libertas: tx watch dog timeout
[  899.020103] libertas: command 0x001f timed out
[  899.024664] libertas: Timeout submitting command 0x001f
[  899.030530] ------------[ cut here ]------------
[  899.035468] WARNING: at lib/list_debug.c:30 __list_add+0x44/0x5a()
(the list corruption triggered by this failure must be another issue)
I'm still trying to figure out if there is some conflict in command
sequencing with the 0x1f GET_RSSI command submitted upon the timeout,
and 0xb which seems to be submitted by lbs_get_wireless_stats
(unfortunately enabling debug messages seems to avoid the issue)
We're also on 2.6.35; newer kernels don't submit the GET_RSSI command
so we'll be sure to test the latest code as well.
In the mean time, lbs_tx_timeout() seems a bit suspect. It would be
good to get some eyes on it.
I don't understand what this does:
dev->trans_start = jiffies; /* prevent tx timeout */
And the work done by lbs_send_tx_feedback() seems odd (we RX a
being-transmitted packet? Can't see any other driver that does this)
Is calling lbs_host_to_card_done() here likely to screw with any
pending commands?
Finally, how are TX timeouts detected by the network layer? I guess it
could be confused because of time elapsed during suspend? It seems
suspect that we receive a timeout immediately upon resume.
Thanks,
Daniel
------------------------------
_______________________________________________
libertas-dev mailing list
libertas-dev at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/libertas-dev
End of libertas-dev Digest, Vol 58, Issue 11
********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/libertas-dev/attachments/20110422/855300f3/attachment.html>