From: Antonio Quartulli <antonio@meshcoding.com>
To: Oleksij Rempel <linux@rempel-privat.de>,
mail@fuerstflorian.de, ath9k-devel@lists.ath9k.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302
Date: Mon, 27 Jan 2014 20:12:23 +0100 [thread overview]
Message-ID: <52E6AF97.4040602@meshcoding.com> (raw)
In-Reply-To: <52E6AD5C.3020005@rempel-privat.de>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On 27/01/14 20:02, Oleksij Rempel wrote:
> Hi Johannes,
>
> i found this bug report with your response:
> https://bugzilla.redhat.com/show_bug.cgi?id=990955
> "I don't think adding a workqueue is a good idea because that would
> significantly delay the calls in many situations."
>
> The problem on ath9k_htc is that the call is already dramatically
> delayed. It will try to send WMI command over USB with delay of some
> _msec_ not usec. There are two options right now, use workqueue or do
> not support sta_rc_update.
>
Unfortunately not supporting sta_rc_update() means making adhoc mode
unusable.. :(
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-27 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-b8018ef9-8037-4688-a363-2deb3aed68fc-1390501815918@3capp-1and1-bs02>
[not found] ` <52E1712B.70202@rempel-privat.de>
[not found] ` <52E191B3.2070601@meshcoding.com>
[not found] ` <trinity-14f555a0-3945-448b-a908-b12f1cb532e3-1390546291559@3capp-1and1-bs03>
[not found] ` <trinity-c1a620e7-f7e8-4bb0-b583-b36b6fa6bfd8-1390546555391@3capp-1and1-bs03>
2014-01-27 19:02 ` [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302 Oleksij Rempel
2014-01-27 19:12 ` Antonio Quartulli [this message]
2014-01-27 22:22 ` Johannes Berg
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=52E6AF97.4040602@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mail@fuerstflorian.de \
/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).