From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Denton Gentry <denton.gentry@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Firmware crash w/ 10.2 diagnosis?
Date: Tue, 9 Sep 2014 15:08:21 +0300 [thread overview]
Message-ID: <87tx4h8096.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABnBrYVb+BN4BFxrj82dj0KypxEy6GGYXtOitVW7twtzTeCArA@mail.gmail.com> (Denton Gentry's message of "Mon, 8 Sep 2014 05:42:02 -0700")
Denton Gentry <denton.gentry@gmail.com> writes:
> The ath10k is operating in AP mode.
>
> Its using a base ath10k driver from a few months ago:
>
> git fetch git://github.com/kvalo/ath.git ath-next
> git checkout v3.15-rc1-237-gd9bc4b9
What is the kernel version? Do you use backports?
> The data from the firmware shows something about a monitor vdev being
> removed? hostapd does create a monitor interface, though I don't see
> an indication that it was being removed at the time of the crash.
> hostapd had exited and restarted well before though, is it possible
> that removal of a monitor interface some time ago might be
> contributing?
So are you still using the old cooked monitor interface for management
frames? I strongly recommend switching to the new way of transmitting
and receiving management frames through nl80211 as then hostapd will not
a create monitor interface. This is what most people use and is most
extensively tested.
Commit 6e3e939f3b1bf8534b32ad09ff199d88800835a0 ('net: add wireless TX
status socket option') adds this capability to the kernel, first
released in Linux 3.3. There might be some dependencies in case you are
porting it to an older kernel, so be extra careful.
Please note that updating backports is not enough for SO_WIFI_STATUS
status, you need to update the kernel itself.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-09-09 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 20:56 Firmware crash w/ 10.2 diagnosis? Denton Gentry
2014-09-08 6:28 ` Michal Kazior
2014-09-08 12:42 ` Denton Gentry
2014-09-09 12:08 ` Kalle Valo [this message]
2014-09-09 12:48 ` Michal Kazior
2014-09-09 20:05 ` Denton Gentry
2014-09-10 15:26 ` 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=87tx4h8096.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=denton.gentry@gmail.com \
--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