ath10k: Firmware crash after removing VAP
I had vap1 on an ath10k NIC, and wlan2 also existed. I deleted the vap1, and very shortly afterwords, the firmware crashed:
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 0x0098EEF0 0x00000000
ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098EEF0
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
Kernel is 3.11.0-rc1+
Is there any way short of reboot to recover from firmware crash currently?
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Hi Ben,
Quoted 15 lines · Ben Greear
I had vap1 on an ath10k NIC, and wlan2 also existed. I deleted the vap1, and very shortly afterwords, the firmware crashed:
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location:0x00401930
ath10k: target Register Dump
ath10k: [00]:0x4100016C0x000000000x0098EEF00x00000000
ath10k: [04]:0x000000000x000000000x000000000x00000000
ath10k: [08]:0x000000000x000000000x000000000x00000000
ath10k: [12]:0x000000000x000000000x000000000x00000000
ath10k: [16]:0x000000000x000000000x000000000x0098EEF0
ath10k: [20]:0x000000000x004019300x000000000x00000000
ath10k: [24]:0x000000000x000000000x000000000x00000000
Quoted 8 lines
ath10k: [28]:
0x000000000x000000000x000000000x00000000
ath10k: [32]:0x000000000x000000000x000000000x00000000
ath10k: [36]:0x000000000x000000000x000000000x00000000
ath10k: [40]:0x000000000x000000000x000000000x00000000
ath10k: [44]:0x000000000x000000000x000000000x00000000
ath10k: [48]:0x000000000x000000000x000000000x00000000
ath10k: [52]:0x000000000x000000000x000000000x00000000
ath10k: [56]:0x000000000x000000000x000000000x00000000
This dump looks suspicious. Are you using vanilla kernel or do you have a ath regulatory hack patch from OpenWRT applied? If so the channel scan list is not sent to the firmware and this will cause firmware to crash.
Quoted 5 lines
Kernel is 3.11.0-rc1+
Is there any way short of reboot to recover from firmware crash currently?
I've posted some patches recently and are currently under review. You can try applying them yourself and test it.
http://lists.infradead.org/pipermail/ath10k/2013-July/000023.html
http://lists.infradead.org/pipermail/ath10k/2013-July/000035.html
Pozdrawiam / Best regards,
Michał Kazior.
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 27 lines · Michal Kazior
Hi Ben,
Quoted 15 lines · Ben Greear
I had vap1 on an ath10k NIC, and wlan2 also existed. I deleted the vap1, and very shortly afterwords, the firmware crashed:
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location:0x00401930
ath10k: target Register Dump
ath10k: [00]:0x4100016C0x000000000x0098EEF00x00000000
ath10k: [04]:0x000000000x000000000x000000000x00000000
ath10k: [08]:0x000000000x000000000x000000000x00000000
ath10k: [12]:0x000000000x000000000x000000000x00000000
ath10k: [16]:0x000000000x000000000x000000000x0098EEF0
ath10k: [20]:0x000000000x004019300x000000000x00000000
ath10k: [24]:0x000000000x000000000x000000000x00000000Quoted 8 lines
ath10k: [28]:
0x000000000x000000000x000000000x00000000
ath10k: [32]:0x000000000x000000000x000000000x00000000
ath10k: [36]:0x000000000x000000000x000000000x00000000
ath10k: [40]:0x000000000x000000000x000000000x00000000
ath10k: [44]:0x000000000x000000000x000000000x00000000
ath10k: [48]:0x000000000x000000000x000000000x00000000
ath10k: [52]:0x000000000x000000000x000000000x00000000
ath10k: [56]:0x000000000x000000000x000000000x00000000
Quoted 4 lines
This dump looks suspicious. Are you using vanilla kernel or do you have a ath regulatory hack patch from OpenWRT applied? If so the channel scan list is not sent to the firmware and this will cause firmware to crash.
I had some of my own patches in the 3.11 kernel. I tried the vanilla ath kernel from github and it crashes when adding a second station.
Can you (or whoever has firmware access) get something resembling a stack trace from the firmware dump to see where it's crashing?
Has anyone been able to successfully use more than one station with ath10k so far?
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 37 lines · Ben Greear
Quoted 30 lines · Michal Kazior
Hi Ben,
Quoted 16 lines · Ben Greear
I had vap1 on an ath10k NIC, and wlan2 also existed. I deleted the vap1, and very shortly afterwords, the firmware crashed:
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location:0x00401930
ath10k: target Register Dump
ath10k: [00]:0x4100016C0x000000000x0098EEF00x00000000
ath10k: [04]:0x000000000x000000000x000000000x00000000
ath10k: [08]:0x000000000x000000000x000000000x00000000
ath10k: [12]:0x000000000x000000000x000000000x00000000
ath10k: [16]:0x000000000x000000000x000000000x0098EEF0
ath10k: [20]:0x000000000x004019300x000000000x00000000
ath10k: [24]:0x000000000x000000000x000000000x00000000Quoted 8 lines
ath10k: [28]:
0x000000000x000000000x000000000x00000000
ath10k: [32]:0x000000000x000000000x000000000x00000000
ath10k: [36]:0x000000000x000000000x000000000x00000000
ath10k: [40]:0x000000000x000000000x000000000x00000000
ath10k: [44]:0x000000000x000000000x000000000x00000000
ath10k: [48]:0x000000000x000000000x000000000x00000000
ath10k: [52]:0x000000000x000000000x000000000x00000000
ath10k: [56]:0x000000000x000000000x000000000x00000000Quoted 4 lines
This dump looks suspicious. Are you using vanilla kernel or do you have a ath regulatory hack patch from OpenWRT applied? If so the channel scan list is not sent to the firmware and this will cause firmware to crash.
Quoted 5 lines
I had some of my own patches in the 3.11 kernel. I tried the vanilla ath kernel from github and it crashes when adding a second station.
Can you (or whoever has firmware access) get something resembling a stack trace from the firmware dump to see where it's crashing?
I don't have access to the firmware to do such a thing.
Quoted 2 lines
Has anyone been able to successfully use more than one station with ath10k so far?
Well, it works for me on ath branch.
I'm able to successfully associate 2 STA interfaces or a couple of AP interfaces through hostapd's multi bssid support.
One thing you should know - it's impossible to associate with two ath10k STA interfaces to the same AP. This is a firmware limitation and I'm guessing you're trying to do that because 'Failed to add peer' is visible in your other logs.
Pozdrawiam / Best regards,
Michał Kazior.
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 52 lines · Michal Kazior
Quoted 37 lines · Ben Greear
Quoted 30 lines · Michal Kazior
Hi Ben,
Quoted 16 lines · Ben Greear
I had vap1 on an ath10k NIC, and wlan2 also existed. I deleted the vap1, and very shortly afterwords, the firmware crashed:
ath10k: firmware crashed!
ath10k: hardware name qca988x hw2.0 version0x4100016c
ath10k: firmware version: 1.0.0.636
ath10k: target register Dump Location:0x00401930
ath10k: target Register Dump
ath10k: [00]:0x4100016C0x000000000x0098EEF00x00000000
ath10k: [04]:0x000000000x000000000x000000000x00000000
ath10k: [08]:0x000000000x000000000x000000000x00000000
ath10k: [12]:0x000000000x000000000x000000000x00000000
ath10k: [16]:0x000000000x000000000x000000000x0098EEF0
ath10k: [20]:0x000000000x004019300x000000000x00000000
ath10k: [24]:0x000000000x000000000x000000000x00000000Quoted 8 lines
ath10k: [28]:
0x000000000x000000000x000000000x00000000
ath10k: [32]:0x000000000x000000000x000000000x00000000
ath10k: [36]:0x000000000x000000000x000000000x00000000
ath10k: [40]:0x000000000x000000000x000000000x00000000
ath10k: [44]:0x000000000x000000000x000000000x00000000
ath10k: [48]:0x000000000x000000000x000000000x00000000
ath10k: [52]:0x000000000x000000000x000000000x00000000
ath10k: [56]:0x000000000x000000000x000000000x00000000Quoted 4 lines
This dump looks suspicious. Are you using vanilla kernel or do you have a ath regulatory hack patch from OpenWRT applied? If so the channel scan list is not sent to the firmware and this will cause firmware to crash.
Quoted 5 lines
I had some of my own patches in the 3.11 kernel. I tried the vanilla ath kernel from github and it crashes when adding a second station.
Can you (or whoever has firmware access) get something resembling a stack trace from the firmware dump to see where it's crashing?
I don't have access to the firmware to do such a thing.
Quoted 2 lines
Has anyone been able to successfully use more than one station with ath10k so far?
Well, it works for me on ath branch.
Quoted 7 lines
I'm able to successfully associate 2 STA interfaces or a couple of AP interfaces through hostapd's multi bssid support.
One thing you should know - it's impossible to associate with two ath10k STA interfaces to the same AP. This is a firmware limitation and I'm guessing you're trying to do that because 'Failed to add peer' is visible in your other logs.
I was trying to associate to the same AP. Looks like the firmware is just too brittle at present...
Thanks,
Ben
Signature · 8 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
Quoted 5 lines · Michal Kazior
Quoted 2 lines
Has anyone been able to successfully use more than one station with ath10k so far?
Well, it works for me on ath branch.
Quoted 7 lines
I'm able to successfully associate 2 STA interfaces or a couple of AP interfaces through hostapd's multi bssid support.
One thing you should know - it's impossible to associate with two ath10k STA interfaces to the same AP. This is a firmware limitation and I'm guessing you're trying to do that because 'Failed to add peer' is visible in your other logs.
Can you add that to the wiki, please? It would be good to document all these kind of special cases.
Signature · 6 lines
Kalle Valo _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k