[Trac #1271] libertas ad-hoc in build 368 causes backtrace to be printed in dmesg

[Zarro Boogs per Child]

#1271: libertas ad-hoc in build 368 causes backtrace to be printed in dmesg
----------------------+-----------------------------------------------------
 Reporter:  andrey    |       Owner:  marcelo  
     Type:  defect    |      Status:  new      
 Priority:  normal    |   Milestone:  Untriaged
Component:  wireless  |    Keywords:  libertas 
----------------------+-----------------------------------------------------
 I use rc.local to bring msh0 up in ad-hoc on bootup.  In build 368 (driver
 ) I see the following in dmesg, after the usb8xxx and libertas modules are
 loaded and the initial iwconfig runs:

 {{{
 [   72.999905] BUG: at drivers/net/wireless/libertas/join.c:595
 libertas_cmd_80211_ad_hoc_start()
 [   73.009995]  [<c8924df3>] libertas_cmd_80211_ad_hoc_start+0x140/0x428
 [libertas]
 [   73.018988]  [<c891b166>] cleanup_cmdnode+0x29/0x57 [libertas]
 [   73.026011]  [<c891b21d>] libertas_get_free_cmd_ctrl_node+0x89/0x9f
 [libertas]
 [   73.034722]  [<c891c238>]
 libertas_prepare_and_send_command+0x98a/0x1943 [libertas]
 [   73.043969]  [<c041e9a1>] autoremove_wake_function+0x0/0x35
 [   73.050641]  [<c891d446>] libertas_set_radio_control+0x7a/0x120
 [libertas]
 [   73.059003]  [<c8923f8d>] libertas_start_adhoc_network+0x13b/0x142
 [libertas]
 [   73.067634]  [<c892fbe5>] assoc_helper_associate+0x4b6/0x54c [libertas]
 [   73.075573]  [<c041e9a1>] autoremove_wake_function+0x0/0x35
 [   73.082270]  [<c89309cd>] libertas_association_worker+0xd52/0x1001
 [libertas]
 [   73.090976]  [<c0402c35>] __switch_to+0x19/0x143
 [   73.096489]  [<c041be77>] run_workqueue+0x84/0x124
 [   73.102250]  [<c05bb9fd>] _spin_lock_irqsave+0x18/0x1d
 [   73.108508]  [<c892fc7b>] libertas_association_worker+0x0/0x1001
 [libertas]
 [   73.116849]  [<c041c499>] worker_thread+0x105/0x12e
 [   73.122716]  [<c040c597>] default_wake_function+0x0/0xc
 [   73.128965]  [<c041c394>] worker_thread+0x0/0x12e
 [   73.134529]  [<c041e8e8>] kthread+0xa0/0xc8
 [   73.139615]  [<c041e848>] kthread+0x0/0xc8
 [   73.144463]  [<c040404b>] kernel_thread_helper+0x7/0x10
 [   73.150722]  =======================
 [   73.159374] ADDRCONF(NETDEV_CHANGE): msh0: link becomes ready
 }}}

 However the ad-hoc mode seems to work fine and the interface works in
 general.  This is also with Network Manager disabled and I am only using
 ad-hoc to start the radio (for mesh testing).  I'll see if I can reproduce
 it in any other ways, but I thought I'd file this as a start.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1271>
One Laptop Per Child <http://laptop.org/>