* wl1271 watchdog interrupt @ 2012-03-22 1:26 Troy Kisky 2012-03-27 14:25 ` Gary Thomas 0 siblings, 1 reply; 8+ messages in thread From: Troy Kisky @ 2012-03-22 1:26 UTC (permalink / raw) To: linux-wireless Hi all We have a new board using the wl1271. As long as I keep it busy, everything is fine. But once it becomes idle I get, "wl12xx: ERROR watchdog interrupt received! starting recovery." Has this been seen by others? I'm using compat-wireless-2012-01-26 and my kernel is based on 3.0 Other relevant log messages: cfg80211: Calling CRDA to update world regulatory domain add wake up source irq 108 wl12xx: loaded wl12xx: firmware booted (Rev 6.3.0.0.77) wlan0: authenticate with 00:12:17:31:67:e7 (try 1) wlan0: authenticated wlan0: associate with 00:12:17:31:67:e7 (try 1) wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) wlan0: associated wlan0: moving STA 00:12:17:31:67:e7 to state 1 wlan0: moving STA 00:12:17:31:67:e7 to state 2 wlan0: moving STA 00:12:17:31:67:e7 to state 3 wl12xx: Association completed. ....... wl12xx: ERROR watchdog interrupt received! starting recovery. wl12xx: Reading FW panic log wl12xx: ERROR command complete timeout ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-01-26/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) from [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace b6d18e2d5294f64d ]--- wl12xx: ERROR failed to send stop firmware logger command wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 wl12xx: down ieee80211 phy0: Hardware restart was requested mmc2: Timeout waiting for hardware interrupt. sdhci: =========== REGISTER DUMP (mmc2)=========== sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci: Argument: 0x26ff8804 | Trn mode: 0x00000000 sdhci: Present: 0xfff9820e | Host ctl: 0x000000de sdhci: Power: 0x0000000b | Blk gap: 0x00000000 sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff sdhci: Host ctl2: 0x00000088 sdhci: =========================================== wl1271_sdio mmc2:0001:2: sdio read failed (-110) wl1271_sdio mmc2:0001:2: sdio write failed (-84) mmc2: Timeout waiting for hardware interrupt. sdhci: =========== REGISTER DUMP (mmc2)=========== sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci: Argument: 0x279c6804 | Trn mode: 0x00000000 sdhci: Present: 0xfff9820e | Host ctl: 0x000000de sdhci: Power: 0x0000000b | Blk gap: 0x00000000 sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff sdhci: Host ctl2: 0x00000088 sdhci: =========================================== wl1271_sdio mmc2:0001:2: sdio read failed (-110) wl12xx: ERROR chip id doesn't match after firmware boot mmc2: Timeout waiting for hardware interrupt. sdhci: =========== REGISTER DUMP (mmc2)=========== sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci: Argument: 0x24ace804 | Trn mode: 0x00000000 sdhci: Present: 0xfff9820e | Host ctl: 0x000000de sdhci: Power: 0x0000000b | Blk gap: 0x00000000 sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff sdhci: Host ctl2: 0x00000088 sdhci: =========================================== wl1271_sdio mmc2:0001:2: sdio read failed (-110) wl12xx: WARNING unsupported chip id: 0x1 mmc2: Timeout waiting for hardware interrupt. sdhci: =========== REGISTER DUMP (mmc2)=========== sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 sdhci: Argument: 0x24ace804 | Trn mode: 0x00000000 sdhci: Present: 0xfff9820e | Host ctl: 0x000000de sdhci: Power: 0x0000000b | Blk gap: 0x00000000 sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff sdhci: Host ctl2: 0x00000088 sdhci: =========================================== wl1271_sdio mmc2:0001:2: sdio read failed (-110) wl12xx: WARNING unsupported chip id: 0x1 wl12xx: ERROR firmware boot failed despite 3 retries ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-11) ____________________________________________ I've tried the latest compat-wireless, but it gets an error after association is completed. Here's the messages with compat-wireless-2012-03-18; Any tips appreciated. Thanks Troy ************************************************************************* cfg80211: Calling CRDA to update world regulatory domain add wake up source irq 108 wl12xx: loaded wl12xx: firmware booted (Rev 6.3.5.0.98) wlan0: authenticate with 00:12:17:31:67:e7 wlan0: send auth to 00:12:17:31:67:e7 (try 1/3) wlan0: authenticated wlan0: associate with 00:12:17:31:67:e7 (try 1/3) wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) wlan0: associated wl12xx: ERROR command complete timeout ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0abb3c>] (wl1271_cmd_configure+0x38/0x60 [wl12xx]) [<7f0abb3c>] (wl1271_cmd_configure+0x38/0x60 [wl12xx]) from [<7f0b0afc>] (wl1271_acx_set_ht_capabilities+0x80/0xd4 [wl12xx]) [<7f0b0afc>] (wl1271_acx_set_ht_capabilities+0x80/0xd4 [wl12xx]) from [<7f0a64c8>] (wl1271_op_bss_info_changed+0x7c8/0x10ec [wl12xx]) [<7f0a64c8>] (wl1271_op_bss_info_changed+0x7c8/0x10ec [wl12xx]) from [<7f057b10>] (ieee80211_bss_info_change_notify+0xd4/0x1ac [mac80211]) [<7f057b10>] (ieee80211_bss_info_change_notify+0xd4/0x1ac [mac80211]) from [<7f07c9d4>] (ieee80211_assoc_success+0x360/0x5cc [mac80211]) [<7f07c9d4>] (ieee80211_assoc_success+0x360/0x5cc [mac80211]) from [<7f07cd94>] (ieee80211_rx_mgmt_assoc_resp+0x154/0x26c [mac80211]) [<7f07cd94>] (ieee80211_rx_mgmt_assoc_resp+0x154/0x26c [mac80211]) from [<7f07d698>] (ieee80211_sta_rx_queued_mgmt+0xc0/0x518 [mac80211]) [<7f07d698>] (ieee80211_sta_rx_queued_mgmt+0xc0/0x518 [mac80211]) from [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f291393445e ]--- wl12xx: WARNING CONFIGURE command NOK wl12xx: WARNING acx ht capabilities setting failed: -110 wl12xx: WARNING Set ht cap false failed -110 wl12xx: ERROR watchdog interrupt received! starting recovery. wl12xx: ERROR command complete timeout ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0ab1cc>] (wl12xx_cmd_set_default_wep_key+0x80/0xb0 [wl12xx]) [<7f0ab1cc>] (wl12xx_cmd_set_default_wep_key+0x80/0xb0 [wl12xx]) from [<7f0a5180>] (wl1271_set_key+0x2ec/0x3e4 [wl12xx]) [<7f0a5180>] (wl1271_set_key+0x2ec/0x3e4 [wl12xx]) from [<7f0a53c0>] (wl1271_op_set_key+0x148/0x2d0 [wl12xx]) [<7f0a53c0>] (wl1271_op_set_key+0x148/0x2d0 [wl12xx]) from [<7f074de4>] (ieee80211_key_enable_hw_accel+0xd4/0x1b4 [mac80211]) [<7f074de4>] (ieee80211_key_enable_hw_accel+0xd4/0x1b4 [mac80211]) from [<7f075350>] (ieee80211_key_link+0xa4/0x13c [mac80211]) [<7f075350>] (ieee80211_key_link+0xa4/0x13c [mac80211]) from [<7f06c654>] (ieee80211_add_key+0xc0/0x140 [mac80211]) [<7f06c654>] (ieee80211_add_key+0xc0/0x140 [mac80211]) from [<7f025198>] (cfg80211_upload_connect_keys+0xb0/0x654 [cfg80211]) [<7f025198>] (cfg80211_upload_connect_keys+0xb0/0x654 [cfg80211]) from [<7f03ce98>] (__cfg80211_connect_result+0x1e8/0x330 [cfg80211]) [<7f03ce98>] (__cfg80211_connect_result+0x1e8/0x330 [cfg80211]) from [<7f03abb0>] (cfg80211_send_rx_assoc+0x104/0x12c [cfg80211]) [<7f03abb0>] (cfg80211_send_rx_assoc+0x104/0x12c [cfg80211]) from [<7f07d77c>] (ieee80211_sta_rx_queued_mgmt+0x1a4/0x518 [mac80211]) [<7f07d77c>] (ieee80211_sta_rx_queued_mgmt+0x1a4/0x518 [mac80211]) from [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f291393445f ]--- wl12xx: WARNING cmd set_default_wep_key failed: -110 wl12xx: ERROR Could not add or replace key ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-110) wl12xx: Reading FW panic log wl12xx: ERROR command complete timeout ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0aa8ec>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) [<7f0aa8ec>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) from [<7f0a8dac>] (wl1271_recovery_work+0x228/0x328 [wl12xx]) [<7f0a8dac>] (wl1271_recovery_work+0x228/0x328 [wl12xx]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f2913934460 ]--- wl12xx: ERROR failed to send stop firmware logger command wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.5.0.98 pc: 0x9a16 wl12xx: down ieee80211 phy0: Hardware restart was requested wl12xx: ERROR timeout waiting for the hardware to complete initialization wl12xx: ERROR timeout waiting for the hardware to complete initialization wl12xx: ERROR timeout waiting for the hardware to complete initialization wl12xx: ERROR firmware boot failed despite 3 retries ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f2913934461 ]--- ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f2913934462 ]--- ------------[ cut here ]------------ WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) ---[ end trace 211b9f2913934463 ]--- ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-11) ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-03-22 1:26 wl1271 watchdog interrupt Troy Kisky @ 2012-03-27 14:25 ` Gary Thomas 2012-04-02 8:39 ` Luciano Coelho 0 siblings, 1 reply; 8+ messages in thread From: Gary Thomas @ 2012-03-27 14:25 UTC (permalink / raw) To: Troy Kisky; +Cc: linux-wireless, Luciano Coelho On 2012-03-21 19:26, Troy Kisky wrote: > Hi all > > We have a new board using the wl1271. As long as I keep it busy, > everything is fine. But once it becomes idle I get, > "wl12xx: ERROR watchdog interrupt received! starting recovery." > > Has this been seen by others? I'm getting very similar problems and my messages to this list (and the wl12xx maintainer) are now waiting for nearly two weeks for an answer. Can someone help with these wl12xx issues? > I'm using compat-wireless-2012-01-26 and my kernel is based on 3.0 > > Other relevant log messages: > cfg80211: Calling CRDA to update world regulatory domain > add wake up source irq 108 > wl12xx: loaded > wl12xx: firmware booted (Rev 6.3.0.0.77) > wlan0: authenticate with 00:12:17:31:67:e7 (try 1) > wlan0: authenticated > wlan0: associate with 00:12:17:31:67:e7 (try 1) > wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) > wlan0: associated > wlan0: moving STA 00:12:17:31:67:e7 to state 1 > wlan0: moving STA 00:12:17:31:67:e7 to state 2 > wlan0: moving STA 00:12:17:31:67:e7 to state 3 > wl12xx: Association completed. > > ....... > wl12xx: ERROR watchdog interrupt received! starting recovery. > wl12xx: Reading FW panic log > wl12xx: ERROR command complete timeout > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-01-26/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) > [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) > [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) from [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) > [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace b6d18e2d5294f64d ]--- > wl12xx: ERROR failed to send stop firmware logger command > wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 > wl12xx: down > ieee80211 phy0: Hardware restart was requested > mmc2: Timeout waiting for hardware interrupt. > sdhci: =========== REGISTER DUMP (mmc2)=========== > sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 > sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci: Argument: 0x26ff8804 | Trn mode: 0x00000000 > sdhci: Present: 0xfff9820e | Host ctl: 0x000000de > sdhci: Power: 0x0000000b | Blk gap: 0x00000000 > sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f > sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 > sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b > sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 > sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 > sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff > sdhci: Host ctl2: 0x00000088 > sdhci: =========================================== > wl1271_sdio mmc2:0001:2: sdio read failed (-110) > wl1271_sdio mmc2:0001:2: sdio write failed (-84) > mmc2: Timeout waiting for hardware interrupt. > sdhci: =========== REGISTER DUMP (mmc2)=========== > sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 > sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci: Argument: 0x279c6804 | Trn mode: 0x00000000 > sdhci: Present: 0xfff9820e | Host ctl: 0x000000de > sdhci: Power: 0x0000000b | Blk gap: 0x00000000 > sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f > sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 > sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b > sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 > sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 > sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff > sdhci: Host ctl2: 0x00000088 > sdhci: =========================================== > wl1271_sdio mmc2:0001:2: sdio read failed (-110) > wl12xx: ERROR chip id doesn't match after firmware boot > > mmc2: Timeout waiting for hardware interrupt. > sdhci: =========== REGISTER DUMP (mmc2)=========== > sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 > sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci: Argument: 0x24ace804 | Trn mode: 0x00000000 > sdhci: Present: 0xfff9820e | Host ctl: 0x000000de > sdhci: Power: 0x0000000b | Blk gap: 0x00000000 > sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f > sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 > sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b > sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 > sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 > sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff > sdhci: Host ctl2: 0x00000088 > sdhci: =========================================== > wl1271_sdio mmc2:0001:2: sdio read failed (-110) > wl12xx: WARNING unsupported chip id: 0x1 > mmc2: Timeout waiting for hardware interrupt. > sdhci: =========== REGISTER DUMP (mmc2)=========== > sdhci: Sys addr: 0x4a3b1ae8 | Version: 0x00000003 > sdhci: Blk size: 0x00000004 | Blk cnt: 0x00000001 > sdhci: Argument: 0x24ace804 | Trn mode: 0x00000000 > sdhci: Present: 0xfff9820e | Host ctl: 0x000000de > sdhci: Power: 0x0000000b | Blk gap: 0x00000000 > sdhci: Wake-up: 0x00000000 | Clock: 0x0000007f > sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 > sdhci: Int enab: 0x007f000b | Sig enab: 0x007f000b > sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003 > sdhci: Caps: 0x07f30000 | Caps_1: 0x00000007 > sdhci: Cmd: 0x0000353a | Max curr: 0x00ffffff > sdhci: Host ctl2: 0x00000088 > sdhci: =========================================== > wl1271_sdio mmc2:0001:2: sdio read failed (-110) > wl12xx: WARNING unsupported chip id: 0x1 > wl12xx: ERROR firmware boot failed despite 3 retries > ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-11) > > ____________________________________________ > I've tried the latest compat-wireless, but it gets an error after association is completed. > > Here's the messages with compat-wireless-2012-03-18; > Any tips appreciated. > Thanks > Troy > > > ************************************************************************* > > cfg80211: Calling CRDA to update world regulatory domain > add wake up source irq 108 > wl12xx: loaded > wl12xx: firmware booted (Rev 6.3.5.0.98) > wlan0: authenticate with 00:12:17:31:67:e7 > wlan0: send auth to 00:12:17:31:67:e7 (try 1/3) > wlan0: authenticated > wlan0: associate with 00:12:17:31:67:e7 (try 1/3) > wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) > wlan0: associated > wl12xx: ERROR command complete timeout > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) > [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0abb3c>] (wl1271_cmd_configure+0x38/0x60 [wl12xx]) > [<7f0abb3c>] (wl1271_cmd_configure+0x38/0x60 [wl12xx]) from [<7f0b0afc>] (wl1271_acx_set_ht_capabilities+0x80/0xd4 [wl12xx]) > [<7f0b0afc>] (wl1271_acx_set_ht_capabilities+0x80/0xd4 [wl12xx]) from [<7f0a64c8>] (wl1271_op_bss_info_changed+0x7c8/0x10ec [wl12xx]) > [<7f0a64c8>] (wl1271_op_bss_info_changed+0x7c8/0x10ec [wl12xx]) from [<7f057b10>] (ieee80211_bss_info_change_notify+0xd4/0x1ac [mac80211]) > [<7f057b10>] (ieee80211_bss_info_change_notify+0xd4/0x1ac [mac80211]) from [<7f07c9d4>] (ieee80211_assoc_success+0x360/0x5cc [mac80211]) > [<7f07c9d4>] (ieee80211_assoc_success+0x360/0x5cc [mac80211]) from [<7f07cd94>] (ieee80211_rx_mgmt_assoc_resp+0x154/0x26c [mac80211]) > [<7f07cd94>] (ieee80211_rx_mgmt_assoc_resp+0x154/0x26c [mac80211]) from [<7f07d698>] (ieee80211_sta_rx_queued_mgmt+0xc0/0x518 [mac80211]) > [<7f07d698>] (ieee80211_sta_rx_queued_mgmt+0xc0/0x518 [mac80211]) from [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) > [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f291393445e ]--- > wl12xx: WARNING CONFIGURE command NOK > wl12xx: WARNING acx ht capabilities setting failed: -110 > wl12xx: WARNING Set ht cap false failed -110 > wl12xx: ERROR watchdog interrupt received! starting recovery. > wl12xx: ERROR command complete timeout > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) > [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0ab1cc>] (wl12xx_cmd_set_default_wep_key+0x80/0xb0 [wl12xx]) > [<7f0ab1cc>] (wl12xx_cmd_set_default_wep_key+0x80/0xb0 [wl12xx]) from [<7f0a5180>] (wl1271_set_key+0x2ec/0x3e4 [wl12xx]) > [<7f0a5180>] (wl1271_set_key+0x2ec/0x3e4 [wl12xx]) from [<7f0a53c0>] (wl1271_op_set_key+0x148/0x2d0 [wl12xx]) > [<7f0a53c0>] (wl1271_op_set_key+0x148/0x2d0 [wl12xx]) from [<7f074de4>] (ieee80211_key_enable_hw_accel+0xd4/0x1b4 [mac80211]) > [<7f074de4>] (ieee80211_key_enable_hw_accel+0xd4/0x1b4 [mac80211]) from [<7f075350>] (ieee80211_key_link+0xa4/0x13c [mac80211]) > [<7f075350>] (ieee80211_key_link+0xa4/0x13c [mac80211]) from [<7f06c654>] (ieee80211_add_key+0xc0/0x140 [mac80211]) > [<7f06c654>] (ieee80211_add_key+0xc0/0x140 [mac80211]) from [<7f025198>] (cfg80211_upload_connect_keys+0xb0/0x654 [cfg80211]) > [<7f025198>] (cfg80211_upload_connect_keys+0xb0/0x654 [cfg80211]) from [<7f03ce98>] (__cfg80211_connect_result+0x1e8/0x330 [cfg80211]) > [<7f03ce98>] (__cfg80211_connect_result+0x1e8/0x330 [cfg80211]) from [<7f03abb0>] (cfg80211_send_rx_assoc+0x104/0x12c [cfg80211]) > [<7f03abb0>] (cfg80211_send_rx_assoc+0x104/0x12c [cfg80211]) from [<7f07d77c>] (ieee80211_sta_rx_queued_mgmt+0x1a4/0x518 [mac80211]) > [<7f07d77c>] (ieee80211_sta_rx_queued_mgmt+0x1a4/0x518 [mac80211]) from [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) > [<7f065824>] (ieee80211_iface_work+0x1c4/0x2cc [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f291393445f ]--- > wl12xx: WARNING cmd set_default_wep_key failed: -110 > wl12xx: ERROR Could not add or replace key > ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-110) > wl12xx: Reading FW panic log > wl12xx: ERROR command complete timeout > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) > [<7f0aa1fc>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f0aa8ec>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) > [<7f0aa8ec>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) from [<7f0a8dac>] (wl1271_recovery_work+0x228/0x328 [wl12xx]) > [<7f0a8dac>] (wl1271_recovery_work+0x228/0x328 [wl12xx]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f2913934460 ]--- > wl12xx: ERROR failed to send stop firmware logger command > wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.5.0.98 pc: 0x9a16 > wl12xx: down > ieee80211 phy0: Hardware restart was requested > wl12xx: ERROR timeout waiting for the hardware to complete initialization > wl12xx: ERROR timeout waiting for the hardware to complete initialization > wl12xx: ERROR timeout waiting for the hardware to complete initialization > wl12xx: ERROR firmware boot failed despite 3 retries > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) > [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) > [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f2913934461 ]--- > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) > [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) > [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f2913934462 ]--- > ------------[ cut here ]------------ > WARNING: at /home/tkisky/compat-wireless-2012-03-18/net/mac80211/util.c:1254 ieee80211_reconfig+0x39c/0x6bc [mac80211]() > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio compat ov5642_camera > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) > [<7f077f00>] (ieee80211_reconfig+0x39c/0x6bc [mac80211]) from [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) > [<7f05834c>] (ieee80211_restart_work+0x68/0x84 [mac80211]) from [<80079b90>] (process_one_work+0x10c/0x408) > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > ---[ end trace 211b9f2913934463 ]--- > ieee80211 phy0: failed to set key (0, ff:ff:ff:ff:ff:ff) to hardware (-11) > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-03-27 14:25 ` Gary Thomas @ 2012-04-02 8:39 ` Luciano Coelho 2012-04-04 1:26 ` Troy Kisky 0 siblings, 1 reply; 8+ messages in thread From: Luciano Coelho @ 2012-04-02 8:39 UTC (permalink / raw) To: Gary Thomas; +Cc: Troy Kisky, linux-wireless Hi, On Tue, 2012-03-27 at 08:25 -0600, Gary Thomas wrote: > On 2012-03-21 19:26, Troy Kisky wrote: > > Hi all > > > > We have a new board using the wl1271. As long as I keep it busy, > > everything is fine. But once it becomes idle I get, > > "wl12xx: ERROR watchdog interrupt received! starting recovery." > > > > Has this been seen by others? > > I'm getting very similar problems and my messages to this list (and the > wl12xx maintainer) are now waiting for nearly two weeks for an answer. > > Can someone help with these wl12xx issues? Sorry for the delay, I've been busy traveling and on vacations in the past weeks. > > I'm using compat-wireless-2012-01-26 and my kernel is based on 3.0 > > > > Other relevant log messages: > > cfg80211: Calling CRDA to update world regulatory domain > > add wake up source irq 108 > > wl12xx: loaded > > wl12xx: firmware booted (Rev 6.3.0.0.77) > > wlan0: authenticate with 00:12:17:31:67:e7 (try 1) > > wlan0: authenticated > > wlan0: associate with 00:12:17:31:67:e7 (try 1) > > wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) > > wlan0: associated > > wlan0: moving STA 00:12:17:31:67:e7 to state 1 > > wlan0: moving STA 00:12:17:31:67:e7 to state 2 > > wlan0: moving STA 00:12:17:31:67:e7 to state 3 > > wl12xx: Association completed. > > > > ....... > > wl12xx: ERROR watchdog interrupt received! starting recovery. > > wl12xx: Reading FW panic log > > wl12xx: ERROR command complete timeout This is a firmware bug. Can you please take the contents of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to us so we can take a look at what's going on? > > ------------[ cut here ]------------ > > WARNING: at /home/tkisky/compat-wireless-2012-01-26/drivers/net/wireless/wl12xx/cmd.c:108 wl1271_cmd_send+0x378/0x3d0 [wl12xx]() > > Modules linked in: wl12xx mac80211 cfg80211 wl12xx_sdio ov5642_camera > > [<800416f8>] (unwind_backtrace+0x0/0xfc) from [<80064074>] (warn_slowpath_common+0x54/0x64) > > [<80064074>] (warn_slowpath_common+0x54/0x64) from [<800640a0>] (warn_slowpath_null+0x1c/0x24) > > [<800640a0>] (warn_slowpath_null+0x1c/0x24) from [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) > > [<7f09e080>] (wl1271_cmd_send+0x378/0x3d0 [wl12xx]) from [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) > > [<7f09e720>] (wl12xx_cmd_stop_fwlog+0x54/0x80 [wl12xx]) from [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) > > [<7f09ce18>] (wl1271_recovery_work+0x220/0x314 [wl12xx]) from [<80079b90>] (process_one_work+0x10c/0x408) > > [<80079b90>] (process_one_work+0x10c/0x408) from [<8007a228>] (worker_thread+0x19c/0x470) > > [<8007a228>] (worker_thread+0x19c/0x470) from [<8008071c>] (kthread+0x8c/0x90) > > [<8008071c>] (kthread+0x8c/0x90) from [<8003c474>] (kernel_thread_exit+0x0/0x8) > > ---[ end trace b6d18e2d5294f64d ]--- > > wl12xx: ERROR failed to send stop firmware logger command > > wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 This tells us where the PC was when the crash happened. I'll ask our firmware team to analyze this. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-04-02 8:39 ` Luciano Coelho @ 2012-04-04 1:26 ` Troy Kisky 2012-04-04 2:58 ` Luciano Coelho 0 siblings, 1 reply; 8+ messages in thread From: Troy Kisky @ 2012-04-04 1:26 UTC (permalink / raw) To: Luciano Coelho; +Cc: Gary Thomas, linux-wireless On 4/2/2012 1:39 AM, Luciano Coelho wrote: > Hi, > > On Tue, 2012-03-27 at 08:25 -0600, Gary Thomas wrote: >> On 2012-03-21 19:26, Troy Kisky wrote: >>> Hi all >>> >>> We have a new board using the wl1271. As long as I keep it busy, >>> everything is fine. But once it becomes idle I get, >>> "wl12xx: ERROR watchdog interrupt received! starting recovery." >>> >>> Has this been seen by others? >> I'm getting very similar problems and my messages to this list (and the >> wl12xx maintainer) are now waiting for nearly two weeks for an answer. >> >> Can someone help with these wl12xx issues? > Sorry for the delay, I've been busy traveling and on vacations in the > past weeks. > > >>> I'm using compat-wireless-2012-01-26 and my kernel is based on 3.0 >>> >>> Other relevant log messages: >>> cfg80211: Calling CRDA to update world regulatory domain >>> add wake up source irq 108 >>> wl12xx: loaded >>> wl12xx: firmware booted (Rev 6.3.0.0.77) >>> wlan0: authenticate with 00:12:17:31:67:e7 (try 1) >>> wlan0: authenticated >>> wlan0: associate with 00:12:17:31:67:e7 (try 1) >>> wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3) >>> wlan0: associated >>> wlan0: moving STA 00:12:17:31:67:e7 to state 1 >>> wlan0: moving STA 00:12:17:31:67:e7 to state 2 >>> wlan0: moving STA 00:12:17:31:67:e7 to state 3 >>> wl12xx: Association completed. >>> >>> ....... >>> wl12xx: ERROR watchdog interrupt received! starting recovery. >>> wl12xx: Reading FW panic log >>> wl12xx: ERROR command complete timeout > This is a firmware bug. Can you please take the contents > of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to > us so we can take a look at what's going on? Sorry, it isn't a firmware bug. It was a configuration problem on my part. The defconfig file I was using was enabling a TVOUT driver which this board doesn't have. When the driver wanted to blank the screen, it was turning off my slow clock to my WL1271. When the WL1271 later becomes idle, it goes into a low power state which depends upon slow clock. So please tell your firmware guys, "never mind." >> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 > This tells us where the PC was when the crash happened. I'll ask our > firmware team to analyze this. "Never mind...." Thanks Troy ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-04-04 1:26 ` Troy Kisky @ 2012-04-04 2:58 ` Luciano Coelho 2012-04-04 11:20 ` Gary Thomas 0 siblings, 1 reply; 8+ messages in thread From: Luciano Coelho @ 2012-04-04 2:58 UTC (permalink / raw) To: Troy Kisky, Gary Thomas; +Cc: linux-wireless On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote: > On 4/2/2012 1:39 AM, Luciano Coelho wrote: > >>> wl12xx: ERROR watchdog interrupt received! starting recovery. > >>> wl12xx: Reading FW panic log > >>> wl12xx: ERROR command complete timeout > > This is a firmware bug. Can you please take the contents > > of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to > > us so we can take a look at what's going on? > Sorry, it isn't a firmware bug. It was a configuration problem on my > part. The defconfig > file I was using was enabling a TVOUT driver which this board doesn't > have. When > the driver wanted to blank the screen, it was turning off my slow clock > to my WL1271. > > When the WL1271 later becomes idle, it goes into a low power state which > depends upon > slow clock. So please tell your firmware guys, "never mind." Okay, cool that you found the reason for the problem. :) I thought it was a firmware problem because all the symptoms show that the chip stopped responding. :) > >> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 > > This tells us where the PC was when the crash happened. I'll ask our > > firmware team to analyze this. > "Never mind...." Cool! Now, Gary, do you still have the same (or a similar) problem with your setup? -- Cheers, Luca. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-04-04 2:58 ` Luciano Coelho @ 2012-04-04 11:20 ` Gary Thomas 2012-04-10 6:24 ` Luciano Coelho 0 siblings, 1 reply; 8+ messages in thread From: Gary Thomas @ 2012-04-04 11:20 UTC (permalink / raw) To: Luciano Coelho; +Cc: linux-wireless On 2012-04-03 20:58, Luciano Coelho wrote: > On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote: >> On 4/2/2012 1:39 AM, Luciano Coelho wrote: >>>>> wl12xx: ERROR watchdog interrupt received! starting recovery. >>>>> wl12xx: Reading FW panic log >>>>> wl12xx: ERROR command complete timeout >>> This is a firmware bug. Can you please take the contents >>> of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to >>> us so we can take a look at what's going on? >> Sorry, it isn't a firmware bug. It was a configuration problem on my >> part. The defconfig >> file I was using was enabling a TVOUT driver which this board doesn't >> have. When >> the driver wanted to blank the screen, it was turning off my slow clock >> to my WL1271. >> >> When the WL1271 later becomes idle, it goes into a low power state which >> depends upon >> slow clock. So please tell your firmware guys, "never mind." > > Okay, cool that you found the reason for the problem. :) I thought it > was a firmware problem because all the symptoms show that the chip > stopped responding. :) > > >>>> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 >>> This tells us where the PC was when the crash happened. I'll ask our >>> firmware team to analyze this. >> "Never mind...." > > Cool! > > Now, Gary, do you still have the same (or a similar) problem with your > setup? > Yes, I still have issues. One problem is that the wlan interface will not come up unless I manually perform a scan. If I just do this to bring it up (my AP uses WPA2) # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 # ifconfig wlan0 up ADDRCONF(NETDEV_UP): wlan0: link is not ready # ifup wlan0 udhcpc (v1.19.3) started Sending discover... Read error: Network is down, reopening socket wl1271: ERROR timeout waiting for the hardware to complete initialization Sending discover... udhcpc: sendto: Network is down Read error: Network is down, reopening socket Sending discover... udhcpc: sendto: Network is down Read error: Network is down, reopening socket No lease, failing root@cobra8148p81:~# wl1271: ERROR sdio read failed (-110) wl1271: ERROR sdio write failed (-110) wl1271: ERROR sdio read failed (-110) wl1271: ERROR chip id doesn't match after firmware boot wl1271: ERROR firmware boot failed despite 3 retries However, if I bring it up with this sequence, it works: # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 # ifconfig wlan0 up ADDRCONF(NETDEV_UP): wlan0: link is not ready # iw wlan0 scan ... many AP shown # ifup wlan0 udhcpc (v1.19.3) started Sending discover... ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Sending discover... Sending select for 192.168.12.184... Lease of 192.168.12.184 obtained, lease time 600 adding dns 192.168.12.1 # dmesg | tail -n 50 PM: Adding info for No Bus:8:0 PM: Adding info for No Bus:sda sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 PM: Adding info for No Bus:sda1 sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Attached SCSI removable disk PM: Adding info for platform:regulatory.0 cfg80211: Calling CRDA to update world regulatory domain PM: Adding info for platform:wl1271 PM: Adding info for No Bus:phy0 PM: Adding info for No Bus:wlan0 wl1271: loaded wl1271: initialized NET: Registered protocol family 10 CPSW phy found : id is : 0x1410e11 PHY 0:01 not found ADDRCONF(NETDEV_UP): eth0: link is not ready PHY: 0:00 - Link is Up - 100/Full ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: no IPv6 routers present PM: Adding info for No Bus:mmc1:0001:2 PM: Removing info for No Bus:mmc1:0001:2 PM: Adding info for No Bus:mmc1:0001:2 PM: Removing info for No Bus:mmc1:0001:2 wl1271: firmware booted (Rev 6.1.0.50.350) ieee80211 phy0: device now idle ADDRCONF(NETDEV_UP): wlan0: link is not ready ieee80211 phy0: device no longer idle - scanning ieee80211 phy0: device now idle ieee80211 phy0: device no longer idle - scanning ieee80211 phy0: device now idle ieee80211 phy0: device no longer idle - working wlan0: authenticate with 00:24:b2:49:ef:12 (try 1) wlan0: authenticated ieee80211 phy0: device now idle ieee80211 phy0: device no longer idle - working wlan0: associate with 00:24:b2:49:ef:12 (try 1) wlan0: RX AssocResp from 00:24:b2:49:ef:12 (capab=0x411 status=0 aid=4) wlan0: associated ieee80211 phy0: Allocated STA 00:24:b2:49:ef:12 ieee80211 phy0: Inserted STA 00:24:b2:49:ef:12 ieee80211 phy0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0 uapsd=1 ieee80211 phy0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0 uapsd=1 ieee80211 phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 uapsd=1 ieee80211 phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=1 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wl1271: Association completed. wlan0: no IPv6 routers present This connection will now work fine - here's a ping via the WiFi to a foreign network (actually across the Atlantic via VPN): # ifconfig eth0 down # ping 192.168.1.101 PING 192.168.1.101 (192.168.1.101): 56 data bytes 64 bytes from 192.168.1.101: seq=0 ttl=63 time=267.885 ms 64 bytes from 192.168.1.101: seq=1 ttl=63 time=291.215 ms 64 bytes from 192.168.1.101: seq=2 ttl=63 time=213.565 ms ^C --- 192.168.1.101 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 213.565/257.555/291.215 ms # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.12.0 * 255.255.255.0 U 0 0 0 wlan0 default ns.local.org 0.0.0.0 UG 0 0 0 wlan0 However, if I ever shut down the wlan0, it hangs up and the only way to get it back is to reboot. # ifdown wlan0 cfg80211: Calling CRDA to update world regulatory domain # ifup wlan0 wl1271: ERROR timeout waiting for the hardware to complete initialization wl1271: ERROR timeout waiting for the hardware to complete initialization wl1271: ERROR sdio read failed (-110) ^C # dmesg | tail -n2wl1271: ERROR sdio read failed (-110) wl1271: ERROR chip id doesn't match after firmware boot wl1271: ERROR firmware boot failed despite 3 retries 0 ieee80211 phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 uapsd=1 ieee80211 phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=1 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wl1271: Association completed. wlan0: no IPv6 routers present wlan0: deauthenticating from 00:24:b2:49:ef:12 by local choice (reason=3) ieee80211 phy0: Removed STA 00:24:b2:49:ef:12 ieee80211 phy0: Destroyed STA 00:24:b2:49:ef:12 ieee80211 phy0: device now idle cfg80211: All devices are disconnected, going to restore regulatory settings cfg80211: Restoring regulatory settings cfg80211: Calling CRDA to update world regulatory domain wl1271: down wl1271: ERROR timeout waiting for the hardware to complete initialization wl1271: ERROR timeout waiting for the hardware to complete initialization wl1271: ERROR sdio read failed (-110) wl1271: ERROR sdio write failed (-110) wl1271: ERROR sdio read failed (-110) wl1271: ERROR chip id doesn't match after firmware boot wl1271: ERROR firmware boot failed despite 3 retries I'm using the 2012-02-28 snapshot of compat-wireless, my kernel is 2.6.37 Ideas? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-04-04 11:20 ` Gary Thomas @ 2012-04-10 6:24 ` Luciano Coelho 2012-04-10 12:05 ` Gary Thomas 0 siblings, 1 reply; 8+ messages in thread From: Luciano Coelho @ 2012-04-10 6:24 UTC (permalink / raw) To: Gary Thomas; +Cc: linux-wireless On Wed, 2012-04-04 at 05:20 -0600, Gary Thomas wrote: > On 2012-04-03 20:58, Luciano Coelho wrote: > > On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote: > >> On 4/2/2012 1:39 AM, Luciano Coelho wrote: [...] > > Cool! > > > > Now, Gary, do you still have the same (or a similar) problem with your > > setup? > > > > Yes, I still have issues. One problem is that the wlan interface will > not come up unless I manually perform a scan. If I just do this to > bring it up (my AP uses WPA2) This is pretty weird. Something to do with the interrupts, apparently. > # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 > # ifconfig wlan0 up > ADDRCONF(NETDEV_UP): wlan0: link is not ready > # ifup wlan0 > udhcpc (v1.19.3) started > Sending discover... > Read error: Network is down, reopening socket > wl1271: ERROR timeout waiting for the hardware to complete initialization > Sending discover... > udhcpc: sendto: Network is down > Read error: Network is down, reopening socket > Sending discover... > udhcpc: sendto: Network is down > Read error: Network is down, reopening socket > No lease, failing > root@cobra8148p81:~# wl1271: ERROR sdio read failed (-110) > wl1271: ERROR sdio write failed (-110) > wl1271: ERROR sdio read failed (-110) > wl1271: ERROR chip id doesn't match after firmware boot > wl1271: ERROR firmware boot failed despite 3 retries Hard to tell what's happening here. What do you have in your /etc/network/interfaces file? > However, if I bring it up with this sequence, it works: > > # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 > # ifconfig wlan0 up > ADDRCONF(NETDEV_UP): wlan0: link is not ready > # iw wlan0 scan > ... many AP shown > # ifup wlan0 > udhcpc (v1.19.3) started > Sending discover... > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > Sending discover... > Sending select for 192.168.12.184... > Lease of 192.168.12.184 obtained, lease time 600 > adding dns 192.168.12.1 Pretty weird. Somehow triggering the scan is making things go more smoothly. When booting the chip, we don't really wait for an interrupt, but poll the chip for completion. [...] > However, if I ever shut down the wlan0, it hangs up and the only > way to get it back is to reboot. > > # ifdown wlan0 > cfg80211: Calling CRDA to update world regulatory domain > # ifup wlan0 > wl1271: ERROR timeout waiting for the hardware to complete initialization > wl1271: ERROR timeout waiting for the hardware to complete initialization > wl1271: ERROR sdio read failed (-110) This looks like your MMC setup is not able to power on and off correctly. Are you sure you have all the settings necessary in your board file? Especially the clock frequencies and the caps flag in the hsmmc_info configuration? Make sure you have MMC_CAP_POWER_OFF_CARD in the .caps field of your mmc info struct. > # dmesg | tail -n2wl1271: ERROR sdio read failed (-110) > wl1271: ERROR chip id doesn't match after firmware boot > wl1271: ERROR firmware boot failed despite 3 retries > 0 > ieee80211 phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 uapsd=1 > ieee80211 phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=1 > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > wl1271: Association completed. > wlan0: no IPv6 routers present > wlan0: deauthenticating from 00:24:b2:49:ef:12 by local choice (reason=3) > ieee80211 phy0: Removed STA 00:24:b2:49:ef:12 > ieee80211 phy0: Destroyed STA 00:24:b2:49:ef:12 > ieee80211 phy0: device now idle > cfg80211: All devices are disconnected, going to restore regulatory settings > cfg80211: Restoring regulatory settings > cfg80211: Calling CRDA to update world regulatory domain > wl1271: down > wl1271: ERROR timeout waiting for the hardware to complete initialization > wl1271: ERROR timeout waiting for the hardware to complete initialization > wl1271: ERROR sdio read failed (-110) > wl1271: ERROR sdio write failed (-110) > wl1271: ERROR sdio read failed (-110) > wl1271: ERROR chip id doesn't match after firmware boot > wl1271: ERROR firmware boot failed despite 3 retries > > I'm using the 2012-02-28 snapshot of compat-wireless, my kernel is 2.6.37 > > Ideas? I'm running out of ideas. And 2.6.37 is quite ancient, but AFAIK it should work as it is the first version that supports powering the MMC card on and off. Any chance you could try a newer kernel? Just to find out it everything is working fine with newer kernels. If it works, then we should focus on why 2.6.37 doesn't work. Maybe we will have to cherry-pick some patches for the MMC subsystem. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: wl1271 watchdog interrupt 2012-04-10 6:24 ` Luciano Coelho @ 2012-04-10 12:05 ` Gary Thomas 0 siblings, 0 replies; 8+ messages in thread From: Gary Thomas @ 2012-04-10 12:05 UTC (permalink / raw) To: Luciano Coelho; +Cc: linux-wireless On 2012-04-10 00:24, Luciano Coelho wrote: > On Wed, 2012-04-04 at 05:20 -0600, Gary Thomas wrote: >> On 2012-04-03 20:58, Luciano Coelho wrote: >>> On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote: >>>> On 4/2/2012 1:39 AM, Luciano Coelho wrote: > > [...] > >>> Cool! >>> >>> Now, Gary, do you still have the same (or a similar) problem with your >>> setup? >>> >> >> Yes, I still have issues. One problem is that the wlan interface will >> not come up unless I manually perform a scan. If I just do this to >> bring it up (my AP uses WPA2) > > This is pretty weird. Something to do with the interrupts, apparently. > > >> # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 >> # ifconfig wlan0 up >> ADDRCONF(NETDEV_UP): wlan0: link is not ready >> # ifup wlan0 >> udhcpc (v1.19.3) started >> Sending discover... >> Read error: Network is down, reopening socket >> wl1271: ERROR timeout waiting for the hardware to complete initialization >> Sending discover... >> udhcpc: sendto: Network is down >> Read error: Network is down, reopening socket >> Sending discover... >> udhcpc: sendto: Network is down >> Read error: Network is down, reopening socket >> No lease, failing >> root@cobra8148p81:~# wl1271: ERROR sdio read failed (-110) >> wl1271: ERROR sdio write failed (-110) >> wl1271: ERROR sdio read failed (-110) >> wl1271: ERROR chip id doesn't match after firmware boot >> wl1271: ERROR firmware boot failed despite 3 retries > > Hard to tell what's happening here. What do you have in > your /etc/network/interfaces file? Here are the relevant parts. =================== /etc/network/interfaces (partial) ====================== # Wireless interfaces iface wlan0 inet dhcp wireless_mode managed wireless_essid any wpa-driver wext wpa-conf /etc/wpa_supplicant.conf ============================================================================ ================== /etc/wpa_supplicant.conf (partial) ====================== network={ ssid="LeManegeEnchante" scan_ssid=1 key_mgmt=WPA-PSK psk="SOMEPASSWORD" } ============================================================================ > >> However, if I bring it up with this sequence, it works: >> >> # ifconfig wlan0 hw ether D4:94:A1:8E:1E:17 >> # ifconfig wlan0 up >> ADDRCONF(NETDEV_UP): wlan0: link is not ready >> # iw wlan0 scan >> ... many AP shown >> # ifup wlan0 >> udhcpc (v1.19.3) started >> Sending discover... >> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> Sending discover... >> Sending select for 192.168.12.184... >> Lease of 192.168.12.184 obtained, lease time 600 >> adding dns 192.168.12.1 > > Pretty weird. Somehow triggering the scan is making things go more > smoothly. When booting the chip, we don't really wait for an interrupt, > but poll the chip for completion. Perhaps there's a stray interrupt laying around which the scan path handles better than the other way. I'll look into this. > [...] > >> However, if I ever shut down the wlan0, it hangs up and the only >> way to get it back is to reboot. >> >> # ifdown wlan0 >> cfg80211: Calling CRDA to update world regulatory domain >> # ifup wlan0 >> wl1271: ERROR timeout waiting for the hardware to complete initialization >> wl1271: ERROR timeout waiting for the hardware to complete initialization >> wl1271: ERROR sdio read failed (-110) > > This looks like your MMC setup is not able to power on and off > correctly. Are you sure you have all the settings necessary in your > board file? Especially the clock frequencies and the caps flag in the > hsmmc_info configuration? > > Make sure you have MMC_CAP_POWER_OFF_CARD in the .caps field of your mmc > info struct. Is this absolutely necessary? My device can't be powered off (it's soldered on and the power supply is fixed, not regulated). I do have control over the RESET pin. If power control is essential for this device we'll have to fix the design. > >> # dmesg | tail -n2wl1271: ERROR sdio read failed (-110) >> wl1271: ERROR chip id doesn't match after firmware boot >> wl1271: ERROR firmware boot failed despite 3 retries >> 0 >> ieee80211 phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 uapsd=1 >> ieee80211 phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=1 >> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> wl1271: Association completed. >> wlan0: no IPv6 routers present >> wlan0: deauthenticating from 00:24:b2:49:ef:12 by local choice (reason=3) >> ieee80211 phy0: Removed STA 00:24:b2:49:ef:12 >> ieee80211 phy0: Destroyed STA 00:24:b2:49:ef:12 >> ieee80211 phy0: device now idle >> cfg80211: All devices are disconnected, going to restore regulatory settings >> cfg80211: Restoring regulatory settings >> cfg80211: Calling CRDA to update world regulatory domain >> wl1271: down >> wl1271: ERROR timeout waiting for the hardware to complete initialization >> wl1271: ERROR timeout waiting for the hardware to complete initialization >> wl1271: ERROR sdio read failed (-110) >> wl1271: ERROR sdio write failed (-110) >> wl1271: ERROR sdio read failed (-110) >> wl1271: ERROR chip id doesn't match after firmware boot >> wl1271: ERROR firmware boot failed despite 3 retries >> >> I'm using the 2012-02-28 snapshot of compat-wireless, my kernel is 2.6.37 >> >> Ideas? > > I'm running out of ideas. And 2.6.37 is quite ancient, but AFAIK it > should work as it is the first version that supports powering the MMC > card on and off. Any chance you could try a newer kernel? Just to find > out it everything is working fine with newer kernels. If it works, then > we should focus on why 2.6.37 doesn't work. Maybe we will have to > cherry-pick some patches for the MMC subsystem. > Sadly, I'm stuck with this one. The processor is DM8148/AM3874 which TI only has 2.6.37 Thanks for your time -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-04-10 12:05 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-03-22 1:26 wl1271 watchdog interrupt Troy Kisky 2012-03-27 14:25 ` Gary Thomas 2012-04-02 8:39 ` Luciano Coelho 2012-04-04 1:26 ` Troy Kisky 2012-04-04 2:58 ` Luciano Coelho 2012-04-04 11:20 ` Gary Thomas 2012-04-10 6:24 ` Luciano Coelho 2012-04-10 12:05 ` Gary Thomas
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).