From: Rouven Czerwinski <rouven@czerwinskis.de>
To: Ryan Hsu <ryanhsu@qti.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Firmware Crash on qca61741 hw3.2
Date: Thu, 25 Jan 2018 08:43:36 +0100 [thread overview]
Message-ID: <87fu6us7rr.fsf@czerwinskis.de> (raw)
In-Reply-To: <848cf7f7-fdfc-ef85-d1b7-eefdd8672112@qti.qualcomm.com>
Ryan Hsu <ryanhsu@qti.qualcomm.com> writes:
> On 01/08/2018 03:28 AM, Rouven Czerwinski wrote:
>
>> Hello,
>>
>> I just experienced a firmware crash:
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: firmware crashed! (guid 07b97ee6-5eb2-4196-b038-e3cad581c735)
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00051-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 c3fd4411
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 0e26ef70
>> [Mo Jan 8 12:15:44 2018] ath10k_pci 0000:01:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
>>
>> Complete dmesg attached.
>>
>> Is this issue fixed in newer firmware versions?
>
> It seems the failure is due to the BANDWIDTH information mismatch in firmware
> when the initial connection is made with narrower PHYMODE and BANDWIDTH and
> then AP changed that later.
>
> I've seen similar issue earlier but I can't reproduce at my setup.
>
> I've sent out a patch to address that, to reconfigure the PHYMODE while
> changing the BANDWIDTH.
>
> Can you help to give it test to see if that helps at your end?
Sure, the failure was pretty reliable on my universities wireless
network. I'll apply and report back, thanks!
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2018-01-25 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 11:28 Firmware Crash on qca61741 hw3.2 Rouven Czerwinski
2018-01-25 1:10 ` Ryan Hsu
2018-01-25 7:43 ` Rouven Czerwinski [this message]
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=87fu6us7rr.fsf@czerwinskis.de \
--to=rouven@czerwinskis.de \
--cc=ath10k@lists.infradead.org \
--cc=ryanhsu@qti.qualcomm.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 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.