ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Le Sueur <thefishface@gmail.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k failing with firmware RM.4.4-00022-QCARMSWPZ-2 on QCA6174 (Killer 1535)
Date: Sun, 22 Jan 2017 02:01:37 +0000	[thread overview]
Message-ID: <1485050497.3853.1.camel@gmail.com> (raw)
In-Reply-To: <CACKGw+FXdcKHU80fZ8zWwZFwePrF0GPv5ksqLEJMP-gusvOjHw@mail.gmail.com>


On Tue, 2017-01-17 at 11:30 +0100, Bartosz Markowski wrote:
> On 16 January 2017 at 20:24, Chris Le Sueur <thefishface@gmail.com>
> wrote:
> > Dear all,
> > 
> > (per request by kvalo on #ath10k)
> > 
> > I was trying out the firmware-5 from git to see if it would fix
> > throughput issues, but instead the driver just failed to work. I am
> > using kernel 4.8.15 on Fedora 25, and the following was printed to
> > the
> > kernel log:
> > 
> > ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
> > reset_mode 0
> > ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-
> > pci-
> > 0000:3a:00.0 .bin failed with error -2
> > ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-
> > 0000:3a:00.0.bin failed with error -2
> > ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
> > 0x00340aff sub 1a56:1535
> > ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0
> > testmode 0
> > ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 
> > api
> > 5 features wowlan,ignore-otp crc32 4d458559
> > ath10k_pci 0000:3a:00.0: failed to fetch board data for
> > bus=pci,bmi-
> > chip-id=0,bmi-board-id=0 from ath10k/QCA6174/hw3.0/board-2.bin
> > ath10k_pci 0000:3a:00.0: board_file api 1 bmi_id 0:0 crc32 ed5f849a
> 
> Please try to apply this patch -
> https://patchwork.kernel.org/patch/9486941/ and retry.
> 
> -Bartosz

This also fails. I have had to update my kernel as part of obtaining
the module source (I am using 4.9.4 as distributed with Fedora 25) so
the messages are a bit different; I've included both the patched and
stock output. I see the debug message added in that patch is also not
printed, so I assume the difference here is due to some transient
situation and not the patch itself.

Patched:

ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-
0000:3a:00.0.bin failed with error -2
ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-
0000:3a:00.0.bin failed with error -2
ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
0x00340aff sub 1a56:1535
ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0
testmode 0
ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api
5 features wowlan,ignore-otp crc32 4d458559
ath10k_pci 0000:3a:00.0: failed to fetch board data for bus=pci,bmi-
chip-id=0,bmi-board-id=0 from ath10k/QCA6174/hw3.0/board-2.bin
ath10k_pci 0000:3a:00.0: board_file api 1 bmi_id 0:0 crc32 ed5f849a
ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
ath10k_pci 0000:3a:00.0: htt version request timed out
ath10k_pci 0000:3a:00.0: failed to setup htt: -110
ath10k_pci 0000:3a:00.0: could not init core (-110)
ath10k_pci 0000:3a:00.0: could not probe fw (-110)

Stock:

ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-
0000:3a:00.0.bin failed with error -2
ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-
0000:3a:00.0.bin failed with error -2
ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
0x00340aff sub 1a56:1535
ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0
testmode 0
ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api
5 features wowlan,ignore-otp crc32 4d458559
ath10k_pci 0000:3a:00.0: failed to fetch board data for bus=pci,bmi-
chip-id=0,bmi-board-id=0 from ath10k/QCA6174/hw3.0/board-2.bin
ath10k_pci 0000:3a:00.0: board_file api 1 bmi_id 0:0 crc32 ed5f849a
ath10k_pci 0000:3a:00.0: Unknown eventid: 90118
ath10k_pci 0000:3a:00.0: failed to ping firmware: -110
ath10k_pci 0000:3a:00.0: failed to reset rx filter: -110
ath10k_pci 0000:3a:00.0: could not init core (-110)
ath10k_pci 0000:3a:00.0: could not probe fw (-110)

Regards,
Chris

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-01-22  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:24 ath10k failing with firmware RM.4.4-00022-QCARMSWPZ-2 on QCA6174 (Killer 1535) Chris Le Sueur
2017-01-17 10:30 ` Bartosz Markowski
2017-01-22  2:01   ` Chris Le Sueur [this message]
2017-01-23 22:57     ` Hsu, Ryan

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=1485050497.3853.1.camel@gmail.com \
    --to=thefishface@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=bartosz.markowski@tieto.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