From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: OMAP2+: Use pdata quirks for wl12xx on the AM335x EV-MSK
Date: Tue, 18 Mar 2014 20:03:18 +0100 [thread overview]
Message-ID: <op.xcxlvsl42s3iss@ecaz> (raw)
In-Reply-To: <5326BB1B.8030900@visionsystems.de>
Hi Yegor,
On Mon, 17 Mar 2014 10:06:35 +0100, Yegor Yefremov <yegor.yefremov@visionsystems.de> wrote:
> I have some trouble with WLAN. If I make extensive scanning (just start NetworkManager and wait a minute or so) I get following errors over and over again:
>
> [ 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)
>
> Have you experienced such behavior?
With older firmwares, quite often. 6.3.10.0.133 sounds amazingly old, the latest is 8.8.0.0.13. What kernel are you on?
Imre
next prev parent reply other threads:[~2014-03-18 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 9:02 [PATCHv2] ARM: OMAP2+: Use pdata quirks for wl12xx on the AM335x EV-MSK Imre Kaloz
2014-03-04 18:47 ` Tony Lindgren
2014-03-17 9:06 ` Yegor Yefremov
2014-03-18 19:03 ` Imre Kaloz [this message]
2014-03-19 10:39 ` Yegor Yefremov
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=op.xcxlvsl42s3iss@ecaz \
--to=kaloz@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.