From: Kalle Valo <kvalo@codeaurora.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: ath10k@lists.infradead.org
Subject: Re: 9984 with 10.4.3.5.3-0057 crashes
Date: Wed, 25 Apr 2018 18:23:28 +0300 [thread overview]
Message-ID: <87a7tr8g3z.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <a58d42c2-84ca-1c17-8591-b20bfd91660c@dd-wrt.com> (Sebastian Gottschall's message of "Tue, 24 Apr 2018 08:08:07 +0200")
Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
> Am 24.04.2018 um 07:27 schrieb Kalle Valo:
>> Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
>>
>>> just for your notice. 10.4.3.5.3-0057 on 9984 which was just released
>>> crashes in vht160 operation mode immediatly after first station
>>> associates
>>> last known working stable fw so far is 10.4-3.4-00104. the whole
>>> 10.4.3.5.3 series seem to be seriously broken or the api has been
>>> changed in a way
>>> which is unsupported by ath10k (which i think is the cause of the
>>> problem)
>>> it would be good to know what has been changed.
>>
>> At least I was not informed any changes in the firmware interface. What
>> version of ath10k are you using? Do you have any custom patches on
>> ath10k?
>
> i'm using latest git version for testing here but there is one
> relevant patch required for more recent firmwares like 3.4 series (see
> below) i posted already a long time ago, that vht160 will not work
> anymore without that patch in newer firmwares since qca changed the api
> for channel mapping in vht160.
I don't remember what happened to that patch, but please resubmit it
with a proper commit log and S-o-b line.
I was told that the firmware crash is an assert triggered by host not
populating the parameter 'peer_bw_rxnss_override' in
WMI_PEER_ASSOC_CMDID which is needed for 160/80+80 operation.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-25 15:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 12:06 [PATCH v2 0/4] Support for STA idle mode power save(IMPS) pillair
2018-04-17 12:06 ` [PATCH v2 1/4] ath10k: Add hw params for shadow register support pillair
2018-04-24 6:05 ` [v2,1/4] " Kalle Valo
2018-04-17 12:06 ` [PATCH v2 2/4] ath10k: Add support for shadow register for WNC3990 pillair
2018-04-17 12:07 ` [PATCH v2 3/4] ath10k: Enable SRRI/DRRI support on ddr for WCN3990 pillair
2018-04-17 12:07 ` [PATCH v2 4/4] ath10k: Enable sta idle power save pillair
2018-04-18 7:06 ` Sebastian Gottschall
2018-04-18 13:07 ` govinds
2018-04-18 13:16 ` Kalle Valo
2018-04-18 14:44 ` Arend van Spriel
2018-04-19 4:32 ` govinds
2018-04-19 16:36 ` Kalle Valo
2018-04-19 17:00 ` Adrian Chadd
2018-04-20 7:21 ` Sebastian Gottschall
2018-04-20 8:16 ` Arend van Spriel
2018-04-20 12:43 ` govinds
2018-04-23 15:50 ` Kalle Valo
2018-04-23 16:17 ` 9984 with 10.4.3.5.3-0057 crashes Sebastian Gottschall
2018-04-24 5:27 ` Kalle Valo
2018-04-24 6:08 ` Sebastian Gottschall
2018-04-25 15:23 ` Kalle Valo [this message]
2018-04-26 6:23 ` Sebastian Gottschall
2018-04-26 7:36 ` Sebastian Gottschall
2018-04-23 16:41 ` [PATCH v2 4/4] ath10k: Enable sta idle power save Adrian Chadd
2018-04-24 5:35 ` Kalle Valo
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=87a7tr8g3z.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@dd-wrt.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