Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Matthias Klein]

I also try to get a pcie wifi card (Compex WLE600VX) running in the 
clearfog pro board with kernel 4.4.

As I read in this thread the "irg.mode=1" shoud help: 
https://www.spinics.net/lists/linux-wireless/msg155685.html

But it is not working for me:

debian@clearfog:~$ lsmod
Module Size Used by
8021q 36864 0
garp 16384 1 8021q
mrp 20480 1 8021q
stp 16384 1 garp
llc 16384 2 stp,garp
bnep 20480 2
ath10k_pci 45056 0
ath10k_core 249856 1 ath10k_pci
ath 32768 1 ath10k_core
mac80211 786432 1 ath10k_core
bluetooth 385024 7 bnep
qcserial 16384 0
cfg80211 561152 3 ath,mac80211,ath10k_core
usb_wwan 16384 1 qcserial
qmi_wwan 24576 0
cdc_wdm 20480 1 qmi_wwan
usbserial 40960 2 qcserial,usb_wwan
usbnet 36864 1 qmi_wwan
mii 16384 1 usbnet
rfkill 32768 4 cfg80211,bluetooth
firmware_class 24576 1 ath10k_core
marvell_cesa 45056 0
ehci_orion 16384 0
des_generic 28672 1 marvell_cesa
mcp3021 16384 0
hwmon 16384 1 mcp3021
evbug 16384 0
uio_pdrv_genirq 16384 0
uio 20480 1 uio_pdrv_genirq
fuse 102400 1
ipv6 532480 0
autofs4 36864 2

debian@clearfog:~$ uname -a
Linux clearfog 4.4.15-clearfog #1 SMP Wed Oct 5 00:03:36 UTC 2016 armv7l 
GNU/Linux

debian@clearfog:~$ sudo rmmod ath10k_pci ath10k_core
debian@clearfog:~$ sudo modprobe ath10k_core
debian@clearfog:~$ sudo modprobe ath10k_pci
[ 69.529351] ath10k_pci 0000:01:00.0: Refused to change power state, 
currently in D3
[ 69.567989] ath10k_pci 0000:01:00.0: failed to wake up device : -110
[ 69.575267] ath10k_pci: probe of 0000:01:00.0 failed with error -110

debian@clearfog:~$ sudo rmmod ath10k_pci ath10k_core
debian@clearfog:~$ sudo modprobe ath10k_core
debian@clearfog:~$ sudo modprobe ath10k_pci irq_mode=1
[ 97.899370] ath10k_pci 0000:01:00.0: Refused to change power state, 
currently in D3
[ 97.938045] ath10k_pci 0000:01:00.0: failed to wake up device : -110
[ 97.944973] ath10k_pci: probe of 0000:01:00.0 failed with error -110

debian@clearfog:~$ lspci -vvv
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 
(prog-if 00 [Normal decode])
         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr+ Stepping- SERR+ FastB2B- DisINTx-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
         Latency: 0, Cache Line Size: 64 bytes
         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
         I/O behind bridge: 0000f000-00000fff
         Memory behind bridge: f8000000-f82fffff
         Prefetchable memory behind bridge: 00000000-000fffff
         Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- <SERR- <PERR-
         BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                 PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
         Capabilities: <access denied>

00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 
(prog-if 00 [Normal decode])
         Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr+ Stepping- SERR+ FastB2B- DisINTx-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
         Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
         I/O behind bridge: 0000f000-00000fff
         Memory behind bridge: fff00000-000fffff
         Prefetchable memory behind bridge: 00000000-000fffff
         Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- <SERR- <PERR-
         BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
                 PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
         Capabilities: <access denied>

01:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless 
Network Adapter (rev ff) (prog-if ff)
         !!! Unknown header type 7f


Something else what I can try?

Best regards,
Matthias

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Michal Kazior]

On 24 October 2016 at 12:18, Matthias Klein <matthias.klein@optimeas.de> wr=
ote:
> I also try to get a pcie wifi card (Compex WLE600VX) running in the clear=
fog
> pro board with kernel 4.4.
>
> As I read in this thread the "irg.mode=3D1" shoud help:
> https://www.spinics.net/lists/linux-wireless/msg155685.html
>
> But it is not working for me:
>
[...]
> [ 97.899370] ath10k_pci 0000:01:00.0: Refused to change power state,
> currently in D3
> [ 97.938045] ath10k_pci 0000:01:00.0: failed to wake up device : -110
> [ 97.944973] ath10k_pci: probe of 0000:01:00.0 failed with error -110
[...]
> 01:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
> Network Adapter (rev ff) (prog-if ff)
>         !!! Unknown header type 7f

The device looks completely unresponsive.

I don't think this is MSI problem. This error happens before
interrupts are even set up.

I suspect platform/PCI/PM specific problem. I would suggest bisecting
the kernel and seeing which patch is making the difference.

I (naively) went through pci/pm git log and found the following was
applied on 4.7-rc2 (i.e. prior to 4.7 release):

 commit 006d44e49a259b39947366728d65a873a19aadc0
 Author: Mika Westerberg <mika.westerberg@linux.intel.com>
 Date:   Thu Jun 2 11:17:15 2016 +0300

     PCI: Add runtime PM support for PCIe ports

>From reading the commit log it seems to me like it could be it.

ath10k tries to wake up the device during probing before it starts
talking to it and it does so through MMIO/PCI config space. If it's
not mapped properly then driver will not be able to wake it up and
will timeout waiting for it.

Can you try cherry-picking it into your 4.4.24 and see if it helps?


Micha=C5=82

Re[2]: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Matthias Klein]

>I (naively) went through pci/pm git log and found the following was
>applied on 4.7-rc2 (i.e. prior to 4.7 release):
>
>  commit 006d44e49a259b39947366728d65a873a19aadc0
>  Author: Mika Westerberg <mika.westerberg@linux.intel.com>
>  Date:   Thu Jun 2 11:17:15 2016 +0300
>
>      PCI: Add runtime PM support for PCIe ports
>
>From reading the commit log it seems to me like it could be it.
>
>ath10k tries to wake up the device during probing before it starts
>talking to it and it does so through MMIO/PCI config space. If it's
>not mapped properly then driver will not be able to wake it up and
>will timeout waiting for it.
>
>Can you try cherry-picking it into your 4.4.24 and see if it helps?
>
>
Thanks for the help!

Until now I did not compile a kernel for the board.
I will give it a try and come back with the results ...


Best regards,
Matthias

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

>> Can you try cherry-picking it into your 4.4.24 and see if it helps?
I created a patch which should work for 4.4.24 (at least for arch linux 
arm it applied successful)

diff --git a/drivers/pci/pcie/portdrv_core.c 
b/drivers/pci/pcie/portdrv_core.c
index 88122dc..f2caf38 100644
--- a/drivers/pci/pcie/portdrv_core.c
+++ b/drivers/pci/pcie/portdrv_core.c
@@ -8,6 +8,7 @@

  #include <linux/module.h>
  #include <linux/pci.h>
+#include <linux/pm_runtime.h>
  #include <linux/kernel.h>
  #include <linux/errno.h>
  #include <linux/pm.h>
@@ -350,6 +351,8 @@ static int pcie_device_init(struct pci_dev *pdev, 
int service, int irq)
          return retval;
      }

+        pm_runtime_no_callbacks(device);
+
      return 0;
  }

diff --git a/drivers/pci/pcie/portdrv_pci.c b/drivers/pci/pcie/portdrv_pci.c
index be35da2..1624cc3 100644
--- a/drivers/pci/pcie/portdrv_pci.c
+++ b/drivers/pci/pcie/portdrv_pci.c
@@ -93,6 +93,28 @@ static int pcie_port_resume_noirq(struct device *dev)
      return 0;
  }

+static int pcie_port_runtime_suspend(struct device *dev)
+{
+    return to_pci_dev(dev)->bridge_d3 ? 0 : -EBUSY;
+}
+
+static int pcie_port_runtime_resume(struct device *dev)
+{
+    return 0;
+}
+
+static int pcie_port_runtime_idle(struct device *dev)
+{
+    /*
+     * Assume the PCI core has set bridge_d3 whenever it thinks the port
+     * should be good to go to D3.  Everything else, including moving
+     * the port to D3, is handled by the PCI core.
+     */
+    return to_pci_dev(dev)->bridge_d3 ? 0 : -EBUSY;
+}
++
+
+
  static const struct dev_pm_ops pcie_portdrv_pm_ops = {
      .suspend    = pcie_port_device_suspend,
      .resume        = pcie_port_device_resume,
@@ -101,6 +123,9 @@ static const struct dev_pm_ops pcie_portdrv_pm_ops = {
      .poweroff    = pcie_port_device_suspend,
      .restore    = pcie_port_device_resume,
      .resume_noirq    = pcie_port_resume_noirq,
+    .runtime_suspend = pcie_port_runtime_suspend,
+    .runtime_resume    = pcie_port_runtime_resume,
+    .runtime_idle    = pcie_port_runtime_idle,
  };

  #define PCIE_PORTDRV_PM_OPS    (&pcie_portdrv_pm_ops)
@@ -139,11 +164,39 @@ static int pcie_portdrv_probe(struct pci_dev *dev,
       * it by default.
       */
      dev->d3cold_allowed = false;
+
+    /*
+     * Prevent runtime PM if the port is advertising support for PCIe
+     * hotplug.  Otherwise the BIOS hotplug SMI code might not be able
+     * to enumerate devices behind this port properly (the port is
+     * powered down preventing all config space accesses to the
+     * subordinate devices).  We can't be sure for native PCIe hotplug
+     * either so prevent that as well.
+     */
+    if (!dev->is_hotplug_bridge) {
+        /*
+         * Keep the port resumed 100ms to make sure things like
+         * config space accesses from userspace (lspci) will not
+         * cause the port to repeatedly suspend and resume.
+         */
+        pm_runtime_set_autosuspend_delay(&dev->dev, 100);
+        pm_runtime_use_autosuspend(&dev->dev);
+        pm_runtime_mark_last_busy(&dev->dev);
+        pm_runtime_put_autosuspend(&dev->dev);
+        pm_runtime_allow(&dev->dev);
+    }
+
      return 0;
  }

  static void pcie_portdrv_remove(struct pci_dev *dev)
  {
+    if (!dev->is_hotplug_bridge) {
+        pm_runtime_forbid(&dev->dev);
+        pm_runtime_get_noresume(&dev->dev);
+        pm_runtime_dont_use_autosuspend(&dev->dev);
+    }
+
      pcie_port_device_remove(dev);
  }

Just compiling the kernel... lets see what happens

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

> I created a patch which should work for 4.4.24 (at least for arch 
> linux arm it applied successful)
>
> Just compiling the kernel... lets see what happens
Did not work. First, there was a + which was wrong, guess i have this 
simply overseen. After fixing that i got:

drivers/pci/pcie/portdrv_pci.c: In function 'pcie_port_runtime_suspend':
drivers/pci/pcie/portdrv_pci.c:98:24: error: 'struct pci_dev' has no 
member named 'bridge_d3'
   return to_pci_dev(dev)->bridge_d3 ? 0 : -EBUSY;
                         ^~
drivers/pci/pcie/portdrv_pci.c: In function 'pcie_port_runtime_idle':
drivers/pci/pcie/portdrv_pci.c:113:24: error: 'struct pci_dev' has no 
member named 'bridge_d3'
   return to_pci_dev(dev)->bridge_d3 ? 0 : -EBUSY;
                         ^~
drivers/pci/pcie/portdrv_pci.c:114:1: warning: control reaches end of 
non-void function [-Wreturn-type]
  }
  ^
drivers/pci/pcie/portdrv_pci.c: In function 'pcie_port_runtime_suspend':
drivers/pci/pcie/portdrv_pci.c:99:1: warning: control reaches end of 
non-void function [-Wreturn-type]
  }
  ^
make[3]: *** [scripts/Makefile.build:259: 
drivers/pci/pcie/portdrv_pci.o] Error 1
make[2]: *** [scripts/Makefile.build:403: drivers/pci/pcie] Error 2
make[1]: *** [scripts/Makefile.build:403: drivers/pci] Error 2
make: *** [Makefile:959: drivers] Error 2
==> ERROR: A failure occurred in build().
     Aborting...

A simple cherry pick does not work in that case.

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

>
>> I (naively) went through pci/pm git log and found the following was
>> applied on 4.7-rc2 (i.e. prior to 4.7 release):
>>
>>  commit 006d44e49a259b39947366728d65a873a19aadc0
>>  Author: Mika Westerberg <mika.westerberg@linux.intel.com>
>>  Date:   Thu Jun 2 11:17:15 2016 +0300
>>
>>      PCI: Add runtime PM support for PCIe ports
>>
>> From reading the commit log it seems to me like it could be it.
>>
>> ath10k tries to wake up the device during probing before it starts
>> talking to it and it does so through MMIO/PCI config space. If it's
>> not mapped properly then driver will not be able to wake it up and
>> will timeout waiting for it.
>>
>> Can you try cherry-picking it into your 4.4.24 and see if it helps?
>>
>>
> Thanks for the help!
>
> Until now I did not compile a kernel for the board.
> I will give it a try and come back with the results ...
>
>
> Best regards,
> Matthias
>
Any news on that? I am in contact with the support of SolidRun 
(clearfog). Unfortunately they will stay at 4.4.x - no upgrade to 4.8 
nor 4.9 planned. Unfortunately the commit (006d44e) is incompatible to 
4.4. because pci_dev does not know bridge_d3

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

 >> I (naively) went through pci/pm git log and found the following was
 >> applied on 4.7-rc2 (i.e. prior to 4.7 release):
 >>
 >>  commit 006d44e49a259b39947366728d65a873a19aadc0
 >>  Author: Mika Westerberg <mika.westerberg@linux.intel.com>
 >>  Date:   Thu Jun 2 11:17:15 2016 +0300
 >>
 >>      PCI: Add runtime PM support for PCIe ports
 >>
 >> From reading the commit log it seems to me like it could be it.
 >>
 >> ath10k tries to wake up the device during probing before it starts
 >> talking to it and it does so through MMIO/PCI config space. If it's
 >> not mapped properly then driver will not be able to wake it up and
 >> will timeout waiting for it.
 >>
 >> Can you try cherry-picking it into your 4.4.24 and see if it helps?
 >>
 >>
 > Thanks for the help!
 >
 > Until now I did not compile a kernel for the board.
 > I will give it a try and come back with the results ...
 >
 >
 > Best regards,
 > Matthias
 >
  good news, just got a message from the support with a quote from one 
of their developers:
  Have the customer that needs support for the ath cards to use this 
branch. https://github.com/SolidRun/linux-stable/tree/linux-4.4.y-marvell
  note that the device-tree is board specific and for now they should 
create a symlink from their board file to armada-388-clearfog.dtb

  when i look at the change, 
https://github.com/SolidRun/linux-stable/commit/e12aa24ca56ca773b5c59a3cc2915b4e82e6be18 
this looks exactly like the problem we had :)

  I will try this today.

  Regards
  Oli

compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. 
Unfortunately, it does not work.
I am not sure if this is a bug in the module or even in some pci-e 
driver. Maybe someone could tell me that.

dmesg:

[ 5.348307] mvebu-pcie soc:pcie-controller: 
/soc/pcie-controller/pcie@2,0: reset gpio is active low
[ 5.358026] mvebu-pcie soc:pcie-controller: 
/soc/pcie-controller/pcie@3,0: reset gpio is active low
[ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 5.434680] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
[ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
[ 5.447295] PCI: bus0: Fast back to back transfers disabled
[ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus 
00-00]), reconfiguring
[ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus 
00-00]), reconfiguring
[ 5.468986] PCI: bus1: Fast back to back transfers enabled
[ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000
[ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[ 5.474667] pci 0000:02:00.0: supports D1 D2
[ 5.511395] PCI: bus2: Fast back to back transfers enabled
[ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134
[ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem 0xf8000000-0xf82fffff]
[ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01]
[ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8000000-0xf81fffff 
64bit]
[ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != 
0xffffffff)
[ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 
0xffffffff)
[ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem 0xf8200000-0xf820ffff 
pref]
[ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02]
[ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff]
[ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142)

lspci:


[root@alarm alarm]# lspci
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac 
Wireless Network Adapter (rev ff)

Thanks!

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Sebastian Gottschall]

could you please attach a full log? i see no driver loading here. this 
is just a small part of the kernel boot log, but no driver intialisation

Am 15.10.2016 um 16:00 schrieb Oliver Zemann:
> I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. 
> Unfortunately, it does not work.
> I am not sure if this is a bug in the module or even in some pci-e 
> driver. Maybe someone could tell me that.
>
> dmesg:
>
> [ 5.348307] mvebu-pcie soc:pcie-controller: 
> /soc/pcie-controller/pcie@2,0: reset gpio is active low
> [ 5.358026] mvebu-pcie soc:pcie-controller: 
> /soc/pcie-controller/pcie@3,0: reset gpio is active low
> [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 
> 0000:00
> [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
> [ 5.434680] pci_bus 0000:00: root bus resource [mem 
> 0xf8000000-0xffdfffff]
> [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff]
> [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
> [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
> [ 5.447295] PCI: bus0: Fast back to back transfers disabled
> [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus 
> 00-00]), reconfiguring
> [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus 
> 00-00]), reconfiguring
> [ 5.468986] PCI: bus1: Fast back to back transfers enabled
> [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
> [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000
> [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
> [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
> [ 5.474667] pci 0000:02:00.0: supports D1 D2
> [ 5.511395] PCI: bus2: Fast back to back transfers enabled
> [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
> [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134
> [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem 
> 0xf8000000-0xf82fffff]
> [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01]
> [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem 
> 0xf8000000-0xf81fffff 64bit]
> [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != 
> 0xffffffff)
> [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 
> 0xffffffff)
> [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem 
> 0xf8200000-0xf820ffff pref]
> [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02]
> [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff]
> [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142)
>
> lspci:
>
>
> [root@alarm alarm]# lspci
> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac 
> Wireless Network Adapter (rev ff)

>
> Thanks!
>
>


-- 
Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

I hope thats what you mean. I am not that familiar with linux drivers

[root@alarm ~]# lsmod
Module                  Size  Used by
ath10k_pci             30053  0
ath10k_core           193491  1 ath10k_pci
ath                    18176  1 ath10k_core
mac80211              405739  1 ath10k_core
cfg80211              215848  3 ath,mac80211,ath10k_core
rfkill                 14391  2 cfg80211
marvell_cesa           25839  0
des_generic            16747  1 marvell_cesa
sch_fq_codel            7757  9
ip_tables              11170  0
x_tables               11520  1 ip_tables
autofs4                22783  2
[root@alarm ~]# rmmod ath10k_pci ath10k_core
[root@alarm ~]# modprobe ath10k_core
[root@alarm ~]# modprobe ath10k_pci
[28501.637198] ath10k_pci 0000:02:00.0: Refused to change power state, 
currently in D3
[28501.675138] ath10k_pci 0000:02:00.0: failed to wake up device : -110
[28501.681625] ath10k_pci: probe of 0000:02:00.0 failed with error -110


Am 15.10.2016 um 16:44 schrieb Sebastian Gottschall:
> could you please attach a full log? i see no driver loading here. this 
> is just a small part of the kernel boot log, but no driver intialisation
>
> Am 15.10.2016 um 16:00 schrieb Oliver Zemann:
>> I have a clearfog pro (arm7) from marvel and bought a pcie wifi card. 
>> Unfortunately, it does not work.
>> I am not sure if this is a bug in the module or even in some pci-e 
>> driver. Maybe someone could tell me that.
>>
>> dmesg:
>>
>> [ 5.348307] mvebu-pcie soc:pcie-controller: 
>> /soc/pcie-controller/pcie@2,0: reset gpio is active low
>> [ 5.358026] mvebu-pcie soc:pcie-controller: 
>> /soc/pcie-controller/pcie@3,0: reset gpio is active low
>> [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 
>> 0000:00
>> [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
>> [ 5.434680] pci_bus 0000:00: root bus resource [mem 
>> 0xf8000000-0xffdfffff]
>> [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff]
>> [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
>> [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
>> [ 5.447295] PCI: bus0: Fast back to back transfers disabled
>> [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus 
>> 00-00]), reconfiguring
>> [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus 
>> 00-00]), reconfiguring
>> [ 5.468986] PCI: bus1: Fast back to back transfers enabled
>> [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
>> [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000
>> [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 
>> 64bit]
>> [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
>> [ 5.474667] pci 0000:02:00.0: supports D1 D2
>> [ 5.511395] PCI: bus2: Fast back to back transfers enabled
>> [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
>> [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134
>> [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem 
>> 0xf8000000-0xf82fffff]
>> [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01]
>> [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem 
>> 0xf8000000-0xf81fffff 64bit]
>> [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != 
>> 0xffffffff)
>> [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 != 
>> 0xffffffff)
>> [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem 
>> 0xf8200000-0xf820ffff pref]
>> [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02]
>> [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff]
>> [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142)
>>
>> lspci:
>>
>>
>> [root@alarm alarm]# lspci
>> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
>> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
>> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac 
>> Wireless Network Adapter (rev ff)
>
>>
>> Thanks!
>>
>>
>
>

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

The problem is gone with kernel 4.7.3 on armbian - both compex cards 
work (wle600, wle900), unfortunately that kernel does not support sfp 
(seems like its kind of proprietary drivers from clearfog). So its a 
driver issue but i have no clue who to contact or where to file a bug 
report. The only available kernel which supports sfp (from solidrun, 
vendor of the clearfog board) is 4.4.23

I am wondering if i could simply checkout the 4.4.x sources, merge the 
atheros drivers in it and try to rebuild the kernel?



Am 15.10.2016 um 19:04 schrieb Oliver Zemann:
> I hope thats what you mean. I am not that familiar with linux drivers
>
> [root@alarm ~]# lsmod
> Module                  Size  Used by
> ath10k_pci             30053  0
> ath10k_core           193491  1 ath10k_pci
> ath                    18176  1 ath10k_core
> mac80211              405739  1 ath10k_core
> cfg80211              215848  3 ath,mac80211,ath10k_core
> rfkill                 14391  2 cfg80211
> marvell_cesa           25839  0
> des_generic            16747  1 marvell_cesa
> sch_fq_codel            7757  9
> ip_tables              11170  0
> x_tables               11520  1 ip_tables
> autofs4                22783  2
> [root@alarm ~]# rmmod ath10k_pci ath10k_core
> [root@alarm ~]# modprobe ath10k_core
> [root@alarm ~]# modprobe ath10k_pci
> [28501.637198] ath10k_pci 0000:02:00.0: Refused to change power state, 
> currently in D3
> [28501.675138] ath10k_pci 0000:02:00.0: failed to wake up device : -110
> [28501.681625] ath10k_pci: probe of 0000:02:00.0 failed with error -110
>
>
> Am 15.10.2016 um 16:44 schrieb Sebastian Gottschall:
>> could you please attach a full log? i see no driver loading here. 
>> this is just a small part of the kernel boot log, but no driver 
>> intialisation
>>
>> Am 15.10.2016 um 16:00 schrieb Oliver Zemann:
>>> I have a clearfog pro (arm7) from marvel and bought a pcie wifi 
>>> card. Unfortunately, it does not work.
>>> I am not sure if this is a bug in the module or even in some pci-e 
>>> driver. Maybe someone could tell me that.
>>>
>>> dmesg:
>>>
>>> [ 5.348307] mvebu-pcie soc:pcie-controller: 
>>> /soc/pcie-controller/pcie@2,0: reset gpio is active low
>>> [ 5.358026] mvebu-pcie soc:pcie-controller: 
>>> /soc/pcie-controller/pcie@3,0: reset gpio is active low
>>> [ 5.421496] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 
>>> 0000:00
>>> [ 5.428390] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
>>> [ 5.434680] pci_bus 0000:00: root bus resource [mem 
>>> 0xf8000000-0xffdfffff]
>>> [ 5.441575] pci_bus 0000:00: root bus resource [bus 00-ff]
>>> [ 5.447083] pci 0000:00:02.0: [11ab:6828] type 01 class 0x060400
>>> [ 5.447198] pci 0000:00:03.0: [11ab:6828] type 01 class 0x060400
>>> [ 5.447295] PCI: bus0: Fast back to back transfers disabled
>>> [ 5.452887] pci 0000:00:02.0: bridge configuration invalid ([bus 
>>> 00-00]), reconfiguring
>>> [ 5.460911] pci 0000:00:03.0: bridge configuration invalid ([bus 
>>> 00-00]), reconfiguring
>>> [ 5.468986] PCI: bus1: Fast back to back transfers enabled
>>> [ 5.474491] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
>>> [ 5.474561] pci 0000:02:00.0: [168c:003c] type 00 class 0x028000
>>> [ 5.474593] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x001fffff 
>>> 64bit]
>>> [ 5.474617] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff 
>>> pref]
>>> [ 5.474667] pci 0000:02:00.0: supports D1 D2
>>> [ 5.511395] PCI: bus2: Fast back to back transfers enabled
>>> [ 5.516894] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
>>> [ 5.516905] pci 0000:02:00.0: of_irq_parse_pci() failed with rc=134
>>> [ 5.523207] pci 0000:00:03.0: BAR 14: assigned [mem 
>>> 0xf8000000-0xf82fffff]
>>> [ 5.530098] pci 0000:00:02.0: PCI bridge to [bus 01]
>>> [ 5.535082] pci 0000:02:00.0: BAR 0: assigned [mem 
>>> 0xf8000000-0xf81fffff 64bit]
>>> [ 5.542413] pci 0000:02:00.0: BAR 0: error updating (0xf8000004 != 
>>> 0xffffffff)
>>> [ 5.549652] pci 0000:02:00.0: BAR 0: error updating (high 0x000000 
>>> != 0xffffffff)
>>> [ 5.557155] pci 0000:02:00.0: BAR 6: assigned [mem 
>>> 0xf8200000-0xf820ffff pref]
>>> [ 5.564396] pci 0000:00:03.0: PCI bridge to [bus 02]
>>> [ 5.569372] pci 0000:00:03.0: bridge window [mem 0xf8000000-0xf82fffff]
>>> [ 5.576256] pcieport 0000:00:03.0: enabling device (0140 -> 0142)
>>>
>>> lspci:
>>>
>>>
>>> [root@alarm alarm]# lspci
>>> 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
>>> 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04)
>>> 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac 
>>> Wireless Network Adapter (rev ff)
>>
>>>
>>> Thanks!
>>>
>>>
>>
>>
>

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Michal Kazior]

On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote:
> The problem is gone with kernel 4.7.3 on armbian - both compex cards work
> (wle600, wle900), unfortunately that kernel does not support sfp (seems l=
ike
> its kind of proprietary drivers from clearfog). So its a driver issue but=
 i
> have no clue who to contact or where to file a bug report. The only
> available kernel which supports sfp (from solidrun, vendor of the clearfo=
g
> board) is 4.4.23
>
> I am wondering if i could simply checkout the 4.4.x sources, merge the
> atheros drivers in it and try to rebuild the kernel?

That's what backports[1] are for.

The problem could be in the pci subsystem though so backporting the
driver itself might not solve your problem.

[1]: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports


Micha=C5=82

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Jonas Gorski]

Hi,

On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote:
> The problem is gone with kernel 4.7.3 on armbian - both compex cards work
> (wle600, wle900),

Interesting to know this issue isn't present in 4.7 - I also
encountered it in 4.4 with LEDE.

> unfortunately that kernel does not support sfp (seems like
> its kind of proprietary drivers from clearfog).

They aren't really proprietary, they are proper patches that were
submitted as RFC once, so it shouldn't be much effort to port them to
e.g. 4.7. Anyways ...

> So its a driver issue but i
> have no clue who to contact or where to file a bug report. The only
> available kernel which supports sfp (from solidrun, vendor of the clearfog
> board) is 4.4.23
>
> I am wondering if i could simply checkout the 4.4.x sources, merge the
> atheros drivers in it and try to rebuild the kernel?

the issue seems to be that MSI interrupts do not work on 4.4 (at least
with ath10k, didn't have any other drivers that support it to test).
Your options are either to disable support for them in the kernel
config, or pass irq_mode=1 to ath10k_pci on probe to force legacy
interrupts; it should work then properly.


Regards
Jonas

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

Thanks for that info Jonas. I passed optargs=irq_mode=1 in 
/boot/uEnv.txt on archlinux arm (kernel 4.4.23) and verified with

[root@alarm ~]# cat /proc/cmdline
console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1

But it still does not work:

[root@alarm ~]# rmmod ath10k_pci
[root@alarm ~]# modprobe ath10k_pci
[   28.791404] ath10k_pci 0000:02:00.0: Refused to change power state, 
currently in D3
[   28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110
[   28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110

Did i do something wrong? If somehow possible, i would prefer to not 
rebuild the kernel and somehow configure the existing one without changes.

Kind regards

Oli


Am 22.10.2016 um 13:55 schrieb Jonas Gorski:
> Hi,
>
> On 21 October 2016 at 18:25, Oliver Zemann <oliver.zemann@gmail.com> wrote:
>> The problem is gone with kernel 4.7.3 on armbian - both compex cards work
>> (wle600, wle900),
> Interesting to know this issue isn't present in 4.7 - I also
> encountered it in 4.4 with LEDE.
>
>> unfortunately that kernel does not support sfp (seems like
>> its kind of proprietary drivers from clearfog).
> They aren't really proprietary, they are proper patches that were
> submitted as RFC once, so it shouldn't be much effort to port them to
> e.g. 4.7. Anyways ...
>
>> So its a driver issue but i
>> have no clue who to contact or where to file a bug report. The only
>> available kernel which supports sfp (from solidrun, vendor of the clearfog
>> board) is 4.4.23
>>
>> I am wondering if i could simply checkout the 4.4.x sources, merge the
>> atheros drivers in it and try to rebuild the kernel?
> the issue seems to be that MSI interrupts do not work on 4.4 (at least
> with ath10k, didn't have any other drivers that support it to test).
> Your options are either to disable support for them in the kernel
> config, or pass irq_mode=1 to ath10k_pci on probe to force legacy
> interrupts; it should work then properly.
>
>
> Regards
> Jonas

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Jonas Gorski]

On 23 October 2016 at 17:53, Oliver Zemann <oliver.zemann@gmail.com> wrote:
> Thanks for that info Jonas. I passed optargs=irq_mode=1 in /boot/uEnv.txt on
> archlinux arm (kernel 4.4.23) and verified with
>
> [root@alarm ~]# cat /proc/cmdline
> console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1
>
> But it still does not work:
>
> [root@alarm ~]# rmmod ath10k_pci
> [root@alarm ~]# modprobe ath10k_pci
> [   28.791404] ath10k_pci 0000:02:00.0: Refused to change power state,
> currently in D3
> [   28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110
> [   28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110
>
> Did i do something wrong? If somehow possible, i would prefer to not rebuild
> the kernel and somehow configure the existing one without changes.

For the kernel command line you need to prefix with the module name,
i.e. "ath10k_pci.irq_mode=1". Alternative is while modprobing with
"modprobe ath10_pci irq_mode=1". See
<https://www.kernel.org/doc/Documentation/kernel-parameters.txt> for
details.

Regards
Jonas

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

Thanks, but its still not working. I dont get any error now when i do 
modprobe and installed is the wle900

[root@alarm alarm]# rmmod ath10k_pci
[root@alarm alarm]# modprobe ath10k_pci irq_mode=1

but:

[root@alarm alarm]# dmesg | grep ath10k
[  220.356314] ath10k_pci 0000:02:00.0: Refused to change power state, 
currently in D3
[  220.394265] ath10k_pci 0000:02:00.0: failed to wake up device : -110
[  220.400770] ath10k_pci: probe of 0000:02:00.0 failed with error -110

[root@alarm alarm]# cat /proc/cmdline
console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait ath10k_pci.irq_mode=1

Thanks for your patience

Regards
Oli

Am 23.10.2016 um 21:33 schrieb Jonas Gorski:
> On 23 October 2016 at 17:53, Oliver Zemann <oliver.zemann@gmail.com> wrote:
>> Thanks for that info Jonas. I passed optargs=irq_mode=1 in /boot/uEnv.txt on
>> archlinux arm (kernel 4.4.23) and verified with
>>
>> [root@alarm ~]# cat /proc/cmdline
>> console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait irq_mode=1
>>
>> But it still does not work:
>>
>> [root@alarm ~]# rmmod ath10k_pci
>> [root@alarm ~]# modprobe ath10k_pci
>> [   28.791404] ath10k_pci 0000:02:00.0: Refused to change power state,
>> currently in D3
>> [   28.829352] ath10k_pci 0000:02:00.0: failed to wake up device : -110
>> [   28.835861] ath10k_pci: probe of 0000:02:00.0 failed with error -110
>>
>> Did i do something wrong? If somehow possible, i would prefer to not rebuild
>> the kernel and somehow configure the existing one without changes.
> For the kernel command line you need to prefix with the module name,
> i.e. "ath10k_pci.irq_mode=1". Alternative is while modprobing with
> "modprobe ath10_pci irq_mode=1". See
> <https://www.kernel.org/doc/Documentation/kernel-parameters.txt> for
> details.
>
> Regards
> Jonas

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Jonas Gorski]

Hi,

(please don't toppost)

On 23 October 2016 at 21:42, Oliver Zemann <oliver.zemann@gmail.com> wrote:
> Thanks, but its still not working. I dont get any error now when i do
> modprobe and installed is the wle900
>
> [root@alarm alarm]# rmmod ath10k_pci
> [root@alarm alarm]# modprobe ath10k_pci irq_mode=1

Strange, this was working for me with a Sparklan WPEA-352ACN.

>
> but:
>
> [root@alarm alarm]# dmesg | grep ath10k
> [  220.356314] ath10k_pci 0000:02:00.0: Refused to change power state,
> currently in D3

Maybe there is a separate issue related to this. I don't remember
seeing this message in my kernel log. (At least to me) it would be
interesting to know if it works using a LEDE image, or if it fails
there as well. I don't have a Compex card here.

You can find an sd-card image at
https://downloads.lede-project.org/snapshots/targets/mvebu/generic/ -
it won't contain any wifi drivers though, you will need to install
them separately - easiest by providing internet access over the wan
port (the single ethernet port for the pro, it defaults to dhcp
client), then running "opkg install kmod-ath10k" on shell.

Note that this kernel has MSI disabled, so you don't need to do
anything there extra.

> [  220.394265] ath10k_pci 0000:02:00.0: failed to wake up device : -110
> [  220.400770] ath10k_pci: probe of 0000:02:00.0 failed with error -110
>
> [root@alarm alarm]# cat /proc/cmdline
> console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait ath10k_pci.irq_mode=1
>
> Thanks for your patience

Regards
Jonas

Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7

[Oliver Zemann]

>
> (please don't toppost)
Did not know that this is forbidden, sorry
> You can find an sd-card image at
> https://downloads.lede-project.org/snapshots/targets/mvebu/generic/ -
> it won't contain any wifi drivers though, you will need to install
> them separately - easiest by providing internet access over the wan
> port (the single ethernet port for the pro, it defaults to dhcp
> client), then running "opkg install kmod-ath10k" on shell.
I used dd to install the latest image from today to the SD. I am 
connected through usb with screen, thats a very nice feature of the 
board :)
I logged in, updated the packages with opkg update and then installed 
kmod-ath10k but i received many errors:

[  380.987440] ath10k_core: Unknown symbol cfg80211_find_ie_match (err 0)
[  380.993996] ath10k_core: Unknown symbol ieee80211_wake_queue (err 0)
[  381.000383] ath10k_core: Unknown symbol ieee80211_find_sta (err 0)
[  381.006586] ath10k_core: Unknown symbol 
ieee80211_stop_rx_ba_session_offl (err 0)
[  381.014101] ath10k_core: Unknown symbol ieee80211_tx_status_irqsafe 
(err 0)
[  381.021096] ath10k_core: Unknown symbol 
ieee80211_iter_chan_contexts_atomic (err 0)
[  381.028778] ath10k_core: Unknown symbol __cfg80211_alloc_reply_skb 
(err 0)
[  381.035681] ath10k_core: Unknown symbol __cfg80211_alloc_event_skb 
(err 0)
[  381.042584] ath10k_core: Unknown symbol cfg80211_put_bss (err 0)
[  381.048623] ath10k_core: Unknown symbol ieee80211_bss_get_ie (err 0)
[  381.055005] ath10k_core: Unknown symbol wiphy_to_ieee80211_hw (err 0)
[  381.061472] ath10k_core: Unknown symbol __cfg80211_send_event_skb (err 0)
[  381.068284] ath10k_core: Unknown symbol ath_reg_notifier_apply (err 0)
[  381.074878] ath10k_core: Unknown symbol ieee80211_queue_delayed_work 
(err 0)
[  381.081959] ath10k_core: Unknown symbol ieee80211_proberesp_get (err 0)
[  381.088610] ath10k_core: Unknown symbol ieee80211_find_sta_by_ifaddr 
(err 0)
[  381.095689] ath10k_core: Unknown symbol 
ieee80211_remain_on_channel_expired (err 0)
[  381.103379] ath10k_core: Unknown symbol ath_is_world_regd (err 0)
[  381.109503] ath10k_core: Unknown symbol ieee80211_wake_queues (err 0)
[  381.115965] ath10k_core: Unknown symbol ieee80211_report_low_ack (err 0)
[  381.122691] ath10k_core: Unknown symbol ieee80211_beacon_get_template 
(err 0)
[  381.129855] ath10k_core: Unknown symbol ieee80211_free_txskb (err 0)
[  381.136232] ath10k_core: Unknown symbol ieee80211_alloc_hw_nm (err 0)
[  381.142699] ath10k_core: Unknown symbol cfg80211_get_bss (err 0)
[  381.148731] ath10k_core: Unknown symbol ieee80211_tx_dequeue (err 0)
[  381.155111] ath10k_core: Unknown symbol __ieee80211_get_channel (err 0)
[  381.161755] ath10k_core: Unknown symbol cfg80211_vendor_cmd_reply (err 0)
[  381.168574] ath10k_core: Unknown symbol ieee80211_tx_status (err 0)
[  381.174866] ath10k_core: Unknown symbol ieee80211_stop_queue (err 0)
[  381.181246] ath10k_core: Unknown symbol ieee80211_ready_on_channel 
(err 0)
[  381.188142] ath10k_core: Unknown symbol ieee80211_stop_queues (err 0)
[  381.194621] ath10k_core: Unknown symbol ieee80211_scan_completed (err 0)
[  381.201349] ath10k_core: Unknown symbol 
ieee80211_iterate_active_interfaces_atomic (err 0)
[  381.209651] ath10k_core: Unknown symbol 
ieee80211_channel_to_frequency (err 0)
[  381.216896] ath10k_core: Unknown symbol ieee80211_unregister_hw (err 0)
[  381.223537] ath10k_core: Unknown symbol dfs_pattern_detector_init (err 0)
[  381.230354] ath10k_core: Unknown symbol ath_regd_init (err 0)
[  381.236119] ath10k_core: Unknown symbol ieee80211_csa_update_counter 
(err 0)
[  381.243195] ath10k_core: Unknown symbol ieee80211_beacon_get_tim (err 0)
[  381.249924] ath10k_core: Unknown symbol ieee80211_hdrlen (err 0)
[  381.255951] ath10k_core: Unknown symbol 
ieee80211_start_rx_ba_session_offl (err 0)
[  381.263548] ath10k_core: Unknown symbol ieee80211_radar_detected (err 0)
[  381.270276] ath10k_core: Unknown symbol ieee80211_csa_is_complete (err 0)
[  381.277090] ath10k_core: Unknown symbol ieee80211_queue_work (err 0)
[  381.283475] ath10k_core: Unknown symbol cfg80211_find_vendor_ie (err 0)
[  381.290123] ath10k_core: Unknown symbol ieee80211_csa_finish (err 0)
[  381.296498] ath10k_core: Unknown symbol ieee80211_rx_napi (err 0)
[  381.330745] ath10k_pci: Unknown symbol ath10k_warn (err 0)
[  381.336261] ath10k_pci: Unknown symbol ath10k_err (err 0)
[  381.341699] ath10k_pci: Unknown symbol ath10k_print_driver_info (err 0)
[  381.348340] ath10k_pci: Unknown symbol ath10k_htt_hif_tx_complete (err 0)
[  381.355162] ath10k_pci: Unknown symbol 
ath10k_htc_tx_completion_handler (err 0)
[  381.362509] ath10k_pci: Unknown symbol 
ath10k_debug_get_new_fw_crash_data (err 0)
[  381.370020] ath10k_pci: Unknown symbol ath10k_core_create (err 0)
[  381.376143] ath10k_pci: Unknown symbol 
ath10k_htt_rx_pktlog_completion_handler (err 0)
[  381.384097] ath10k_pci: Unknown symbol ath10k_core_destroy (err 0)
[  381.390304] ath10k_pci: Unknown symbol 
ath10k_htc_rx_completion_handler (err 0)
[  381.397637] ath10k_pci: Unknown symbol ath10k_core_register (err 0)
[  381.403930] ath10k_pci: Unknown symbol ath10k_info (err 0)
[  381.409445] ath10k_pci: Unknown symbol backport_dependency_symbol (err 0)
[  381.416255] ath10k_pci: Unknown symbol ath10k_htt_t2h_msg_handler (err 0)
[  381.423072] ath10k_pci: Unknown symbol ath10k_core_unregister (err 0)
[  381.429537] ath10k_pci: Unknown symbol ath10k_htt_txrx_compl_task (err 0)

Regards
Oli