From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Ben Greear" <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k will not tx packets sometimes.
Date: Tue, 30 Jan 2018 21:09:06 +0100 [thread overview]
Message-ID: <0e4aa72c-83da-e879-052d-505d8658177d@dd-wrt.com> (raw)
In-Reply-To: <87wozzyy5e.fsf@toke.dk>
Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
> Ben Greear <greearb@candelatech.com> writes:
>
>>> I'm actually working on reworking that whole scheduler logic, and move
>>> some of it into mac80211. Could you test this (WiP) patch and see if
>>> that has the same problem?
>> It had some serious conflicts in ath10k, due to my local changes, so
>> I did not actually test this.
> Can send you a version without the ath10k changes tomorrow if you'd like
> to test - but will try to reproduce myself as well...
>
>> But, a revert of the atf patches (a6e56d749 and 63fefa050) appear to
>> have resolved the issue. I'll test more with these reverted, and maybe
>> will have time to work more on actually fixing upstream code next time
>> I move to a newer kernel (and/or after your pending changes get in).
> Ah, that narrows it down some. Well, that is the code I'm hacking on
> currently anyway, so let's see if we can't get it fixed as part of that
> series :)
i have some addition information for you maybe. in the same timeframe i
noticed a increased memory usage for ath9k devices.
maybe that helps. so i hit memory boundaries on embedded devices with
dual interfaces and just 32 mb ram now which wasnt the case before
is this patch worth to try from my side?
Sebastian
--
Mit freundlichen Grüssen / Regards
Sebastian Gottschall / CTO
NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565
next prev parent reply other threads:[~2018-01-30 20:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 22:53 ath9k will not tx packets sometimes Ben Greear
2018-01-27 13:11 ` Toke Høiland-Jørgensen
2018-01-29 21:34 ` Ben Greear
2018-01-29 21:47 ` Toke Høiland-Jørgensen
2018-01-29 21:54 ` Ben Greear
2018-01-29 22:35 ` Toke Høiland-Jørgensen
2018-01-29 23:00 ` Ben Greear
2018-01-30 12:07 ` Toke Høiland-Jørgensen
2018-01-30 17:32 ` Ben Greear
2018-01-30 18:55 ` Toke Høiland-Jørgensen
2018-01-30 20:09 ` Sebastian Gottschall [this message]
2018-01-31 11:50 ` Toke Høiland-Jørgensen
2018-01-31 13:37 ` Sebastian Gottschall
2018-01-31 13:46 ` Toke Høiland-Jørgensen
2018-01-31 14:52 ` Sebastian Gottschall
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=0e4aa72c-83da-e879-052d-505d8658177d@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
/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.