ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k: Firmware crash after removing VAP
Date: Wed, 17 Jul 2013 22:21:12 -0700	[thread overview]
Message-ID: <51E77B48.9040005@candelatech.com> (raw)
In-Reply-To: <CA+BoTQk5GtWzmZA=TJqk4dWnMmEqC5fQJGkGguYsuLpTCca0mw@mail.gmail.com>

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

  reply	other threads:[~2013-07-18  5:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2013-07-18  5:37     ` Michal Kazior
2013-07-18 14:25       ` Ben Greear
2013-07-19 10:46       ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E77B48.9040005@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox