Hi!
ok, thanks! I've seen some .. annoying rate control related firmware
crashes if you aren't using 11ac / 11n rates (ie you're /really/
legacy, so I wondered if something similar is going on here.
Thanks!
-a
On 13 December 2016 at 22:06, Alexis Green wrote:
> Hi Adrian,
>
> I have not done
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Adrian,
I have not done much t
Hi!
Hm! So is there a firmware bug if there are 11n only capable nodes in
an 11s mesh?
-adrian
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Thank you for your help Rajkumar,
> Tested the 10.2.4.70.59-2 firmware and wpa_supplicant running WITHOUT
> encryption and it still crashes. I suspect this means wpa_supplicant is
> setting up
> the interface incorrectly and/or transmitting a malformed packet that is
> causing
> the driver to crash.
>
Ben,
IIRC mesh support was
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Tested the 10.2.4.70.59-2 firmware
Just tested the latest 10.2.4.70.59-2 firmware and it still crashes with
wpa_supplicant encrypted mesh =(
[ 85.201440] ath10k_pci :01:00.0: firmware crashed! (uuid
b7f44483-0488-46af-8dff-db88f4b56327)
[ 85.210573] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c
chip_id 0x0432
1. Yes, this appears to happens every time a unicast packet with
wpa_supplicant encryption in VHT80 mode is received. I haven't seen a
successful ping-pong pair.
2. We tried with 10.2.4.70.42-2 firmware and still saw crashes.
3. We ran our experiment again with extra debugging turned on.
Nod
>> Applied the patch and tried with 10.2.4.70.54 firmware and it still crashes:
>> [ 142.438377] ath10k_pci :01:00.0: firmware crashed! (uuid
>> a5499582-e220-46d2-9359-0b44219f69ea)
>> [ 142.447512] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c
>> chip_id 0x043202ff sub :00
Applied the patch and tried with 10.2.4.70.54 firmware and it still crashes:
[ 142.438377] ath10k_pci :01:00.0: firmware crashed! (uuid
a5499582-e220-46d2-9359-0b44219f69ea)
[ 142.447512] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c
chip_id 0x043202ff sub :
[ 142.4568
https://patchwork.kernel.org/patch/9437519/
(sorry missed this in the previous thread)
On Sat, Dec 03, 2016 at 06:13:58PM +0530, Mohammed Shafi Shajakhan wrote:
> Hi Benjamin,
>
> On Fri, Dec 02, 2016 at 05:28:02PM -0800, Benjamin Morgan wrote:
> > Just tried 10.2.4.70.58 firmware that you linked
Hi Benjamin,
On Fri, Dec 02, 2016 at 05:28:02PM -0800, Benjamin Morgan wrote:
> Just tried 10.2.4.70.58 firmware that you linked to and it still crashes:
>
> [ 131.568989] ath10k_pci :01:00.0: firmware crashed! (uuid
> 1838347e-9380-4a26-ac9d-2963ee95968b)
> [ 131.578124] ath10k_pci :01
Just tried 10.2.4.70.58 firmware that you linked to and it still crashes:
[ 131.568989] ath10k_pci :01:00.0: firmware crashed! (uuid
1838347e-9380-4a26-ac9d-2963ee95968b)
[ 131.578124] ath10k_pci :01:00.0: qca988x hw2.0 target 0x4100016c
chip_id 0x043202ff sub :
[ 131.587491]
Hi,
On Tue, Nov 29, 2016 at 11:22:12AM -0800, Benjamin Morgan wrote:
> When we try to transmit traffic (ping) between two meshed ath10k
> devices running latest lede we keep experiencing ath10k firmware
> crashes. This seems to only happen when running in 802.11n/ac mode
> but not in 802.11a/g mod
When we try to transmit traffic (ping) between two meshed ath10k devices
running latest lede we keep experiencing ath10k firmware crashes. This
seems to only happen when running in 802.11n/ac mode but not in
802.11a/g mode. Also, from the station dumps it appears that management
traffic is flow
15 matches
Mail list logo