From: Daniel Mack <zonque@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: s.neumann@raumfeld.com, afenkart@gmail.com, bzhao@marvell.com,
linville@tuxdriver.com, johannes.berg@intel.com,
Daniel Mack <zonque@gmail.com>
Subject: [PATCH] mwifiex: fix command timeout with SDIO interrupts enabled
Date: Mon, 16 Sep 2013 13:39:05 +0200 [thread overview]
Message-ID: <1379331546-30617-1-git-send-email-zonque@gmail.com> (raw)
We've been hunting a command timeout issue in the mwifiex driver which
occurs on an AM33xx platform when Andreas Fenkart's omap_hsmmc SDIO IRQ
patches are applied (they are not yet in the mainline kernel). We first
suspected the mmc host driver to be racy, but that wasn't the case.
I dug a little through the changes between 3.7 and 3.10 on the mwifiex
driver, and it turned out that the culprit is 601216e12 ("mwifiex:
process RX packets in SDIO IRQ thread directly"), especially the
situation where mwifiex_main_process() bails when mwifiex_processing is
set.
In other words: if an SDIO irq arrives while the driver is processing
mwifiex_main_process() from the work queue, we effectively loose the
interrupt, which then results in a command timeout.
I've written a little test case scenario that calls
mwifiex_dump_station_info() through the SIOCGIWSTATS ioctl excessively,
and that reproduces the problem after a couple of seconds already:
https://gist.github.com/zonque/6579314
The fix for this issue is quite simple and works very well.
Thanks,
Daniel
Daniel Mack (1):
mwifiex: queue main work from main process when bailing on races
drivers/net/wireless/mwifiex/main.c | 1 +
1 file changed, 1 insertion(+)
--
1.8.3.1
next reply other threads:[~2013-09-16 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 11:39 Daniel Mack [this message]
2013-09-16 11:39 ` [PATCH 1/1] mwifiex: queue main work from main process when bailing on races Daniel Mack
2013-09-16 21:14 ` Bing Zhao
2013-09-16 23:00 ` Daniel Mack
2013-09-17 18:19 ` Bing Zhao
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=1379331546-30617-1-git-send-email-zonque@gmail.com \
--to=zonque@gmail.com \
--cc=afenkart@gmail.com \
--cc=bzhao@marvell.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=s.neumann@raumfeld.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;
as well as URLs for NNTP newsgroup(s).