From: gloudon.jamie@gmail.com
To: ath10k@lists.infradead.org
Subject: QCA6174 firmware crash in monitor mode
Date: Sat, 13 Feb 2016 02:39:26 -0400 [thread overview]
Message-ID: <20160213063926.GA1767@darkstar> (raw)
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
Feb 13 01:39:36 darkstar kernel: [ 34.014358] ath10k_pci 0000:01:00.0: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014366] ath10k_pci 0000:01:00.0: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014375] ath10k_pci 0000:01:00.0: [16]: 0x00000000 0x00000000 0x00000000 0x0099987C
Feb 13 01:39:36 darkstar kernel: [ 34.014384] ath10k_pci 0000:01:00.0: [20]: 0x00000000 0x004018F0 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014392] ath10k_pci 0000:01:00.0: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014401] ath10k_pci 0000:01:00.0: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014409] ath10k_pci 0000:01:00.0: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014418] ath10k_pci 0000:01:00.0: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014426] ath10k_pci 0000:01:00.0: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014435] ath10k_pci 0000:01:00.0: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014443] ath10k_pci 0000:01:00.0: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014452] ath10k_pci 0000:01:00.0: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014460] ath10k_pci 0000:01:00.0: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014625] ath10k_pci 0000:01:00.0: failed to set 2g txpower 0: -108
Feb 13 01:39:36 darkstar kernel: [ 34.014636] ath10k_pci 0000:01:00.0: failed to setup tx power 0: -108
Feb 13 01:39:36 darkstar kernel: [ 34.014644] ath10k_pci 0000:01:00.0: failed to recalc tx power: -108
Feb 13 01:39:36 darkstar kernel: [ 34.014714] ------------[ cut here ]------------
Feb 13 01:39:36 darkstar kernel: [ 34.014730] WARNING: CPU: 1 PID: 1471 at net/mac80211/iface.c:421 ieee80211_add_virtual_monitor+0xd7/0x17c()
Feb 13 01:39:36 darkstar kernel: [ 34.014739] CPU: 1 PID: 1471 Comm: ifconfig Not tainted 4.5.0-rc3 #3
Feb 13 01:39:36 darkstar kernel: [ 34.014745] Hardware name: Dell Inc. Inspiron 11 - 3147/06G7R2, BIOS A05 03/16/2015
Feb 13 01:39:36 darkstar kernel: [ 34.014750] 00000000 00000286 f53fbdb4 c11c002d 00000000 c1732845 f53fbdcc c1037740
Feb 13 01:39:36 darkstar kernel: [ 34.014767] c14d18e6 f58e6000 f54803e0 ffffff94 f53fbddc c10377f1 00000009 00000000
Feb 13 01:39:36 darkstar kernel: [ 34.014782] f53fbdf4 c14d18e6 698e7e68 f63454c8 f63454c0 00000000 f53fbe1c c14d22a5
Feb 13 01:39:36 darkstar kernel: [ 34.014796] Call Trace:
Feb 13 01:39:36 darkstar kernel: [ 34.014809] [<c11c002d>] dump_stack+0x47/0x5b
Feb 13 01:39:36 darkstar kernel: [ 34.014820] [<c1037740>] warn_slowpath_common+0x7e/0x95
Feb 13 01:39:36 darkstar kernel: [ 34.014828] [<c14d18e6>] ? ieee80211_add_virtual_monitor+0xd7/0x17c
Feb 13 01:39:36 darkstar kernel: [ 34.014837] [<c10377f1>] warn_slowpath_null+0x14/0x18
Feb 13 01:39:36 darkstar kernel: [ 34.014845] [<c14d18e6>] ieee80211_add_virtual_monitor+0xd7/0x17c
Feb 13 01:39:36 darkstar kernel: [ 34.014853] [<c14d22a5>] ieee80211_do_open+0x285/0x5be
Feb 13 01:39:36 darkstar kernel: [ 34.014862] [<c14d2620>] ieee80211_open+0x42/0x4d
Feb 13 01:39:36 darkstar kernel: [ 34.014871] [<c1436d6a>] __dev_open+0x7e/0xd1
Feb 13 01:39:36 darkstar kernel: [ 34.014879] [<c1436fc7>] __dev_change_flags+0x98/0x124
Feb 13 01:39:36 darkstar kernel: [ 34.014888] [<c1437078>] dev_change_flags+0x25/0x50
Feb 13 01:39:36 darkstar kernel: [ 34.014897] [<c147cee9>] devinet_ioctl+0x211/0x4b0
Feb 13 01:39:36 darkstar kernel: [ 34.014906] [<c147dc7a>] inet_ioctl+0x81/0x9a
Feb 13 01:39:36 darkstar kernel: [ 34.014916] [<c14228db>] sock_ioctl+0x165/0x186
Feb 13 01:39:36 darkstar kernel: [ 34.014930] [<c1422776>] ? sock_fasync+0x6b/0x6b
Feb 13 01:39:36 darkstar kernel: [ 34.014934] [<c10eb8f7>] vfs_ioctl+0x1c/0x26
Feb 13 01:39:36 darkstar kernel: [ 34.014937] [<c10ec2fb>] do_vfs_ioctl+0x4a6/0x510
Feb 13 01:39:36 darkstar kernel: [ 34.014941] [<c10d79db>] ? virt_to_head_page+0x19/0x1b
Feb 13 01:39:36 darkstar kernel: [ 34.014945] [<c10da3c0>] ? kmem_cache_free+0x37/0xd9
Feb 13 01:39:36 darkstar kernel: [ 34.014949] [<c10e6baa>] ? putname+0x44/0x47
Feb 13 01:39:36 darkstar kernel: [ 34.014952] [<c10e6baa>] ? putname+0x44/0x47
Feb 13 01:39:36 darkstar kernel: [ 34.014956] [<c10dee01>] ? do_sys_open+0xc0/0xca
Feb 13 01:39:36 darkstar kernel: [ 34.014959] [<c10ec3a6>] SyS_ioctl+0x41/0x5b
Feb 13 01:39:36 darkstar kernel: [ 34.014963] [<c1001167>] do_syscall_32_irqs_on+0x3e/0x50
Feb 13 01:39:36 darkstar kernel: [ 34.014968] [<c15072f6>] entry_INT80_32+0x2a/0x2a
Feb 13 01:39:36 darkstar kernel: [ 34.014983] ---[ end trace 46261952c940b8db ]---
Feb 13 01:39:36 darkstar kernel: [ 34.046345] ath10k_pci 0000:01:00.0: device has crashed during init
Feb 13 01:39:36 darkstar kernel: [ 34.067412] ath10k_pci 0000:01:00.0: device has crashed during init
Feb 13 01:39:36 darkstar kernel: [ 34.067426] ath10k_pci 0000:01:00.0: failed to wait for target init: -70
Feb 13 01:39:36 darkstar kernel: [ 34.100453] ath10k_pci 0000:01:00.0: device has crashed during init
Feb 13 01:39:36 darkstar kernel: [ 34.121502] ath10k_pci 0000:01:00.0: device has crashed during init
Feb 13 01:39:36 darkstar kernel: [ 34.121517] ath10k_pci 0000:01:00.0: failed to wait for target init: -70
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2016-02-13 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 6:39 gloudon.jamie [this message]
2016-03-03 15:38 ` QCA6174 firmware crash in monitor mode Valo, Kalle
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=20160213063926.GA1767@darkstar \
--to=gloudon.jamie@gmail.com \
--cc=ath10k@lists.infradead.org \
/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.