From: Oleksij Rempel <linux@rempel-privat.de>
To: 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:02:52 +0100 [thread overview]
Message-ID: <52E6AD5C.3020005@rempel-privat.de> (raw)
In-Reply-To: <trinity-c1a620e7-f7e8-4bb0-b583-b36b6fa6bfd8-1390546555391@3capp-1and1-bs03>
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
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.
Am 24.01.2014 07:55, schrieb mail@fuerstflorian.de:
> Hello Antonio,
>
>> Just as a generic suggestion, have you tried testing a slightly older
>> kernel versions to see if that makes any difference?
>
> Thanks for the suggestion. I will try to use a older kernel version, but it will take some days to be
> sure if it works again (and I naturally will report about).
>
> --
> Flo
>
>> On 23/01/14 23:03, Antonio Quartulli wrote:
>> Von: "Antonio Quartulli" <antonio@meshcoding.com>
>> An: "Oleksij Rempel" <linux@rempel-privat.de>, mail@fuerstflorian.de, ath9k-devel@lists.ath9k.org, "Antonio Quartulli" <ordex@autistici.org>
>> Betreff: Re: [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302
>>
>> Hi all,
>>
>> On 23/01/14 20:44, Oleksij Rempel wrote:
>>> Hi Antonio,
>>>
>>> You probably know more about this issue then me.
>>>
>>> Insight of this mutex are some WMI commands, which are incredible slow
>>> on some USB 2.0 devices.
>>>
>>
>> I implemented the ath9k_htc_sta_rc_update() API but I don't really know
>> the internals of the ath9k_htc driver...therefore I don't know if these
>> WMI commands have any consequence on this..Could it be that this
>> slowness is triggering some reaction in the kernel (due to the fact that
>> this part of the code is executed while holding a lock)?
>>
>> Sorry, but I can't really help.
>>
>> Just as a generic suggestion, have you tried testing a slightly older
>> kernel versions to see if that makes any difference?
>>
>>
>>
>> --
>> Antonio Quartulli
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next parent reply other threads:[~2014-01-27 19:03 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 ` Oleksij Rempel [this message]
2014-01-27 19:12 ` [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302 Antonio Quartulli
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=52E6AD5C.3020005@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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).