* Crash during driver startup.
@ 2014-04-10 4:14 Ben Greear
2014-04-10 10:05 ` Michal Kazior
0 siblings, 1 reply; 36+ messages in thread
From: Ben Greear @ 2014-04-10 4:14 UTC (permalink / raw)
To: ath10k
This is in a fairly hacked code tree, so problem could be mine, but
just in case someone sees something obvious, here's the stack:
I had copied over a new firmware image and was in process of reloading
the ath10k driver and related modules when this happened.
ieee80211 phy0: Atheros AR9300 Rev:3 mem=0xffffc90016f00000, irq=18
e1000e 0000:02:00.0 eth1: registered PHC clock
e1000e 0000:02:00.0 eth1: (PCI Express:2.5GT/s:Width x1) 00:90:0b:26:81:91
e1000e 0000:02:00.0 eth1: Intel(R) PRO/1000 Network Connection
e1000e 0000:02:00.0 eth1: MAC: 3, PHY: 8, PBA No: FFFFFF-0FF
ath10k: boot warm reset complete
ath10k: boot init ce src ring id 0 entries 16 base_addr ffff8800d5418000
ath10k: boot ce dest ring id 1 entries 512 base_addr ffff880034e12000
ath10k: boot ce dest ring id 2 entries 32 base_addr ffff8800d5419000
ath10k: boot init ce src ring id 3 entries 32 base_addr ffff8800d541a000
ath10k: boot init ce src ring id 4 entries 4096 base_addr ffff880034e70000
ath10k: boot init ce src ring id 7 entries 2 base_addr ffff8800d541b000
ath10k: boot ce dest ring id 7 entries 2 base_addr ffff8800d541c000
ath10k_pci 0000:04:00.0: irq 52 for MSI/MSI-X
ath10k: boot waiting target to initialise
ath10k: boot target indicator 0
ath10k: boot target indicator 0
ath10k: boot target indicator 0
ath10k: boot target indicator 2
ath10k: boot target initialised
ath10k: pci irq MSI
ath10k: Hardware name qca988x hw2.0 version 0x4100016c
ath10k: trying fw api 2
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
ath10k: found fw version 10.1.467-ct
ath10k: found fw timestamp 1397084546
ath10k: found firmware features ie (4 B)
ath10k: Enabling feature bit: 1
ath10k: Enabling feature bit: 2
ath10k: Enabling feature bit: 4
ath10k: features
ath10k: found FW bss info, RAM: addr 0x40d650 len 0x1db0 ROM: addr 0x400c00 len 0x5ce8
ath10k: found otp image ie (7561 B)
ath10k: found fw image ie (195877 B)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
ath10k: using fw api 2
ath10k: boot push board extended data addr 0x0
BUG: unable to handle kernel paging request at ffffffff815d6133
IP: [<ffffffff810fc68d>] __lock_acquire+0xf6/0xe48
cfg80211: Ignoring regulatory request set by core since the driver uses its own custom regulatory domain
cfg80211: World regulatory domain updated:
cfg80211: DFS Master region: unset
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm)
cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm)
cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm)
cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
PGD 1a10067 PUD 1a11063 PMD 14001e1
Oops: 0003 [#1] PREEMPT SMP
Modules linked in: iTCO_wdt iTCO_vendor_support joydev cdc_acm microcode snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic pcspkr ath10k_pci(+)
snd_hda_intel ath9k snd_hda_codec ath9k_common serio_raw ath9k_hw snd_hwdep ath10k_core ath snd_seq mac80211 snd_seq_device i2c_i801 snd_pcm cfg80211 e1000e
lpc_ich ptp pps_core snd_timer snd soundcore uinput sunrpc ipv6 i915 video i2c_algo_bit drm_kms_helper drm i2c_core
CPU: 2 PID: 529 Comm: udevd Not tainted 3.14.0+ #15
Hardware name: To be filled by O.E.M. To be filled by O.E.M./HURONRIVER, BIOS 4.6.5 05/02/2012
task: ffff88020fe342a0 ti: ffff8802102a4000 task.ti: ffff8802102a4000
RIP: 0010:[<ffffffff810fc68d>] [<ffffffff810fc68d>] __lock_acquire+0xf6/0xe48
RSP: 0018:ffff8802102a5628 EFLAGS: 00010082
RAX: ffffffff815d5f9b RBX: ffff88020fe342a0 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8802102a5758
RBP: ffff8802102a56e8 R08: 0000000000000002 R09: 0000000000000001
R10: ffffffff810f5999 R11: ffff8802105da510 R12: 0000000000000046
R13: ffff8800d5e2aaa0 R14: ffff8802102a5758 R15: 00000000fffb9169
FS: 00007f4bfaa71840(0000) GS:ffff88021fb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff815d6133 CR3: 0000000214120000 CR4: 00000000000407e0
Stack:
ffff880200000000 0000550200000000 0000000000000001 ffffffff00000002
0000000000000000 ffff88020fe342a0 00000000815d5d7c 0000000000000002
ffff88020fe342a0 ffff88020fe34ae0 0000000000000006 0000000000000007
Call Trace:
[<ffffffff810fdaf4>] ? mark_held_locks+0x71/0x99
[<ffffffff810c6b6d>] ? __local_bh_enable_ip+0xaa/0xd9
[<ffffffff810fd7eb>] lock_acquire+0x82/0x9d
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810c6b72>] ? __local_bh_enable_ip+0xaf/0xd9
[<ffffffff815d5f9b>] _raw_spin_lock_irqsave+0x47/0x5a
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810f5999>] complete+0x19/0x45
[<ffffffffa056d977>] ath10k_pci_hif_exchange_bmi_msg+0x267/0x3f4 [ath10k_pci]
[<ffffffffa0471b42>] ath10k_hif_exchange_bmi_msg+0xe/0x10 [ath10k_core]
[<ffffffffa0471f01>] ath10k_bmi_write_memory+0xc4/0x12d [ath10k_core]
[<ffffffffa046877f>] ath10k_core_start+0x207/0x828 [ath10k_core]
[<ffffffffa0469723>] ath10k_core_register+0x5ca/0x77f [ath10k_core]
[<ffffffffa056e935>] ath10k_pci_probe+0x362/0x37d [ath10k_pci]
[<ffffffff81313783>] local_pci_probe+0x38/0x7e
[<ffffffff813d209c>] ? driver_probe_device+0x2f9/0x2f9
[<ffffffff813139d6>] pci_device_probe+0xc6/0xec
[<ffffffff813d1ec8>] driver_probe_device+0x125/0x2f9
[<ffffffff813d209c>] ? driver_probe_device+0x2f9/0x2f9
[<ffffffff813d20ea>] __driver_attach+0x4e/0x6f
[<ffffffff813d0330>] bus_for_each_dev+0x5a/0x8c
[<ffffffff813d1878>] driver_attach+0x19/0x1b
[<ffffffff813d1555>] bus_add_driver+0x110/0x1f5
[<ffffffff813d26dd>] driver_register+0x87/0xbe
[<ffffffff81312df6>] __pci_register_driver+0x5c/0x60
[<ffffffffa0576000>] ? 0xffffffffa0575fff
[<ffffffffa0576020>] ath10k_pci_init+0x20/0x3c [ath10k_pci]
[<ffffffffa0576000>] ? 0xffffffffa0575fff
[<ffffffff81002124>] do_one_initcall+0xae/0x156
[<ffffffff810f9f3a>] ? up_read+0x24/0x29
[<ffffffff81150aa1>] ? jump_label_lock+0x12/0x14
[<ffffffff810e0965>] ? __blocking_notifier_call_chain+0x4c/0x5a
[<ffffffff81125188>] load_module+0x1b2e/0x1e42
[<ffffffff811224b5>] ? mod_kobject_put+0x9b/0x9b
[<ffffffff812e9c8e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff81125568>] SyS_init_module+0xcc/0xdb
[<ffffffff815dac7d>] system_call_fastpath+0x1a/0x1f
Code: 4c 89 f7 89 8d 58 ff ff ff 44 89 8d 50 ff ff ff e8 d9 ea ff ff 48 85 c0 8b 8d 58 ff ff ff 44 8b 8d 50 ff ff ff 0f 84 9f 04 00 00 <f0> ff 80 98 01 00 00 83
3d 0d 82 35 01 00 44 8b ab e8 07 00 00
RIP [<ffffffff810fc68d>] __lock_acquire+0xf6/0xe48
RSP <ffff8802102a5628>
CR2: ffffffff815d6133
---[ end trace d566585fb1bbffa2 ]---
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* [PATCH] ath10k: double check bmi xfer pointers
2014-04-10 4:14 Crash during driver startup Ben Greear
@ 2014-04-10 10:05 ` Michal Kazior
0 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-10 10:05 UTC (permalink / raw)
To: ath10k; +Cc: linux-wireless, greearb, Michal Kazior
If for some reason copy engine ring buffer became
corrupt ath10k could crash the machine due to
invalid pointer dereference. It's very unlikely
but devices can never be fully trusted so verify
if the bmi xfer pointer read back from copy engine
matches the original pointer. The bug looked as
follows:
BUG: unable to handle kernel paging request at ffffffff815d6133
...
Call Trace:
[<ffffffff810fdaf4>] ? mark_held_locks+0x71/0x99
[<ffffffff810c6b6d>] ? __local_bh_enable_ip+0xaa/0xd9
[<ffffffff810fd7eb>] lock_acquire+0x82/0x9d
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810c6b72>] ? __local_bh_enable_ip+0xaf/0xd9
[<ffffffff815d5f9b>] _raw_spin_lock_irqsave+0x47/0x5a
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810f5999>] complete+0x19/0x45
[<ffffffffa056d977>] ath10k_pci_hif_exchange_bmi_msg+0x267/0x3f4 [ath10k_pci]
[<ffffffffa0471b42>] ath10k_hif_exchange_bmi_msg+0xe/0x10 [ath10k_core]
[<ffffffffa0471f01>] ath10k_bmi_write_memory+0xc4/0x12d [ath10k_core]
[<ffffffffa046877f>] ath10k_core_start+0x207/0x828 [ath10k_core]
[<ffffffffa0469723>] ath10k_core_register+0x5ca/0x77f [ath10k_core]
...
Reported-By: Ben Greear <greearb@candelatech.com>
Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
---
drivers/net/wireless/ath/ath10k/pci.c | 30 ++++++++++++++++++++++--------
1 file changed, 22 insertions(+), 8 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index bf1083d..85e84c9 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
@@ -1390,35 +1390,49 @@ err_dma:
return ret;
}
-static void ath10k_pci_bmi_send_done(struct ath10k_ce_pipe *ce_state)
+static void ath10k_pci_bmi_send_done(struct ath10k_ce_pipe *ce_state,
+ struct bmi_xfer *xfer)
{
- struct bmi_xfer *xfer;
+ void *ptr;
u32 ce_data;
unsigned int nbytes;
unsigned int transfer_id;
- if (ath10k_ce_completed_send_next(ce_state, (void **)&xfer, &ce_data,
+ if (ath10k_ce_completed_send_next(ce_state, (void **)&ptr, &ce_data,
&nbytes, &transfer_id))
return;
+ if (xfer != ptr) {
+ ath10k_warn("failed to verify bmi xfer tx pointer (got %p expected %p)\n",
+ ptr, xfer);
+ return;
+ }
+
if (xfer->wait_for_resp)
return;
complete(&xfer->done);
}
-static void ath10k_pci_bmi_recv_data(struct ath10k_ce_pipe *ce_state)
+static void ath10k_pci_bmi_recv_data(struct ath10k_ce_pipe *ce_state,
+ struct bmi_xfer *xfer)
{
- struct bmi_xfer *xfer;
+ void *ptr;
u32 ce_data;
unsigned int nbytes;
unsigned int transfer_id;
unsigned int flags;
- if (ath10k_ce_completed_recv_next(ce_state, (void **)&xfer, &ce_data,
+ if (ath10k_ce_completed_recv_next(ce_state, (void **)&ptr, &ce_data,
&nbytes, &transfer_id, &flags))
return;
+ if (xfer != ptr) {
+ ath10k_warn("failed to verify bmi xfer rx pointer (got %p expected %p)\n",
+ ptr, xfer);
+ return;
+ }
+
if (!xfer->wait_for_resp) {
ath10k_warn("unexpected: BMI data received; ignoring\n");
return;
@@ -1435,8 +1449,8 @@ static int ath10k_pci_bmi_wait(struct ath10k_ce_pipe *tx_pipe,
unsigned long timeout = jiffies + BMI_COMMUNICATION_TIMEOUT_HZ;
while (time_before_eq(jiffies, timeout)) {
- ath10k_pci_bmi_send_done(tx_pipe);
- ath10k_pci_bmi_recv_data(rx_pipe);
+ ath10k_pci_bmi_send_done(tx_pipe, xfer);
+ ath10k_pci_bmi_recv_data(rx_pipe, xfer);
if (completion_done(&xfer->done))
return 0;
--
1.8.5.3
^ permalink raw reply related [flat|nested] 36+ messages in thread
* [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-10 10:05 ` Michal Kazior
0 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-10 10:05 UTC (permalink / raw)
To: ath10k; +Cc: greearb, linux-wireless, Michal Kazior
If for some reason copy engine ring buffer became
corrupt ath10k could crash the machine due to
invalid pointer dereference. It's very unlikely
but devices can never be fully trusted so verify
if the bmi xfer pointer read back from copy engine
matches the original pointer. The bug looked as
follows:
BUG: unable to handle kernel paging request at ffffffff815d6133
...
Call Trace:
[<ffffffff810fdaf4>] ? mark_held_locks+0x71/0x99
[<ffffffff810c6b6d>] ? __local_bh_enable_ip+0xaa/0xd9
[<ffffffff810fd7eb>] lock_acquire+0x82/0x9d
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810c6b72>] ? __local_bh_enable_ip+0xaf/0xd9
[<ffffffff815d5f9b>] _raw_spin_lock_irqsave+0x47/0x5a
[<ffffffff810f5999>] ? complete+0x19/0x45
[<ffffffff810f5999>] complete+0x19/0x45
[<ffffffffa056d977>] ath10k_pci_hif_exchange_bmi_msg+0x267/0x3f4 [ath10k_pci]
[<ffffffffa0471b42>] ath10k_hif_exchange_bmi_msg+0xe/0x10 [ath10k_core]
[<ffffffffa0471f01>] ath10k_bmi_write_memory+0xc4/0x12d [ath10k_core]
[<ffffffffa046877f>] ath10k_core_start+0x207/0x828 [ath10k_core]
[<ffffffffa0469723>] ath10k_core_register+0x5ca/0x77f [ath10k_core]
...
Reported-By: Ben Greear <greearb@candelatech.com>
Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
---
drivers/net/wireless/ath/ath10k/pci.c | 30 ++++++++++++++++++++++--------
1 file changed, 22 insertions(+), 8 deletions(-)
diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index bf1083d..85e84c9 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
@@ -1390,35 +1390,49 @@ err_dma:
return ret;
}
-static void ath10k_pci_bmi_send_done(struct ath10k_ce_pipe *ce_state)
+static void ath10k_pci_bmi_send_done(struct ath10k_ce_pipe *ce_state,
+ struct bmi_xfer *xfer)
{
- struct bmi_xfer *xfer;
+ void *ptr;
u32 ce_data;
unsigned int nbytes;
unsigned int transfer_id;
- if (ath10k_ce_completed_send_next(ce_state, (void **)&xfer, &ce_data,
+ if (ath10k_ce_completed_send_next(ce_state, (void **)&ptr, &ce_data,
&nbytes, &transfer_id))
return;
+ if (xfer != ptr) {
+ ath10k_warn("failed to verify bmi xfer tx pointer (got %p expected %p)\n",
+ ptr, xfer);
+ return;
+ }
+
if (xfer->wait_for_resp)
return;
complete(&xfer->done);
}
-static void ath10k_pci_bmi_recv_data(struct ath10k_ce_pipe *ce_state)
+static void ath10k_pci_bmi_recv_data(struct ath10k_ce_pipe *ce_state,
+ struct bmi_xfer *xfer)
{
- struct bmi_xfer *xfer;
+ void *ptr;
u32 ce_data;
unsigned int nbytes;
unsigned int transfer_id;
unsigned int flags;
- if (ath10k_ce_completed_recv_next(ce_state, (void **)&xfer, &ce_data,
+ if (ath10k_ce_completed_recv_next(ce_state, (void **)&ptr, &ce_data,
&nbytes, &transfer_id, &flags))
return;
+ if (xfer != ptr) {
+ ath10k_warn("failed to verify bmi xfer rx pointer (got %p expected %p)\n",
+ ptr, xfer);
+ return;
+ }
+
if (!xfer->wait_for_resp) {
ath10k_warn("unexpected: BMI data received; ignoring\n");
return;
@@ -1435,8 +1449,8 @@ static int ath10k_pci_bmi_wait(struct ath10k_ce_pipe *tx_pipe,
unsigned long timeout = jiffies + BMI_COMMUNICATION_TIMEOUT_HZ;
while (time_before_eq(jiffies, timeout)) {
- ath10k_pci_bmi_send_done(tx_pipe);
- ath10k_pci_bmi_recv_data(rx_pipe);
+ ath10k_pci_bmi_send_done(tx_pipe, xfer);
+ ath10k_pci_bmi_recv_data(rx_pipe, xfer);
if (completion_done(&xfer->done))
return 0;
--
1.8.5.3
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply related [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
2014-04-10 10:05 ` Michal Kazior
@ 2014-04-10 13:42 ` Ben Greear
-1 siblings, 0 replies; 36+ messages in thread
From: Ben Greear @ 2014-04-10 13:42 UTC (permalink / raw)
To: Michal Kazior, ath10k; +Cc: linux-wireless
On 04/10/2014 03:05 AM, Michal Kazior wrote:
> If for some reason copy engine ring buffer became
> corrupt ath10k could crash the machine due to
> invalid pointer dereference. It's very unlikely
> but devices can never be fully trusted so verify
> if the bmi xfer pointer read back from copy engine
> matches the original pointer. The bug looked as
> follows:
Thanks for fixing this. I'll add this patch to my
tree and run more tests today.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-10 13:42 ` Ben Greear
0 siblings, 0 replies; 36+ messages in thread
From: Ben Greear @ 2014-04-10 13:42 UTC (permalink / raw)
To: Michal Kazior, ath10k; +Cc: linux-wireless
On 04/10/2014 03:05 AM, Michal Kazior wrote:
> If for some reason copy engine ring buffer became
> corrupt ath10k could crash the machine due to
> invalid pointer dereference. It's very unlikely
> but devices can never be fully trusted so verify
> if the bmi xfer pointer read back from copy engine
> matches the original pointer. The bug looked as
> follows:
Thanks for fixing this. I'll add this patch to my
tree and run more tests today.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
2014-04-10 10:05 ` Michal Kazior
@ 2014-04-11 5:40 ` Kalle Valo
-1 siblings, 0 replies; 36+ messages in thread
From: Kalle Valo @ 2014-04-11 5:40 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k, greearb, linux-wireless
Michal Kazior <michal.kazior@tieto.com> writes:
> If for some reason copy engine ring buffer became
> corrupt ath10k could crash the machine due to
> invalid pointer dereference. It's very unlikely
> but devices can never be fully trusted so verify
> if the bmi xfer pointer read back from copy engine
> matches the original pointer.
The big question is why does this happen? Does this happen only with
Ben's firmware or is it a more generic problem?
--
Kalle Valo
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-11 5:40 ` Kalle Valo
0 siblings, 0 replies; 36+ messages in thread
From: Kalle Valo @ 2014-04-11 5:40 UTC (permalink / raw)
To: Michal Kazior; +Cc: greearb, linux-wireless, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> If for some reason copy engine ring buffer became
> corrupt ath10k could crash the machine due to
> invalid pointer dereference. It's very unlikely
> but devices can never be fully trusted so verify
> if the bmi xfer pointer read back from copy engine
> matches the original pointer.
The big question is why does this happen? Does this happen only with
Ben's firmware or is it a more generic problem?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
2014-04-11 5:40 ` Kalle Valo
@ 2014-04-11 5:47 ` Michal Kazior
-1 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-11 5:47 UTC (permalink / raw)
To: Kalle Valo; +Cc: ath10k, Ben Greear, linux-wireless
On 11 April 2014 07:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> If for some reason copy engine ring buffer became
>> corrupt ath10k could crash the machine due to
>> invalid pointer dereference. It's very unlikely
>> but devices can never be fully trusted so verify
>> if the bmi xfer pointer read back from copy engine
>> matches the original pointer.
>
> The big question is why does this happen? Does this happen only with
> Ben's firmware or is it a more generic problem?
I'll look more into this.
Michał
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-11 5:47 ` Michal Kazior
0 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-11 5:47 UTC (permalink / raw)
To: Kalle Valo; +Cc: Ben Greear, linux-wireless, ath10k
On 11 April 2014 07:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> If for some reason copy engine ring buffer became
>> corrupt ath10k could crash the machine due to
>> invalid pointer dereference. It's very unlikely
>> but devices can never be fully trusted so verify
>> if the bmi xfer pointer read back from copy engine
>> matches the original pointer.
>
> The big question is why does this happen? Does this happen only with
> Ben's firmware or is it a more generic problem?
I'll look more into this.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
2014-04-11 5:47 ` Michal Kazior
@ 2014-04-11 7:58 ` Michal Kazior
-1 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-11 7:58 UTC (permalink / raw)
To: Kalle Valo; +Cc: ath10k, Ben Greear, linux-wireless
On 11 April 2014 07:47, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 11 April 2014 07:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> If for some reason copy engine ring buffer became
>>> corrupt ath10k could crash the machine due to
>>> invalid pointer dereference. It's very unlikely
>>> but devices can never be fully trusted so verify
>>> if the bmi xfer pointer read back from copy engine
>>> matches the original pointer.
>>
>> The big question is why does this happen? Does this happen only with
>> Ben's firmware or is it a more generic problem?
>
> I'll look more into this.
Hmm.. After going through the code a few times I think the bug is
actually something else.
If the crash happened in complete() it means the completion structure
wasn't set up properly. However it is always initialized in
ath10k_pci_hif_exchange_bmi_msg() before proceeding. This means xfer
pointer read back from ath10k_ce_completed_send_next() or
ath10k_ce_completed_recv_next() is wrong. Since the pointer to it is
kept on host getting wrong xfer means sw_index must be wrong. If I
assume indexes are managed correctly (i.e. no overflows, locking is
fine) then it is the entry the sw_index points to that is actually
unexpected.
This could happen if concurrent transfers occur on pipe 0 or 1 (used
for bmi communication) during device bootup. This could be either a
concurrent bmi transfer or a non-bmi buffer or an old bmi xfer data.
The latter shouldn't be the case because
ath10k_pci_hif_exchange_bmi_msg() cleans up after itself. Concurrent
access doesn't seem to be the case either.
I conclude the bug is not present in the vanilla ath10k code.
TL;DR drop the patch, please
Michał
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-11 7:58 ` Michal Kazior
0 siblings, 0 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-11 7:58 UTC (permalink / raw)
To: Kalle Valo; +Cc: Ben Greear, linux-wireless, ath10k
On 11 April 2014 07:47, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 11 April 2014 07:40, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> If for some reason copy engine ring buffer became
>>> corrupt ath10k could crash the machine due to
>>> invalid pointer dereference. It's very unlikely
>>> but devices can never be fully trusted so verify
>>> if the bmi xfer pointer read back from copy engine
>>> matches the original pointer.
>>
>> The big question is why does this happen? Does this happen only with
>> Ben's firmware or is it a more generic problem?
>
> I'll look more into this.
Hmm.. After going through the code a few times I think the bug is
actually something else.
If the crash happened in complete() it means the completion structure
wasn't set up properly. However it is always initialized in
ath10k_pci_hif_exchange_bmi_msg() before proceeding. This means xfer
pointer read back from ath10k_ce_completed_send_next() or
ath10k_ce_completed_recv_next() is wrong. Since the pointer to it is
kept on host getting wrong xfer means sw_index must be wrong. If I
assume indexes are managed correctly (i.e. no overflows, locking is
fine) then it is the entry the sw_index points to that is actually
unexpected.
This could happen if concurrent transfers occur on pipe 0 or 1 (used
for bmi communication) during device bootup. This could be either a
concurrent bmi transfer or a non-bmi buffer or an old bmi xfer data.
The latter shouldn't be the case because
ath10k_pci_hif_exchange_bmi_msg() cleans up after itself. Concurrent
access doesn't seem to be the case either.
I conclude the bug is not present in the vanilla ath10k code.
TL;DR drop the patch, please
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
2014-04-11 7:58 ` Michal Kazior
(?)
@ 2014-04-11 15:09 ` Vu Hai NGUYEN
2014-04-14 6:39 ` Michal Kazior
-1 siblings, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-11 15:09 UTC (permalink / raw)
To: ath10k; +Cc: Patrick CARNEIRO RODRIGUEZ
Hello everyone,
I try to load the module of driver ath10k on a cpu marvell 370 which ran linux 3.2.36, my module wifi is WLE900VX.
These modules was built from backport 3.13.2-1.
After loading the module, I use the command "lsmod" and saw that 6 modules was loaded.
But my "dmesg" show an error:
ieee80211 phy0: Failed to initialize wep: -2
And the interface ath0 can not be recognized.
Does any one have any idea about this problem????
Thank you in advanced and have a nice weekend :D
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
2014-04-11 15:09 ` load module ath10k: ieee80211 phy0: Failed to initialize wep: -2 Vu Hai NGUYEN
@ 2014-04-14 6:39 ` Michal Kazior
2014-04-14 8:10 ` Kalle Valo
0 siblings, 1 reply; 36+ messages in thread
From: Michal Kazior @ 2014-04-14 6:39 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
On 11 April 2014 17:09, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> Hello everyone,
> I try to load the module of driver ath10k on a cpu marvell 370 which ran linux 3.2.36, my module wifi is WLE900VX.
> These modules was built from backport 3.13.2-1.
> After loading the module, I use the command "lsmod" and saw that 6 modules was loaded.
> But my "dmesg" show an error:
> ieee80211 phy0: Failed to initialize wep: -2
> And the interface ath0 can not be recognized.
> Does any one have any idea about this problem????
I'm guessing here, but I suspect you tried to load a backports driver
against cfg80211/mac80211 modules from your distro kernel.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
2014-04-11 7:58 ` Michal Kazior
@ 2014-04-14 8:05 ` Kalle Valo
-1 siblings, 0 replies; 36+ messages in thread
From: Kalle Valo @ 2014-04-14 8:05 UTC (permalink / raw)
To: Michal Kazior; +Cc: Ben Greear, linux-wireless, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> I conclude the bug is not present in the vanilla ath10k code.
>
> TL;DR drop the patch, please
Hehe. Thanks, I have dropped the patch.
--
Kalle Valo
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [PATCH] ath10k: double check bmi xfer pointers
@ 2014-04-14 8:05 ` Kalle Valo
0 siblings, 0 replies; 36+ messages in thread
From: Kalle Valo @ 2014-04-14 8:05 UTC (permalink / raw)
To: Michal Kazior; +Cc: Ben Greear, linux-wireless, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> I conclude the bug is not present in the vanilla ath10k code.
>
> TL;DR drop the patch, please
Hehe. Thanks, I have dropped the patch.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
2014-04-14 6:39 ` Michal Kazior
@ 2014-04-14 8:10 ` Kalle Valo
2014-04-14 15:49 ` RE : " Vu Hai NGUYEN
0 siblings, 1 reply; 36+ messages in thread
From: Kalle Valo @ 2014-04-14 8:10 UTC (permalink / raw)
To: Michal Kazior; +Cc: Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> On 11 April 2014 17:09, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>> Hello everyone,
>> I try to load the module of driver ath10k on a cpu marvell 370 which ran linux 3.2.36, my module wifi is WLE900VX.
>> These modules was built from backport 3.13.2-1.
>> After loading the module, I use the command "lsmod" and saw that 6 modules was loaded.
>> But my "dmesg" show an error:
>> ieee80211 phy0: Failed to initialize wep: -2
>> And the interface ath0 can not be recognized.
ath0 interface? ath10k does not use interface names like that, that
smells like the proprietary driver.
>> Does any one have any idea about this problem????
>
> I'm guessing here, but I suspect you tried to load a backports driver
> against cfg80211/mac80211 modules from your distro kernel.
Another option is that there's a some sort of problem with the crypto
modules.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
2014-04-14 8:10 ` Kalle Valo
@ 2014-04-14 15:49 ` Vu Hai NGUYEN
2014-04-15 8:20 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
0 siblings, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-14 15:49 UTC (permalink / raw)
To: Kalle Valo, Michal Kazior; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
Thank you guys,
My mistake, the interface is wlan0, not ath0 (which is created before from the driver Aquila supplied by Atheros)
And the problem about cfg80211/mac80211 is because that I didn't activate cfg80211 in my new kernel of linux when I re-compile my project. (I just take the modules ath10k that I compiled before from the kernel that I had modified to compile ath10k and then put in my new project)
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : lundi 14 avril 2014 10:10
À : Michal Kazior
Cc : Vu Hai NGUYEN; Patrick CARNEIRO RODRIGUEZ; ath10k@lists.infradead.org
Objet : Re: load module ath10k: ieee80211 phy0: Failed to initialize wep: -2
Michal Kazior <michal.kazior@tieto.com> writes:
> On 11 April 2014 17:09, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>> Hello everyone,
>> I try to load the module of driver ath10k on a cpu marvell 370 which ran linux 3.2.36, my module wifi is WLE900VX.
>> These modules was built from backport 3.13.2-1.
>> After loading the module, I use the command "lsmod" and saw that 6 modules was loaded.
>> But my "dmesg" show an error:
>> ieee80211 phy0: Failed to initialize wep: -2
>> And the interface ath0 can not be recognized.
ath0 interface? ath10k does not use interface names like that, that
smells like the proprietary driver.
>> Does any one have any idea about this problem????
>
> I'm guessing here, but I suspect you tried to load a backports driver
> against cfg80211/mac80211 modules from your distro kernel.
Another option is that there's a some sort of problem with the crypto
modules.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-14 15:49 ` RE : " Vu Hai NGUYEN
@ 2014-04-15 8:20 ` Vu Hai NGUYEN
2014-04-15 11:02 ` Kalle Valo
0 siblings, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-15 8:20 UTC (permalink / raw)
To: ath10k; +Cc: Patrick CARNEIRO RODRIGUEZ
Hi guys,
When I load the firmware-2.bin_10.1.467.2-1 I got this error when I put my device in mode ACCESS POINT:
"PCI express error: irq - 228, Pex number: 0, Interrupt Cause Register value: 10"
But if I use the version 999.999.0.x. I don't have this error.
So I just report it here, I don't know what kind of other information do you guys need to know what may cause that error.
Please feel free to ask me to provide other information
Sincerely,
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-15 8:20 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
@ 2014-04-15 11:02 ` Kalle Valo
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
0 siblings, 1 reply; 36+ messages in thread
From: Kalle Valo @ 2014-04-15 11:02 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> When I load the firmware-2.bin_10.1.467.2-1 I got this error when I
> put my device in mode ACCESS POINT: "PCI express error: irq - 228, Pex
> number: 0, Interrupt Cause Register value: 10" But if I use the
> version 999.999.0.x. I don't have this error.
I wonder if this has something to do with cold reset causing PCI bus
errors? But we need more information to say more. Can you send the full
dmesg output (from the beginning of kernel boot) along with detailed
descriptions of your host platform and what kind qca98xx board you have.
Even better is if you can also send a debug log output using debug mask
value 0x432. More info:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug#Useful_debug_masks
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-15 11:02 ` Kalle Valo
@ 2014-04-16 11:51 ` Vu Hai NGUYEN
2014-04-16 11:51 ` Vu Hai NGUYEN
2014-04-24 6:35 ` Kalle Valo
0 siblings, 2 replies; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-16 11:51 UTC (permalink / raw)
To: ath10k; +Cc: Patrick CARNEIRO RODRIGUEZ
Thank you for your response,
I didn't power down my cible to reboot, I just upload new program with new firmware and run it. The problem is when that error appear my console keep print it and I Have no longer access to my system, I can not type another command (dmesg) , then I have to reset my platform. I'll try to get the dmesg and sent you later.
My host platform is using processor Marvell Armada 370 and my module of wifi is Compex WLE900VX.
There's another problem: when I used the firmware version 999.999 some times when I ran my program and change the parameter of configuration, the firmware crash and I got a output dmesg which indicate a strange version of firmware (1.0.0.636 ???) :
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location: 0x00401930
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
and then It reload the firmware 999.999. :
ath10k: firmware 999.999.0.636 booted
You can see the output of my dmesg
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : mardi 15 avril 2014 13:02
À : Vu Hai NGUYEN
Cc : ath10k@lists.infradead.org; Patrick CARNEIRO RODRIGUEZ
Objet : Re: Report Firmware firmware-2.bin_10.1.467.2-1 Error
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> When I load the firmware-2.bin_10.1.467.2-1 I got this error when I
> put my device in mode ACCESS POINT: "PCI express error: irq - 228, Pex
> number: 0, Interrupt Cause Register value: 10" But if I use the
> version 999.999.0.x. I don't have this error.
I wonder if this has something to do with cold reset causing PCI bus
errors? But we need more information to say more. Can you send the full
dmesg output (from the beginning of kernel boot) along with detailed
descriptions of your host platform and what kind qca98xx board you have.
Even better is if you can also send a debug log output using debug mask
value 0x432. More info:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug#Useful_debug_masks
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
@ 2014-04-16 11:51 ` Vu Hai NGUYEN
2014-04-24 6:35 ` Kalle Valo
1 sibling, 0 replies; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-16 11:51 UTC (permalink / raw)
To: ath10k; +Cc: Patrick CARNEIRO RODRIGUEZ
[-- Attachment #1: Type: text/plain, Size: 3515 bytes --]
I forgot to join the dmesg output, you can see detail in the attached file
Sincerely,
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Vu Hai NGUYEN
Date d'envoi : mercredi 16 avril 2014 13:51
À : ath10k@lists.infradead.org
Cc : Patrick CARNEIRO RODRIGUEZ
Objet : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
Thank you for your response,
I didn't power down my cible to reboot, I just upload new program with new firmware and run it. The problem is when that error appear my console keep print it and I Have no longer access to my system, I can not type another command (dmesg) , then I have to reset my platform. I'll try to get the dmesg and sent you later.
My host platform is using processor Marvell Armada 370 and my module of wifi is Compex WLE900VX.
There's another problem: when I used the firmware version 999.999 some times when I ran my program and change the parameter of configuration, the firmware crash and I got a output dmesg which indicate a strange version of firmware (1.0.0.636 ???) :
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location: 0x00401930
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
and then It reload the firmware 999.999. :
ath10k: firmware 999.999.0.636 booted
You can see the output of my dmesg
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : mardi 15 avril 2014 13:02
À : Vu Hai NGUYEN
Cc : ath10k@lists.infradead.org; Patrick CARNEIRO RODRIGUEZ
Objet : Re: Report Firmware firmware-2.bin_10.1.467.2-1 Error
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> When I load the firmware-2.bin_10.1.467.2-1 I got this error when I
> put my device in mode ACCESS POINT: "PCI express error: irq - 228, Pex
> number: 0, Interrupt Cause Register value: 10" But if I use the
> version 999.999.0.x. I don't have this error.
I wonder if this has something to do with cold reset causing PCI bus
errors? But we need more information to say more. Can you send the full
dmesg output (from the beginning of kernel boot) along with detailed
descriptions of your host platform and what kind qca98xx board you have.
Even better is if you can also send a debug log output using debug mask
value 0x432. More info:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug#Useful_debug_masks
--
Kalle Valo
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 102715 bytes --]
Linux version 3.2.36 (alberix2@nguyen-actiasodielec) (gcc version 4.6.2 (Linaro4
CPU: Marvell PJ4Bv7 Processor [561f5811] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine: Marvell Armada-370
Using UBoot passing parameters structure
>>>>>>>Tag MAC 00:00:00:00:00:00
>>>>>>>Tag MAC 86:48:25:43:50:00
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c1065538, node_mem_map c10a8000
Normal zone: 1024 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 130048 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 130048
Kernel command line: console=ttyS0,115200 panic=1 modeboot=1 vboot=0
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 498596k/498596k available, 25692k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xe0800000 - 0xfa800000 ( 416 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc06e4000 (7024 kB)
.init : 0xc06e4000 - 0xc1002000 (9336 kB)
.data : 0xc1002000 - 0xc106ff48 ( 440 kB)
.bss : 0xc106ff6c - 0xc10a749c ( 222 kB)
NR_IRQS:256
a370_time_init
sched_clock: 32 bits at 600MHz, resolution 1ns, wraps every 7158ms
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: no hardware support available
devtmpfs: initialized
xor: measuring software checksum speed
arm4regs : 1150.000 MB/sec
8regs : 814.400 MB/sec
32regs : 1145.200 MB/sec
xor: using function: arm4regs (1150.000 MB/sec)
NET: Registered protocol family 16
L0 cache Enabled
Speculative Prefetch Disabled
Aurora L2 Cache Enabled
Support IO coherency.
Enable DLB and DRAM write coalescing
CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 512MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
DEVICE_CS0 ....base f2000000, size 32MB
DEVICE_CS1 ....no such
DEVICE_CS2 ....no such
DEVICE_CS3 ....no such
PEX0_MEM ....base e0000000, size 32MB
PEX0_IO ....base f1100000, size 1MB
PEX1_MEM ....base e2000000, size 32MB
PEX1_IO ....base f1200000, size 1MB
INTER_REGS ....base d0000000, size 1MB
DMA_UART ....no such
SPI_CS0 ....base f0000000, size 16MB
SPI_CS1 ....no such
SPI_CS2 ....no such
SPI_CS3 ....no such
SPI_CS4 ....no such
SPI_CS5 ....no such
SPI_CS6 ....no such
SPI_CS7 ....no such
BOOT_ROM_CS ....no such
DEV_BOOTCS ....base f5000000, size 16MB
PMU_SCRATCHPAD ....no such
CRYPT0_ENG ....base c8010000, size 64KB
Marvell Armada370 Board-- RD-88F6710 Soc: MV6710 A1 LE
LSP version: linux-3.2.y-2013_Q1.0p2
Detected Tclk 200000000, SysClk 600000000, FabricClk 600000000
Marvell USB EHCI Host controller #0: d004a600
Marvell USB EHCI Host controller #1: d004a400
pci 0000:00:00.0: [168c:003c] type 0 class 0x000280
pci 0000:00:00.0: reg 10: [mem 0x40000000-0x401fffff 64bit]
pci 0000:00:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
pci 0000:00:00.0: supports D1 D2
pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:00.0: PME# disabled
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
pci 0000:00:00.0: BAR 0: set to [mem 0xe0000000-0xe01fffff 64bit] (PCI address )
pci 0000:00:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
bio: create slab <bio-0> at 0
raid6: int32x1 135 MB/s
raid6: int32x2 210 MB/s
raid6: int32x4 202 MB/s
raid6: int32x8 232 MB/s
raid6: using algorithm int32x8 (232 MB/s)
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource armada370_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
cesadev_init(c06ebfd4)
mvCesaInit: channels=1, session=640, queue=64
Armada XP hwmon thermal sensor initialized.
Initializing Armada-XP CPU power management (WFI)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
SGI XFS with security attributes, large block/inode numbers, no debug enabled
msgmni has been set to 973
async_tx: api initialized (async)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Initializing ths8200_init
Initializing dove_adi9889_init
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor )
mv_xor mv_xor.1: Marvell XOR: ( xor )
mv_xor mv_xor.2: Marvell XOR: ( cpy )
mv_xor mv_xor.3: Marvell XOR: ( fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xd0012000 (irq = 41) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
lkdtm: No crash points registered, enable through debugfs
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 55
ata2: SATA max UDMA/133 irq 55
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.
armada-nand armada-nand.0: Initialize HAL based NFC in 8bit mode with DMA DisabC
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x38 (Micron NAND 1GiB 3,3V 8-bit)
Bad block table found at page 262016, version 0x01
Bad block table found at page 261888, version 0x01
Creating 7 MTD partitions on "armada-nand":
0x000000000000-0x000000400000 : "uboot"
0x000000400000-0x000000800000 : "uboot-env"
0x000000800000-0x000004800000 : "App1"
0x000004800000-0x000008800000 : "App2"
0x000008800000-0x00000c800000 : "nand-config"
0x00000c800000-0x000010800000 : "nand-jdb"
0x000010800000-0x000040000000 : "User"
mv_eth_probe: port_mask=0x2, cpu_mask=0x1
0 - Base 0x00000000 , Size = 0x00000000.
4 - Base 0xf2000000 , Size = 0x00000000.
8 - Base 0xe0000000 , Size = 0x00000000.
9 - Base 0xf1100000 , Size = 0x00000000.
10 - Base 0xe2000000 , Size = 0x00000000.
11 - Base 0xf1200000 , Size = 0x00000000.
12 - Base 0xd0000000 , Size = 0x00000000.
14 - Base 0xf0000000 , Size = 0x00000000.
23 - Base 0xf5000000 , Size = 0x00000000.
25 - Base 0xc8010000 , Size = 0x00000000.
o 2 Giga ports supported
o SKB recycle supported (Enabled)
o NETA acceleration mode 1
o RX Queue support: 8 Queues * 128 Descriptors
o TX Queue support: 8 Queues * 532 Descriptors
o GSO supported
o GRO supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Driver ERROR statistics enabled
o Switch support enabled
o Loading Switch QuarterDeck driver
o Device ID : 0x176
o No. of Ports : 7
o CPU Port : 5
o Disable disconnected Switch Port #4 and force link down
o Setting Switch Port #5 connected to GMAC port for 1000 Full with FC
o Disable disconnected Switch Port #6 and force link down
o Loading network interface(s)
o Port 1 is connected to Linux netdevice
o Using default netconfig string from Kconfig for port 1
net_config_str[1]: 0
o Working in External Switch mode
Port 1: Link-up, Full-duplex, Speed-100Mbps.
giga p=1: mtu=1500, mac=d002be64
o eth0, ifindex = 2, GbE port = 1
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
sky2: driver version 1.30
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.0: Marvell Orion EHCI
ehci_marvell ehci_marvell.0: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.0: irq 45, io base 0xfbb50100
ehci_marvell ehci_marvell.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ata1: SATA link down (SStatus 0 SControl F300)
ehci_marvell ehci_marvell.1: Marvell Orion EHCI
ehci_marvell ehci_marvell.1: new USB bus registered, assigned bus number 2
ehci_marvell ehci_marvell.1: irq 46, io base 0xfbb51100
ehci_marvell ehci_marvell.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
Linux telephony interface: v1.00
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
cpuidle: using governor ladder
cpuidle: using governor menu
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 1-1: new high-speed USB device number 2 using ehci_marvell
cs42l51-codec 0-004a: failed to read I2C
ata2: SATA link down (SStatus 0 SControl F300)
ALSA device list:
No soundcards found.
oprofile: no performance counters
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
rtc-mv rtc-mv: setting system clock to 2014-04-15 06:55:09 UTC (1397544909)
Freeing init memory: 9336K
UBI: attaching mtd4 to ubi0
UBI DBG (pid 669): ubi_attach_mtd_dev: sizeof(struct ubi_scan_leb) 40
UBI DBG (pid 669): ubi_attach_mtd_dev: sizeof(struct ubi_wl_entry) 20
UBI DBG (pid 669): io_init: min_io_size 4096
UBI DBG (pid 669): io_init: max_write_size 4096
UBI DBG (pid 669): io_init: hdrs_min_io_size 4096
UBI DBG (pid 669): io_init: ec_hdr_alsize 4096
UBI DBG (pid 669): io_init: vid_hdr_alsize 4096
UBI DBG (pid 669): io_init: vid_hdr_offset 4096
UBI DBG (pid 669): io_init: vid_hdr_aloffset 4096
UBI DBG (pid 669): io_init: vid_hdr_shift 0
UBI DBG (pid 669): io_init: leb_start 8192
UBI DBG (pid 669): io_init: max_erroneous 16
UBI: physical eraseblock size: 524288 bytes (512 KiB)
UBI: logical eraseblock size: 516096 bytes
UBI: smallest flash I/O unit: 4096
UBI: VID header offset: 4096 (aligned 4096)
UBI: data offset: 8192
UBI DBG (pid 669): ubi_scan: scanning is finished
UBI: max. sequence number: 133
UBI: attached mtd4 to ubi0
UBI: MTD device name: "nand-config"
UBI: MTD device size: 64 MiB
UBI: number of good PEBs: 128
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 105
UBI: total number of reserved PEBs: 23
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 590045203
UBI: background thread "ubi_bgt0d" started, PID 672
UBI: attaching mtd5 to ubi1
UBI DBG (pid 673): ubi_attach_mtd_dev: sizeof(struct ubi_scan_leb) 40
UBI DBG (pid 673): ubi_attach_mtd_dev: sizeof(struct ubi_wl_entry) 20
UBI DBG (pid 673): io_init: min_io_size 4096
UBI DBG (pid 673): io_init: max_write_size 4096
UBI DBG (pid 673): io_init: hdrs_min_io_size 4096
UBI DBG (pid 673): io_init: ec_hdr_alsize 4096
UBI DBG (pid 673): io_init: vid_hdr_alsize 4096
UBI DBG (pid 673): io_init: vid_hdr_offset 4096
UBI DBG (pid 673): io_init: vid_hdr_aloffset 4096
UBI DBG (pid 673): io_init: vid_hdr_shift 0
UBI DBG (pid 673): io_init: leb_start 8192
UBI DBG (pid 673): io_init: max_erroneous 16
UBI: physical eraseblock size: 524288 bytes (512 KiB)
UBI: logical eraseblock size: 516096 bytes
UBI: smallest flash I/O unit: 4096
UBI: VID header offset: 4096 (aligned 4096)
UBI: data offset: 8192
UBI DBG (pid 673): ubi_scan: scanning is finished
UBI: max. sequence number: 132
UBI: attached mtd5 to ubi1
UBI: MTD device name: "nand-jdb"
UBI: MTD device size: 64 MiB
UBI: number of good PEBs: 128
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 105
UBI: total number of reserved PEBs: 23
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 1893155953
UBI: background thread "ubi_bgt1d" started, PID 676
UBI error: ubi_create_volume: volume "config" exists (ID 0)
UBI error: ubi_create_volume: cannot create volume 1, error -17
UBI error: ubi_create_volume: volume "jdb" exists (ID 0)
UBI error: ubi_create_volume: cannot create volume 1, error -17
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "config"
UBIFS: file system size: 4644864 bytes (4536 KiB, 4 MiB, 9 LEBs)
UBIFS: journal size: 3612673 bytes (3528 KiB, 3 MiB, 5 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 219388 bytes (214 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 1, volume 0, name "jdb"
UBIFS: file system size: 4644864 bytes (4536 KiB, 4 MiB, 9 LEBs)
UBIFS: journal size: 3612673 bytes (3528 KiB, 3 MiB, 5 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 219388 bytes (214 KiB)
pool #1: pkt_size=1536, buf_size=1632 - 2048 of 2048 buffers added
Port 0: Link-down
eth0: link up
Port 1: Link-up, Full-duplex, Speed-100Mbps.
Port 2: Link-down
Port 3: Link-down
Port -1: Link-down
eth0: started
Loading modules backported from Linux version v3.13.2-0-gfd82174
Backport generated by backports.git v3.13.2-1-0-gaef13bc
cfg80211: Calling CRDA to update world regulatory domain
ath10k: device supports MSI-X
ath10k_pci 0000:00:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
ath10k_pci 0000:00:00.0: BAR 0: set to [mem 0xe0000000-0xe01fffff 64bit] (PCI a)
ath10k: boot pci_mem 0xe2400000
ath10k: boot chip_id 0x043202ff hw_revision 0x2
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr d24cd000
ath10k: boot ce dest ring id 1 entries 512 base_addr d24d8000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2520000
ath10k: boot ce src ring id 3 entries 32 base_addr d24e8000
ath10k: boot ce src ring id 4 entries 2048 base_addr d24f0000
ath10k: boot ce src ring id 7 entries 2 base_addr d24f7000
ath10k: boot ce dest ring id 7 entries 2 base_addr d24f6000
ath10k: bmi get target info
ath10k: Hardware name qca988x hw2.0 version 0x4100016c
ath10k: found fw version 999.999.0.636
ath10k: found fw timestamp 1381153613
ath10k: found otp image ie (5402 B)
ath10k: found fw image ie (249093 B)
ath10k: using fw api 2
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xd2511ccc length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xd2511ccc length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr c0bae000
ath10k: boot ce dest ring id 1 entries 512 base_addr d1efc000
ath10k: boot ce dest ring id 2 entries 32 base_addr d24a2000
ath10k: boot ce src ring id 3 entries 32 base_addr d2521000
ath10k: boot ce src ring id 4 entries 2048 base_addr d2a50000
ath10k: boot ce src ring id 7 entries 2 base_addr d2a57000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2a56000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xd1ed9d4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xd1ed9d4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath10k: wmi pdev set param 34 value 1
ath10k: wmi pdev set param 10 value 0
ath10k: mac channel [0/19] freq 2412 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [1/19] freq 2417 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [2/19] freq 2422 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [3/19] freq 2427 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [4/19] freq 2432 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [5/19] freq 2437 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [6/19] freq 2442 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [7/19] freq 2447 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [8/19] freq 2452 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [9/19] freq 2457 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [10/19] freq 2462 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [11/19] freq 5180 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 00:03:07:12:34:56
ath10k: wmi vdev id 0x0 set param 33 value 0
ath10k: wmi vdev id 0x0 set param 48 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 44 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ath10k: mac vdev delete 0 (remove interface)
ath10k: WMI vdev delete id 0
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr c0baa000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2496000
ath10k: boot ce dest ring id 2 entries 32 base_addr d255e000
ath10k: boot ce src ring id 3 entries 32 base_addr c0b95000
ath10k: boot ce src ring id 4 entries 2048 base_addr d2820000
ath10k: boot ce src ring id 7 entries 2 base_addr d2827000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2826000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath10k: wmi pdev set param 34 value 1
ath10k: wmi pdev set param 10 value 0
ath10k: mac channel [0/19] freq 2412 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [1/19] freq 2417 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [2/19] freq 2422 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [3/19] freq 2427 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [4/19] freq 2432 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [5/19] freq 2437 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [6/19] freq 2442 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [7/19] freq 2447 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [8/19] freq 2452 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [9/19] freq 2457 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [10/19] freq 2462 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [11/19] freq 5180 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 00:03:07:12:34:56
ath10k: wmi vdev id 0x0 set param 33 value 0
ath10k: wmi vdev id 0x0 set param 48 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 44 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
eth0: stopped
ath10k: mac vdev delete 0 (remove interface)
ath10k: WMI vdev delete id 0
Port 0: Link-down
eth0: link up
Port 1: Link-up, Full-duplex, Speed-100Mbps.
Port 2: Link-down
Port 3: Link-down
Port -1: Link-down
eth0: started
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr c0b9d000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2510000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2823000
ath10k: boot ce src ring id 3 entries 32 base_addr d0478000
ath10k: boot ce src ring id 4 entries 2048 base_addr d29f0000
ath10k: boot ce src ring id 7 entries 2 base_addr d29f7000
ath10k: boot ce dest ring id 7 entries 2 base_addr d29f6000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath10k: wmi pdev set param 34 value 1
ath10k: wmi pdev set param 10 value 0
ath10k: mac channel [0/19] freq 2412 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [1/19] freq 2417 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [2/19] freq 2422 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [3/19] freq 2427 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [4/19] freq 2432 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [5/19] freq 2437 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [6/19] freq 2442 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [7/19] freq 2447 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [8/19] freq 2452 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [9/19] freq 2457 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [10/19] freq 2462 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [11/19] freq 5180 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 00:03:07:12:34:56
ath10k: wmi vdev id 0x0 set param 33 value 0
ath10k: wmi vdev id 0x0 set param 48 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 44 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
mv_eth_tool_get_settings is not supported on eth0
device eth0 entered promiscuous mode
device wlan0 entered promiscuous mode
ath10k: mac monitor 0 start
ath10k: wmi vdev start id 0x0 freq 2412, mode 1, ch_flags: 0x0,max_power: 80
ath10k: WMI_VDEV_START_RESP_EVENTID
ath10k: wmi mgmt vdev up id 0x0 assoc id 0 bssid 00:03:07:12:34:56
br0: port 1(eth0) entering forwarding state
br0: port 1(eth0) entering forwarding state
ath10k: mac vdev delete 0 (remove interface)
ath10k: WMI vdev delete id 0
br0: port 2(wlan0) entering disabled state
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr d29f1000
ath10k: boot ce dest ring id 1 entries 512 base_addr d24da000
ath10k: boot ce dest ring id 2 entries 32 base_addr d293b000
ath10k: boot ce src ring id 3 entries 32 base_addr c0b9d000
ath10k: boot ce src ring id 4 entries 2048 base_addr d27e0000
ath10k: boot ce src ring id 7 entries 2 base_addr d27e7000
ath10k: boot ce dest ring id 7 entries 2 base_addr d27e6000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xc0badd4c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath10k: wmi pdev set param 34 value 1
ath10k: wmi pdev set param 10 value 0
ath10k: mac channel [0/19] freq 2412 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [1/19] freq 2417 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [2/19] freq 2422 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [3/19] freq 2427 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [4/19] freq 2432 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [5/19] freq 2437 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [6/19] freq 2442 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [7/19] freq 2447 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [8/19] freq 2452 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [9/19] freq 2457 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [10/19] freq 2462 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [11/19] freq 5180 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac vdev create 0 (add interface) type 1 subtype 0
ath10k: WMI vdev create: id 0 type 1 subtype 0 macaddr 00:03:07:12:34:56
ath10k: wmi vdev id 0x0 set param 33 value 0
ath10k: wmi vdev id 0x0 set param 48 value 1
ath10k: wmi peer create vdev_id 0 peer_addr 00:03:07:12:34:56
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac monitor 0 stop
ath10k: wmi mgmt vdev down id 0x0
ath10k: wmi vdev stop id 0x0
ath10k: WMI_VDEV_STOPPED_EVENTID
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 44 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: mac config channel 2412 mhz
ath10k: mac monitor 0 start
ath10k: wmi vdev start id 0x0 freq 2412, mode 1, ch_flags: 0x0,max_power: 80
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath10k: WMI_VDEV_START_RESP_EVENTID
ath10k: wmi mgmt vdev up id 0x0 assoc id 0 bssid 00:03:07:12:34:56
ath10k: WMI_TBTTOFFSET_UPDATE_EVENTID
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: WMI_DEBUG_MESG_EVENTID
net_ratelimit: 28 callbacks suppressed
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: wmi start scan
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 1 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_STARTED
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 2412 cmd_flags 1 noise_floor -112 rx_clear_co0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 0 noise_floor 0 rx_clear_count4
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 1 noise_floor -98 rx_clear_cou0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 0 noise_floor 0 rx_clear_count2
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 1 noise_floor -98 rx_clear_cou0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 0 noise_floor 0 rx_clear_count9
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 1 noise_floor -97 rx_clear_cou0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 0 noise_floor 0 rx_clear_count4
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 1 noise_floor -98 rx_clear_cou0
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 2 reason 0 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_COMPLETED
ath10k: SCAN_REASON_COMPLETED
ath10k: wmi start scan
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 1 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_STARTED
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 2412 cmd_flags 1 noise_floor -113 rx_clear_co4
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 0 noise_floor 0 rx_clear_count8
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 1 noise_floor -98 rx_clear_cou1
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 0 noise_floor 0 rx_clear_count1
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 1 noise_floor -98 rx_clear_cou7
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 0 noise_floor 0 rx_clear_count2
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 1 noise_floor -97 rx_clear_cou3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 0 noise_floor 0 rx_clear_count7
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 1 noise_floor -99 rx_clear_cou1
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 2 reason 0 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_COMPLETED
ath10k: SCAN_REASON_COMPLETED
ath10k: wmi start scan
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 1 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_STARTED
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 2412 cmd_flags 1 noise_floor -112 rx_clear_co3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 0 noise_floor 0 rx_clear_count0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 1 noise_floor -98 rx_clear_cou3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 0 noise_floor 0 rx_clear_count5
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 1 noise_floor -98 rx_clear_cou9
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 0 noise_floor 0 rx_clear_count9
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 1 noise_floor -98 rx_clear_cou7
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 0 noise_floor 0 rx_clear_count3
eth0: no IPv6 routers present
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 1 noise_floor -99 rx_clear_cou1
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 2 reason 0 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_COMPLETED
ath10k: SCAN_REASON_COMPLETED
ath10k: wmi start scan
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 1 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_STARTED
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 2412 cmd_flags 1 noise_floor -113 rx_clear_co7
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 0 noise_floor 0 rx_clear_count0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 1 noise_floor -98 rx_clear_cou7
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 0 noise_floor 0 rx_clear_count0
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 1 noise_floor -98 rx_clear_cou7
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 0 noise_floor 0 rx_clear_count3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 1 noise_floor -98 rx_clear_cou3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 0 noise_floor 0 rx_clear_count3
net_ratelimit: 40 callbacks suppressed
ath10k: could not get mac80211 beacon
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 1 noise_floor -98 rx_clear_cou5
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 2 reason 0 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_COMPLETED
ath10k: SCAN_REASON_COMPLETED
ath10k: wmi start scan
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 1 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_STARTED
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 2412 cmd_flags 1 noise_floor -113 rx_clear_co5
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 0 noise_floor 0 rx_clear_count2
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5260 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5260 cmd_flags 1 noise_floor -98 rx_clear_cou7
br0: no IPv6 routers present
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 0 noise_floor 0 rx_clear_count7
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5280 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5280 cmd_flags 1 noise_floor -98 rx_clear_cou1
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 0 noise_floor 0 rx_clear_count7
ath10k: could not get mac80211 beacon
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5300 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5300 cmd_flags 1 noise_floor -98 rx_clear_cou9
ath10k: could not get mac80211 beacon
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 8 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_FOREIGN_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 0 noise_floor 0 rx_clear_count1
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 4 reason 4 freq 5320 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_BSS_CHANNEL
ath10k: chan info err_code 0 freq 5320 cmd_flags 1 noise_floor -98 rx_clear_cou3
ath10k: WMI_SCAN_EVENTID
ath10k: scan event type 2 reason 0 freq 2412 req_id 40961 scan_id 40960 vdev_id0
ath10k: SCAN_EVENT_COMPLETED
ath10k: SCAN_REASON_COMPLETED
ath10k: WMI_DEBUG_MESG_EVENTID
ath10k: wmi peer delete vdev_id 0 peer_addr 00:03:07:12:34:56
ath10k: mac vdev delete 0 (remove interface)
ath10k: WMI vdev delete id 0
ath10k: mac monitor 0 stop
ath10k: wmi mgmt vdev down id 0x0
ath10k: wmi vdev stop id 0x0
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location: 0x00401930
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
net_ratelimit: 30 callbacks suppressed
ath10k: Monitor_down sync failed: -110
ath10k: Unable to stop monitor mode
ieee80211 phy0: Hardware restart was requested
br0: port 2(wlan0) entering disabled state
ath10k: MSI-X didn't succeed (-1), trying MSI
ath10k: MSI didn't succeed (-1), trying legacy INTR
ath10k: legacy interrupt handling
ath10k: boot ce src ring id 0 entries 16 base_addr d2b77000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2b54000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2491000
ath10k: boot ce src ring id 3 entries 32 base_addr d2b76000
ath10k: boot ce src ring id 4 entries 2048 base_addr d2ba0000
ath10k: boot ce src ring id 7 entries 2 base_addr d2ba7000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2ba6000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe2075038 length 5402
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe2075038 length 5400
ath10k: bmi lz data buffer 0xd0145e7c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe207655c length 249093
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe207655c length 249092
ath10k: bmi lz data buffer 0xd0145e7c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: UART prints disabled
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 2047
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: wmi event service ready sw_ver 0x01000000 sw_ver1 0x0000027c abi_ver 3 2
ath10k: boot wmi ready
ath10k: firmware 999.999.0.636 booted
ath10k: wmi init
ath10k: wmi event ready sw_version 16777216 abi_version 3 mac_addr 00:03:07:12:0
ath10k: htt target version 2.1
ath10k: wmi pdev set param 34 value 1
ath10k: wmi pdev set param 10 value 0
ath10k: mac channel [0/19] freq 2412 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [1/19] freq 2417 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [2/19] freq 2422 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [3/19] freq 2427 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [4/19] freq 2432 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [5/19] freq 2437 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [6/19] freq 2442 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [7/19] freq 2447 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [8/19] freq 2452 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [9/19] freq 2457 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [10/19] freq 2462 maxpower 80 regpower 80 antenna 6 mode 1
ath10k: mac channel [11/19] freq 5180 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac config channel 2412 mhz
ath10k: device successfully recovered
# dmesg | tail
ath10k: mac channel [12/19] freq 5200 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [13/19] freq 5220 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [14/19] freq 5240 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [15/19] freq 5260 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [16/19] freq 5280 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [17/19] freq 5300 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: mac channel [18/19] freq 5320 maxpower 80 regpower 80 antenna 6 mode 0
ath10k: wmi pdev regdomain rd 3a rd2g 3a rd5g 3a ctl2g 10 ctl5g 10
ath10k: mac config channel 2412 mhz
ath10k: device successfully recovered
#
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
2014-04-16 11:51 ` Vu Hai NGUYEN
@ 2014-04-24 6:35 ` Kalle Valo
2014-04-24 9:03 ` RE : " Vu Hai NGUYEN
1 sibling, 1 reply; 36+ messages in thread
From: Kalle Valo @ 2014-04-24 6:35 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> There's another problem: when I used the firmware version 999.999 some
> times when I ran my program and change the parameter of configuration,
> the firmware crash and I got a output dmesg which indicate a strange
> version of firmware (1.0.0.636 ???) :
>
> ath10k: firmware crashed!
> ath10k: hardware name qca988x hw2.0 version 0x4100016c
> ath10k: firmware version: 1.0.0.636
> ath10k: target register Dump Location: 0x00401930
> ath10k: target Register Dump
> ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
> ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
> ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
> ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
>
> and then It reload the firmware 999.999. :
>
> ath10k: firmware 999.999.0.636 booted
>
> You can see the output of my dmesg
The patch below should fix it. I suspect you don't have that.
commit 5ba88b395cb447af756d12411456024d65a07814
Author: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Date: Tue Jan 21 17:21:21 2014 +0800
ath10k: fix the printing of 10.x FW version when FW crashed
10.x FW has no structure member sw_version_1. Thus,
both fw_version_release and fw_version_build are not
available. The provided fw_version_major is also wrong.
Fix this by using the fw_version from struct wiphy.
Signed-off-by: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-24 6:35 ` Kalle Valo
@ 2014-04-24 9:03 ` Vu Hai NGUYEN
2014-04-24 9:41 ` Michal Kazior
0 siblings, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-24 9:03 UTC (permalink / raw)
To: Kalle Valo; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
Thank you for your response, the problem is solved when I download the latest version of backport (3.15) and compile ath10k with it (last time my version is 3.13 and as you said, It might not include the patch).
Now I can load the firmware 10.1.467.2-1 but I get new problem too.
Does ath10k support all the command of "iw"?
For example I set up mode access point and tried to change the txpower by the command: "iw wlan0 set txpower fixed 1200" (same thing as "iwconfig wlan0 txpower 12dBm" , right?)
The output of "iwconfig" is:
wlan0 IEEE 802.11abgn Mode:Master Tx-Power=12 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
And output of "dmesg":
ath10k: mac config power 12
ath10k: wmi pdev set param 3 value 24
ath10k: wmi pdev set param 4 value 24
It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
Same thing when I do with the command set bit rates: "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4"
Out put of dmesg:
ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
ath10k: wmi vdev id 0x0 set param 27 value 4
ath10k: wmi vdev id 0x0 set param 34 value 1
ath10k: wmi vdev id 0x0 set param 28 value 0
ath10k: wmi event debug mesg len 16
But the out put of " iw wlan0 station dump" did not show any change when I varied the bit rate of my access point too.
Do you guys have any suggestion about it?
Thanks in advance :)
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Kalle Valo [kvalo@qca.qualcomm.com]
Date d'envoi : jeudi 24 avril 2014 08:35
À : Vu Hai NGUYEN
Cc : ath10k@lists.infradead.org; Patrick CARNEIRO RODRIGUEZ
Objet : Re: RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> writes:
> There's another problem: when I used the firmware version 999.999 some
> times when I ran my program and change the parameter of configuration,
> the firmware crash and I got a output dmesg which indicate a strange
> version of firmware (1.0.0.636 ???) :
>
> ath10k: firmware crashed!
> ath10k: hardware name qca988x hw2.0 version 0x4100016c
> ath10k: firmware version: 1.0.0.636
> ath10k: target register Dump Location: 0x00401930
> ath10k: target Register Dump
> ath10k: [00]: 0x4100016C 0x00000000 0x0098E3A9 0x00000000
> ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098E3A9
> ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
> ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
>
> and then It reload the firmware 999.999. :
>
> ath10k: firmware 999.999.0.636 booted
>
> You can see the output of my dmesg
The patch below should fix it. I suspect you don't have that.
commit 5ba88b395cb447af756d12411456024d65a07814
Author: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Date: Tue Jan 21 17:21:21 2014 +0800
ath10k: fix the printing of 10.x FW version when FW crashed
10.x FW has no structure member sw_version_1. Thus,
both fw_version_release and fw_version_build are not
available. The provided fw_version_major is also wrong.
Fix this by using the fw_version from struct wiphy.
Signed-off-by: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-24 9:03 ` RE : " Vu Hai NGUYEN
@ 2014-04-24 9:41 ` Michal Kazior
2014-04-24 10:18 ` Yeoh Chun-Yeow
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
0 siblings, 2 replies; 36+ messages in thread
From: Michal Kazior @ 2014-04-24 9:41 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, Kalle Valo, ath10k
On 24 April 2014 11:03, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> Thank you for your response, the problem is solved when I download the latest version of backport (3.15) and compile ath10k with it (last time my version is 3.13 and as you said, It might not include the patch).
> Now I can load the firmware 10.1.467.2-1 but I get new problem too.
> Does ath10k support all the command of "iw"?
> For example I set up mode access point and tried to change the txpower by the command: "iw wlan0 set txpower fixed 1200" (same thing as "iwconfig wlan0 txpower 12dBm" , right?)
> The output of "iwconfig" is:
> wlan0 IEEE 802.11abgn Mode:Master Tx-Power=12 dBm
> Retry short limit:7 RTS thr:off Fragment thr:off
> Power Management:on
>
> And output of "dmesg":
> ath10k: mac config power 12
> ath10k: wmi pdev set param 3 value 24
> ath10k: wmi pdev set param 4 value 24
>
> It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
This works for me (latest github.com/kvalo/ath/master with 467.2).
I can see "signal" values change in iw station dump on the connected
client when I set different txpower values on ath10k AP.
> Same thing when I do with the command set bit rates: "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4"
>
> Out put of dmesg:
> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
> ath10k: wmi vdev id 0x0 set param 27 value 4
> ath10k: wmi vdev id 0x0 set param 34 value 1
> ath10k: wmi vdev id 0x0 set param 28 value 0
> ath10k: wmi event debug mesg len 16
>
> But the out put of " iw wlan0 station dump" did not show any change when I varied the bit rate of my access point too.
Again, this works for me.
To be clear - ath10k is incapable of reporting "tx bitrate" (it always
reports 6mbps). If you want to verify if the bitrate mask works you
must check "rx bitrate" on the other side, i.e. on the connected
client.
Or just use a separate sniffer and see if AP is sends frames with
different txpower/bitrate values.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-24 9:41 ` Michal Kazior
@ 2014-04-24 10:18 ` Yeoh Chun-Yeow
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
1 sibling, 0 replies; 36+ messages in thread
From: Yeoh Chun-Yeow @ 2014-04-24 10:18 UTC (permalink / raw)
To: Michal Kazior
Cc: Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ, Kalle Valo, ath10k
> To be clear - ath10k is incapable of reporting "tx bitrate" (it always
> reports 6mbps). If you want to verify if the bitrate mask works you
> must check "rx bitrate" on the other side, i.e. on the connected
> client.
>
> Or just use a separate sniffer and see if AP is sends frames with
> different txpower/bitrate values.
>
For TxRate, another option would be looking at
"/sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats".
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
2014-04-24 9:41 ` Michal Kazior
2014-04-24 10:18 ` Yeoh Chun-Yeow
@ 2014-04-30 12:39 ` Vu Hai NGUYEN
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
1 sibling, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-04-30 12:39 UTC (permalink / raw)
To: Michal Kazior; +Cc: Patrick CARNEIRO RODRIGUEZ, Kalle Valo, ath10k
[-- Attachment #1: Type: text/plain, Size: 10216 bytes --]
>> It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the >>station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
>This works for me (latest github.com/kvalo/ath/master with 467.2).
>I can see "signal" values change in iw station dump on the connected
>client when I set different txpower values on ath10k AP.
I replace the ath from backports with the one from master tree of ath, but it is worse.
When I set a channel from 52 (or higher) for AP mode using the version of backports, I get a backtrace message output and then my wlan0 become ready:
br0: port 2(wlan0) entering disabled state
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: interface------------[ cut here ]------------
state UNINITIALWARNING: at /home/alberix2/Desktop/Wilinks_ath10k/ACCESS_POINT_A
PPLI/Source/Driver_ath10k/backports-3.15-rc1-1/net/wireless/nl80211.c:5824 nl802
11_start_radar_detection+0xf8/0x16c [cfg80211]()
IZED->COUNTRY_UPModules linked in:DATE
wlan0: int ath10k_pci(O)erface state COU ath10k_core(O)NTRY_UPDATE->DFS ath(O)
wlan0: DFS-CAC mac80211(O)-START freq=5260 cfg80211(O) chan=52 sec_cha compat(O)
n=0
arc4 ubifs ubi [last unloaded: compat]
Backtrace:
[<c0011938>] (dump_backtrace+0x0/0x118) from [<c050205c>] (dump_stack+0x18/0x20)
r6:bf49a62b r5:000016c0 r4:00000000 r3:c10b27ac
[<c0502044>] (dump_stack+0x0/0x20) from [<c0066c38>] (warn_slowpath_common+0x54/
0x70)
[<c0066be4>] (warn_slowpath_common+0x0/0x70) from [<c0066c78>] (warn_slowpath_nu
ll+0x24/0x2c)
r8:00000000 r7:00000000 r6:d2f9f000 r5:d2aa0000 r4:d2f9f3c8
r3:00000009
[<c0066c54>] (warn_slowpath_null+0x0/0x2c) from [<bf45eae8>] (nl80211_start_rada
r_detection+0xf8/0x16c [cfg80211])
[<bf45e9f0>] (nl80211_start_radar_detection+0x0/0x16c [cfg80211]) from [<c045348
8>] (genl_rcv_msg+0x1b4/0x1f4)
[<c04532d4>] (genl_rcv_msg+0x0/0x1f4) from [<c0452904>] (netlink_rcv_skb+0x58/0x
b8)
[<c04528ac>] (netlink_rcv_skb+0x0/0xb8) from [<c04532c4>] (genl_rcv+0x20/0x30)
r6:c082f600 r5:d2a7d0e0 r4:d2a7d0e0 r3:c04532a4
[<c04532a4>] (genl_rcv+0x0/0x30) from [<c04522d0>] (netlink_unicast+0x224/0x2c4)
r4:d0074400 r3:c04532a4
[<c04520ac>] (netlink_unicast+0x0/0x2c4) from [<c04526a4>] (netlink_sendmsg+0x29
0/0x320)
[<c0452414>] (netlink_sendmsg+0x0/0x320) from [<c0428eac>] (sock_sendmsg+0x98/0x
b4)
[<c0428e14>] (sock_sendmsg+0x0/0xb4) from [<c0429150>] (__sys_sendmsg+0x1d0/0x26
c)
r4:d281bf64
[<c0428f80>] (__sys_sendmsg+0x0/0x26c) from [<c042ab30>] (sys_sendmsg+0x44/0x68)
[<c042aaec>] (sys_sendmsg+0x0/0x68) from [<c000ddc0>] (ret_fast_syscall+0x0/0x30
)
r6:0012d850 r5:0012d888 r4:400c8900
---[ end trace c03fd18534c1267a ]---
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
br0: port 2(wlan0) entering forwarding state
br0: port 2(wlan0) entering forwarding state
But with the version from ath master tree, I always get wlan0: link is not ready (and there is no backtrace msg).
And in both versions, the firmware usually crashed when I set a channel lower than 52 (I don't get backtrace msg in these cases):
wlan0: AP-ENABLED
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 10.1.467.2-1
ath10k: target register Dump Location: 0x0040AAA4
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x000015B3 0x0099F306 0x00955B31
ath10k: [04]: 0x0099F306 0x00060530 0x00000005 0x00000000
ath10k: [08]: 0x009B8164 0x004118C4 0x0043DD84 0x00400000
ath10k: [12]: 0x00000009 0xFFFFFFFF 0x0095808C 0x009580A2
ath10k: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
ath10k: [20]: 0x4099F306 0x0040ABB4 0x00955A00 0x00000003
ath10k: [24]: 0x809995A1 0x0040AC14 0x0040ACB4 0xC099F306
ath10k: [28]: 0x80999400 0x0040AC44 0x004343F0 0x0040ACCC
ath10k: [32]: 0x8098CE0E 0x0040AC64 0x004343F0 0x0040ACCC
ath10k: [36]: 0x809912AC 0x0040AC84 0x004343F0 0x0040ACCC
ath10k: [40]: 0x8099147A 0x0040ACA4 0x0041ED48 0x00434488
ath10k: [44]: 0x80991661 0x0040AD24 0x00000000 0x0042F2A0
ath10k: [48]: 0x8099081C 0x0040AD84 0x00434488 0x0042F1CC
ath10k: [52]: 0x809909D0 0x0040ADA4 0x00000000 0x0042D704
ath10k: [56]: 0x809968F1 0x0040AEC4 0x0041ED48 0x00000000
ath10k: suspend timed out - target pause event never came
ieee80211 phy0: Hardware restart was requested
ath10k: device successfully recovered
There is an ouput of my dmesg in the attached file if someone is interested in :D
One more question: The default country for regulatory domain of ath is US?
I found that it was defined in file "regd.c" and that's why even I set my country to FR ("iw reg set FR") I was not able to set up the channel 12 and 13. (Marked as disabled in output of "iw list" so I replace CTRY_UNITED_STATES with CTRY_FRANCE and then I can get the channel 12 and 13 worked. Is this legal?
@ Chun-Yeow:
>For TxRate, another option would be looking at
>"/sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats".
When I "cat" that file there is nothing appear (it looks like empty) (But I can view other information from others files, such as: simulate_fw_crash, fw_dbglog, htt_stats_mask, wmi_services). Do you have any idea? :D
Thank you all of you for your support
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Michal Kazior [michal.kazior@tieto.com]
Date d'envoi : jeudi 24 avril 2014 11:41
À : Vu Hai NGUYEN
Cc : Kalle Valo; Patrick CARNEIRO RODRIGUEZ; ath10k@lists.infradead.org
Objet : Re: RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
On 24 April 2014 11:03, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> Thank you for your response, the problem is solved when I download the latest version of backport (3.15) and compile ath10k with it (last time my version is 3.13 and as you said, It might not include the patch).
> Now I can load the firmware 10.1.467.2-1 but I get new problem too.
> Does ath10k support all the command of "iw"?
> For example I set up mode access point and tried to change the txpower by the command: "iw wlan0 set txpower fixed 1200" (same thing as "iwconfig wlan0 txpower 12dBm" , right?)
> The output of "iwconfig" is:
> wlan0 IEEE 802.11abgn Mode:Master Tx-Power=12 dBm
> Retry short limit:7 RTS thr:off Fragment thr:off
> Power Management:on
>
> And output of "dmesg":
> ath10k: mac config power 12
> ath10k: wmi pdev set param 3 value 24
> ath10k: wmi pdev set param 4 value 24
>
> It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
This works for me (latest github.com/kvalo/ath/master with 467.2).
I can see "signal" values change in iw station dump on the connected
client when I set different txpower values on ath10k AP.
> Same thing when I do with the command set bit rates: "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4"
>
> Out put of dmesg:
> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
> ath10k: wmi vdev id 0x0 set param 27 value 4
> ath10k: wmi vdev id 0x0 set param 34 value 1
> ath10k: wmi vdev id 0x0 set param 28 value 0
> ath10k: wmi event debug mesg len 16
>
> But the out put of " iw wlan0 station dump" did not show any change when I varied the bit rate of my access point too.
Again, this works for me.
To be clear - ath10k is incapable of reporting "tx bitrate" (it always
reports 6mbps). If you want to verify if the bitrate mask works you
must check "rx bitrate" on the other side, i.e. on the connected
client.
Or just use a separate sniffer and see if AP is sends frames with
different txpower/bitrate values.
Michał
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 127056 bytes --]
Linux version 3.2.36 (alberix2@nguyen-actiasodielec) (gcc version 4.6.2 (Linaro
GCC branch-4.6.2. Marvell GCC 201201-883.01c949de) ) #157 Wed Apr 30 12:47:13 CE
ST 2014
CPU: Marvell PJ4Bv7 Processor [561f5811] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine: Marvell Armada-370
Using UBoot passing parameters structure
>>>>>>>Tag MAC 00:00:00:00:00:00
>>>>>>>Tag MAC 86:48:25:43:50:00
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c111a7bc, node_mem_map c1184000
Normal zone: 1024 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 130048 pages, LIFO batch:31
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 130048
Kernel command line: console=ttyS0,115200 panic=1 modeboot=2 vboot=0
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 497716k/497716k available, 26572k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xe0800000 - 0xfa800000 ( 416 MB)
lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc0772000 (7592 kB)
.init : 0xc0772000 - 0xc10a8000 (9432 kB)
.data : 0xc10a8000 - 0xc1127f38 ( 512 kB)
.bss : 0xc1127f5c - 0xc11837ac ( 367 kB)
NR_IRQS:256
a370_time_init
sched_clock: 32 bits at 600MHz, resolution 1ns, wraps every 7158ms
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: no hardware support available
devtmpfs: initialized
xor: measuring software checksum speed
arm4regs : 1150.400 MB/sec
8regs : 814.000 MB/sec
32regs : 1145.200 MB/sec
xor: using function: arm4regs (1150.400 MB/sec)
NET: Registered protocol family 16
L0 cache Enabled
Speculative Prefetch Disabled
Aurora L2 Cache Enabled
Support IO coherency.
Enable DLB and DRAM write coalescing
CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 512MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
DEVICE_CS0 ....base f2000000, size 32MB
DEVICE_CS1 ....no such
DEVICE_CS2 ....no such
DEVICE_CS3 ....no such
PEX0_MEM ....base e0000000, size 32MB
PEX0_IO ....base f1100000, size 1MB
PEX1_MEM ....base e2000000, size 32MB
PEX1_IO ....base f1200000, size 1MB
INTER_REGS ....base d0000000, size 1MB
DMA_UART ....no such
SPI_CS0 ....base f0000000, size 16MB
SPI_CS1 ....no such
SPI_CS2 ....no such
SPI_CS3 ....no such
SPI_CS4 ....no such
SPI_CS5 ....no such
SPI_CS6 ....no such
SPI_CS7 ....no such
BOOT_ROM_CS ....no such
DEV_BOOTCS ....base f5000000, size 16MB
PMU_SCRATCHPAD ....no such
CRYPT0_ENG ....base c8010000, size 64KB
Marvell Armada370 Board-- RD-88F6710 Soc: MV6710 A1 LE
LSP version: linux-3.2.y-2013_Q1.0p2
Detected Tclk 200000000, SysClk 600000000, FabricClk 600000000
Marvell USB EHCI Host controller #0: d004d600
Marvell USB EHCI Host controller #1: d004d400
pci 0000:00:00.0: [168c:003c] type 0 class 0x000280
pci 0000:00:00.0: reg 10: [mem 0x40000000-0x401fffff 64bit]
pci 0000:00:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
pci 0000:00:00.0: supports D1 D2
pci 0000:00:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:00:00.0: PME# disabled
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
pci 0000:00:00.0: BAR 0: set to [mem 0xe0000000-0xe01fffff 64bit] (PCI address [
0xe0000000-0xe01fffff])
pci 0000:00:00.0: BAR 6: assigned [mem 0xe0200000-0xe020ffff pref]
bio: create slab <bio-0> at 0
raid6: int32x1 135 MB/s
raid6: int32x2 210 MB/s
raid6: int32x4 202 MB/s
raid6: int32x8 232 MB/s
raid6: using algorithm int32x8 (232 MB/s)
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource armada370_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 32 bytes, default 32
cesadev_init(c077a004)
mvCesaInit: channels=1, session=640, queue=64
Armada XP hwmon thermal sensor initialized.
Initializing Armada-XP CPU power management (WFI)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
SGI XFS with security attributes, large block/inode numbers, no debug enabled
msgmni has been set to 972
async_tx: api initialized (async)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Initializing ths8200_init
Initializing dove_adi9889_init
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor )
mv_xor mv_xor.1: Marvell XOR: ( xor )
mv_xor mv_xor.2: Marvell XOR: ( cpy )
mv_xor mv_xor.3: Marvell XOR: ( fill cpy )
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xd0012000 (irq = 41) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
lkdtm: No crash points registered, enable through debugfs
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 55
ata2: SATA max UDMA/133 irq 55
mvSFlashInit ERROR: Unknown SPI flash device!
ERROR: sflash_probe - Failed to initialize the SFlash.
armada-nand armada-nand.0: Initialize HAL based NFC in 8bit mode with DMA Disabl
ed using BCH 4bit ECC
NAND device: Manufacturer ID: 0x2c, Chip ID: 0x38 (Micron NAND 1GiB 3,3V 8-bit)
Bad block table found at page 262016, version 0x01
Bad block table found at page 261888, version 0x01
Creating 7 MTD partitions on "armada-nand":
0x000000000000-0x000000400000 : "uboot"
0x000000400000-0x000000800000 : "uboot-env"
0x000000800000-0x000004800000 : "App1"
0x000004800000-0x000008800000 : "App2"
0x000008800000-0x00000c800000 : "nand-config"
0x00000c800000-0x000010800000 : "nand-jdb"
0x000010800000-0x000040000000 : "User"
mv_eth_probe: port_mask=0x2, cpu_mask=0x1
0 - Base 0x00000000 , Size = 0x00000000.
4 - Base 0xf2000000 , Size = 0x00000000.
8 - Base 0xe0000000 , Size = 0x00000000.
9 - Base 0xf1100000 , Size = 0x00000000.
10 - Base 0xe2000000 , Size = 0x00000000.
11 - Base 0xf1200000 , Size = 0x00000000.
12 - Base 0xd0000000 , Size = 0x00000000.
14 - Base 0xf0000000 , Size = 0x00000000.
23 - Base 0xf5000000 , Size = 0x00000000.
25 - Base 0xc8010000 , Size = 0x00000000.
o 2 Giga ports supported
o SKB recycle supported (Enabled)
o NETA acceleration mode 1
o RX Queue support: 8 Queues * 128 Descriptors
o TX Queue support: 8 Queues * 532 Descriptors
o GSO supported
o GRO supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Driver ERROR statistics enabled
o Switch support enabled
o Loading Switch QuarterDeck driver
o Device ID : 0x176
o No. of Ports : 7
o CPU Port : 5
o Disable disconnected Switch Port #4 and force link down
o Setting Switch Port #5 connected to GMAC port for 1000 Full with FC
o Disable disconnected Switch Port #6 and force link down
o Loading network interface(s)
o Port 1 is connected to Linux netdevice
o Using default netconfig string from Kconfig for port 1
net_config_str[1]: 0
o Working in External Switch mode
Port 1: Link-up, Full-duplex, Speed-100Mbps.
giga p=1: mtu=1500, mac=d002be64
o eth0, ifindex = 2, GbE port = 1
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
sky2: driver version 1.30
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.0: Marvell Orion EHCI
ehci_marvell ehci_marvell.0: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.0: irq 45, io base 0xfbb50100
ata1: SATA link down (SStatus 0 SControl F300)
ehci_marvell ehci_marvell.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ehci_marvell ehci_marvell.1: Marvell Orion EHCI
ehci_marvell ehci_marvell.1: new USB bus registered, assigned bus number 2
ehci_marvell ehci_marvell.1: irq 46, io base 0xfbb51100
ehci_marvell ehci_marvell.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mousedev: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
Linux telephony interface: v1.00
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
cpuidle: using governor ladder
cpuidle: using governor menu
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usb 1-1: new high-speed USB device number 2 using ehci_marvell
ata2: SATA link down (SStatus 0 SControl F300)
cs42l51-codec 0-004a: failed to read I2C
ALSA device list:
No soundcards found.
oprofile: no performance counters
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
rtc-mv rtc-mv: setting system clock to 2014-04-28 16:02:19 UTC (1398700939)
Freeing init memory: 9432K
UBI: attaching mtd4 to ubi0
UBI DBG (pid 670): ubi_attach_mtd_dev: sizeof(struct ubi_scan_leb) 40
UBI DBG (pid 670): ubi_attach_mtd_dev: sizeof(struct ubi_wl_entry) 20
UBI DBG (pid 670): io_init: min_io_size 4096
UBI DBG (pid 670): io_init: max_write_size 4096
UBI DBG (pid 670): io_init: hdrs_min_io_size 4096
UBI DBG (pid 670): io_init: ec_hdr_alsize 4096
UBI DBG (pid 670): io_init: vid_hdr_alsize 4096
UBI DBG (pid 670): io_init: vid_hdr_offset 4096
UBI DBG (pid 670): io_init: vid_hdr_aloffset 4096
UBI DBG (pid 670): io_init: vid_hdr_shift 0
UBI DBG (pid 670): io_init: leb_start 8192
UBI DBG (pid 670): io_init: max_erroneous 16
UBI: physical eraseblock size: 524288 bytes (512 KiB)
UBI: logical eraseblock size: 516096 bytes
UBI: smallest flash I/O unit: 4096
UBI: VID header offset: 4096 (aligned 4096)
UBI: data offset: 8192
UBI DBG (pid 670): ubi_scan: scanning is finished
UBI: max. sequence number: 675
UBI: attached mtd4 to ubi0
UBI: MTD device name: "nand-config"
UBI: MTD device size: 64 MiB
UBI: number of good PEBs: 128
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 105
UBI: total number of reserved PEBs: 23
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 6/5
UBI: image sequence number: 590045203
UBI: background thread "ubi_bgt0d" started, PID 673
UBI: attaching mtd5 to ubi1
UBI DBG (pid 674): ubi_attach_mtd_dev: sizeof(struct ubi_scan_leb) 40
UBI DBG (pid 674): ubi_attach_mtd_dev: sizeof(struct ubi_wl_entry) 20
UBI DBG (pid 674): io_init: min_io_size 4096
UBI DBG (pid 674): io_init: max_write_size 4096
UBI DBG (pid 674): io_init: hdrs_min_io_size 4096
UBI DBG (pid 674): io_init: ec_hdr_alsize 4096
UBI DBG (pid 674): io_init: vid_hdr_alsize 4096
UBI DBG (pid 674): io_init: vid_hdr_offset 4096
UBI DBG (pid 674): io_init: vid_hdr_aloffset 4096
UBI DBG (pid 674): io_init: vid_hdr_shift 0
UBI DBG (pid 674): io_init: leb_start 8192
UBI DBG (pid 674): io_init: max_erroneous 16
UBI: physical eraseblock size: 524288 bytes (512 KiB)
UBI: logical eraseblock size: 516096 bytes
UBI: smallest flash I/O unit: 4096
UBI: VID header offset: 4096 (aligned 4096)
UBI: data offset: 8192
UBI DBG (pid 674): ubi_scan: scanning is finished
UBI: max. sequence number: 715
UBI: attached mtd5 to ubi1
UBI: MTD device name: "nand-jdb"
UBI: MTD device size: 64 MiB
UBI: number of good PEBs: 128
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 105
UBI: total number of reserved PEBs: 23
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 7/5
UBI: image sequence number: 1893155953
UBI: background thread "ubi_bgt1d" started, PID 677
UBI error: ubi_create_volume: volume "config" exists (ID 0)
UBI error: ubi_create_volume: cannot create volume 1, error -17
UBI error: ubi_create_volume: volume "jdb" exists (ID 0)
UBI error: ubi_create_volume: cannot create volume 1, error -17
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "config"
UBIFS: file system size: 4644864 bytes (4536 KiB, 4 MiB, 9 LEBs)
UBIFS: journal size: 3612673 bytes (3528 KiB, 3 MiB, 5 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 219388 bytes (214 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 1, volume 0, name "jdb"
UBIFS: file system size: 4644864 bytes (4536 KiB, 4 MiB, 9 LEBs)
UBIFS: journal size: 3612673 bytes (3528 KiB, 3 MiB, 5 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 219388 bytes (214 KiB)
pool #1: pkt_size=1536, buf_size=1632 - 2048 of 2048 buffers added
Port 0: Link-down
eth0: link up
Port 1: Link-up, Full-duplex, Speed-100Mbps.
Port 2: Link-down
Port 3: Link-down
Port -1: Link-down
eth0: started
Loading modules backported from Linux version v3.15-rc1-0-gc9eaa44
Backport generated by backports.git v3.15-rc1-1-0-g2a25483
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
cfg80211: DFS Master region: unset
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (
dfs_cac_time)
cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm), (N/A)
cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm), (N/A)
cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
ath10k: device supports MSI-X
ath10k_pci 0000:00:00.0: BAR 0: assigned [mem 0xe0000000-0xe01fffff 64bit]
ath10k_pci 0000:00:00.0: BAR 0: set to [mem 0xe0000000-0xe01fffff 64bit] (PCI ad
dress [0xe0000000-0xe01fffff])
ath10k: boot pci_mem 0xe2400000
ath10k: boot chip_id 0x043202ff hw_revision 0x2
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr d26ca000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2858000
ath10k: boot ce dest ring id 2 entries 32 base_addr d26c7000
ath10k: boot ce src ring id 3 entries 32 base_addr d268d000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2920000
ath10k: boot ce src ring id 7 entries 2 base_addr d292f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d292e000
ath10k: pci irq legacy
ath10k: bmi get target info
ath10k: Hardware name qca988x hw2.0 version 0x4100016c
ath10k: found fw version 10.1.467.2-1
ath10k: found fw timestamp 1391440175
ath10k: found otp image ie (6917 B)
ath10k: found fw image ie (190250 B)
ath10k: found firmware features ie (1 B)
ath10k: Enabling feature bit: 1
ath10k: Enabling feature bit: 2
ath10k: features
00000000: 06 00 00 00 ....
ath10k: using fw api 2
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd2751cbc length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd2751cbc length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12de0000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: qca988x hw2.0 (0x4100016c) fw 10.1.467.2-1 api 2 htt 2.1
ath10k: boot suspend complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00001000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000804
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x37
ath: Country alpha2 being used: FR
ath: Regpair used: 0x37
Debug PCR pour etre sur qu'on passe bien ici
cfg80211: Calling CRDA for country: FR
cfg80211: Regulatory domain changed to country: FR
cfg80211: DFS Master region: ETSI
cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (
dfs_cac_time)
cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
cfg80211: (5490000 KHz - 5710000 KHz @ 80000 KHz), (N/A, 2700 mBm), (0 s)
cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr c09ae000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2d3a000
ath10k: boot ce dest ring id 2 entries 32 base_addr d269b000
ath10k: boot ce src ring id 3 entries 32 base_addr c09c1000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2d50000
ath10k: boot ce src ring id 7 entries 2 base_addr d2d5f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2d5e000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd20edd3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd20edd3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12bd0000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz flags 0x1a0
ath10k: mac radar config update: chan 2412MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config channel to 2412MHz (cf1 2412MHz cf2 0MHz width 20 (noht))
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ath10k: mac vdev 0 delete (remove interface)
ath10k: WMI vdev delete id 0
ath10k: peer-unmap-event: unknown peer id 2
ath10k: boot suspend complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00001000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000804
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr c09be000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2886000
ath10k: boot ce dest ring id 2 entries 32 base_addr c09bd000
ath10k: boot ce src ring id 3 entries 32 base_addr d2d5f000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2a90000
ath10k: boot ce src ring id 7 entries 2 base_addr d2a9f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2a9e000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd2973d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd2973d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12cd0000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz flags 0x1a0
ath10k: mac radar config update: chan 2412MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath10k: mac vdev 0 delete (remove interface)
ath10k: WMI vdev delete id 0
ath10k: peer-unmap-event: unknown peer id 2
ath10k: boot suspend complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00001000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000804
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr d2bd8000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2966000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2a9f000
ath10k: boot ce src ring id 3 entries 32 base_addr d2a97000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2a00000
ath10k: boot ce src ring id 7 entries 2 base_addr d2a0f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2a0e000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12ad0000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz flags 0x1a0
ath10k: mac radar config update: chan 2412MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
eth0: stopped
ath10k: mac vdev 0 delete (remove interface)
ath10k: WMI vdev delete id 0
ath10k: peer-unmap-event: unknown peer id 2
ath10k: boot suspend complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00001000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000804
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
Port 0: Link-down
eth0: link up
Port 1: Link-up, Full-duplex, Speed-100Mbps.
Port 2: Link-down
Port 3: Link-down
Port -1: Link-down
eth0: started
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr c09c1000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2d1a000
ath10k: boot ce dest ring id 2 entries 32 base_addr c099b000
ath10k: boot ce src ring id 3 entries 32 base_addr d2a07000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2af0000
ath10k: boot ce src ring id 7 entries 2 base_addr d2aff000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2afe000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12b10000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 2 subtype 0
ath10k: WMI vdev create: id 0 type 2 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 1 value 1
ath10k: wmi sta ps param vdev_id 0x0 param 2 value 0
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: wmi pdev set wmm params
ath10k: wmi sta ps param vdev_id 0x0 param 4 value 0
ath10k: wmi sta ps param vdev_id 0x0 param 0 value 0
ath10k: mac config channel 2412 mhz flags 0x1a0
ath10k: mac radar config update: chan 2412MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ath10k: mac vdev 0 psmode disable
ath10k: wmi set powersave id 0x0 mode 0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
mv_eth_tool_get_settings is not supported on eth0
device eth0 entered promiscuous mode
device wlan0 entered promiscuous mode
br0: port 1(eth0) entering forwarding state
br0: port 1(eth0) entering forwarding state
ath10k: mac vdev 0 delete (remove interface)
ath10k: WMI vdev delete id 0
ath10k: peer-unmap-event: unknown peer id 2
ath10k: boot suspend complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00001000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000804
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
br0: port 2(wlan0) entering disabled state
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x00000000
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr d2afe000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2ca0000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2aff000
ath10k: boot ce src ring id 3 entries 32 base_addr d2af8000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2950000
ath10k: boot ce src ring id 7 entries 2 base_addr d295f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d295e000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd2925d3c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12e60000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 1 subtype 0
ath10k: WMI vdev create: id 0 type 1 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0e:38:be
ath10k: wmi pdev set param 13 value 50
ath10k: wmi vdev id 0x0 set param 38 value 3747
ath10k: wmi vdev id 0x0 set param 39 value 3895
ath10k: wmi vdev id 0x0 set param 40 value 3900
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 1
ath10k: wmi vdev id 0x0 set param 7 value 1
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: mac config channel 2412 mhz flags 0x1a0
ath10k: mac radar config update: chan 2412MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath10k: mac vdev 0 rts threshold -1
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi mgmt tx skb d2b47c20 len 52 ftype 00 stype c0
ath10k: mac config channel 5240 mhz flags 0x100
ath10k: mac radar config update: chan 5240MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config channel to 5240MHz (cf1 5240MHz cf2 0MHz width 20)
ath10k: mac config power 14
ath10k: wmi pdev set param 3 value 28
ath10k: wmi pdev set param 4 value 28
ath10k: wmi vdev id 0x0 set param 3 value 100
ath10k: mac vdev 0 beacon_interval 100
ath10k: vdev 0 set beacon tx mode to staggered
ath10k: wmi pdev set param 7 value 0
ath10k: mac vdev 0 start center_freq 5240 phymode 11na-ht20
ath10k: wmi vdev start id 0x0 flags: 0x0, freq 5240, mode 4, ch_flags: 0x4, max_
power: 40
ath10k: WMI_VDEV_START_RESP_EVENTID
ath10k: wmi mgmt vdev up id 0x0 assoc id 0 bssid 04:f0:21:0e:38:be
ath10k: mac vdev 0 up
ath10k: WMI_TBTTOFFSET_UPDATE_EVENTID
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
br0: port 2(wlan0) entering forwarding state
br0: port 2(wlan0) entering forwarding state
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 2
ath10k: wmi vdev id 0x0 set param 7 value 2
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi mgmt tx skb d2a429e0 len 52 ftype 00 stype c0
ath10k: wmi mgmt tx skb d2c5d900 len 56 ftype 00 stype b0
ath10k: vdev 0 set beacon tx mode to staggered
ath10k: wmi pdev set param 7 value 0
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: wmi mgmt tx skb d2c48820 len 152 ftype 00 stype 10
ath10k: mac vdev 0 peer create 00:15:61:10:51:de (new sta) num_peers 1
ath10k: wmi peer create vdev_id 0 peer_addr 00:15:61:10:51:de
ath10k: mac sta 00:15:61:10:51:de associated
ath10k: mac ht peer 00:15:61:10:51:de mcs cnt 8 nss 1
ath10k: mac peer 00:15:61:10:51:de phymode 11na-ht20
ath10k: wmi peer assoc vdev 0 addr 00:15:61:10:51:de
ath10k: wmi vdev 0 peer 0x00:15:61:10:51:de set param 1 value 0
ath10k: wmi event debug mesg len 64
br0: received packet on eth0 with own address as source address
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 10.1.467.2-1
ath10k: target register Dump Location: 0x0040AAA4
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x000015B3 0x0099F306 0x00955B31
ath10k: [04]: 0x0099F306 0x00060530 0x00000005 0x0040AC62
ath10k: [08]: 0x009B8164 0x004118C4 0x0043DD84 0x00400000
ath10k: [12]: 0x00000009 0xFFFFFFFF 0x0095808C 0x009580A2
ath10k: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
ath10k: [20]: 0x4099F306 0x0040ABB4 0x00955A00 0x00000003
ath10k: [24]: 0x809995A1 0x0040AC14 0x0040ACB4 0xC099F306
ath10k: [28]: 0x80999400 0x0040AC44 0x004343F0 0x0040ACCC
ath10k: [32]: 0x8098CE0E 0x0040AC64 0x004343F0 0x0040ACCC
ath10k: [36]: 0x809912AC 0x0040AC84 0x004343F0 0x0040ACCC
ath10k: [40]: 0x8099147A 0x0040ACA4 0x0041ED48 0x00434488
ath10k: [44]: 0x80991661 0x0040AD24 0x00000000 0x0042E9FC
ath10k: [48]: 0x8099081C 0x0040AD84 0x00434488 0x0042E928
ath10k: [52]: 0x809909D0 0x0040ADA4 0x00000000 0x0042D704
ath10k: [56]: 0x809968F1 0x0040AEC4 0x0041ED48 0x00000000
ath10k: suspend timed out - target pause event never came
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000c00a
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000000a
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000000a
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000000a
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ieee80211 phy0: Hardware restart was requested
ath10k: boot performing warm chip reset
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000000a
ath10k: boot host cpu intr cause: 0x00000000
ath10k: boot target cpu intr cause: 0x0000000a
ath10k: boot target reset state: 0x00000800
ath10k: boot warm reset complete
ath10k: boot ce src ring id 0 entries 16 base_addr d2951000
ath10k: boot ce dest ring id 1 entries 512 base_addr d2996000
ath10k: boot ce dest ring id 2 entries 32 base_addr d2e89000
ath10k: boot ce src ring id 3 entries 32 base_addr d2bff000
ath10k: boot ce src ring id 4 entries 4096 base_addr d2d10000
ath10k: boot ce src ring id 7 entries 2 base_addr d2d1f000
ath10k: boot ce dest ring id 7 entries 2 base_addr d2d1e000
ath10k: bmi start
ath10k: bmi write address 0x400800 length 4
ath10k: bmi read address 0x400810 length 4
ath10k: bmi write address 0x400810 length 4
ath10k: bmi write address 0x400844 length 4
ath10k: bmi write address 0x400904 length 4
ath10k: bmi read address 0x4008ac length 4
ath10k: boot push board extended data addr 0x0
ath10k: bmi read address 0x400854 length 4
ath10k: bmi write address 0x401cc0 length 2116
ath10k: bmi write address 0x400858 length 4
ath10k: bmi fast download address 0x1234 buffer 0xe211a034 length 6917
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211a034 length 6916
ath10k: bmi lz data buffer 0xd02d9e6c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi execute address 0x1234 param 0x0
ath10k: bmi fast download address 0x1234 buffer 0xe211bb44 length 190250
ath10k: bmi lz stream start address 0x1234
ath10k: bmi lz data buffer 0xe211bb44 length 190248
ath10k: bmi lz data buffer 0xd02d9e6c length 4
ath10k: bmi lz stream start address 0x0
ath10k: bmi write address 0x400814 length 4
ath10k: bmi done
ath10k: boot htc service 'Control' ul pipe 0 dl pipe 1 eid 0 ready
ath10k: boot htc ep 0 ul polled 0 dl polled 0
ath10k: boot htc service 'Control' eid 0 TX flow control disabled
ath10k: boot htc service HTT Data does not allocate target credits
ath10k: boot htc service 'HTT Data' ul pipe 4 dl pipe 1 eid 1 ready
ath10k: boot htc ep 1 ul polled 1 dl polled 0
ath10k: boot htc service 'HTT Data' eid 1 TX flow control disabled
ath10k: htt tx max num pending tx 1424
ath10k: htt rx ring size 1024 fill_level 1000
ath10k: boot htc service 'WMI' ul pipe 3 dl pipe 2 eid 2 ready
ath10k: boot htc ep 2 ul polled 0 dl polled 0
ath10k: firmware has requested 1 memory chunks
ath10k: wmi mem_req_id 1 num_units 0 num_unit_info 2 unit size 404 actual units
145
ath10k: wmi event service ready sw_ver 0x4100270f abi_ver 1 phy_cap 0x00000003 h
t_cap 0x0000085b vht_cap 0x338001b2 vht_supp_msc 0x0000ffea sys_cap_info 0x00000
000 mem_reqs 1 num_rf_chains 3
ath10k: boot wmi ready
ath10k: firmware 10.1.467.2-1 booted
ath10k: wmi sending 1 memory chunks info.
ath10k: wmi chunk 0 len 58580 requested, addr 0x12a60000
ath10k: wmi init 10x
ath10k: wmi event debug print 'P 145 V 16 T 443'
ath10k: wmi event ready sw_version 1090529039 abi_version 1 mac_addr 04:f0:21:0e
:38:be status 0 skb->len 20 ev-sz 20
ath10k: htt target version 2.1
ath10k: wmi pdev set param 30 value 1
ath10k: wmi pdev set param 10 value 1
ath10k: wmi pdev set param 31 value 0
ath10k: mac channel [0/32] freq 2412 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [1/32] freq 2417 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [2/32] freq 2422 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [3/32] freq 2427 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [4/32] freq 2432 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [5/32] freq 2437 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [6/32] freq 2442 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [7/32] freq 2447 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [8/32] freq 2452 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [9/32] freq 2457 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [10/32] freq 2462 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [11/32] freq 2467 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [12/32] freq 2472 maxpower 40 regpower 40 antenna 0 mode 1
ath10k: mac channel [13/32] freq 5180 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [14/32] freq 5200 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [15/32] freq 5220 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [16/32] freq 5240 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [17/32] freq 5260 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [18/32] freq 5280 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [19/32] freq 5300 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [20/32] freq 5320 maxpower 40 regpower 40 antenna 0 mode 0
ath10k: mac channel [21/32] freq 5500 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [22/32] freq 5520 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [23/32] freq 5540 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [24/32] freq 5560 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [25/32] freq 5580 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [26/32] freq 5600 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [27/32] freq 5620 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [28/32] freq 5640 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [29/32] freq 5660 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [30/32] freq 5680 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: mac channel [31/32] freq 5700 maxpower 54 regpower 54 antenna 0 mode 0
ath10k: wmi pdev regdomain rd 37 rd2g 37 rd5g 37 ctl2g 30 ctl5g 30
ath10k: mac vdev create 0 (add interface) type 1 subtype 0
ath10k: WMI vdev create: id 0 type 1 subtype 0 macaddr 04:f0:21:0e:38:be
ath10k: wmi vdev id 0x0 set param 31 value 0
ath10k: vdev param 0 not supported by firmware
ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0e:38:be
ath10k: wmi pdev set param 13 value 50
ath10k: wmi vdev id 0x0 set param 38 value 3747
ath10k: wmi vdev id 0x0 set param 39 value 3895
ath10k: wmi vdev id 0x0 set param 40 value 3900
ath10k: wmi vdev id 0x0 set param 1 value -1
ath10k: wmi vdev id 0x0 set param 2 value -1
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: wmi pdev set wmm params
ath10k: mac config channel 5240 mhz flags 0x100
ath10k: mac radar config update: chan 5240MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config power 14
ath10k: wmi pdev set param 3 value 28
ath10k: wmi pdev set param 4 value 28
ath10k: wmi vdev id 0x0 set param 3 value 100
ath10k: mac vdev 0 beacon_interval 100
ath10k: vdev 0 set beacon tx mode to staggered
ath10k: wmi pdev set param 7 value 0
ath10k: mac vdev 0 create peer 04:f0:21:0e:38:be
ath10k: wmi peer create vdev_id 0 peer_addr 04:f0:21:0e:38:be
ath10k: mac vdev 0 start center_freq 5240 phymode 11na-ht20
ath10k: wmi vdev start id 0x0 flags: 0x0, freq 5240, mode 4, ch_flags: 0x4, max_
power: 40
ath10k: WMI_VDEV_START_RESP_EVENTID
ath10k: wmi mgmt vdev up id 0x0 assoc id 0 bssid 04:f0:21:0e:38:be
ath10k: mac vdev 0 up
ath10k: mac vdev 0 cts_prot 0
ath10k: wmi vdev id 0x0 set param 43 value 0
ath10k: mac vdev 0 slot_time 2
ath10k: wmi vdev id 0x0 set param 7 value 2
ath10k: WMI_TBTTOFFSET_UPDATE_EVENTID
ath10k: mac vdev 0 preamble 1n
ath10k: wmi vdev id 0x0 set param 8 value 1
ath10k: mac vdev 0 peer create 00:15:61:10:51:de (new sta) num_peers 2
ath10k: wmi peer create vdev_id 0 peer_addr 00:15:61:10:51:de
ath10k: mac sta 00:15:61:10:51:de associated
ath10k: mac ht peer 00:15:61:10:51:de mcs cnt 8 nss 1
ath10k: mac peer 00:15:61:10:51:de phymode 11na-ht20
ath10k: wmi peer assoc vdev 0 addr 00:15:61:10:51:de
ath10k: wmi vdev 0 peer 0x00:15:61:10:51:de set param 1 value 0
ath10k: device successfully recovered
ath10k: wmi mgmt tx skb d2c5d3c0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc6460 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc6520 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc65e0 len 180 ftype 00 stype 50
ath10k: wmi event debug mesg len 52
ath10k: wmi mgmt tx skb d2bc62e0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc6220 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc6160 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bc60a0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcaf00 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcae40 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcad80 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcacc0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcac00 len 180 ftype 00 stype 50
eth0: no IPv6 routers present
ath10k: wmi mgmt tx skb d2bcab40 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bcaa80 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca9c0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca900 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca840 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca780 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca6c0 len 180 ftype 00 stype 50
br0: no IPv6 routers present
ath10k: wmi mgmt tx skb d2bca600 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca540 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca480 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca3c0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca300 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca240 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca180 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2bca0c0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64f20 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64e60 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64da0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64ce0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64c20 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64b60 len 180 ftype 00 stype 50
wlan0: no IPv6 routers present
ath10k: wmi mgmt tx skb d2b64aa0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b649e0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64920 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b64860 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b647a0 len 180 ftype 00 stype 50
ath10k: wmi mgmt tx skb d2b646e0 len 180 ftype 00 stype 50
ath10k: mac sta 00:15:61:10:51:de disassociated
ath10k: mac vdev 0 peer delete 00:15:61:10:51:de (sta gone)
ath10k: wmi peer delete vdev_id 0 peer_addr 00:15:61:10:51:de
ath10k: wmi vdev stop id 0x0
ath10k: WMI_VDEV_STOPPED_EVENTID
ath10k: mac config channel 5240 mhz flags 0x100
ath10k: mac radar config update: chan 5240MHz radar 0 chan radar 0 chan state US
ABLE
ath10k: mac config channel to 5240MHz (cf1 5240MHz cf2 0MHz width 20 (noht))
ath10k: mac config power 20
ath10k: wmi pdev set param 3 value 40
ath10k: wmi pdev set param 4 value 40
ath10k: wmi peer delete vdev_id 0 peer_addr 04:f0:21:0e:38:be
ath10k: Failed to remove peer for AP vdev 0: -110
ath10k: mac vdev 0 delete (remove interface)
ath10k: WMI vdev delete id 0
ath10k: removing stale peer 04:f0:21:0e:38:be from vdev_id 0
br0: port 2(wlan0) entering forwarding state
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* ath10k does not support selection antenna yet?
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
@ 2014-05-07 7:36 ` Vu Hai NGUYEN
2014-05-07 7:48 ` Michal Kazior
2014-05-07 15:09 ` Ben Greear
0 siblings, 2 replies; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-05-07 7:36 UTC (permalink / raw)
To: ath10k; +Cc: Patrick CARNEIRO RODRIGUEZ
I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
Btw, I still try to deal with the bitrates problem, the file /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats give me nothing when I "cat" it and if I run : "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4", the dmesg output is:
ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
ath10k: wmi vdev id 0x0 set param 25 value 4
ath10k: wmi vdev id 0x0 set param 32 value 1
ath10k: wmi vdev id 0x0 set param 26 value 0
ath10k: wmi event debug mesg len 16
but the order of these parameters are normally 27 (fixed rates) , 34 (nss) and 28(sgi) in the map of parameter, I have no idea why the offset is minus 2 ?
Do you guys have any suggestion for this? :D
Thank you in advande.
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : ath10k [ath10k-bounces@lists.infradead.org] de la part de Vu Hai NGUYEN [vh.nguyen@actiasodielec.fr]
Date d'envoi : mercredi 30 avril 2014 14:39
À : Michal Kazior
Cc : Patrick CARNEIRO RODRIGUEZ; Kalle Valo; ath10k@lists.infradead.org
Objet : RE : RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
>> It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the >>station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
>This works for me (latest github.com/kvalo/ath/master with 467.2).
>I can see "signal" values change in iw station dump on the connected
>client when I set different txpower values on ath10k AP.
I replace the ath from backports with the one from master tree of ath, but it is worse.
When I set a channel from 52 (or higher) for AP mode using the version of backports, I get a backtrace message output and then my wlan0 become ready:
br0: port 2(wlan0) entering disabled state
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: interface------------[ cut here ]------------
state UNINITIALWARNING: at /home/alberix2/Desktop/Wilinks_ath10k/ACCESS_POINT_A
PPLI/Source/Driver_ath10k/backports-3.15-rc1-1/net/wireless/nl80211.c:5824 nl802
11_start_radar_detection+0xf8/0x16c [cfg80211]()
IZED->COUNTRY_UPModules linked in:DATE
wlan0: int ath10k_pci(O)erface state COU ath10k_core(O)NTRY_UPDATE->DFS ath(O)
wlan0: DFS-CAC mac80211(O)-START freq=5260 cfg80211(O) chan=52 sec_cha compat(O)
n=0
arc4 ubifs ubi [last unloaded: compat]
Backtrace:
[<c0011938>] (dump_backtrace+0x0/0x118) from [<c050205c>] (dump_stack+0x18/0x20)
r6:bf49a62b r5:000016c0 r4:00000000 r3:c10b27ac
[<c0502044>] (dump_stack+0x0/0x20) from [<c0066c38>] (warn_slowpath_common+0x54/
0x70)
[<c0066be4>] (warn_slowpath_common+0x0/0x70) from [<c0066c78>] (warn_slowpath_nu
ll+0x24/0x2c)
r8:00000000 r7:00000000 r6:d2f9f000 r5:d2aa0000 r4:d2f9f3c8
r3:00000009
[<c0066c54>] (warn_slowpath_null+0x0/0x2c) from [<bf45eae8>] (nl80211_start_rada
r_detection+0xf8/0x16c [cfg80211])
[<bf45e9f0>] (nl80211_start_radar_detection+0x0/0x16c [cfg80211]) from [<c045348
8>] (genl_rcv_msg+0x1b4/0x1f4)
[<c04532d4>] (genl_rcv_msg+0x0/0x1f4) from [<c0452904>] (netlink_rcv_skb+0x58/0x
b8)
[<c04528ac>] (netlink_rcv_skb+0x0/0xb8) from [<c04532c4>] (genl_rcv+0x20/0x30)
r6:c082f600 r5:d2a7d0e0 r4:d2a7d0e0 r3:c04532a4
[<c04532a4>] (genl_rcv+0x0/0x30) from [<c04522d0>] (netlink_unicast+0x224/0x2c4)
r4:d0074400 r3:c04532a4
[<c04520ac>] (netlink_unicast+0x0/0x2c4) from [<c04526a4>] (netlink_sendmsg+0x29
0/0x320)
[<c0452414>] (netlink_sendmsg+0x0/0x320) from [<c0428eac>] (sock_sendmsg+0x98/0x
b4)
[<c0428e14>] (sock_sendmsg+0x0/0xb4) from [<c0429150>] (__sys_sendmsg+0x1d0/0x26
c)
r4:d281bf64
[<c0428f80>] (__sys_sendmsg+0x0/0x26c) from [<c042ab30>] (sys_sendmsg+0x44/0x68)
[<c042aaec>] (sys_sendmsg+0x0/0x68) from [<c000ddc0>] (ret_fast_syscall+0x0/0x30
)
r6:0012d850 r5:0012d888 r4:400c8900
---[ end trace c03fd18534c1267a ]---
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
br0: port 2(wlan0) entering forwarding state
br0: port 2(wlan0) entering forwarding state
But with the version from ath master tree, I always get wlan0: link is not ready (and there is no backtrace msg).
And in both versions, the firmware usually crashed when I set a channel lower than 52 (I don't get backtrace msg in these cases):
wlan0: AP-ENABLED
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version 0x4100016c
ath10k: firmware version: 10.1.467.2-1
ath10k: target register Dump Location: 0x0040AAA4
ath10k: target Register Dump
ath10k: [00]: 0x4100016C 0x000015B3 0x0099F306 0x00955B31
ath10k: [04]: 0x0099F306 0x00060530 0x00000005 0x00000000
ath10k: [08]: 0x009B8164 0x004118C4 0x0043DD84 0x00400000
ath10k: [12]: 0x00000009 0xFFFFFFFF 0x0095808C 0x009580A2
ath10k: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
ath10k: [20]: 0x4099F306 0x0040ABB4 0x00955A00 0x00000003
ath10k: [24]: 0x809995A1 0x0040AC14 0x0040ACB4 0xC099F306
ath10k: [28]: 0x80999400 0x0040AC44 0x004343F0 0x0040ACCC
ath10k: [32]: 0x8098CE0E 0x0040AC64 0x004343F0 0x0040ACCC
ath10k: [36]: 0x809912AC 0x0040AC84 0x004343F0 0x0040ACCC
ath10k: [40]: 0x8099147A 0x0040ACA4 0x0041ED48 0x00434488
ath10k: [44]: 0x80991661 0x0040AD24 0x00000000 0x0042F2A0
ath10k: [48]: 0x8099081C 0x0040AD84 0x00434488 0x0042F1CC
ath10k: [52]: 0x809909D0 0x0040ADA4 0x00000000 0x0042D704
ath10k: [56]: 0x809968F1 0x0040AEC4 0x0041ED48 0x00000000
ath10k: suspend timed out - target pause event never came
ieee80211 phy0: Hardware restart was requested
ath10k: device successfully recovered
There is an ouput of my dmesg in the attached file if someone is interested in :D
One more question: The default country for regulatory domain of ath is US?
I found that it was defined in file "regd.c" and that's why even I set my country to FR ("iw reg set FR") I was not able to set up the channel 12 and 13. (Marked as disabled in output of "iw list" so I replace CTRY_UNITED_STATES with CTRY_FRANCE and then I can get the channel 12 and 13 worked. Is this legal?
@ Chun-Yeow:
>For TxRate, another option would be looking at
>"/sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats".
When I "cat" that file there is nothing appear (it looks like empty) (But I can view other information from others files, such as: simulate_fw_crash, fw_dbglog, htt_stats_mask, wmi_services). Do you have any idea? :D
Thank you all of you for your support
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
________________________________________
De : Michal Kazior [michal.kazior@tieto.com]
Date d'envoi : jeudi 24 avril 2014 11:41
À : Vu Hai NGUYEN
Cc : Kalle Valo; Patrick CARNEIRO RODRIGUEZ; ath10k@lists.infradead.org
Objet : Re: RE : RE : Report Firmware firmware-2.bin_10.1.467.2-1 Error
On 24 April 2014 11:03, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> Thank you for your response, the problem is solved when I download the latest version of backport (3.15) and compile ath10k with it (last time my version is 3.13 and as you said, It might not include the patch).
> Now I can load the firmware 10.1.467.2-1 but I get new problem too.
> Does ath10k support all the command of "iw"?
> For example I set up mode access point and tried to change the txpower by the command: "iw wlan0 set txpower fixed 1200" (same thing as "iwconfig wlan0 txpower 12dBm" , right?)
> The output of "iwconfig" is:
> wlan0 IEEE 802.11abgn Mode:Master Tx-Power=12 dBm
> Retry short limit:7 RTS thr:off Fragment thr:off
> Power Management:on
>
> And output of "dmesg":
> ath10k: mac config power 12
> ath10k: wmi pdev set param 3 value 24
> ath10k: wmi pdev set param 4 value 24
>
> It seems that the command arrives until the level of driver ath10k and works but when I verified by connecting a station to my access point and look at the out put of "iw wlan0 station dump", the value of txpower received at the station didn't change even when I changed the txpower of my access point from 1dBm to 20dBm (my station is near the access point).
This works for me (latest github.com/kvalo/ath/master with 467.2).
I can see "signal" values change in iw station dump on the connected
client when I set different txpower values on ath10k AP.
> Same thing when I do with the command set bit rates: "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4"
>
> Out put of dmesg:
> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
> ath10k: wmi vdev id 0x0 set param 27 value 4
> ath10k: wmi vdev id 0x0 set param 34 value 1
> ath10k: wmi vdev id 0x0 set param 28 value 0
> ath10k: wmi event debug mesg len 16
>
> But the out put of " iw wlan0 station dump" did not show any change when I varied the bit rate of my access point too.
Again, this works for me.
To be clear - ath10k is incapable of reporting "tx bitrate" (it always
reports 6mbps). If you want to verify if the bitrate mask works you
must check "rx bitrate" on the other side, i.e. on the connected
client.
Or just use a separate sniffer and see if AP is sends frames with
different txpower/bitrate values.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: ath10k does not support selection antenna yet?
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
@ 2014-05-07 7:48 ` Michal Kazior
2014-05-07 8:16 ` Yeoh Chun-Yeow
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
2014-05-07 15:09 ` Ben Greear
1 sibling, 2 replies; 36+ messages in thread
From: Michal Kazior @ 2014-05-07 7:48 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
On 7 May 2014 09:36, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
I'm not aware if that's possible.
> Btw, I still try to deal with the bitrates problem, the file /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats give me nothing when I "cat" it and if I run : "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4", the dmesg output is:
fw_stats was broken for a long time due to some firmware ABI
differences. I'm not sure if this was finally fixed or no. See mailing
list archives for more details, please.
> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
> ath10k: wmi vdev id 0x0 set param 25 value 4
> ath10k: wmi vdev id 0x0 set param 32 value 1
> ath10k: wmi vdev id 0x0 set param 26 value 0
> ath10k: wmi event debug mesg len 16
>
> but the order of these parameters are normally 27 (fixed rates) , 34 (nss) and 28(sgi) in the map of parameter, I have no idea why the offset is minus 2 ?
You're looking at the wrong enum. There are two vdev param enums:
wmi_vdev_param and wmi_10x_vdev_param.
I'm going to re-iterate - you can check rx bitrate on the other end to
verify your fixed rate setting. tx bitrate reporting is broken in
ath10k due to firmware deficiency.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: ath10k does not support selection antenna yet?
2014-05-07 7:48 ` Michal Kazior
@ 2014-05-07 8:16 ` Yeoh Chun-Yeow
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
1 sibling, 0 replies; 36+ messages in thread
From: Yeoh Chun-Yeow @ 2014-05-07 8:16 UTC (permalink / raw)
To: Michal Kazior; +Cc: Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ, ath10k
> fw_stats was broken for a long time due to some firmware ABI
> differences. I'm not sure if this was finally fixed or no. See mailing
> list archives for more details, please.
The master branch in https://github.com/kvalo/ath should have the
fixing the FW print stats.
----
Chun-Yeow
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* RE : ath10k does not support selection antenna yet?
2014-05-07 7:48 ` Michal Kazior
2014-05-07 8:16 ` Yeoh Chun-Yeow
@ 2014-05-07 8:16 ` Vu Hai NGUYEN
2014-05-07 9:26 ` Janusz Dziedzic
1 sibling, 1 reply; 36+ messages in thread
From: Vu Hai NGUYEN @ 2014-05-07 8:16 UTC (permalink / raw)
To: Michal Kazior; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>I'm not aware if that's possible.
Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x1 RX 0x1
>> Btw, I still try to deal with the bitrates problem, the file /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats give me nothing when I "cat" it and if I run : "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4", the dmesg output is:
fw_stats was broken for a long time due to some firmware ABI
differences. I'm not sure if this was finally fixed or no. See mailing
list archives for more details, please.
>> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
>> ath10k: wmi vdev id 0x0 set param 25 value 4
>> ath10k: wmi vdev id 0x0 set param 32 value 1
>> ath10k: wmi vdev id 0x0 set param 26 value 0
>> ath10k: wmi event debug mesg len 16
>>
>>but the order of these parameters are normally 27 (fixed rates) , 34 (nss) and 28(sgi) in the map of parameter, I have no idea why the offset is minus 2 ?
>You're looking at the wrong enum. There are two vdev param enums:
>wmi_vdev_param and wmi_10x_vdev_param.
>I'm going to re-iterate - you can check rx bitrate on the other end to
>verify your fixed rate setting. tx bitrate reporting is broken in
>ath10k due to firmware deficiency.
I check the rx bit rates on my station and it always depend on the rates that is set on my station, it is not limitted by the access point (for example: I set bit rates equal 65 Mbps on my station and 39 Mbps on my access point, I get the rx bit rates on my station equal 65 Mbps (normally it is limitted at 39 Mbps because of the access point?)
NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : ath10k does not support selection antenna yet?
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
@ 2014-05-07 9:26 ` Janusz Dziedzic
2014-05-07 14:11 ` Ben Greear
0 siblings, 1 reply; 36+ messages in thread
From: Janusz Dziedzic @ 2014-05-07 9:26 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, Michal Kazior, ath10k
On 7 May 2014 10:16, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>
>>I'm not aware if that's possible.
>
> Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
> Available Antennas: TX 0x3 RX 0x3
> Configured Antennas: TX 0x1 RX 0x1
>
>
>>> Btw, I still try to deal with the bitrates problem, the file /sys/kernel/debug/ieee80211/phy0/ath10k/fw_stats give me nothing when I "cat" it and if I run : "iw wlan0 set bitrates legacy-2.4 54 ht-mcs-2.4", the dmesg output is:
>
> fw_stats was broken for a long time due to some firmware ABI
> differences. I'm not sure if this was finally fixed or no. See mailing
> list archives for more details, please.
>
>
>>> ath10k: mac fixed rate pream 0x00 nss 0x00 rate 0x04
>>> ath10k: wmi vdev id 0x0 set param 25 value 4
>>> ath10k: wmi vdev id 0x0 set param 32 value 1
>>> ath10k: wmi vdev id 0x0 set param 26 value 0
>>> ath10k: wmi event debug mesg len 16
>>>
>>>but the order of these parameters are normally 27 (fixed rates) , 34 (nss) and 28(sgi) in the map of parameter, I have no idea why the offset is minus 2 ?
>
>>You're looking at the wrong enum. There are two vdev param enums:
>>wmi_vdev_param and wmi_10x_vdev_param.
>
>>I'm going to re-iterate - you can check rx bitrate on the other end to
>>verify your fixed rate setting. tx bitrate reporting is broken in
>>ath10k due to firmware deficiency.
>
> I check the rx bit rates on my station and it always depend on the rates that is set on my station, it is not limitted by the access point (for example: I set bit rates equal 65 Mbps on my station and 39 Mbps on my access point, I get the rx bit rates on my station equal 65 Mbps (normally it is limitted at 39 Mbps because of the access point?)
>
Try to set bitrates after you are connected (STA) and ap started (AP).
This is only test command, so have some limitation.
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : ath10k does not support selection antenna yet?
2014-05-07 9:26 ` Janusz Dziedzic
@ 2014-05-07 14:11 ` Ben Greear
2014-05-07 14:21 ` Adrian Chadd
0 siblings, 1 reply; 36+ messages in thread
From: Ben Greear @ 2014-05-07 14:11 UTC (permalink / raw)
To: Janusz Dziedzic
Cc: Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ, Michal Kazior, ath10k
On 05/07/2014 02:26 AM, Janusz Dziedzic wrote:
> On 7 May 2014 10:16, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>>>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>>
>>> I'm not aware if that's possible.
>>
>> Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
>> Available Antennas: TX 0x3 RX 0x3
>> Configured Antennas: TX 0x1 RX 0x1
From looking at the 10.1.467 firmware, it appears it would support setting
the tx and rx chainmask, and it seems the ath10k driver has at least some
of the support needed to implement this. grep for TX_CHAIN_MASK.
I do NOT see a way in standard firmware to read the current chainmask.
I have a way to read this in my customized firmware, but I have not yet
tied it into the driver, and I am not certain my current method is the best option
at this point...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : ath10k does not support selection antenna yet?
2014-05-07 14:11 ` Ben Greear
@ 2014-05-07 14:21 ` Adrian Chadd
2014-05-07 14:33 ` Ben Greear
0 siblings, 1 reply; 36+ messages in thread
From: Adrian Chadd @ 2014-05-07 14:21 UTC (permalink / raw)
To: Ben Greear
Cc: Janusz Dziedzic, Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ,
Michal Kazior, ath10k
On 7 May 2014 07:11, Ben Greear <greearb@candelatech.com> wrote:
> On 05/07/2014 02:26 AM, Janusz Dziedzic wrote:
>> On 7 May 2014 10:16, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>>>>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>>>
>>>> I'm not aware if that's possible.
>>>
>>> Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
>>> Available Antennas: TX 0x3 RX 0x3
>>> Configured Antennas: TX 0x1 RX 0x1
>
> From looking at the 10.1.467 firmware, it appears it would support setting
> the tx and rx chainmask, and it seems the ath10k driver has at least some
> of the support needed to implement this. grep for TX_CHAIN_MASK.
>
> I do NOT see a way in standard firmware to read the current chainmask.
>
> I have a way to read this in my customized firmware, but I have not yet
> tied it into the driver, and I am not certain my current method is the best option
> at this point...
The STA design of the firmware is that it is supposed to be completely
asynchronous - the firmware itself can make decisions about what the
current config is at any time. For example, if it's doing background
scanning, it may transmit the basic rate probe request frames using
one chain. Or it may go into a powersave mode where it shuts down
all-but-one tx and/or rx chain until they're needed.
Now, assuming they didn't go and break that design philosophy after I
left, you should try to keep that setup in mind. So ideally, you'd
send the firmware some command relevant to the current vdev, then you
either send a vdev query or you just get told about it when the radio
finishes vdev setup/association. But querying the "current chainmask"
may not reflect what's currently going on.
-a
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : ath10k does not support selection antenna yet?
2014-05-07 14:21 ` Adrian Chadd
@ 2014-05-07 14:33 ` Ben Greear
2014-05-07 14:50 ` Adrian Chadd
0 siblings, 1 reply; 36+ messages in thread
From: Ben Greear @ 2014-05-07 14:33 UTC (permalink / raw)
To: Adrian Chadd
Cc: Janusz Dziedzic, Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ,
Michal Kazior, ath10k
On 05/07/2014 07:21 AM, Adrian Chadd wrote:
> On 7 May 2014 07:11, Ben Greear <greearb@candelatech.com> wrote:
>> On 05/07/2014 02:26 AM, Janusz Dziedzic wrote:
>>> On 7 May 2014 10:16, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>>>>>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>>>>
>>>>> I'm not aware if that's possible.
>>>>
>>>> Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
>>>> Available Antennas: TX 0x3 RX 0x3
>>>> Configured Antennas: TX 0x1 RX 0x1
>>
>> From looking at the 10.1.467 firmware, it appears it would support setting
>> the tx and rx chainmask, and it seems the ath10k driver has at least some
>> of the support needed to implement this. grep for TX_CHAIN_MASK.
>>
>> I do NOT see a way in standard firmware to read the current chainmask.
>>
>> I have a way to read this in my customized firmware, but I have not yet
>> tied it into the driver, and I am not certain my current method is the best option
>> at this point...
>
> The STA design of the firmware is that it is supposed to be completely
> asynchronous - the firmware itself can make decisions about what the
> current config is at any time. For example, if it's doing background
> scanning, it may transmit the basic rate probe request frames using
> one chain. Or it may go into a powersave mode where it shuts down
> all-but-one tx and/or rx chain until they're needed.
>
> Now, assuming they didn't go and break that design philosophy after I
> left, you should try to keep that setup in mind. So ideally, you'd
> send the firmware some command relevant to the current vdev, then you
> either send a vdev query or you just get told about it when the radio
> finishes vdev setup/association. But querying the "current chainmask"
> may not reflect what's currently going on.
I think the idea of the driver API is to put upper-bound limits on
all stations. So, if hardware disables 1 of the three antenna, then
all stations must therefore start using no more than 2 of them.
This appears to work in ath9k, and from reading firmware code,
it appears it would work in ath10k as well.
I don't know of any use for setting the tx chains aside from testing
purposes. Maybe if you are cabling up to something and only have
2 cables for a 3-antenna system that would be useful :)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: RE : ath10k does not support selection antenna yet?
2014-05-07 14:33 ` Ben Greear
@ 2014-05-07 14:50 ` Adrian Chadd
0 siblings, 0 replies; 36+ messages in thread
From: Adrian Chadd @ 2014-05-07 14:50 UTC (permalink / raw)
To: Ben Greear
Cc: Janusz Dziedzic, Vu Hai NGUYEN, Patrick CARNEIRO RODRIGUEZ,
Michal Kazior, ath10k
A big reason is power saving, eg "green AP". Ie, they reduce the tx
power and number of tx chains transmitted on.
-a
On 7 May 2014 07:33, Ben Greear <greearb@candelatech.com> wrote:
> On 05/07/2014 07:21 AM, Adrian Chadd wrote:
>> On 7 May 2014 07:11, Ben Greear <greearb@candelatech.com> wrote:
>>> On 05/07/2014 02:26 AM, Janusz Dziedzic wrote:
>>>> On 7 May 2014 10:16, Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr> wrote:
>>>>>>> I read in the debug's page that ath10k HW is currently limited to handle only single fixed rate setting or limit number of used spatial streams. Does it mean that the selection of antenna is not possible for this moment? Because if I look in the code of ath9k, there are 2 fonctions set_antenna and get_antenna in the structure: struct ieee80211_ops (file main.c) and that's why the out put of "iw list" for ath10k give me: Available Antennas: TX0 RX0 and I can not select the antenna?
>>>>>
>>>>>> I'm not aware if that's possible.
>>>>>
>>>>> Thank you for your response. I think if the select and set antenna work, the out put of "iw list" may have some thing like this:
>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>> Configured Antennas: TX 0x1 RX 0x1
>>>
>>> From looking at the 10.1.467 firmware, it appears it would support setting
>>> the tx and rx chainmask, and it seems the ath10k driver has at least some
>>> of the support needed to implement this. grep for TX_CHAIN_MASK.
>>>
>>> I do NOT see a way in standard firmware to read the current chainmask.
>>>
>>> I have a way to read this in my customized firmware, but I have not yet
>>> tied it into the driver, and I am not certain my current method is the best option
>>> at this point...
>>
>> The STA design of the firmware is that it is supposed to be completely
>> asynchronous - the firmware itself can make decisions about what the
>> current config is at any time. For example, if it's doing background
>> scanning, it may transmit the basic rate probe request frames using
>> one chain. Or it may go into a powersave mode where it shuts down
>> all-but-one tx and/or rx chain until they're needed.
>>
>> Now, assuming they didn't go and break that design philosophy after I
>> left, you should try to keep that setup in mind. So ideally, you'd
>> send the firmware some command relevant to the current vdev, then you
>> either send a vdev query or you just get told about it when the radio
>> finishes vdev setup/association. But querying the "current chainmask"
>> may not reflect what's currently going on.
>
> I think the idea of the driver API is to put upper-bound limits on
> all stations. So, if hardware disables 1 of the three antenna, then
> all stations must therefore start using no more than 2 of them.
>
> This appears to work in ath9k, and from reading firmware code,
> it appears it would work in ath10k as well.
>
> I don't know of any use for setting the tx chains aside from testing
> purposes. Maybe if you are cabling up to something and only have
> 2 cables for a 3-antenna system that would be useful :)
>
> Thanks,
> Ben
>
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: ath10k does not support selection antenna yet?
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
2014-05-07 7:48 ` Michal Kazior
@ 2014-05-07 15:09 ` Ben Greear
1 sibling, 0 replies; 36+ messages in thread
From: Ben Greear @ 2014-05-07 15:09 UTC (permalink / raw)
To: Vu Hai NGUYEN; +Cc: Patrick CARNEIRO RODRIGUEZ, ath10k
Can you let me know what command you used to get this firmware
crash?
On 05/07/2014 12:36 AM, Vu Hai NGUYEN wrote:
> But with the version from ath master tree, I always get wlan0: link is not ready (and there is no backtrace msg).
> And in both versions, the firmware usually crashed when I set a channel lower than 52 (I don't get backtrace msg in these cases):
>
> wlan0: AP-ENABLED
> ath10k: firmware crashed!
> ath10k: hardware name qca988x hw2.0 version 0x4100016c
> ath10k: firmware version: 10.1.467.2-1
> ath10k: target register Dump Location: 0x0040AAA4
> ath10k: target Register Dump
> ath10k: [00]: 0x4100016C 0x000015B3 0x0099F306 0x00955B31
> ath10k: [04]: 0x0099F306 0x00060530 0x00000005 0x00000000
> ath10k: [08]: 0x009B8164 0x004118C4 0x0043DD84 0x00400000
> ath10k: [12]: 0x00000009 0xFFFFFFFF 0x0095808C 0x009580A2
> ath10k: [16]: 0x00958080 0x0094085D 0x00000000 0x00000000
> ath10k: [20]: 0x4099F306 0x0040ABB4 0x00955A00 0x00000003
> ath10k: [24]: 0x809995A1 0x0040AC14 0x0040ACB4 0xC099F306
> ath10k: [28]: 0x80999400 0x0040AC44 0x004343F0 0x0040ACCC
> ath10k: [32]: 0x8098CE0E 0x0040AC64 0x004343F0 0x0040ACCC
> ath10k: [36]: 0x809912AC 0x0040AC84 0x004343F0 0x0040ACCC
> ath10k: [40]: 0x8099147A 0x0040ACA4 0x0041ED48 0x00434488
> ath10k: [44]: 0x80991661 0x0040AD24 0x00000000 0x0042F2A0
> ath10k: [48]: 0x8099081C 0x0040AD84 0x00434488 0x0042F1CC
> ath10k: [52]: 0x809909D0 0x0040ADA4 0x00000000 0x0042D704
> ath10k: [56]: 0x809968F1 0x0040AEC4 0x0041ED48 0x00000000
> ath10k: suspend timed out - target pause event never came
> ieee80211 phy0: Hardware restart was requested
> ath10k: device successfully recovered
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 36+ messages in thread
end of thread, other threads:[~2014-05-07 15:10 UTC | newest]
Thread overview: 36+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-04-10 4:14 Crash during driver startup Ben Greear
2014-04-10 10:05 ` [PATCH] ath10k: double check bmi xfer pointers Michal Kazior
2014-04-10 10:05 ` Michal Kazior
2014-04-10 13:42 ` Ben Greear
2014-04-10 13:42 ` Ben Greear
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:40 ` Kalle Valo
2014-04-11 5:47 ` Michal Kazior
2014-04-11 5:47 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-11 15:09 ` load module ath10k: ieee80211 phy0: Failed to initialize wep: -2 Vu Hai NGUYEN
2014-04-14 6:39 ` Michal Kazior
2014-04-14 8:10 ` Kalle Valo
2014-04-14 15:49 ` RE : " Vu Hai NGUYEN
2014-04-15 8:20 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
2014-04-15 11:02 ` Kalle Valo
2014-04-16 11:51 ` RE : " Vu Hai NGUYEN
2014-04-16 11:51 ` Vu Hai NGUYEN
2014-04-24 6:35 ` Kalle Valo
2014-04-24 9:03 ` RE : " Vu Hai NGUYEN
2014-04-24 9:41 ` Michal Kazior
2014-04-24 10:18 ` Yeoh Chun-Yeow
2014-04-30 12:39 ` RE : " Vu Hai NGUYEN
2014-05-07 7:36 ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
2014-05-07 7:48 ` Michal Kazior
2014-05-07 8:16 ` Yeoh Chun-Yeow
2014-05-07 8:16 ` RE : " Vu Hai NGUYEN
2014-05-07 9:26 ` Janusz Dziedzic
2014-05-07 14:11 ` Ben Greear
2014-05-07 14:21 ` Adrian Chadd
2014-05-07 14:33 ` Ben Greear
2014-05-07 14:50 ` Adrian Chadd
2014-05-07 15:09 ` Ben Greear
2014-04-14 8:05 ` [PATCH] ath10k: double check bmi xfer pointers Kalle Valo
2014-04-14 8:05 ` Kalle Valo
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.