Linux wireless drivers development
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wl1271: tx stuck in firmware
Date: Tue, 08 Apr 2014 23:29:09 +0300	[thread overview]
Message-ID: <1396988949.4418.46.camel@dubbel> (raw)
In-Reply-To: <CAGm1_ktNAyqWhkTPycA-yKz9iXgqGvx3unjB7JHQpmiKFnFXuA@mail.gmail.com>

On Tue, 2014-04-08 at 17:28 +0200, Yegor Yefremov wrote:
> I'm using kernel 3.14.0-rc4-12738-g674748b-dirty on a am335x-evmsk as
> also on a custom board. I get following issue on both systems, when
> working with various calibrator functions:

That's not a very nice kernel, right? How am I supposed to know what the
12738 patches you have on top of 3.14.0-rc4 are? Even worse because your
tree is dirty. :(


> # calibrator wlan0 plt power_mode on
> [  252.935208] wlcore: power up
> [  253.502531] wlcore: firmware booted in PLT mode PLT_ON (PLT 6.3.10.0.133)
> # [  399.656192] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery

This sounds really strange.  The TX watchdog should not be armed in PLT
mode.

> or following error, when I start NetworkManager and wait for 5 minutes or so:
> 
> [  717.608550] wlcore: Scan completed due to error.
> [  717.613422] ------------[ cut here ]------------
> [  717.618405] WARNING: CPU: 0 PID: 940 at
> drivers/net/wireless/ti/wlcore/main.c:789
> wl12xx_queue_recovery_work+0x60/0x6c()
> [  717.629832] Modules linked in:
> [  717.633055] CPU: 0 PID: 940 Comm: kworker/u2:2 Tainted: G        W
>   3.14.0-rc4-12737-gefb78a0-dirty #214
> [  717.643264] Workqueue: phy0 wl1271_scan_complete_work
> [  717.648649] [<c00151e0>] (unwind_backtrace) from [<c0011e38>]
> (show_stack+0x10/0x14)
> [  717.656762] [<c0011e38>] (show_stack) from [<c05a1944>]
> (dump_stack+0x7c/0x94)
> [  717.664372] [<c05a1944>] (dump_stack) from [<c00402bc>]
> (warn_slowpath_common+0x6c/0x90)
> [  717.672876] [<c00402bc>] (warn_slowpath_common) from [<c004037c>]
> (warn_slowpath_null+0x1c/0x24)
> [  717.682110] [<c004037c>] (warn_slowpath_null) from [<c035be0c>]
> (wl12xx_queue_recovery_work+0x60/0x6c)
> [  717.691889] [<c035be0c>] (wl12xx_queue_recovery_work) from
> [<c036d804>] (wl1271_scan_complete_work+0xf8/0x108)
> [  717.702391] [<c036d804>] (wl1271_scan_complete_work) from
> [<c0058ff4>] (process_one_work+0x1ac/0x4c4)
> [  717.712110] [<c0058ff4>] (process_one_work) from [<c0059e88>]
> (worker_thread+0x114/0x3b4)
> [  717.720707] [<c0059e88>] (worker_thread) from [<c005fa44>]
> (kthread+0xcc/0xe8)
> [  717.728306] [<c005fa44>] (kthread) from [<c000e388>]
> (ret_from_fork+0x14/0x2c)
> [  717.735856] ---[ end trace f4d374bb2ca37664 ]---
> [  717.743587] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133
> [  717.752600] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 6
> [  717.759609] wlcore: down
> [  717.764108] ieee80211 phy0: Hardware restart was requested
> [  718.250930] wlcore: firmware booted (Rev 6.3.10.0.133)
> 
> Any idea, what could be wrong?

First of all, try a clean kernel.

--
Luca.


  reply	other threads:[~2014-04-08 20:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 15:28 wl1271: tx stuck in firmware Yegor Yefremov
2014-04-08 20:29 ` Luca Coelho [this message]
2014-04-09  9:14   ` Yegor Yefremov
2014-04-09  9:21     ` Luca Coelho
2014-04-09 10:16       ` Yegor Yefremov
2014-04-09 11:49         ` Luca Coelho
2014-04-09 12:20           ` Arik Nemtsov
2014-04-09 12:41             ` Luca Coelho
2014-04-09 13:07               ` Arik Nemtsov
2014-04-09 13:20                 ` Yegor Yefremov
2014-04-09 13:25                   ` Arik Nemtsov
2014-04-09 15:28                     ` Yegor Yefremov
2014-04-10  7:21                       ` Yegor Yefremov
2014-04-10  7:43                         ` Arik Nemtsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1396988949.4418.46.camel@dubbel \
    --to=luca@coelho.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yegorslists@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox