From: Kalle Valo <kvalo@codeaurora.org>
To: Adam Porter <porter.adam@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 SDIO crashing after few days
Date: Fri, 26 Jan 2018 11:35:59 +0200 [thread overview]
Message-ID: <87lgglufls.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAFR5RwTCNV-135E16fXJLECsart-cTjVJq8QcDB3wKH+JrsHnw@mail.gmail.com> (Adam Porter's message of "Thu, 25 Jan 2018 11:11:37 -0800")
Adam Porter <porter.adam@gmail.com> writes:
> Firmware WLAN.RMH.4.1.1-00014-QCARMSWPZ-1
>
> Using branch ath10k-pending-sdio-usb
What commit id? BTW, I'm planning to add a tag everytime I rebase that
branch so that it's easier to find older commits and identify what
version is used.
> I'm using this module as an access point. After a while of uptime, it
> appears that all communication with the module ceases. Hostapd goes to
> disassociate clients due to inactivity, then I see in the log the
> resulting failures:
>
> [94216.098042] ath10k_sdio mmc0:0001:1: failed to install key for vdev
> 0 peer c8:21:58:10:b3:b4: -110
> [94219.170075] ath10k_sdio mmc0:0001:1: failed to install key for vdev
> 0 peer b8:27:eb:f2:52:22: -110
> [94219.191719] ath10k_sdio mmc0:0001:1: cipher 0 is not supported
> [94219.207948] ath10k_sdio mmc0:0001:1: failed to remove peer wep key 0: -95
> [94219.222155] ath10k_sdio mmc0:0001:1: failed to clear all peer wep
> keys for vdev 0: -95
> [94219.237937] ath10k_sdio mmc0:0001:1: failed to disassociate
> station: c8:21:58:10:b3:b4 vdev 0: -95
>
> It seems that I can reproduce this issue faster by connecting more
> clients and pushing a lot of throughput. So perhaps this is a resource
> leak in the firmware?
I would blame ath10k first :) Can you estimate how much data needs to be
transferred before this happens?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-01-26 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 19:11 QCA6174 SDIO crashing after few days Adam Porter
2018-01-26 9:35 ` Kalle Valo [this message]
2018-01-26 19:11 ` Adam Porter
2018-02-08 20:52 ` Adam Porter
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=87lgglufls.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=porter.adam@gmail.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