All of lore.kernel.org
 help / color / mirror / Atom feed
* ath10k:  Firmware crash after removing VAP
@ 2013-07-17 21:20 Ben Greear
  2013-07-18  5:12 ` Michal Kazior
  0 siblings, 1 reply; 6+ messages in thread
From: Ben Greear @ 2013-07-17 21:20 UTC (permalink / raw)
  To: ath10k

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

-- 
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] 6+ messages in thread

* Re: ath10k: Firmware crash after removing VAP
  2013-07-17 21:20 ath10k: Firmware crash after removing VAP Ben Greear
@ 2013-07-18  5:12 ` Michal Kazior
  2013-07-18  5:21   ` Ben Greear
  0 siblings, 1 reply; 6+ messages in thread
From: Michal Kazior @ 2013-07-18  5:12 UTC (permalink / raw)
  To: Ben Greear; +Cc: ath10k

Hi Ben,

On 17 July 2013 23:20, Ben Greear <greearb@candelatech.com> wrote:
> 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

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.


> 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
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ath10k: Firmware crash after removing VAP
  2013-07-18  5:12 ` Michal Kazior
@ 2013-07-18  5:21   ` Ben Greear
  2013-07-18  5:37     ` Michal Kazior
  0 siblings, 1 reply; 6+ messages in thread
From: Ben Greear @ 2013-07-18  5:21 UTC (permalink / raw)
  To: Michal Kazior; +Cc: ath10k

On 07/17/2013 10:12 PM, Michal Kazior wrote:
> Hi Ben,
>
> On 17 July 2013 23:20, Ben Greear <greearb@candelatech.com> wrote:
>> 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
>
> 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

-- 
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] 6+ messages in thread

* Re: ath10k: Firmware crash after removing VAP
  2013-07-18  5:21   ` Ben Greear
@ 2013-07-18  5:37     ` Michal Kazior
  2013-07-18 14:25       ` Ben Greear
  2013-07-19 10:46       ` Kalle Valo
  0 siblings, 2 replies; 6+ messages in thread
From: Michal Kazior @ 2013-07-18  5:37 UTC (permalink / raw)
  To: Ben Greear; +Cc: ath10k

On 18 July 2013 07:21, Ben Greear <greearb@candelatech.com> wrote:
> On 07/17/2013 10:12 PM, Michal Kazior wrote:
>>
>> Hi Ben,
>>
>> On 17 July 2013 23:20, Ben Greear <greearb@candelatech.com> wrote:
>>>
>>> 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
>>
>>
>> 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?

I don't have access to the firmware to do such a thing.


> 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
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: ath10k: Firmware crash after removing VAP
  2013-07-18  5:37     ` Michal Kazior
@ 2013-07-18 14:25       ` Ben Greear
  2013-07-19 10:46       ` Kalle Valo
  1 sibling, 0 replies; 6+ messages in thread
From: Ben Greear @ 2013-07-18 14:25 UTC (permalink / raw)
  To: Michal Kazior; +Cc: ath10k

On 07/17/2013 10:37 PM, Michal Kazior wrote:
> On 18 July 2013 07:21, Ben Greear <greearb@candelatech.com> wrote:
>> On 07/17/2013 10:12 PM, Michal Kazior wrote:
>>>
>>> Hi Ben,
>>>
>>> On 17 July 2013 23:20, Ben Greear <greearb@candelatech.com> wrote:
>>>>
>>>> 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
>>>
>>>
>>> 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?
>
> I don't have access to the firmware to do such a thing.
>
>
>> 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.

I was trying to associate to the same AP.  Looks like the firmware
is just too brittle at present...

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] 6+ messages in thread

* Re: ath10k: Firmware crash after removing VAP
  2013-07-18  5:37     ` Michal Kazior
  2013-07-18 14:25       ` Ben Greear
@ 2013-07-19 10:46       ` Kalle Valo
  1 sibling, 0 replies; 6+ messages in thread
From: Kalle Valo @ 2013-07-19 10:46 UTC (permalink / raw)
  To: Michal Kazior; +Cc: Ben Greear, ath10k

Michal Kazior <michal.kazior@tieto.com> writes:

>> 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.

Can you add that to the wiki, please? It would be good to document all
these kind of special cases.

-- 
Kalle Valo

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-07-19 10:46 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-17 21:20 ath10k: Firmware crash after removing VAP Ben Greear
2013-07-18  5:12 ` Michal Kazior
2013-07-18  5:21   ` Ben Greear
2013-07-18  5:37     ` Michal Kazior
2013-07-18 14:25       ` Ben Greear
2013-07-19 10:46       ` 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.