ath10k firmware crash

ath10k firmware crash

[Cedric VONCKEN]

	Hi all, 

	I'm trying to use ath10k in client mode and AP mode with 2 wireless cards (Ap on one card and client on another card).
	The AP mode work, but the client mode always crash. Please find below the ath10k crash information

[   79.131301] ath10k: hardware name qca988x hw2.0 version 0x4100016c
[   79.149420] ath10k: firmware version: 999.999.0.636
[   79.167248] ath10k: target register Dump Location: 0x0040AC14
[   79.185939] ath10k: target Register Dump
[   79.201804] ath10k: [00]: 0x4100016C 0x00000000 0x009C4521 0x00000000
[   79.220184] ath10k: [04]: 0x009C4521 0x00060330 0x00000019 0x00955A00
[   79.238566] ath10k: [08]: 0x0000D0CE 0x00000000 0x0040CC94 0x00000020
[   79.256945] ath10k: [12]: 0x00000000 0x00000000 0x00958360 0x0095836B
[   79.275327] ath10k: [16]: 0x809A0978 0x0040AD94 0x00439304 0x0040D074
[   79.293706] ath10k: [20]: 0x0000FFFF 0x00000000 0x0041EFB8 0x00000000
[   79.312086] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x0343389A
[   79.330466] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F68C
[   79.348845] ath10k: [32]: 0x809B01DA 0x00000000 0x00410110 0x0041937C
[   79.367224] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
[   79.385604] ath10k: [40]: 0x00000000 0x00000000 0x00000071 0x00412700
[   79.403984] ath10k: [44]: 0x00439BB8 0x00000000 0x00000000 0x00400000
[   79.422364] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x00400000 0x0043F68C
[   79.440744] ath10k: [52]: 0x00000001 0x00000000 0x004231F0 0x00400000
[   79.459124] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310

	I'm using openwrt, and I have the same problem with/without configuration option "Firmware optimized for sta operation".

	Is it possible to use at the same time on 2 different cards the AP mode and client mode?

Cedric Voncken 


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

Re: ath10k firmware crash

[Michal Kazior]

On 10 October 2014 16:46, Cedric VONCKEN <cedric.voncken@acksys.fr> wrote:
>         Hi all,
>
>         I'm trying to use ath10k in client mode and AP mode with 2 wireless cards (Ap on one card and client on another card).
>         The AP mode work, but the client mode always crash. Please find below the ath10k crash information
>
> [   79.131301] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> [   79.149420] ath10k: firmware version: 999.999.0.636
> [   79.167248] ath10k: target register Dump Location: 0x0040AC14
> [   79.185939] ath10k: target Register Dump
> [   79.201804] ath10k: [00]: 0x4100016C 0x00000000 0x009C4521 0x00000000
> [   79.220184] ath10k: [04]: 0x009C4521 0x00060330 0x00000019 0x00955A00
> [   79.238566] ath10k: [08]: 0x0000D0CE 0x00000000 0x0040CC94 0x00000020
> [   79.256945] ath10k: [12]: 0x00000000 0x00000000 0x00958360 0x0095836B
> [   79.275327] ath10k: [16]: 0x809A0978 0x0040AD94 0x00439304 0x0040D074
> [   79.293706] ath10k: [20]: 0x0000FFFF 0x00000000 0x0041EFB8 0x00000000
> [   79.312086] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x0343389A
> [   79.330466] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F68C
> [   79.348845] ath10k: [32]: 0x809B01DA 0x00000000 0x00410110 0x0041937C
> [   79.367224] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> [   79.385604] ath10k: [40]: 0x00000000 0x00000000 0x00000071 0x00412700
> [   79.403984] ath10k: [44]: 0x00439BB8 0x00000000 0x00000000 0x00400000
> [   79.422364] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x00400000 0x0043F68C
> [   79.440744] ath10k: [52]: 0x00000001 0x00000000 0x004231F0 0x00400000
> [   79.459124] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310
>
>         I'm using openwrt, and I have the same problem with/without configuration option "Firmware optimized for sta operation".

Can you then provide a crash register dump for 10.1, please? I can't
help you much with the 636 dump.

Are you perhaps trying to run STA with 4addr bridging? If so then make
sure you use recent ath10k as this was known to be a problem.

Can you also provide ath10k traces or debug logs, please?


>         Is it possible to use at the same time on 2 different cards the AP mode and client mode?

Yes, it is possible.


Michał

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

RE: ath10k firmware crash

[voncken]

	Thanks for your reply,

> 
> Can you then provide a crash register dump for 10.1, please? I can't help you
> much with the 636 dump.
> 
Yes I can, but where I find it?

> Are you perhaps trying to run STA with 4addr bridging? If so then make sure
> you use recent ath10k as this was known to be a problem.
> 
Yes I'm testing with 4 addr bridging because I need to bridge this interface. I' ll try without this option.
I'm testing with commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It is the latest version in openwrt. 

> Can you also provide ath10k traces or debug logs, please?
> 
I'll send a trace.
> 
> >         Is it possible to use at the same time on 2 different cards the AP
> mode and client mode?
> 
> Yes, it is possible.
> 
> 
> Michał


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

Re: ath10k firmware crash

[Michal Kazior]

On 13 October 2014 09:35, voncken <cedric.voncken@acksys.fr> wrote:
>         Thanks for your reply,
>
>>
>> Can you then provide a crash register dump for 10.1, please? I can't help you
>> much with the 636 dump.
>>
> Yes I can, but where I find it?

https://github.com/kvalo/ath10k-firmware/blob/master/10.1/firmware-2.bin_10.1.467.2-1


>> Are you perhaps trying to run STA with 4addr bridging? If so then make sure
>> you use recent ath10k as this was known to be a problem.
>>
> Yes I'm testing with 4 addr bridging because I need to bridge this interface. I' ll try without this option.
> I'm testing with commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It is the latest version in openwrt.
>
>> Can you also provide ath10k traces or debug logs, please?
>>
> I'll send a trace.

Thanks.

By the way, what kernel/compat-wireless are you using? I'm suspecting
your build might be missing the fix for STA bridging.


Michał

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

RE: ath10k firmware crash

[voncken]

> -----Message d'origine-----
> De : Michal Kazior [mailto:michal.kazior@tieto.com]
> Envoyé : lundi 13 octobre 2014 09:54
> À : voncken
> Cc : ath10k@lists.infradead.org; linux-wireless
> Objet : Re: ath10k firmware crash
> 
> On 13 October 2014 09:35, voncken <cedric.voncken@acksys.fr> wrote:
> >         Thanks for your reply,
> >
> >>
> >> Can you then provide a crash register dump for 10.1, please? I can't
> >> help you much with the 636 dump.
> >>
> > Yes I can, but where I find it?
> 
> https://github.com/kvalo/ath10k-firmware/blob/master/10.1/firmware-
> 2.bin_10.1.467.2-1
> 
> 
> >> Are you perhaps trying to run STA with 4addr bridging? If so then
> >> make sure you use recent ath10k as this was known to be a problem.
> >>
> > Yes I'm testing with 4 addr bridging because I need to bridge this
> interface. I' ll try without this option.
> > I'm testing with commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It is the
> latest version in openwrt.
> >
> >> Can you also provide ath10k traces or debug logs, please?
> >>
> > I'll send a trace.
> 
I'm using the compat wireless from Openwrt.
	Compat wireless version 2014-05-22, but we updated the firmware with the latest version provided by openwrt (commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)

> Thanks.
> 
> By the way, what kernel/compat-wireless are you using? I'm suspecting your
> build might be missing the fix for STA bridging.
Thanks.

> 
> 
> Michał


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

Re: ath10k firmware crash

[Michal Kazior]

On 13 October 2014 11:20, voncken <cedric.voncken@acksys.fr> wrote:
>
>
>> -----Message d'origine-----
>> De : Michal Kazior [mailto:michal.kazior@tieto.com]
>> Envoyé : lundi 13 octobre 2014 09:54
>> À : voncken
>> Cc : ath10k@lists.infradead.org; linux-wireless
>> Objet : Re: ath10k firmware crash
>>
>> On 13 October 2014 09:35, voncken <cedric.voncken@acksys.fr> wrote:
>> >         Thanks for your reply,
>> >
>> >>
>> >> Can you then provide a crash register dump for 10.1, please? I can't
>> >> help you much with the 636 dump.
>> >>
>> > Yes I can, but where I find it?
>>
>> https://github.com/kvalo/ath10k-firmware/blob/master/10.1/firmware-
>> 2.bin_10.1.467.2-1
>>
>>
>> >> Are you perhaps trying to run STA with 4addr bridging? If so then
>> >> make sure you use recent ath10k as this was known to be a problem.
>> >>
>> > Yes I'm testing with 4 addr bridging because I need to bridge this
>> interface. I' ll try without this option.
>> > I'm testing with commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
>> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It is the
>> latest version in openwrt.
>> >
>> >> Can you also provide ath10k traces or debug logs, please?
>> >>
>> > I'll send a trace.
>>
> I'm using the compat wireless from Openwrt.
>         Compat wireless version 2014-05-22, but we updated the firmware with the latest version provided by openwrt (commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)

The fix for 4addr STA bridging is in the driver, not the firmware.

The compat version you're using doesn't contain the required fix. I'm
pretty sure openwrt compat 2014-09-26 contains it.


Michał

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

RE: ath10k firmware crash

[voncken]

> > I'm using the compat wireless from Openwrt.
> >         Compat wireless version 2014-05-22, but we updated the
> > firmware with the latest version provided by openwrt (commit number
> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from
> > kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)
> 
> The fix for 4addr STA bridging is in the driver, not the firmware.
> 
> The compat version you're using doesn't contain the required fix. I'm pretty
> sure openwrt compat 2014-09-26 contains it.
> 
Ok, I will test with this version. Thanks for your help.
> 
> Michał




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

RE: ath10k firmware crash

[voncken]

> >>
> >> >> Are you perhaps trying to run STA with 4addr bridging? If so then
> >> >> make sure you use recent ath10k as this was known to be a problem.
> >> >>
> >> > Yes I'm testing with 4 addr bridging because I need to bridge this
> >> interface. I' ll try without this option.
> >> > I'm testing with commit number
> >> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
> >> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It
> >> is the latest version in openwrt.
> >> >
> >> >> Can you also provide ath10k traces or debug logs, please?
> >> >>
> >> > I'll send a trace.
> >>
> > I'm using the compat wireless from Openwrt.
> >         Compat wireless version 2014-05-22, but we updated the
> > firmware with the latest version provided by openwrt (commit number
> > 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from
> > kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)
> 
> The fix for 4addr STA bridging is in the driver, not the firmware.
> 
> The compat version you're using doesn't contain the required fix. I'm pretty
> sure openwrt compat 2014-09-26 contains it.
It fix my issue. Thanks for your help.

Cedric Voncken
> 
> 
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html


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

RE: ath10k firmware crash

[voncken]

> 
> Are you perhaps trying to run STA with 4addr bridging? If so then make sure
> you use recent ath10k as this was known to be a problem.
> 
We tested without the 4addr bridging, that works fine but we can't add the interface in bridge :-(

Have you a benchmark reference with ATH10K ? at this time we can send around 700 Mbit/s, is it the maximum or we can expected better ?
> 
> Michał

Thanks

Cedric Voncken


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

Re: ath10k firmware crash

[Michal Kazior]

On 13 October 2014 11:23, voncken <cedric.voncken@acksys.fr> wrote:
>
>
>>
>> Are you perhaps trying to run STA with 4addr bridging? If so then make sure
>> you use recent ath10k as this was known to be a problem.
>>
> We tested without the 4addr bridging, that works fine but we can't add the interface in bridge :-(
>
> Have you a benchmark reference with ATH10K ? at this time we can send around 700 Mbit/s, is it the maximum or we can expected better ?

If this is OTA then this is pretty good. If this is cabled RF w/
attentuator it should be possible to get ~900mbps of UDP traffic with
multiple streams on iperf. At least that's what I was getting on 10.1
firmware (on both AP and STA) last time I checked.

Getting more than 700mbps OTA requires AP and STA antenna alignment voodoo.


Michał

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

RE: ath10k firmware crash

[voncken]

> >
> > Have you a benchmark reference with ATH10K ? at this time we can send
> around 700 Mbit/s, is it the maximum or we can expected better ?
> 
> If this is OTA then this is pretty good. If this is cabled RF w/ attentuator
> it should be possible to get ~900mbps of UDP traffic with multiple streams on
> iperf. At least that's what I was getting on 10.1 firmware (on both AP and
> STA) last time I checked.
> 
> Getting more than 700mbps OTA requires AP and STA antenna alignment voodoo.
> 
I did some tests with a linksys WRT1900AC and I have ~950 mbps OTA easily.
> 
> Michał
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html


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

Re: ath10k firmware crash

[Bartosz Markowski]

On 13 October 2014 14:06, voncken <cedric.voncken@acksys.fr> wrote:
>> >
>> > Have you a benchmark reference with ATH10K ? at this time we can send
>> around 700 Mbit/s, is it the maximum or we can expected better ?
>>
>> If this is OTA then this is pretty good. If this is cabled RF w/ attentuator
>> it should be possible to get ~900mbps of UDP traffic with multiple streams on
>> iperf. At least that's what I was getting on 10.1 firmware (on both AP and
>> STA) last time I checked.
>>
>> Getting more than 700mbps OTA requires AP and STA antenna alignment voodoo.
>>
> I did some tests with a linksys WRT1900AC and I have ~950 mbps OTA easily.

You mean ath10k (STA) VS WRT1900AC get up ~950mbps?
If so, could you say what's the HW, FW version you use?

-- 
Bartosz

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

RE: ath10k firmware crash

[voncken]

> > I did some tests with a linksys WRT1900AC and I have ~950 mbps OTA easily.
> 
> You mean ath10k (STA) VS WRT1900AC get up ~950mbps?
> If so, could you say what's the HW, FW version you use?
> 
My test platform is one WRT1900AC set in bridge mode with a computer.

If I use the WRT1900AC in AP mode with another computer, I have 950 mbps
If I use the cavium octon III dev plateform + ath10k driver in AP mode, I have around 700 mbps

I'm using the latest compat wireless (2014-09-26) from openwrt.
The wireless card is the WLE900VX from compex or DAXA-O1 from Unex.

The WRT1900AC have mimo 4x4 with 3 streams, and my wireless card have mimo 3x3 with 3 streams. Maybe that explains the difference.

Cedric Voncken.
> --
> Bartosz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html


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

Ath10k firmware crash

[Jamie]

[-- Attachment #1: Type: text/plain, Size: 3516 bytes --]

Greetings

Ath10k firmware crashes periodically with Qualcomm Atheros QCA6174 
802.11ac Wireless Network Adapter. Fedora 41 on Dell XPS 9575. Kernel 
version is 6.12.6-200.fc41.x86_64. The problem is intermittent. The 
driver crashes after some while and network goes down.

driver: ath10k_pci
version: 6.12.6-200.fc41.x86_64
firmware-version: WLAN.RM.4.4.1-00309-
expansion-rom-version:
bus-info: 0000:3b:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

[   20.271862] ath10k_pci 0000:3b:00.0: enabling device (0000 -> 0002)
[   20.276595] ath10k_pci 0000:3b:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0
[   20.552189] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 
chip_id 0x00340aff sub 1a56:1535
[   20.552196] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 0 testmode 0
[   20.552844] ath10k_pci 0000:3b:00.0: firmware ver 
WLAN.RM.4.4.1-00309- api 6 features wowlan,ignore-otp,mfp crc32 0793bcf2
[   20.630913] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A 
crc32 d2863f91
[   20.750779] ath10k_pci 0000:3b:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
[   20.823116] ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0

Snippet of dmesg log that deals with ath10k crash:

[14319.943298] ath10k_pci 0000:3b:00.0: failed to receive scan abortion 
completion: timed out
[14319.943319] ath10k_pci 0000:3b:00.0: failed to stop scan: -110
[14319.943328] ath10k_pci 0000:3b:00.0: failed to start hw scan: -110
[14320.393860] ath10k_pci 0000:3b:00.0: firmware crashed! (guid 
31a1f68d-5c9c-4c3c-b95a-f439e818ba11)
[14320.393875] ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 
chip_id 0x00340aff sub 1a56:1535
[14320.393885] ath10k_pci 0000:3b:00.0: kconfig debug 0 debugfs 1 
tracing 0 dfs 0 testmode 0
[14320.395221] ath10k_pci 0000:3b:00.0: firmware ver 
WLAN.RM.4.4.1-00309- api 6 features wowlan,ignore-otp,mfp crc32 0793bcf2
[14320.396605] ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A 
crc32 d2863f91
[14320.396612] ath10k_pci 0000:3b:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
[14320.407906] ath10k_pci 0000:3b:00.0: failed to get memcpy hi address 
for firmware address 4: -16
[14320.407909] ath10k_pci 0000:3b:00.0: failed to read firmware dump 
area: -16
[14320.407911] ath10k_pci 0000:3b:00.0: Copy Engine register dump:
[14320.407926] ath10k_pci 0000:3b:00.0: [00]: 0x00034400  12  12   3   3
[14320.407936] ath10k_pci 0000:3b:00.0: [01]: 0x00034800  31  30  43  44
[14320.407946] ath10k_pci 0000:3b:00.0: [02]: 0x00034c00  29  24  23  24
[14320.407957] ath10k_pci 0000:3b:00.0: [03]: 0x00035000  31  30  31  29
[14320.407966] ath10k_pci 0000:3b:00.0: [04]: 0x00035400 869 841 229 165
[14320.407976] ath10k_pci 0000:3b:00.0: [05]: 0x00035800   0   0  64   0
[14320.407987] ath10k_pci 0000:3b:00.0: [06]: 0x00035c00   8   6  22  20
[14320.407997] ath10k_pci 0000:3b:00.0: [07]: 0x00036000   1   0   1   0
[14320.408155] ath10k_pci 0000:3b:00.0: failed to set inactivity time 
for vdev 0: -108
[14320.408161] ath10k_pci 0000:3b:00.0: failed to setup powersave: -108
[14320.408169] ath10k_pci 0000:3b:00.0: failed to set PS Mode 0 for vdev 
0: -108
[14320.408171] ath10k_pci 0000:3b:00.0: failed to setup powersave: -108
[14320.408173] ath10k_pci 0000:3b:00.0: failed to setup ps on vdev 0: -108
[14320.408220] ath10k_pci 0000:3b:00.0: failed to read hi_board_data 
address: -28

Thanks in advance





[-- Attachment #2: ath10k logs.zip --]
[-- Type: application/x-zip-compressed, Size: 45525 bytes --]

Re: Ath10k firmware crash

[Kalle Valo]

Jamie <jamie@stimulussoft.com> writes:

> Ath10k firmware crashes periodically with Qualcomm Atheros QCA6174
> 802.11ac Wireless Network Adapter. Fedora 41 on Dell XPS 9575. Kernel
> version is 6.12.6-200.fc41.x86_64. The problem is intermittent. The
> driver crashes after some while and network goes down.

Is this is a regression and an old existing issue? In other words, is
there an older version of kernel which doesn't crash?

My first guess is that this is a bug in the firmware and getting that
fixed is difficult.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches