From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Kouroche Bouchiat <kouroche.bouchiat@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174
Date: Thu, 17 Aug 2017 13:56:15 +0000 [thread overview]
Message-ID: <878tii47sx.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAPYrjBWJ5teJ9SDN0NPEr4Qa=cGvSkbHzLfE=-pyYw=hVgGryA@mail.gmail.com> (Kouroche Bouchiat's message of "Thu, 17 Aug 2017 10:59:04 +0200")
Kouroche Bouchiat <kouroche.bouchiat@gmail.com> writes:
> Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> I was told that 4.4.1 firmare should have a fix for this. Please let me
>> know if you can confirm that and then I'll update the firmware in
>> linux-firmware.
>
> I'm sorry about my previous email. I forgot to disable HTML formatting.
> Been testing the 4.4.1 firmware for around 40 minutes and no
> disconnections so far. It's looking great. dmesg tells me it's been
> correctly upgraded:
> ath10k_pci 0000:02:00.0: enabling device (0000 -> 0002)
> ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
> ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id
> 0x00340aff sub 1a56:1535
> ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00026-QCARMSWP-1
> api 6 features wowlan,ignore-otp,raw-mode crc32 7b90c3fc
> ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 07ee144e
> ath10k_pci 0000:02:00.0: Unknown eventid: 118809
> ath10k_pci 0000:02:00.0: Unknown eventid: 90118
> ath10k_pci 0000:02:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 cal otp
> max-sta 32 raw 0 hwcrypto 1
> ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
> ath10k_pci 0000:02:00.0: Unknown eventid: 118809
> ath10k_pci 0000:02:00.0: Unknown eventid: 90118
> ath10k_pci 0000:02:00.0: Unknown eventid: 118809
> ath10k_pci 0000:02:00.0: Unknown eventid: 90118
>
> A diff on the previous firmware's dmesg (before moving to
> firmware-4.bin) shows the new version:
> 5c5
> < ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2
> api 6 features wowlan,ignore-otp crc32 4d458559
>> ath10k_pci 0000:02:00.0: firmware ver
>> WLAN.RM.4.4.1-00026-QCARMSWP-1 api 6 features
>> wowlan,ignore-otp,raw-mode crc32 7b90c3fc
> 8c9
> < ath10k_pci 0000:02:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp
> max-sta 32 raw 0 hwcrypto 1
>> ath10k_pci 0000:02:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 cal otp
>> max-sta 32 raw 0 hwcrypto 1
>
> Thanks a lot for your help,
> Tell me if you need anything else.
This is enough, thanks. I added an item to my todo list to update the
firmware in linux-firmware.
BTW, the unknown event ids are annoying. Anyone want to submit a patch
to fix (silence) those?
ath10k_pci 0000:02:00.0: Unknown eventid: 118809
ath10k_pci 0000:02:00.0: Unknown eventid: 90118
ath10k_pci 0000:02:00.0: Unknown eventid: 118809
ath10k_pci 0000:02:00.0: Unknown eventid: 90118
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-08-17 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 22:10 ath10k firmware-6.bin bug: Disconnections every 20 minutes on QCA6174 Kouroche Bouchiat
2017-08-16 14:14 ` Kalle Valo
2017-08-16 14:24 ` Gilbert Moisio
2017-08-16 14:42 ` Kalle Valo
2017-08-16 15:13 ` Gilbert Moisio
2017-08-16 16:26 ` Kalle Valo
[not found] ` <CAM8JFhCpWBDv=_rZ_KDTsQ008wjUgv5nix=kxv-RPd2035xGLQ@mail.gmail.com>
2017-08-17 7:11 ` Kalle Valo
[not found] ` <CAPYrjBUrEuuxpO=KYi1EXh-bZU2sPNLEsnNZnnp6_w1viss3wQ@mail.gmail.com>
2017-08-17 7:14 ` Kalle Valo
2017-08-17 8:59 ` Kouroche Bouchiat
2017-08-17 13:56 ` Kalle Valo [this message]
2017-08-17 15:54 ` Adrian Chadd
2017-08-17 16:03 ` 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=878tii47sx.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kouroche.bouchiat@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