From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "gloudon.jamie@gmail.com" <gloudon.jamie@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA6174 firmware crash in monitor mode
Date: Thu, 3 Mar 2016 15:38:37 +0000 [thread overview]
Message-ID: <8737s7372f.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160213063926.GA1767@darkstar> (gloudon jamie's message of "Sat, 13 Feb 2016 02:39:26 -0400")
gloudon.jamie@gmail.com writes:
> QCA6147 monitor mode stopped working ever since after kernel v4.3.
> Here is the firmware crash log:
>
> Feb 13 01:39:36 darkstar kernel: [ 34.010363] ath10k_pci 0000:01:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 168c:3344
> Feb 13 01:39:36 darkstar kernel: [ 34.010373] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
> Feb 13 01:39:36 darkstar kernel: [ 34.012252] ath10k_pci 0000:01:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
> Feb 13 01:39:36 darkstar kernel: [ 34.012291] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 cdb586cf
> Feb 13 01:39:36 darkstar kernel: [ 34.012301] ath10k_pci 0000:01:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
> Feb 13 01:39:36 darkstar kernel: [ 34.067918] ieee80211 phy0: Hardware restart was requested
>
> Feb 13 01:39:36 darkstar kernel: [ 34.010318] ath10k_pci 0000:01:00.0: firmware crashed! (uuid cb6fc88d-918d-4c7a-af69-15a713136bf7)
> Feb 13 01:39:36 darkstar kernel: [ 34.014330] ath10k_pci 0000:01:00.0: firmware register dump:
> Feb 13 01:39:36 darkstar kernel: [ 34.014340] ath10k_pci 0000:01:00.0: [00]: 0x05010000 0x00000000 0x0099987C 0x00000000
> Feb 13 01:39:36 darkstar kernel: [ 34.014349] ath10k_pci 0000:01:00.0: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
Does this patch fix it?
ath10k: fix firmware assert in monitor mode
https://patchwork.kernel.org/patch/8481281/
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-03-03 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 6:39 QCA6174 firmware crash in monitor mode gloudon.jamie
2016-03-03 15:38 ` Valo, Kalle [this message]
2016-03-05 6:46 ` gloudon.jamie
2016-03-05 9:53 ` Valo, Kalle
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=8737s7372f.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=gloudon.jamie@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